@wildo-ai/framework-knowledge 1.1.11 → 1.1.12
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 +4 -0
- package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +25 -3
- package/dist/claude-marketplace/plugins/wildo/references/creation-state.md +40 -12
- package/dist/claude-marketplace/plugins/wildo/references/derived-artifacts.md +3 -3
- package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +12 -0
- package/dist/claude-marketplace/plugins/wildo/skills/answer/SKILL.md +19 -2
- package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +33 -9
- package/dist/esm/framework-knowledge.definitions.d.ts +2 -3
- package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.definitions.js +170 -32
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.loader.js.map +1 -1
- package/dist/esm/framework-knowledge.research-provenance.d.ts +6 -4
- package/dist/esm/framework-knowledge.research-provenance.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.research-provenance.js.map +1 -1
- package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.schemas.js.map +1 -1
- package/dist/esm/index.d.ts.map +1 -1
- package/dist/esm/index.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -3
- 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 +4 -12
- 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.map +1 -1
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +12 -1
- 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 +7 -4
- 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 +76 -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 +0 -4
- 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 -15
- 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.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js +1 -1
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js.map +1 -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 +35 -14
- 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 +16 -8
- 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 +19 -8
- 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 +29 -3
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +80 -16
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts +2 -2
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js +2 -2
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +5 -1
- 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 +3 -2
- 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.map +1 -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 +45 -10
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js +61 -21
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts +4 -3
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +8 -5
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts +2 -2
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js +3 -5
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +3 -3
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +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 +8 -6
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts +5 -0
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js +8 -1
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +4 -1
- 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 +11 -3
- 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.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js +6 -4
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts +3 -1
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js +4 -1
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +10 -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 +36 -13
- 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 +8 -2
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +7 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +4 -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 +34 -6
- 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 +5 -2
- 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 +4 -3
- 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-evidence-adequacy/playbook.definition.js +2 -2
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +22 -10
- 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 +39 -29
- 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.compliance-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +8 -3
- 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 -7
- 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.map +1 -1
- 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.feature-drafts/playbook.definition.js.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-analysis/playbook.definition.js.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-evidence-adequacy/playbook.definition.js +2 -2
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.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-research/playbook.definition.js.map +1 -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 +1 -1
- 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.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +13 -5
- 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 +3 -7
- 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 +12 -14
- 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 +3 -0
- 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 +2 -1
- 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 +3 -1
- 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 +2 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts +4 -1
- package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.service-method/playbook.definition.js +14 -1
- package/dist/esm/playbooks/top_down.service-method/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +3 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +4 -2
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +34 -1
- 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 +35 -17
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
- package/dist/esm/source-anchor-grammar.d.ts.map +1 -1
- package/dist/esm/source-anchor-grammar.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 +7 -7
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +6 -0
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +4 -4
- package/dist/knowledge/playbooks/bottom_up.build/method.md +12 -2
- package/dist/knowledge/playbooks/bottom_up.build/playbook.json +5 -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 +439 -27
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +15 -4
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +203 -7
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -5
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +2 -2
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +2 -1
- 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 +104 -2
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +8 -4
- package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +59 -4
- package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +18 -6
- package/dist/knowledge/playbooks/bottom_up.foundation/method.md +121 -24
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +51 -7
- package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +15 -8
- package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +2 -1
- package/dist/knowledge/playbooks/bottom_up.maturity-reading/method.md +10 -2
- package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +4 -3
- package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +34 -0
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +9 -2
- package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +1 -0
- package/dist/knowledge/playbooks/cross_cutting.application-creation/method.md +27 -12
- package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +11 -5
- package/dist/knowledge/playbooks/cross_cutting.compliance/method.md +4 -4
- package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +7 -2
- package/dist/knowledge/playbooks/cross_cutting.feature-development/playbook.json +1 -0
- package/dist/knowledge/playbooks/cross_cutting.refinement/method.md +6 -6
- package/dist/knowledge/playbooks/cross_cutting.refinement/playbook.json +3 -4
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +56 -5
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +3 -2
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +6 -4
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +5 -1
- package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +8 -1
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +1 -0
- 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/playbook.json +15 -3
- package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +11 -4
- package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +3 -2
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/method.md +16 -6
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +3 -2
- package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +5 -1
- 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 +43 -11
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +24 -8
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +6 -2
- package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +1 -1
- package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +49 -14
- package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +3 -3
- package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +6 -2
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +20 -0
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +4 -3
- package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +69 -65
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +11 -7
- package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.definition/method.md +3 -1
- package/dist/knowledge/playbooks/top_down.definition/playbook.json +11 -3
- package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +4 -2
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +4 -3
- package/dist/knowledge/playbooks/top_down.market-research/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +3 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +3 -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 +1 -0
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +10 -6
- package/dist/knowledge/playbooks/top_down.risk-register/method.md +7 -0
- package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +5 -1
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +6 -1
- package/dist/knowledge/playbooks/top_down.service-method/method.md +19 -1
- package/dist/knowledge/playbooks/top_down.service-method/playbook.json +16 -4
- package/dist/knowledge/playbooks/top_down.value-proposition/method.md +5 -2
- package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +9 -3
- package/dist/knowledge/playbooks/top_down.vision-elicitation/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.vision-elicitation/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +17 -2
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +59 -15
- package/dist/knowledge/references/application-documentation-chapters.config.md +45 -10
- package/dist/knowledge/references/application-documentation-plan.config.md +2 -2
- package/dist/knowledge/references/application-maturity.config.md +27 -1
- package/dist/knowledge/references/backend.inbound-channels.attachment-adoption.md +4 -2
- package/dist/knowledge/references/backend.inbound-channels.handler-definition.md +52 -11
- package/dist/knowledge/references/backend.inbound-handlers.definition.md +38 -1
- package/dist/knowledge/references/brand.name-screening.config.md +30 -3
- package/dist/knowledge/references/build-plan.task-graph.config.md +200 -4
- package/dist/knowledge/references/business-model.pricing-plan.config.md +12 -9
- package/dist/knowledge/references/business-model.snapshot.config.md +29 -2
- package/dist/knowledge/references/business-model.snapshot.validation.md +11 -8
- package/dist/knowledge/references/companion.introspection.behaviors.market.md +3 -0
- package/dist/knowledge/references/companion.market.generation-service.md +46 -5
- package/dist/knowledge/references/companion.market.prompt-renderer.md +1 -1
- package/dist/knowledge/references/companion.technical-doc.service.md +195 -63
- package/dist/knowledge/references/domain-plan.record-partition.md +105 -0
- package/dist/knowledge/references/engine.client-bundle.allow-list.md +3 -1
- package/dist/knowledge/references/engine.saas-technical-doc.config.md +69 -15
- package/dist/knowledge/references/example.authorization.application-roles.office-and-field.md +10 -0
- package/dist/knowledge/references/example.backend.addon-wiring.module.md +6 -0
- package/dist/knowledge/references/example.backend.custom-operation.declared-refusal-code.md +41 -0
- package/dist/knowledge/references/example.backend.custom-operation.external-effect-reservation.md +107 -0
- package/dist/knowledge/references/example.blueprint.definition.internal-tool.md +4 -2
- package/dist/knowledge/references/example.flows-actors.chat-assistant.md +8 -5
- package/dist/knowledge/references/example.infra.environment-config.local.md +13 -66
- package/dist/knowledge/references/example.module.companion-exports.full.md +1 -0
- package/dist/knowledge/references/example.module.relationships.actor-edge-back-to-scope-owner.md +35 -35
- package/dist/knowledge/references/example.navigation.one-entry-per-concept.md +47 -0
- package/dist/knowledge/references/example.organization-identity.system-of-record-partitions.md +18 -0
- package/dist/knowledge/references/example.provider.backend-module-shape.md +28 -4
- package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +0 -4
- package/dist/knowledge/references/example.resource.custom-view.backend-refusal.md +75 -0
- package/dist/knowledge/references/example.resource.status-lifecycle.quote.md +8 -7
- package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +37 -2
- package/dist/knowledge/references/example.resource.ui-behavior.record-template.md +0 -1
- package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +1 -1
- package/dist/knowledge/references/example.resource.ui-behavior.workflow-record-page.md +212 -0
- package/dist/knowledge/references/example.subject-export.portability-archive.md +42 -0
- package/dist/knowledge/references/example.views.app-level.workflow-home.md +238 -0
- package/dist/knowledge/references/example.website.demo.complete-items.md +3 -3
- package/dist/knowledge/references/example.website.pricing.audit-payloads.md +38 -0
- package/dist/knowledge/references/example.website.pricing.catalog-load.md +77 -0
- package/dist/knowledge/references/example.website.pricing.offers.md +43 -0
- package/dist/knowledge/references/example.website.pricing.plans-section.md +20 -0
- package/dist/knowledge/references/example.website.pricing.plans.md +88 -0
- package/dist/knowledge/references/example.website.section.stats.md +1 -1
- package/dist/knowledge/references/experience-plan.config.md +111 -1
- package/dist/knowledge/references/external-connectors.frontend-provider-consent-classification.md +2 -0
- package/dist/knowledge/references/external-connectors.models.file-storage-adapter.md +8 -1
- package/dist/knowledge/references/external-connectors.models.hook-signature-algorithms.md +104 -0
- package/dist/knowledge/references/external-connectors.models.oauth2-audiences.md +11 -6
- package/dist/knowledge/references/external-connectors.models.oauth2-incremental-consent.md +165 -0
- package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +1035 -19
- package/dist/knowledge/references/external-connectors.private.provider-compliance-state-collector.md +36 -0
- package/dist/knowledge/references/external-connectors.private.provider-configuration-check.md +69 -0
- package/dist/knowledge/references/integration-plan.config.md +7 -7
- package/dist/knowledge/references/placement-plan.config.md +19 -0
- package/dist/knowledge/references/platform.config.backing-services.md +9 -11
- package/dist/knowledge/references/platform.config.environment.deployment.md +133 -8
- package/dist/knowledge/references/platform.config.infra-provider-resolution.md +3 -3
- package/dist/knowledge/references/platform.config.infrastructure-host.md +0 -1
- package/dist/knowledge/references/platform.config.platform-key-management.md +84 -8
- package/dist/knowledge/references/platform.config.saas.md +20 -18
- package/dist/knowledge/references/presets.3d.frame-style-resolution.md +65 -0
- package/dist/knowledge/references/presets.layouts-2d.authoring.md +1 -1
- package/dist/knowledge/references/presets.models.field-form-control-variant.md +32 -0
- package/dist/knowledge/references/presets.models.labelling.sections.md +39 -0
- package/dist/knowledge/references/presets.models.surface-policy.defaults.md +3 -3
- package/dist/knowledge/references/presets.models.surface-variant.md +5 -4
- package/dist/knowledge/references/presets.themes.compose-theme.md +2 -1
- package/dist/knowledge/references/requirements.non-functional-requirement.config.md +4 -4
- package/dist/knowledge/references/requirements.snapshot.config.md +2 -3
- package/dist/knowledge/references/saas.approval-seals.admin-endpoints.md +29 -2
- package/dist/knowledge/references/saas.backend.a2a.token-budget.md +11 -4
- package/dist/knowledge/references/saas.backend.actor-execution-continuation.md +21 -0
- package/dist/knowledge/references/saas.backend.app-config.backend-authored.md +5 -1
- package/dist/knowledge/references/saas.backend.application-initialization.assembly.md +1 -1
- package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +13 -1
- package/dist/knowledge/references/saas.backend.custom-operation.authoritative-fields.md +4 -1
- package/dist/knowledge/references/saas.backend.custom-operation.core-write-precondition.md +38 -0
- package/dist/knowledge/references/saas.backend.custom-operation.external-effect-reservation.md +109 -0
- package/dist/knowledge/references/saas.backend.custom-operation.hook-transaction-posture.md +43 -0
- package/dist/knowledge/references/saas.backend.document-sequence.issue-in-operation.md +1 -1
- package/dist/knowledge/references/saas.backend.document-sequence.raise-floor.md +62 -13
- package/dist/knowledge/references/saas.backend.domain-module.md +30 -1
- package/dist/knowledge/references/saas.backend.flows-actors.a2a-task-surface.md +26 -3
- package/dist/knowledge/references/saas.backend.flows-actors.chat-reply-handler.md +13 -1
- package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +363 -2
- package/dist/knowledge/references/saas.backend.flows-actors.invoke-agent.md +5 -3
- package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +1 -1
- package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +9 -4
- package/dist/knowledge/references/saas.backend.flows.start-flow-method.md +2 -1
- package/dist/knowledge/references/saas.backend.privacy.subject-export-archive.md +26 -0
- package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +21 -19
- package/dist/knowledge/references/saas.backend.system-access-service.md +159 -4
- package/dist/knowledge/references/saas.config.content-security-policy.md +26 -9
- package/dist/knowledge/references/saas.data-seeding.definition-input.md +1 -1
- package/dist/knowledge/references/saas.data-seeding.modes.md +4 -1
- package/dist/knowledge/references/saas.data-seeding.row-reference.md +2 -4
- package/dist/knowledge/references/saas.external-providers.backend-provider-loader.md +6 -0
- package/dist/knowledge/references/saas.external-providers.backend-provider-registry.runtime-filter.md +2 -0
- package/dist/knowledge/references/saas.frontend.chart-dashboard-view.md +43 -0
- package/dist/knowledge/references/saas.frontend.chart-dashboard.md +130 -0
- package/dist/knowledge/references/saas.frontend.chart-view.resource-chart-data.md +8 -4
- package/dist/knowledge/references/saas.frontend.collection-filter-presets.md +76 -9
- package/dist/knowledge/references/saas.frontend.command-menu.search-resource.md +3 -3
- package/dist/knowledge/references/saas.frontend.errors.backend-refusal.md +96 -0
- package/dist/knowledge/references/saas.frontend.execution-view.definition.md +40 -0
- package/dist/knowledge/references/saas.frontend.launcher.item-refs.md +4 -0
- package/dist/knowledge/references/saas.frontend.linked-conversations-embed.md +3 -5
- package/dist/knowledge/references/saas.frontend.record-page-parts.md +117 -0
- package/dist/knowledge/references/saas.frontend.related-resource-embeds.md +46 -16
- package/dist/knowledge/references/saas.frontend.related-resource-sections.md +6 -0
- package/dist/knowledge/references/saas.frontend.resource-header-title.md +1 -1
- package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +43 -9
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +259 -15
- package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +4 -2
- package/dist/knowledge/references/saas.frontend.section-stages.md +63 -0
- package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +42 -0
- package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +6 -9
- package/dist/knowledge/references/saas.frontend.viewer-may-perform-operation.md +52 -0
- package/dist/knowledge/references/saas.models.agent-suspension.md +8 -8
- package/dist/knowledge/references/saas.models.audit-trails.actor-attribution.md +21 -0
- package/dist/knowledge/references/saas.models.auth.relationship-grantor-authentication.md +2 -2
- package/dist/knowledge/references/saas.models.config.declared-type-renames.md +246 -0
- package/dist/knowledge/references/saas.models.config.organization-types.md +20 -0
- package/dist/knowledge/references/saas.models.conversation-threads.md +39 -3
- package/dist/knowledge/references/saas.models.crypto-keys.floors.md +10 -0
- package/dist/knowledge/references/saas.models.crypto-keys.local-provider.md +2 -0
- package/dist/knowledge/references/saas.models.crypto-keys.purpose-descriptor.md +39 -0
- package/dist/knowledge/references/saas.models.crypto-keys.purposes.md +7 -0
- package/dist/knowledge/references/saas.models.data-mode-read-list.md +0 -78
- package/dist/knowledge/references/saas.models.engine-capabilities.md +11 -2
- package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +3 -0
- package/dist/knowledge/references/saas.models.external-data-pipeline.md +15 -8
- package/dist/knowledge/references/saas.models.flows-actors.agent-behavior-report.md +13 -9
- package/dist/knowledge/references/saas.models.flows-actors.agent-configuration.md +29 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-operation-record.md +7 -0
- package/dist/knowledge/references/saas.models.flows-actors.human-decision-decider.md +8 -0
- package/dist/knowledge/references/saas.models.flows-actors.human-input-form.md +47 -12
- package/dist/knowledge/references/saas.models.flows-actors.operation-approval-requirement.md +31 -0
- package/dist/knowledge/references/saas.models.flows-actors.review-deadlines-declaration.md +3 -3
- package/dist/knowledge/references/saas.models.flows.runnable-model.md +21 -2
- package/dist/knowledge/references/saas.models.guidance-flow.md +1 -1
- package/dist/knowledge/references/saas.models.http-api-binding.md +19 -8
- package/dist/knowledge/references/saas.models.human-decision-review-marker.md +1 -1
- package/dist/knowledge/references/saas.models.inbound-channels.md +71 -2
- package/dist/knowledge/references/saas.models.model-cost-accounting-config.md +1 -1
- package/dist/knowledge/references/saas.models.notifications.targets.md +3 -1
- package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +201 -15
- package/dist/knowledge/references/saas.models.organization-assigned-rows-declaration.md +2 -1
- package/dist/knowledge/references/saas.models.organization-own-rows-declaration.md +5 -2
- package/dist/knowledge/references/saas.models.organizations.identity-declaration.md +201 -0
- package/dist/knowledge/references/saas.models.organizations.organization-relationships.md +25 -3
- package/dist/knowledge/references/saas.models.organizations.relationship-invitations.md +6 -2
- package/dist/knowledge/references/saas.models.organizations.relationship-kinds.md +14 -0
- package/dist/knowledge/references/saas.models.organizations.relationship-record-separation.md +1 -0
- package/dist/knowledge/references/saas.models.privacy.data-residency.md +676 -0
- package/dist/knowledge/references/saas.models.privacy.legal-holds.md +46 -2
- package/dist/knowledge/references/saas.models.privacy.provider-capability-disclosure.md +6 -0
- package/dist/knowledge/references/saas.models.privacy.retention-binding.md +84 -1
- package/dist/knowledge/references/saas.models.privacy.retention-enforcement-record.md +10 -0
- package/dist/knowledge/references/saas.models.privacy.retention-schedule.md +5 -3
- package/dist/knowledge/references/saas.models.privacy.subject-data-recipients.md +2 -0
- package/dist/knowledge/references/saas.models.privacy.subject-export.md +134 -0
- package/dist/knowledge/references/saas.models.provider-capabilities.md +5 -0
- package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +12 -6
- package/dist/knowledge/references/saas.models.providers.compliance-choice.md +15 -0
- package/dist/knowledge/references/saas.models.providers.processing-region-reach.md +132 -0
- package/dist/knowledge/references/saas.models.providers.processing-region-selection.md +139 -0
- package/dist/knowledge/references/saas.models.representative-activity.md +4 -0
- package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +107 -42
- package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +35 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-auditable-event.md +4 -2
- package/dist/knowledge/references/saas.models.resource-config.operation-condition-parameters.md +56 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-idempotency-key.md +16 -6
- package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +38 -0
- package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +14 -16
- package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +2 -2
- package/dist/knowledge/references/saas.models.resource-config.retention-policy.md +21 -0
- package/dist/knowledge/references/saas.models.resource-config.system-access-policy.md +32 -15
- package/dist/knowledge/references/saas.models.resource-operation-display-risk.md +5 -4
- package/dist/knowledge/references/saas.models.roles.definition.md +12 -1
- package/dist/knowledge/references/saas.models.roles.organization-defaults.md +6 -0
- package/dist/knowledge/references/saas.models.schema-family-builder.md +17 -2
- package/dist/knowledge/references/saas.models.system-of-record-actions.md +65 -1
- package/dist/knowledge/references/saas.models.system-of-record-capabilities.md +3 -1
- package/dist/knowledge/references/saas.models.system-of-record-error-codes.md +16 -0
- package/dist/knowledge/references/saas.models.systems-of-record.md +75 -14
- package/dist/knowledge/references/saas.public-runtime.contract.md +41 -23
- package/dist/knowledge/references/saas.rag.retrieval-refusals.md +3 -2
- package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +12 -4
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +21 -2
- package/dist/knowledge/references/saas.specifications.engine-resource-sub-domain.md +105 -0
- package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +6 -2
- package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +20 -3
- package/dist/knowledge/references/saas.specifications.resource-spec-factory.md +100 -71
- package/dist/knowledge/references/saas.specifications.translation-glossary.md +80 -0
- package/dist/knowledge/references/saas.website.astro.label-loader.md +44 -10
- package/dist/knowledge/references/saas.website.astro.runtime-helper.md +3 -2
- package/dist/knowledge/references/saas.website.blog.collection-config.md +36 -32
- package/dist/knowledge/references/saas.website.blog.cover-resolver.md +1 -1
- package/dist/knowledge/references/saas.website.blog.frontmatter.md +2 -2
- package/dist/knowledge/references/saas.website.blog.post-renderer.md +2 -2
- package/dist/knowledge/references/saas.website.blog.react-mdx-integration.md +26 -19
- package/dist/knowledge/references/saas.website.blog.react-mdx-query.md +1 -1
- package/dist/knowledge/references/saas.website.config.pricing-catalog-loader.md +3 -1
- package/dist/knowledge/references/saas.website.config.site-context-loader.md +6 -3
- package/dist/knowledge/references/saas.website.label-keys.format.md +3 -2
- package/dist/knowledge/references/saas.website.label-pack.validator.md +3 -1
- package/dist/knowledge/references/service-method.config.md +35 -2
- package/dist/knowledge/references/vision.constraint.config.md +4 -2
- package/dist/knowledge/references/zod.decorators.chainable-runtime.md +60 -0
- package/dist/knowledge/references/zod.decorators.data-categories.md +46 -46
- package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +24 -0
- package/dist/knowledge/references/zod.decorators.display-edit-modes.md +11 -0
- package/dist/knowledge/references/zod.decorators.file-schema.md +4 -3
- package/dist/knowledge/references/zod.decorators.rag-source.md +20 -20
- package/dist/knowledge/references/zod.decorators.schema-metadata.md +2 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +30 -24
- package/dist/knowledge/references/zod.decorators.shared-structural-params.md +63 -0
- package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +63 -0
- package/dist/knowledge/references/zod.factories.bigdecimal.md +4 -4
- package/dist/knowledge/references/zod.factories.code.md +4 -4
- package/dist/knowledge/references/zod.factories.duration.md +4 -4
- package/dist/knowledge/references/zod.factories.money.md +4 -4
- package/dist/knowledge/references/zod.factories.phone.md +4 -4
- package/dist/knowledge/references/zod.factories.year-month.md +79 -0
- package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
- package/dist/knowledge/registries/framework-topics.json +415 -2
- package/dist/knowledge/registries/playbooks.json +51 -39
- package/dist/knowledge/registries/source-tags.json +2412 -1604
- package/dist/knowledge/rules/database-migration-obligation.md +6 -7
- package/dist/knowledge/rules/live-context-door.md +1 -1
- package/dist/knowledge/skills/INDEX.md +3 -1
- package/dist/knowledge/skills/agent-work-review/references/framework-actor-execution-continuation-api.md +24 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-marker-api.md +1 -1
- package/dist/knowledge/skills/agent-work-review/references/framework-human-input-form-api.md +47 -12
- package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +30 -19
- package/dist/knowledge/skills/application-consumer-documentation-authoring/references/framework-documentation-chapters-api.md +48 -13
- package/dist/knowledge/skills/application-consumer-documentation-authoring/references/source-and-ownership-routing.md +2 -2
- package/dist/knowledge/skills/application-database-migrations/SKILL.md +10 -11
- package/dist/knowledge/skills/application-database-migrations/references/postgresql-supported-surfaces.md +64 -0
- package/dist/knowledge/skills/application-database-migrations/references/postgresql-vs-mongodb-obligations.md +13 -11
- package/dist/knowledge/skills/application-roles-authoring/SKILL.md +28 -3
- package/dist/knowledge/skills/application-roles-authoring/references/framework-application-roles-api.md +18 -1
- package/dist/knowledge/skills/application-roles-authoring/references/office-and-field-worked-example.md +22 -1
- package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +46 -2
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-assigned-rows-declaration-api.md +5 -3
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-organization-identity-declaration-api.md +247 -0
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-own-rows-declaration-api.md +12 -5
- package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +6 -0
- package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +31 -2
- package/dist/knowledge/skills/backend-custom-operation/SKILL.md +51 -14
- package/dist/knowledge/skills/backend-custom-operation/references/after-the-operation.md +4 -1
- package/dist/knowledge/skills/backend-custom-operation/references/declared-refusal-codes.md +95 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-audit-log-event-api.md +2 -2
- package/dist/knowledge/skills/backend-custom-operation/references/framework-core-write-precondition-api.md +73 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-error-handling-api.md +5 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-external-effect-reservation-api.md +276 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-hook-transaction-posture-api.md +79 -0
- package/dist/knowledge/skills/blueprint-authoring/SKILL.md +4 -2
- package/dist/knowledge/skills/brand-name-screening/SKILL.md +13 -2
- package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +30 -3
- package/dist/knowledge/skills/chat-agent-conversations/SKILL.md +3 -0
- package/dist/knowledge/skills/chat-agent-conversations/references/framework-chat-conversations-api.md +13 -1
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +45 -4
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +17 -7
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +859 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-disclosures.md +6 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-subject-data-recipients.md +2 -0
- package/dist/knowledge/skills/config-app-shell/SKILL.md +5 -1
- package/dist/knowledge/skills/config-app-shell/references/framework-command-menu-omnibox-api.md +3 -3
- package/dist/knowledge/skills/config-app-shell/references/framework-launcher-items-api.md +4 -0
- package/dist/knowledge/skills/config-design-system/SKILL.md +1 -1
- package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +8 -7
- package/dist/knowledge/skills/config-design-system/references/framework-theme-composition-api.md +44 -1
- package/dist/knowledge/skills/config-navigation/SKILL.md +2 -0
- package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +5 -0
- package/dist/knowledge/skills/config-navigation/references/one-entry-per-concept.md +101 -0
- package/dist/knowledge/skills/config-saas/SKILL.md +2 -2
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +40 -3
- package/dist/knowledge/skills/config-saas/references/framework-auditable-event-catalog.md +20 -1
- package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +75 -11
- package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +21 -19
- package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +26 -9
- package/dist/knowledge/skills/config-saas/references/framework-key-management-api.md +197 -9
- package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +16 -2
- package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +116 -16
- package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +20 -18
- package/dist/knowledge/skills/config-saas/references/saas-config-scope.md +1 -1
- package/dist/knowledge/skills/config-saas-backend/SKILL.md +11 -1
- package/dist/knowledge/skills/config-saas-backend/references/framework-backend-authored-config-api.md +5 -1
- package/dist/knowledge/skills/config-saas-backend/references/framework-declared-type-renames-api.md +261 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +20 -0
- package/dist/knowledge/skills/config-saas-backend/references/renaming-organization-and-user-types.md +69 -0
- package/dist/knowledge/skills/configure-billing/SKILL.md +6 -0
- package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +28 -4
- package/dist/knowledge/skills/configure-billing/references/framework-backend-provider-reachability-api.md +2 -0
- package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +4 -1
- package/dist/knowledge/skills/electronic-signature-deliverables/SKILL.md +131 -0
- package/dist/knowledge/skills/electronic-signature-deliverables/references/what-makes-a-request-signed.md +61 -0
- package/dist/knowledge/skills/email-add-template/SKILL.md +1 -1
- package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +11 -8
- package/dist/knowledge/skills/email-add-template/references/framework-email-send-api.md +3 -2
- package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +31 -9
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +11 -4
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +26 -3
- package/dist/knowledge/skills/flows-actors-autonomous-agents/SKILL.md +1 -1
- package/dist/knowledge/skills/flows-actors-autonomous-agents/references/binding-and-review.md +27 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +18 -7
- package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +8 -5
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-behavior-reports-api.md +13 -9
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-content-guardrails-api.md +44 -4
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-operation-record-api.md +7 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-suspension-api.md +11 -9
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-audit-agent-attribution-api.md +21 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-decision-deadlines-api.md +3 -3
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-realtime-catalog.md +7 -1
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +375 -8
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +30 -1
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-model-spend-limits-api.md +36 -15
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +8 -0
- package/dist/knowledge/skills/flows-actors-declared-flow/SKILL.md +1 -1
- package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-flow-model-api.md +21 -2
- package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-start-flow-api.md +2 -1
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +1 -1
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +33 -1
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-invocation-api.md +5 -3
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +3 -3
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +37 -14
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-guidance-flow-api.md +1 -1
- package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +39 -0
- package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +39 -0
- package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +31 -2
- package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +39 -0
- package/dist/knowledge/skills/i18n-translation-rerun/references/framework-translation-glossary-api.md +87 -0
- package/dist/knowledge/skills/inbound-channels/SKILL.md +31 -9
- package/dist/knowledge/skills/inbound-channels/references/email-channel.md +16 -4
- package/dist/knowledge/skills/inbound-channels/references/framework-inbound-channel-api.md +169 -23
- package/dist/knowledge/skills/inbound-channels/references/framework-inbound-handler-api.md +38 -1
- package/dist/knowledge/skills/inbound-channels/references/inbound-delivery-lifecycle.md +43 -4
- package/dist/knowledge/skills/inbound-channels/references/receiving-email.md +15 -3
- package/dist/knowledge/skills/inbound-channels/references/sms-channel.md +93 -0
- package/dist/knowledge/skills/infra-environment-config/SKILL.md +125 -77
- package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +12 -14
- package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +133 -8
- package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +0 -1
- package/dist/knowledge/skills/infra-environment-config/references/framework-platform-key-management-api.md +84 -8
- package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-authoring-api.md +1 -1
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-focal-plane-settings-api.md +16 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-frame-style-overrides-api.md +72 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/manual-adoption-and-removal.md +2 -2
- package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +12 -9
- package/dist/knowledge/skills/local-environment-bootstrap/references/derived-artifact-currency.md +3 -3
- package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +2 -2
- package/dist/knowledge/skills/local-environment-bootstrap/references/local-environment-troubleshooting.md +18 -10
- package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +7 -7
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +24 -2
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +33 -2
- package/dist/knowledge/skills/market-generation-cli/SKILL.md +47 -6
- package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +61 -8
- package/dist/knowledge/skills/model-cost-attribution/SKILL.md +3 -1
- package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-pricing-api.md +1 -1
- package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +107 -42
- package/dist/knowledge/skills/module-companion-exports/SKILL.md +1 -0
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +21 -2
- package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +30 -1
- package/dist/knowledge/skills/module-relationships/SKILL.md +92 -91
- package/dist/knowledge/skills/organization-relationships/references/framework-organization-relationships-api.md +31 -5
- package/dist/knowledge/skills/organization-relationships/references/framework-relationship-grantor-authentication-api.md +2 -2
- package/dist/knowledge/skills/organization-relationships/references/framework-relationship-kinds-api.md +34 -0
- package/dist/knowledge/skills/organization-relationships/references/framework-relationship-record-separation-api.md +1 -0
- package/dist/knowledge/skills/organization-relationships/references/framework-representative-activity-api.md +4 -0
- package/dist/knowledge/skills/professional-qualifications/references/framework-operation-approval-requirement-api.md +31 -0
- package/dist/knowledge/skills/provider-backend-package/SKILL.md +255 -12
- package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +4 -5
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-compliance-state-collector-api.md +96 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-configuration-check-api.md +130 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-file-storage-adapter-api.md +8 -1
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-inbound-endpoint-api.md +124 -3
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-incremental-consent-api.md +165 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-loader-api.md +6 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-processing-region-api.md +340 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-shared-connection-api.md +11 -6
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-consent-api.md +2 -0
- package/dist/knowledge/skills/provider-frontend-module/SKILL.md +5 -2
- package/dist/knowledge/skills/provider-frontend-module/references/package-frontend-facets.md +1 -1
- package/dist/knowledge/skills/provider-operation-calls/SKILL.md +17 -3
- package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +1035 -19
- package/dist/knowledge/skills/resource-add-field/SKILL.md +7 -0
- package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +322 -15
- package/dist/knowledge/skills/resource-add-resource/SKILL.md +9 -5
- package/dist/knowledge/skills/resource-add-resource/references/framework-engine-api-reference-categories-api.md +119 -0
- package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +107 -42
- package/dist/knowledge/skills/resource-chat-commands/SKILL.md +2 -1
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +71 -5
- package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +2 -2
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-approval-api.md +48 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +33 -7
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-bulk-api.md +15 -11
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-idempotency-key-api.md +66 -27
- package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +140 -58
- package/dist/knowledge/skills/resource-config-wiring/references/framework-retention-policy-operations.md +7 -2
- package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +34 -10
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +5 -4
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +158 -138
- package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +52 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +205 -19
- package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +253 -25
- package/dist/knowledge/skills/resource-custom-view/SKILL.md +126 -1
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +259 -15
- package/dist/knowledge/skills/resource-custom-view/references/framework-backend-refusal-api.md +110 -0
- package/dist/knowledge/skills/resource-external-data/SKILL.md +46 -12
- package/dist/knowledge/skills/resource-external-data/references/bidirectional-pipelines.md +1 -1
- package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +15 -8
- package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +19 -8
- package/dist/knowledge/skills/resource-external-data/references/framework-system-of-record-capabilities-api.md +3 -1
- package/dist/knowledge/skills/resource-external-data/references/local-test-doubles.md +121 -0
- package/dist/knowledge/skills/resource-external-data/references/outbound-pipelines.md +1 -1
- package/dist/knowledge/skills/resource-external-data/references/partition-from-the-domain-plan.md +230 -0
- package/dist/knowledge/skills/resource-external-data/references/presenting-a-copy-and-a-read-through.md +73 -0
- package/dist/knowledge/skills/resource-external-data/references/read-through-writes.md +26 -5
- package/dist/knowledge/skills/resource-external-data/references/system-of-record-actions.md +76 -6
- package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +8 -0
- package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +12 -9
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +11 -2
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +29 -2
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-source-decorator-api.md +20 -20
- package/dist/knowledge/skills/resource-retention-binding/SKILL.md +18 -2
- package/dist/knowledge/skills/resource-retention-binding/references/framework-legal-holds-api.md +46 -2
- package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-binding-api.md +84 -1
- package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-enforcement-records-api.md +10 -0
- package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-schedule-api.md +5 -3
- package/dist/knowledge/skills/resource-retention-binding/references/framework-statutory-retention-api.md +21 -0
- package/dist/knowledge/skills/resource-retention-binding/references/start-point-decisions.md +14 -2
- package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +1 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/computed-totals.md +4 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/document-numbers.md +78 -17
- package/dist/knowledge/skills/resource-schema-authoring/references/field-type-selection.md +2 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +26 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +46 -46
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-schema-family-api.md +17 -2
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +36 -24
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +63 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +104 -23
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +123 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +1 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/special-factories.md +72 -0
- package/dist/knowledge/skills/resource-status-lifecycle/SKILL.md +42 -2
- package/dist/knowledge/skills/resource-status-lifecycle/references/framework-operation-condition-parameters-api.md +67 -0
- package/dist/knowledge/skills/resource-status-lifecycle/references/quote-lifecycle-worked-example.md +16 -12
- package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +66 -3
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-collection-filter-presets-api.md +89 -10
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +11 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +263 -17
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-record-page-parts-api.md +155 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-related-resource-embeds-api.md +83 -16
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +44 -10
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-section-stages-api.md +102 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/record-page-anatomy.md +9 -2
- package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +33 -2
- package/dist/knowledge/skills/resource-ui-behavior/references/visual-quality-rubric.md +19 -2
- package/dist/knowledge/skills/resource-ui-behavior/references/workflow-record-page.md +264 -0
- package/dist/knowledge/skills/seeding-authoring/SKILL.md +24 -4
- package/dist/knowledge/skills/seeding-authoring/references/cross-seed-row-references.md +12 -0
- package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +7 -6
- package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +6 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +42 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +6 -9
- package/dist/knowledge/skills/spec-companion-exports/SKILL.md +1 -0
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +21 -2
- package/dist/knowledge/skills/spec-resource-update/SKILL.md +26 -0
- package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +121 -75
- package/dist/knowledge/skills/spec-resource-update/references/workflow-record-page-specification.md +237 -0
- package/dist/knowledge/skills/spec-update-after-change/references/framework-spec-factory-api.md +100 -71
- package/dist/knowledge/skills/subject-data-export/SKILL.md +176 -0
- package/dist/knowledge/skills/subject-data-export/references/file-content-exclusions.md +15 -0
- package/dist/knowledge/skills/subject-data-export/references/framework-subject-export-api.md +142 -0
- package/dist/knowledge/skills/subject-data-export/references/framework-subject-export-archive-api.md +33 -0
- package/dist/knowledge/skills/views-app-level/SKILL.md +3 -1
- package/dist/knowledge/skills/views-app-level/references/workflow-home.md +373 -0
- package/dist/knowledge/skills/views-chart-authoring/SKILL.md +36 -5
- package/dist/knowledge/skills/views-chart-authoring/references/framework-resource-chart-data-api.md +9 -5
- package/dist/knowledge/skills/views-composite-authoring/SKILL.md +4 -0
- package/dist/knowledge/skills/views-composite-authoring/references/framework-chart-dashboard-api.md +244 -0
- package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +40 -0
- package/dist/knowledge/skills/website-blog-authoring/SKILL.md +8 -6
- package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +70 -59
- package/dist/knowledge/skills/website-building-blocks/SKILL.md +1 -1
- package/dist/knowledge/skills/website-building-blocks/references/framework-website-demo-examples.md +3 -3
- package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +4 -2
- package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +3 -1
- package/dist/knowledge/skills/website-label-pack/SKILL.md +20 -5
- package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +6 -3
- package/dist/knowledge/skills/website-section-comparison/SKILL.md +2 -2
- package/dist/knowledge/skills/website-section-contact/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-cta/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-faq/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-hero/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-how-it-works/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-integrations/SKILL.md +3 -3
- package/dist/knowledge/skills/website-section-latest-posts/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-pricing/SKILL.md +142 -98
- package/dist/knowledge/skills/website-section-pricing/examples/pricing-offers.example.md +178 -66
- package/dist/knowledge/skills/website-section-pricing/references/framework-pricing-catalog-api.md +3 -1
- package/dist/knowledge/skills/website-section-problem/SKILL.md +3 -3
- package/dist/knowledge/skills/website-section-product-showcase/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-roadmap/SKILL.md +4 -4
- package/dist/knowledge/skills/website-section-social-proof/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-solution-paths/SKILL.md +2 -2
- package/dist/knowledge/skills/website-section-stats/SKILL.md +3 -3
- package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +3 -2
- package/dist/knowledge/skills/worker-authoring/SKILL.md +4 -2
- package/dist/knowledge/topic-index.json +2275 -715
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/package.json +6 -6
- package/dist/tsconfig.tsbuildinfo +0 -1
|
@@ -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;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;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"]}
|
|
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;gBAC3B;;;;;;;;;mBASG;gBACH,0BAA0B;aAC3B;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.2.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 * The STAFFING step, admitted for one reason: a build task can make an expert's charter stale. The design-system\n * task changes the design system the art director's and the design-system guardian's charters read, and the next\n * generation step that seats them (the logo panel) is refused until they are derived again (#3244). Before this\n * admission the refusal ended the lane and the build sat idle while the root ran other lanes (reference run\n * 42218788356: 32 of 98 tasks, 40 idle minutes). Now the wave holds that step and keeps filling, and the dispatch\n * child runs this staffing step itself after its wave (`staffingRepair`). Admitted so the lane's write scope\n * claims the charters: the conception lane admits it too, so the two lanes never share a root round and never\n * derive a charter at the same time.\n */\n 'top_down.expert-personas',\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,7 +17,7 @@ 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.
|
|
20
|
+
readonly version: "0.5.0";
|
|
21
21
|
readonly phase: "bottom_up";
|
|
22
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 [{
|
|
@@ -82,7 +82,10 @@ export declare const playbookDefinition: {
|
|
|
82
82
|
readonly family: "placement-plan";
|
|
83
83
|
}, {
|
|
84
84
|
readonly family: "vision-brief";
|
|
85
|
-
readonly "//": "
|
|
85
|
+
readonly "//": "The vision's constraints, including the creator's own compliance constraints. No intent slice: they must arrive whole.";
|
|
86
|
+
}, {
|
|
87
|
+
readonly family: "compliance-posture";
|
|
88
|
+
readonly "//": "The landed COMPLIANCE POSTURE (#3362: its own family, no longer constraints on the vision). Measured 2026-09-04 (#309): without the posture in its brief the decomposer, given a landed GDPR/ePrivacy posture, produced ZERO posture-derived tasks — the obligations lived in a family the brief never carried. Read whole.";
|
|
86
89
|
}, {
|
|
87
90
|
readonly family: "brand-brief";
|
|
88
91
|
readonly render: "map";
|
|
@@ -112,12 +115,12 @@ export declare const playbookDefinition: {
|
|
|
112
115
|
readonly outputs: readonly [{
|
|
113
116
|
readonly family: "build-plan";
|
|
114
117
|
readonly schemaRef: "saas-specifications:BuildPlanTaskGraph";
|
|
115
|
-
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;
|
|
118
|
+
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 / APPLICATION_ROLES / ORGANIZATION_MODEL), 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; the billing product the catalogue sells; the application's roles; and the organization model — its organization types, relationship kinds, row confinements and system-of-record bindings), 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 the working tree's files and named declarations, and an agent, an approval gate or a unit of work (#2966) is read from what the task's module REGISTERS with its registration files present; none of them proves 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 plan is also refused when a product is a lie no correct code can satisfy: a product ref that is a phrase, a `RESOURCE_OPERATION` restating a declared transition with something added (`approve-create-job`: a transition that creates a record does so in its own operation, on the transition's task), a `NAVIGATION` declaration that is not a zone key, or a `RELATIONSHIP` target whose `relationshipRefs` disagree with its `RESOURCE_RELATIONSHIP` products. Relationship tasks are ONE PER MODULE relationships file — the runtime regroups a plan that splits them per edge, in chained runs of at most six edges — because two tasks editing one file at once overwrite each other. 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.";
|
|
116
119
|
}];
|
|
117
120
|
readonly method: {
|
|
118
121
|
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.";
|
|
119
122
|
readonly contextSources: readonly ["workspace_truth", "skill_catalog", "coherence_report"];
|
|
120
|
-
readonly skillRefs: readonly ["resource-add-module", "resource-add-resource", "resource-schema-authoring", "resource-config-wiring", "resource-ui-behavior", "frontend-component-catalog", "spec-resource-update", "module-relationships", "module-registration", "application-database-migrations"];
|
|
123
|
+
readonly skillRefs: readonly ["resource-add-module", "resource-add-resource", "resource-schema-authoring", "resource-config-wiring", "resource-ui-behavior", "frontend-component-catalog", "spec-resource-update", "resource-status-lifecycle", "backend-custom-operation", "views-app-level", "module-relationships", "module-registration", "application-database-migrations", "config-saas-backend", "organization-relationships", "authorization-unit-narrowing", "resource-external-data"];
|
|
121
124
|
};
|
|
122
125
|
readonly executor: "companion_agent";
|
|
123
126
|
readonly approval: "approve_result";
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["
|
|
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;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAyFrB,CAAC;AAEX,eAAO,MAAM,yBAAyB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAuiBW,CAAC"}
|
|
@@ -17,7 +17,7 @@ import { MetaWorkflow_AuthorityAssuranceClass, MetaWorkflow_AuthorityDecisionMod
|
|
|
17
17
|
*/
|
|
18
18
|
export const playbookDefinition = {
|
|
19
19
|
"ref": "bottom_up.build-decompose",
|
|
20
|
-
"version": "0.
|
|
20
|
+
"version": "0.5.0",
|
|
21
21
|
"phase": "bottom_up",
|
|
22
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": [
|
|
@@ -56,7 +56,8 @@ export const playbookDefinition = {
|
|
|
56
56
|
{ "family": "requirements" },
|
|
57
57
|
{ "family": "feature-drafts" },
|
|
58
58
|
{ "family": "placement-plan" },
|
|
59
|
-
{ "family": "vision-brief", "//": "
|
|
59
|
+
{ "family": "vision-brief", "//": "The vision's constraints, including the creator's own compliance constraints. No intent slice: they must arrive whole." },
|
|
60
|
+
{ "family": "compliance-posture", "//": "The landed COMPLIANCE POSTURE (#3362: its own family, no longer constraints on the vision). Measured 2026-09-04 (#309): without the posture in its brief the decomposer, given a landed GDPR/ePrivacy posture, produced ZERO posture-derived tasks — the obligations lived in a family the brief never carried. Read whole." },
|
|
60
61
|
{ "family": "brand-brief", "render": "map", "//": "Whether the application HAS a brand decides whether the `logo` generation step is authored (method: companion generation steps; checklist invariant 6). The method only needs to know it exists, so it reads the brand as a map, not its content (#1424)." },
|
|
61
62
|
{ "family": "experience-plan", "//": "The application's own surfaces and its shell composition (#1493). Each view becomes a task over the product kind its KIND names, each configuration an APPLICATION_FRONTEND_CONFIG task, each planned milestone an APPLICATION_MILESTONE task and each planned piece of guidance an APPLICATION_GUIDANCE task — with the skill taken from the experience plan's total maps, never chosen here." },
|
|
62
63
|
{ "family": "documentation-plan", "//": "Which chapters the documentation portal carries (#1494). Each becomes a DOCUMENTATION_CHAPTER task under the TECHNICAL_DOCUMENTATION target, whose scope prohibits the portal's generated tree. A NOT_APPLICABLE plan, or none, emits nothing." },
|
|
@@ -70,7 +71,7 @@ export const playbookDefinition = {
|
|
|
70
71
|
{
|
|
71
72
|
"family": "build-plan",
|
|
72
73
|
"schemaRef": "saas-specifications:BuildPlanTaskGraph",
|
|
73
|
-
"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;
|
|
74
|
+
"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 / APPLICATION_ROLES / ORGANIZATION_MODEL), 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; the billing product the catalogue sells; the application's roles; and the organization model — its organization types, relationship kinds, row confinements and system-of-record bindings), 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 the working tree's files and named declarations, and an agent, an approval gate or a unit of work (#2966) is read from what the task's module REGISTERS with its registration files present; none of them proves 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 plan is also refused when a product is a lie no correct code can satisfy: a product ref that is a phrase, a `RESOURCE_OPERATION` restating a declared transition with something added (`approve-create-job`: a transition that creates a record does so in its own operation, on the transition's task), a `NAVIGATION` declaration that is not a zone key, or a `RELATIONSHIP` target whose `relationshipRefs` disagree with its `RESOURCE_RELATIONSHIP` products. Relationship tasks are ONE PER MODULE relationships file — the runtime regroups a plan that splits them per edge, in chained runs of at most six edges — because two tasks editing one file at once overwrite each other. 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."
|
|
74
75
|
}
|
|
75
76
|
],
|
|
76
77
|
"method": {
|
|
@@ -84,9 +85,16 @@ export const playbookDefinition = {
|
|
|
84
85
|
"resource-ui-behavior",
|
|
85
86
|
"frontend-component-catalog",
|
|
86
87
|
"spec-resource-update",
|
|
88
|
+
"resource-status-lifecycle",
|
|
89
|
+
"backend-custom-operation",
|
|
90
|
+
"views-app-level",
|
|
87
91
|
"module-relationships",
|
|
88
92
|
"module-registration",
|
|
89
|
-
"application-database-migrations"
|
|
93
|
+
"application-database-migrations",
|
|
94
|
+
"config-saas-backend",
|
|
95
|
+
"organization-relationships",
|
|
96
|
+
"authorization-unit-narrowing",
|
|
97
|
+
"resource-external-data"
|
|
90
98
|
]
|
|
91
99
|
},
|
|
92
100
|
"executor": "companion_agent",
|
|
@@ -114,7 +122,17 @@ export const evaluationTreatmentSource = {
|
|
|
114
122
|
// 14: conception-buildable reports an absent experience plan as a conception gap (#2494).
|
|
115
123
|
// 15: conception-buildable names a case of the firm's method the domain plan does not inventory (#2305 S4).
|
|
116
124
|
// 16: and a case lifecycle lacking a stage, or a deliverable from an uninventoried resource (#2305 S6).
|
|
117
|
-
|
|
125
|
+
// 17: organization-model coverage (#3035, #3036, #3039) — each type, relationship kind, confinement and binding has its product.
|
|
126
|
+
// 18: that coverage identifies the owner by ownsApplication and reads the configuration's existing organization model.
|
|
127
|
+
// 19: a binding partitions its instance exactly when the domain plan splits the records by legal entity (#3045).
|
|
128
|
+
// 20: the owner is renamed to the plan's names with renamedFrom, and relationship kinds name the plan's owner key (#3044, #3054).
|
|
129
|
+
// 21: experience coverage carries a VIEW home's blocks; interaction coverage asks for the person's side of each
|
|
130
|
+
// lifecycle — steps offered only from their starting states, worded refusals, a record page (#3066).
|
|
131
|
+
// 22: the record page names the engine's parts (status pill first, record keeping last), transitions carry a
|
|
132
|
+
// displayPriority, and a listing home block is drawn as its rows (collectionToolbar HIDDEN) (#3066 P2 options).
|
|
133
|
+
// 23: conception-buildable names a placement plan that disagrees with the experience plan's one entry per concept
|
|
134
|
+
// (#3066 deep review H1).
|
|
135
|
+
definitionVersion: 23,
|
|
118
136
|
evaluationProtocol: {
|
|
119
137
|
schemaVersion: 1,
|
|
120
138
|
protocolRef: 'application-creation:evaluation-protocol/build-plan-coherent',
|
|
@@ -363,8 +381,10 @@ export const evaluationTreatmentSource = {
|
|
|
363
381
|
{
|
|
364
382
|
schemaVersion: 1,
|
|
365
383
|
criterionRef: 'application-creation:criterion/build-plan-experience-coverage',
|
|
366
|
-
|
|
367
|
-
|
|
384
|
+
// 4: a VIEW home's blocks reach the objective of the task that builds the home view (#3066).
|
|
385
|
+
// 5: a block listing records is drawn as its rows (collectionToolbar HIDDEN) (#3066, #3070).
|
|
386
|
+
criterionVersion: 5,
|
|
387
|
+
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). When the plan decides a HOME, the GLOBAL_VIEWS configuration task's objective must set it: name `homeDefinitionFactory` and the home's view or resource operation. When a VIEW home decides its blocks, the objective of the task that builds the home's application view must carry every block: an AWAITING_DECISION block's resource and the transitions whose waiting records it lists, a MY_RECORDS block's resource, a KEY_FIGURE block's figure, and for a block that lists records, that its embedded list is drawn as its rows only (`collectionToolbar: CollectionToolbarPresence.HIDDEN`). A view, configuration, milestone or guidance entry with no task, or a decided home no objective sets, is a gap: the application would ship without it (a missing home opens on the framework's welcome page) while the plan reads complete. Never conclude the plan is absent because this criterion's own slice does not show it: the accepted application truth either renders the experience plan or says it has none. When the accepted application truth STATES that `experience-plan` has no accepted content, the decomposer has rightly emitted none of these tasks and cannot repair the absence by revising: record PASS, and begin the rationale with the words 'NO EXPERIENCE PLAN:' followed by what the application will therefore lack (its app-level views, its shell and navigation configuration, its milestones and its onboarding), so the absence is on the record instead of silent.",
|
|
368
388
|
assessesAspects: ['build-plan.task', 'experience-plan.view', 'experience-plan.configuration', 'experience-plan.milestone', 'experience-plan.guidance', 'experience-plan.home'],
|
|
369
389
|
evidenceRequirements: [{
|
|
370
390
|
schemaVersion: 1,
|
|
@@ -383,7 +403,7 @@ export const evaluationTreatmentSource = {
|
|
|
383
403
|
}],
|
|
384
404
|
verdictGuidance: {
|
|
385
405
|
[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.",
|
|
386
|
-
[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,
|
|
406
|
+
[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, an onboarding document's hostViewRef, or a block of a VIEW home, or a listing block drawn with its toolbar.",
|
|
387
407
|
[MetaWorkflow_EvaluationVerdict.GAP]: 'A view, configuration, milestone or guidance entry the experience plan declares has no task, a decided home is set by no task\'s objective, or a view task carries a viewRef the plan does not declare.',
|
|
388
408
|
[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.)',
|
|
389
409
|
},
|
|
@@ -421,6 +441,43 @@ export const evaluationTreatmentSource = {
|
|
|
421
441
|
[MetaWorkflow_EvaluationVerdict.INDETERMINATE]: 'The build plan or the requirements are not in evidence.',
|
|
422
442
|
},
|
|
423
443
|
},
|
|
444
|
+
/*
|
|
445
|
+
* #3035, #3036, #3039: the domain plan's organization model decides organization types, relationship kinds, row
|
|
446
|
+
* confinements and where a resource's records live, and nothing asked whether the build plan carried them. A
|
|
447
|
+
* confinement the requirements stated produced no task, so a generated internal tool showed every record to every
|
|
448
|
+
* member. Reads the whole evidence: the organization model's own aspects are the domain plan's to declare.
|
|
449
|
+
*/
|
|
450
|
+
{
|
|
451
|
+
schemaVersion: 1,
|
|
452
|
+
criterionRef: 'application-creation:criterion/build-plan-organization-model-coverage',
|
|
453
|
+
// 2: the owner type is identified by ownsApplication, never by key (#3035, Track C's finding).
|
|
454
|
+
// 3: read against what the configuration already declares, which the evidence now carries (second review, H1).
|
|
455
|
+
// 4: a binding states whether it partitions its instance, as the record location's split by legal entity decides (#3045).
|
|
456
|
+
// 5: the owner is renamed to the plan's names with renamedFrom where the configuration holds others; kinds name the plan's key (#3054).
|
|
457
|
+
criterionVersion: 5,
|
|
458
|
+
instruction: "Determine whether every entry of the domain plan's organizationModel has its build product. Every organization type the model declares is an ORGANIZATION_TYPE product of an ORGANIZATION_MODEL task carrying the entry's offered roles, user types and requiresMfa; the type that ownsApplication carries ownsApplication: true and revises the configuration's existing owner type whatever its key; where that type, or its people's user type, still carries another name than the plan's, its task renames them to the plan's names with renamedFrom (a task adding a second owner type, or replacing the existing one, is a GAP; one that renames a key without renamedFrom is a CONCERN). Every relationship kind the configuration does not already carry is an ORGANIZATION_RELATIONSHIP_KIND product, named by the entry's ref, and names the owner by the plan's key, which the configuration carries once renamed. Every unit confinement is an ORGANIZATION_UNIT_CONFINEMENT product with the entry's resource, mode and field, of an ORGANIZATION_MODEL task ordered after the config task of the resource it confines. Every resource whose records live in a system of record carries a SYSTEM_OF_RECORD_BINDING product on its config task, with partitioned: true when the entry's partition is BY_LEGAL_ENTITY or UNCONFIRMED and partitioned: false when it is NOT_SPLIT or CANNOT_BE_SPLIT (a binding that leaves it out, or says the opposite, is a GAP: the instance would show every entity's records to every member, or partition records the plan does not split); a copied (OWNED_COPY) resource of a partitioned instance also has its objective stamp each row's unit and entity key on its pipeline. A relationship between organizations is never a module or a resource: the engine owns those rows. With no organization model, or an empty one, there is nothing to cover. Compare against the evidence section 'The organization model this application's configuration already declares' (its owner type, relationship kinds and system-of-record instances with their vendors): a binding that names a new instance for a vendor already declared there is a CONCERN; when that section says the configuration could not be read, answer INDETERMINATE for the comparisons that need it.",
|
|
459
|
+
evidenceRequirements: [{
|
|
460
|
+
schemaVersion: 1,
|
|
461
|
+
requirementRef: 'application-creation:evidence-requirement/build-plan-organization-model-coverage',
|
|
462
|
+
requirementVersion: 1,
|
|
463
|
+
kind: MetaWorkflow_EvidenceRequirementKind.MANDATORY,
|
|
464
|
+
subjectRef: 'application-creation:definition-set/domain-plan-and-build-plan-candidate',
|
|
465
|
+
minCount: 1,
|
|
466
|
+
maxCount: 8,
|
|
467
|
+
coveragePolicyRef: 'application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate',
|
|
468
|
+
freshnessPolicyRef: 'application-creation:evidence-policy/current-action-binding',
|
|
469
|
+
conditionRef: null,
|
|
470
|
+
independencePolicyRef: null,
|
|
471
|
+
diversityPolicyRef: null,
|
|
472
|
+
aggregationPolicyRef: null,
|
|
473
|
+
}],
|
|
474
|
+
verdictGuidance: {
|
|
475
|
+
[MetaWorkflow_EvaluationVerdict.PASS]: 'The domain plan carries no organization model, or every type, relationship kind, confinement and system-of-record location it declares has its product.',
|
|
476
|
+
[MetaWorkflow_EvaluationVerdict.CONCERN]: 'Every entry has its product, but a confinement task is ordered before the config task of a resource it confines, or a type or kind is planned that the configuration already carries.',
|
|
477
|
+
[MetaWorkflow_EvaluationVerdict.GAP]: 'An organization type, relationship kind, confinement or system-of-record location the domain plan declares has no product, or a relationship between organizations is built as a module or a resource.',
|
|
478
|
+
[MetaWorkflow_EvaluationVerdict.INDETERMINATE]: 'The build plan or the domain plan is not in evidence.',
|
|
479
|
+
},
|
|
480
|
+
},
|
|
424
481
|
/*
|
|
425
482
|
* #2493: app-creation-test-004 (92 tasks) and -005 (86) planned no operation, document or email at all,
|
|
426
483
|
* and every lifecycle step shipped as a status users edit by hand. Each requirement was "served" by CRUD
|
|
@@ -434,8 +491,12 @@ export const evaluationTreatmentSource = {
|
|
|
434
491
|
// 4: the freeze lives in the objective of the transition into a final state, never in an `update` task (#2491 re-review).
|
|
435
492
|
// 5: locked states (no edits, may still move on) are frozen the same way as final ones (#2491 re-review M1),
|
|
436
493
|
// in both its lifecycle clause and its requirement-verb clause.
|
|
437
|
-
|
|
438
|
-
|
|
494
|
+
// 6: a transition is offered only from its starting states on every variant, a refusal reaches the person as a
|
|
495
|
+
// worded sentence, and a lifecycle resource's ui-behavior task builds its record page (#3066).
|
|
496
|
+
// 7: that record page names the engine's parts (status pill first, record keeping last in RecordKeepingFacts)
|
|
497
|
+
// and orders the transitions by displayPriority (#3066 P2 options).
|
|
498
|
+
criterionVersion: 7,
|
|
499
|
+
instruction: "Determine whether every transition the domain plan's lifecycles declare has a RESOURCE_OPERATION task on its resource (plus a MODULE_BACKEND task when the transition creates another resource), whether, for every lifecycle with locked or final states, the objective of a transition task moving into each of them restricts that resource's UPDATE to the states that are neither locked nor final (a separate RESOURCE_OPERATION named update is not a realisation: the scaffold already writes update, so it reads as built before it runs), and whether every functional acceptance criterion whose verb goes beyond the default resource verbs (create, read, update, list, delete) is served by a task able to realise it: a state change ('an accepted quote', 'issue the invoice', 'mark it paid') by a RESOURCE_OPERATION on the resource whose state changes; one record creating or filling another ('an accepted quote creates a job') by a RESOURCE_OPERATION on the source resource with a MODULE_BACKEND implementation; a record that must stop changing by the objective of the transition task into the locked or final state; a produced document by a PDF_TEMPLATE task; a sent message by the email generation step plus the triggering operation's task. A task citing the requirement in servesRefs does not realise a verb its kind cannot carry: a config or schema task leaves a status freely editable. A value derived from other records (a next action, an overdue flag) planned as a stored field is not a realisation either. Then the person's side of each lifecycle: whether each transition task's objective names its starting states as the only states the action is offered in, on every variant of the operation, and names any refusal the operation can raise for a reason the state does not show as a sentence the person reads; and whether every resource with a lifecycle has a RESOURCE_UI_BEHAVIOR task whose objective states its record page — the status as the leading pill shown once (on layout.header when the page authors one, otherwise RecordState first in layout.display, never both), the next steps as actions with words ordered by displayPriority so each state's main verb keeps a list row's one action slot, the fields in sections in business order, and the creator and timestamps last in RecordKeepingFacts.",
|
|
439
500
|
assessesAspects: ['build-plan.task', 'requirements.functional', 'domain-plan.module', 'domain-plan.resource', 'domain-plan.lifecycle'],
|
|
440
501
|
evidenceRequirements: [{
|
|
441
502
|
schemaVersion: 1,
|
|
@@ -454,8 +515,8 @@ export const evaluationTreatmentSource = {
|
|
|
454
515
|
}],
|
|
455
516
|
verdictGuidance: {
|
|
456
517
|
[MetaWorkflow_EvaluationVerdict.PASS]: 'No functional criterion names a verb beyond the default resource verbs, or each such verb is served by a task of a kind that can realise it, naming the requirement in servesRefs.',
|
|
457
|
-
[MetaWorkflow_EvaluationVerdict.CONCERN]: 'Every verb has a task, but a derived value (a next action, an overdue flag) is planned as a stored field,
|
|
458
|
-
[MetaWorkflow_EvaluationVerdict.GAP]: 'A declared lifecycle transition has no operation task, or no transition task into a locked or final state carries the UPDATE freeze (or it is planned as a separate update task); or a state change, a record creating another, a record that must stop changing, a produced document or a sent message named by a functional criterion has no task of a kind that can realise it — including a workflow-describing plan with no interaction task at all.',
|
|
518
|
+
[MetaWorkflow_EvaluationVerdict.CONCERN]: 'Every verb has a task, but a derived value (a next action, an overdue flag) is planned as a stored field, an operation task does not say which states it moves between or that it is offered only from them, a refusal the operation can raise is not worded for the person, or a lifecycle resource\'s ui-behavior objective does not state its record page (status pill first and shown once, next steps as worded actions ordered by displayPriority, sections in business order, record keeping last).',
|
|
519
|
+
[MetaWorkflow_EvaluationVerdict.GAP]: 'A declared lifecycle transition has no operation task, a resource with a lifecycle has no RESOURCE_UI_BEHAVIOR task (its page would be the engine\'s generated one, which knows no route), or no transition task into a locked or final state carries the UPDATE freeze (or it is planned as a separate update task); or a state change, a record creating another, a record that must stop changing, a produced document or a sent message named by a functional criterion has no task of a kind that can realise it — including a workflow-describing plan with no interaction task at all.',
|
|
459
520
|
[MetaWorkflow_EvaluationVerdict.INDETERMINATE]: 'The build plan or the requirements are not in evidence.',
|
|
460
521
|
},
|
|
461
522
|
},
|
|
@@ -473,8 +534,9 @@ export const evaluationTreatmentSource = {
|
|
|
473
534
|
// 2: an absent experience plan is a conception gap, routed back to the conception lane (#2494).
|
|
474
535
|
// 3: a case of the firm's method the domain plan does not inventory is a conception gap too (#2305 S4).
|
|
475
536
|
// 4: so is a case without the lifecycle its stages describe, and a deliverable from an uninventoried resource (#2305 S6).
|
|
476
|
-
|
|
477
|
-
|
|
537
|
+
// 5: a placement plan that disagrees with the experience plan's one entry per concept is a conception fault (#3066).
|
|
538
|
+
criterionVersion: 5,
|
|
539
|
+
instruction: "Determine whether the CONCEPTION this plan rests on can be built as declared. This criterion faults the domain plan, the capability composition or the surface plans — never the build plan. It is a GAP when (a) the domain plan declares a module, resource or relationship that no build task target can express, however it is decomposed, or (b) the computed coherence report shows a dangling reference or an unrealised decision in the conception (a domain-plan resource another family names that does not exist, a composition surface no plan realises, a case resource of the firm's service method the domain plan does not inventory, a case whose lifecycle lacks one of its stages, a deliverable produced from a resource the domain plan does not inventory, a placement plan that still puts a concept's list on the sidebar, leaves the concept's view off it or leaves one of its lists off the command menu — `concept-list-on-sidebar`, `concept-view-not-on-sidebar`, `concept-list-not-on-command-menu`) that the build would have to invent, or override, to proceed, or (c) the accepted application truth STATES that `experience-plan` has no accepted content: every application with a frontend has an experience, and without its plan the build has no home, no design system from the brand, no navigation decision and no application views, which no revision of this plan can supply; the same when it STATES that `integration-plan` has none, since then nothing decided whether the application runs workers, minions, provider bindings or inbound channels (an integration plan that decides none is content, not an absence). A domain-plan element declared in an expressible shape that the build plan simply omits is NOT this criterion: that is module-and-resource coverage, the decomposer's own fault. Name the conception element in the rationale.",
|
|
478
540
|
// An aspect of each family clause (c) reads, so the slice states an ABSENT experience or integration plan and points at
|
|
479
541
|
// the accepted truth (#2494 review G1, G6); a criterion naming no aspect of a family is told nothing about it.
|
|
480
542
|
assessesAspects: ['build-plan.task', 'domain-plan.module', 'domain-plan.resource', 'domain-plan.relationship', 'domain-plan.lifecycle', 'experience-plan.view', 'integration-plan.worker', 'service-method.service'],
|