@wildo-ai/framework-knowledge 1.1.4 → 1.1.5
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/esm/framework-knowledge.definitions.d.ts +1 -1
- package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.definitions.js +227 -6
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/framework-knowledge.loader.d.ts +19 -0
- package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.loader.js +47 -1
- package/dist/esm/framework-knowledge.loader.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/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +1 -1
- 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 +1 -1
- 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 +125 -0
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +177 -0
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +213 -7
- 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 +326 -8
- 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 +5 -3
- 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 +21 -14
- 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 +57 -0
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js +63 -0
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +132 -0
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +179 -0
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts +67 -0
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js +76 -0
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +5 -4
- 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 +10 -5
- 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 +67 -0
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +82 -0
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +25 -9
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +124 -7
- 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 +67 -0
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +83 -0
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts +69 -0
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js +71 -0
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +1 -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 +1 -1
- 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 +71 -0
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +88 -0
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts +97 -0
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js +156 -0
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts +115 -0
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +152 -0
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +188 -8
- 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 +167 -9
- 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 +171 -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 +146 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts +248 -0
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js +248 -0
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +157 -4
- 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 +172 -4
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +5 -4
- 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 +8 -7
- 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 +3 -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 +22 -3
- 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 +5 -3
- 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 +21 -12
- 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 +192 -27
- 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 +172 -33
- 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 +2 -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 +6 -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 +182 -5
- 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 +191 -5
- 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 +2 -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 +3 -2
- 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 +154 -0
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js +214 -0
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +44 -0
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +51 -0
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +2 -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 +2 -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 +2 -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 +6 -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 +2 -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 +2 -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 +2 -2
- 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 +7 -3
- 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 +32 -4
- 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 +27 -3
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -2
- 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 +4 -2
- 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 +199 -0
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +227 -0
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +5 -3
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +18 -4
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +155 -4
- 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 +187 -4
- 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 +6 -5
- 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 +18 -17
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -0
- package/dist/knowledge/manifest.json +9 -8
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +75 -0
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +43 -0
- package/dist/knowledge/playbooks/bottom_up.build/method.md +79 -0
- package/dist/knowledge/playbooks/bottom_up.build/playbook.json +65 -0
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +1122 -76
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +49 -13
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +671 -47
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +10 -16
- package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +31 -35
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +10 -16
- package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +95 -0
- package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +62 -0
- package/dist/knowledge/playbooks/bottom_up.conception/method.md +80 -0
- package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +90 -0
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +107 -0
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +70 -0
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +8 -8
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +14 -13
- package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +165 -0
- package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +74 -0
- package/dist/knowledge/playbooks/bottom_up.foundation/method.md +219 -140
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +55 -22
- package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +138 -0
- package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +70 -0
- package/dist/knowledge/playbooks/bottom_up.maturity-reading/method.md +87 -0
- package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +69 -0
- package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +236 -0
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +63 -0
- package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +116 -0
- package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +79 -0
- package/dist/knowledge/playbooks/cross_cutting.application-creation/method.md +71 -0
- package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +70 -0
- package/dist/knowledge/playbooks/cross_cutting.compliance/method.md +83 -0
- package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +68 -0
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +873 -15
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +19 -12
- package/dist/knowledge/playbooks/refinement.document-facts/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/refinement.document-facts/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +186 -21
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +12 -16
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/method.md +343 -0
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +54 -0
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.brand-identity/method.md +28 -11
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +15 -17
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +8 -15
- package/dist/knowledge/playbooks/top_down.capability-map/method.md +25 -49
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +14 -17
- package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +41 -0
- package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +101 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +209 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +68 -0
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +61 -0
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +42 -0
- package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +39 -12
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +18 -66
- package/dist/knowledge/playbooks/top_down.compliance-research/method.md +78 -0
- package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +43 -0
- package/dist/knowledge/playbooks/top_down.definition/method.md +103 -0
- package/dist/knowledge/playbooks/top_down.definition/playbook.json +75 -0
- package/dist/knowledge/playbooks/top_down.expert-personas/method.md +56 -0
- package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +48 -0
- package/dist/knowledge/playbooks/top_down.market-analysis/method.md +51 -165
- package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +25 -44
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +56 -0
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +43 -0
- package/dist/knowledge/playbooks/top_down.market-research/method.md +68 -0
- package/dist/knowledge/playbooks/top_down.market-research/playbook.json +45 -0
- package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +247 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +71 -0
- 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/method.md +36 -69
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +12 -9
- package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +11 -7
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +12 -16
- package/dist/knowledge/playbooks/top_down.risk-register/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.risk-register/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.risk-register/method.md +46 -0
- package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +59 -0
- package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +12 -5
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +15 -17
- package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.value-proposition/method.md +23 -14
- package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +12 -17
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +7 -3
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +13 -17
- package/dist/knowledge/references/acp.execution-profile.md +266 -0
- package/dist/knowledge/references/acp.host-configuration-inheritance.md +29 -0
- package/dist/knowledge/references/acp.permission-ceiling.md +105 -0
- package/dist/knowledge/references/acp.permission-escalation.md +37 -0
- package/dist/knowledge/references/application-documentation-chapters.config.md +152 -0
- package/dist/knowledge/references/application-documentation-plan.config.md +136 -0
- package/dist/knowledge/references/application-maturity.config.md +319 -0
- package/dist/knowledge/references/assertions.authored-metadata.config.md +1 -1
- package/dist/knowledge/references/assertions.specification.config.md +1 -1
- package/dist/knowledge/references/brand.asset.config.md +8 -16
- package/dist/knowledge/references/brand.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/brand.logo-direction.config.md +9 -7
- package/dist/knowledge/references/brand.snapshot.config.md +16 -2
- package/dist/knowledge/references/brand.snapshot.validation.md +0 -7
- package/dist/knowledge/references/build-plan.task-graph.config.md +581 -7
- package/dist/knowledge/references/business-model.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/business-model.pricing-plan.config.md +1 -1
- package/dist/knowledge/references/business-model.snapshot.validation.md +15 -0
- package/dist/knowledge/references/capability-composition.config.md +155 -0
- package/dist/knowledge/references/cli.market.utils.md +1 -0
- package/dist/knowledge/references/companion.technical-doc.service.md +453 -98
- package/dist/knowledge/references/engine.client-bundle.allow-list.md +21 -0
- package/dist/knowledge/references/engine.client-bundle.external-connectors-public.discipline.md +20 -1
- package/dist/knowledge/references/engine.saas-technical-doc.config.md +8 -4
- package/dist/knowledge/references/engine.saas-website.config.md +22 -10
- package/dist/knowledge/references/example.backend.addon-wiring.module.md +8 -12
- package/dist/knowledge/references/example.config.app-shell.full.md +42 -7
- package/dist/knowledge/references/example.config.backend.required-floors.md +4 -0
- package/dist/knowledge/references/example.config.design-system.full.md +3 -0
- package/dist/knowledge/references/example.engine.product-definitions.feature-and-profiles.md +19 -7
- package/dist/knowledge/references/example.features.connected-feature.declaration.md +66 -0
- package/dist/knowledge/references/example.features.connected-feature.surface.md +42 -0
- package/dist/knowledge/references/example.flows-actors.chat-assistant.md +4 -3
- package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +6 -10
- package/dist/knowledge/references/example.guidance.bound-survey-flow.md +82 -0
- package/dist/knowledge/references/example.infra.environment-config.local.md +88 -11
- package/dist/knowledge/references/example.milestones.module-definitions.md +73 -0
- package/dist/knowledge/references/example.minion.contained-tick.md +79 -0
- package/dist/knowledge/references/example.module.companion-exports.full.md +38 -3
- package/dist/knowledge/references/example.provider.backend-module-shape.md +31 -13
- package/dist/knowledge/references/example.provider.frontend-app.module.md +103 -0
- package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +20 -0
- package/dist/knowledge/references/example.provider.frontend-file-picker.module.md +7 -3
- package/dist/knowledge/references/example.provider.operation.backend-typed-client.md +30 -0
- package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +11 -0
- package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +3 -0
- package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +94 -10
- package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +79 -0
- package/dist/knowledge/references/example.spec.frontend-component.prop-vocabulary.md +18 -0
- package/dist/knowledge/references/example.worker.node-route.md +94 -0
- package/dist/knowledge/references/experience-plan.config.md +311 -0
- package/dist/knowledge/references/external-connectors.app.frontend-provider-module.md +132 -9
- package/dist/knowledge/references/external-connectors.backend.provider-package-convention.md +36 -0
- package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +269 -0
- package/dist/knowledge/references/integration-plan.config.md +185 -0
- package/dist/knowledge/references/market.alternative.config.md +1 -1
- package/dist/knowledge/references/market.authored-metadata.config.md +12 -9
- package/dist/knowledge/references/market.channel.config.md +3 -3
- package/dist/knowledge/references/market.feature-benefit.config.md +1 -1
- package/dist/knowledge/references/market.gain.config.md +1 -1
- package/dist/knowledge/references/market.icp.config.md +2 -2
- package/dist/knowledge/references/market.job.config.md +1 -1
- package/dist/knowledge/references/market.message-template.config.md +2 -2
- package/dist/knowledge/references/market.objection.config.md +1 -1
- package/dist/knowledge/references/market.pain.config.md +1 -1
- package/dist/knowledge/references/market.persona.config.md +2 -2
- package/dist/knowledge/references/market.proof.config.md +1 -1
- package/dist/knowledge/references/market.snapshot.validation.md +15 -0
- package/dist/knowledge/references/market.tone-of-voice.config.md +1 -1
- package/dist/knowledge/references/market.trigger.config.md +1 -1
- package/dist/knowledge/references/minions.tick-contract.md +83 -0
- package/dist/knowledge/references/placement-plan.config.md +369 -0
- package/dist/knowledge/references/platform.config.application-database.md +5 -2
- package/dist/knowledge/references/platform.config.backing-services.md +0 -21
- package/dist/knowledge/references/platform.config.environment.deployment.md +206 -14
- package/dist/knowledge/references/platform.config.infra-provider-resolution.md +170 -0
- package/dist/knowledge/references/platform.config.infrastructure-host.md +87 -0
- package/dist/knowledge/references/platform.config.saas.md +261 -9
- package/dist/knowledge/references/presets.models.labelling.sections.md +14 -0
- package/dist/knowledge/references/presets.models.surface-policy.md +19 -10
- package/dist/knowledge/references/requirements.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/requirements.snapshot.validation.md +15 -0
- package/dist/knowledge/references/roadmap.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/roadmap.snapshot.validation.md +15 -7
- package/dist/knowledge/references/saas.backend.a2a.token-budget.md +71 -0
- package/dist/knowledge/references/saas.backend.app-config.backend-authored.md +1 -2
- package/dist/knowledge/references/saas.backend.auth.federated-identity-provider-private-networks.md +62 -0
- package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +86 -0
- package/dist/knowledge/references/saas.backend.billing.catalog-sync-result.md +37 -0
- package/dist/knowledge/references/saas.backend.billing.resolution-failure-reasons.md +24 -5
- package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +187 -0
- package/dist/knowledge/references/saas.backend.domain-module.md +25 -1
- package/dist/knowledge/references/saas.backend.error-builder.user-guidance.md +82 -0
- package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +6 -0
- package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +22 -4
- package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +17 -4
- package/dist/knowledge/references/saas.backend.flows-actors.tool-dispatch-obligations.md +84 -0
- package/dist/knowledge/references/saas.backend.health-readiness-contributor.md +73 -0
- package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +200 -0
- package/dist/knowledge/references/saas.backend.providers.operation-executor.md +51 -0
- package/dist/knowledge/references/saas.backend.providers.optional-runtime-peers.md +71 -0
- package/dist/knowledge/references/saas.backend.queue.worker-topology.md +39 -0
- package/dist/knowledge/references/saas.backend.system-access-service.md +51 -42
- package/dist/knowledge/references/saas.composition.scenario-apply.md +51 -0
- package/dist/knowledge/references/saas.config.content-security-policy.md +97 -0
- package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +91 -21
- package/dist/knowledge/references/saas.data-seeding.definition-input.md +4 -0
- package/dist/knowledge/references/saas.external-providers.backend-provider-loader.md +38 -0
- package/dist/knowledge/references/saas.external-providers.backend-provider-registry.runtime-filter.md +27 -27
- package/dist/knowledge/references/saas.external-providers.llm.model-configuration.md +65 -16
- package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +41 -11
- package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +44 -8
- package/dist/knowledge/references/saas.frontend.billing-context.md +108 -0
- package/dist/knowledge/references/saas.frontend.brand-identity.md +38 -0
- package/dist/knowledge/references/saas.frontend.celebration-overlay-contract.md +41 -0
- package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +64 -0
- package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +34 -0
- package/dist/knowledge/references/saas.frontend.errors.user-facing-error-message.md +47 -0
- package/dist/knowledge/references/saas.frontend.execution-view.action-status-contract.per-action-retry-loop.md +7 -1
- package/dist/knowledge/references/saas.frontend.execution-view.definition.md +3 -3
- package/dist/knowledge/references/saas.frontend.flows-actors-view.md +7 -4
- package/dist/knowledge/references/saas.frontend.form-fields.file-provider-constraints.md +30 -48
- package/dist/knowledge/references/saas.frontend.full-custom-view.definition.md +24 -0
- package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +45 -0
- package/dist/knowledge/references/saas.frontend.onboarding-view.md +84 -0
- package/dist/knowledge/references/saas.frontend.providers.execute-operation.md +65 -0
- package/dist/knowledge/references/saas.frontend.public-shell.identity-mode.md +65 -0
- package/dist/knowledge/references/saas.frontend.resource-header-title.md +28 -4
- package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +127 -1
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +327 -11
- package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +198 -0
- package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +220 -0
- package/dist/knowledge/references/saas.market.generation-agent.md +26 -9
- package/dist/knowledge/references/saas.models.analytics.value-moments.md +132 -0
- package/dist/knowledge/references/saas.models.audit.trail-config.md +155 -0
- package/dist/knowledge/references/saas.models.auth.methods.md +513 -0
- package/dist/knowledge/references/saas.models.authorization.administrative-continuity-codes.md +82 -0
- package/dist/knowledge/references/saas.models.billing.catalog-vocabularies.md +77 -0
- package/dist/knowledge/references/saas.models.config.organization-types.md +192 -0
- package/dist/knowledge/references/saas.models.config.registration.md +188 -0
- package/dist/knowledge/references/saas.models.config.tenant-teardown.md +81 -0
- package/dist/knowledge/references/saas.models.data-mode-read-list.md +173 -3
- package/dist/knowledge/references/saas.models.email.template-type.md +40 -0
- package/dist/knowledge/references/saas.models.engine-capabilities.md +85 -7
- package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +61 -0
- package/dist/knowledge/references/saas.models.external-data-pipeline.md +43 -4
- package/dist/knowledge/references/saas.models.features.definition-builders.md +162 -0
- package/dist/knowledge/references/saas.models.file-upload-grant.md +222 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-definition.md +54 -5
- package/dist/knowledge/references/saas.models.governed-document-acceptance-mode.md +116 -0
- package/dist/knowledge/references/saas.models.guidance-flow.md +160 -0
- package/dist/knowledge/references/saas.models.http-api-binding.md +76 -110
- package/dist/knowledge/references/saas.models.milestone-celebration.md +69 -0
- package/dist/knowledge/references/saas.models.milestone-definition.md +209 -0
- package/dist/knowledge/references/saas.models.navigation.layout.md +2 -2
- package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +124 -0
- package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +99 -0
- package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +150 -0
- package/dist/knowledge/references/saas.models.notifications.badge-vocabularies.md +70 -0
- package/dist/knowledge/references/saas.models.notifications.targets.md +138 -0
- package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +256 -0
- package/dist/knowledge/references/saas.models.onboarding-elements.md +375 -0
- package/dist/knowledge/references/saas.models.onboarding-trigger.md +52 -0
- package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +50 -0
- package/dist/knowledge/references/saas.models.organizations.application-owner-codes.md +129 -0
- package/dist/knowledge/references/saas.models.privacy.client-instance-id-scope.md +49 -0
- package/dist/knowledge/references/saas.models.privacy.redaction-treatments.md +106 -0
- package/dist/knowledge/references/saas.models.progression-tracker-variant.md +76 -0
- package/dist/knowledge/references/saas.models.provider-capabilities.md +8 -5
- package/dist/knowledge/references/saas.models.providers.browser-operation-policy.md +72 -0
- package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +50 -0
- package/dist/knowledge/references/saas.models.providers.capability-surface.md +58 -0
- package/dist/knowledge/references/saas.models.providers.compliance-choice.md +111 -0
- package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +156 -0
- package/dist/knowledge/references/saas.models.rate-limit-configuration.md +11 -1
- package/dist/knowledge/references/saas.models.relationship-handling-settings.md +23 -1
- package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +122 -4
- package/dist/knowledge/references/saas.models.resource-config.forwarded-label.md +5 -4
- package/dist/knowledge/references/saas.models.resource-config.metered-usage-recording.md +69 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +15 -2
- package/dist/knowledge/references/saas.models.resource-config.operation-auditable-event.md +66 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-base.md +24 -1
- package/dist/knowledge/references/saas.models.resource-config.operation-cron-job.md +59 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-idempotency-key.md +55 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-mcp-exposure.md +5 -4
- package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +158 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-step-up.md +77 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +42 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-variant-for-key.md +6 -1
- package/dist/knowledge/references/saas.models.resource-config.queue-policy.md +49 -0
- package/dist/knowledge/references/saas.models.resource-config.required-features.md +84 -0
- package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +10 -0
- package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +14 -0
- package/dist/knowledge/references/saas.models.resource-config.system-access-policy.md +111 -4
- package/dist/knowledge/references/saas.models.resource-config.system-managed-fields.md +39 -0
- package/dist/knowledge/references/saas.models.resource-operation-display-risk.md +48 -0
- package/dist/knowledge/references/saas.models.resource-operation-variant-runtime.md +38 -0
- package/dist/knowledge/references/saas.models.resource-primary-scope.md +11 -2
- package/dist/knowledge/references/saas.models.scope-membership.md +3 -4
- package/dist/knowledge/references/saas.models.shared-saas-module.md +25 -0
- package/dist/knowledge/references/saas.models.systems-of-record.md +635 -0
- package/dist/knowledge/references/saas.public-runtime.contract.md +198 -1
- package/dist/knowledge/references/saas.rag.retrieval-result.md +19 -8
- package/dist/knowledge/references/saas.specifications.application-authored-document-fact-specification.contract.md +29 -0
- package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +15 -36
- package/dist/knowledge/references/saas.specifications.application-document-publication.contract.md +9 -5
- package/dist/knowledge/references/saas.specifications.application-document-publication.generation.md +63 -0
- package/dist/knowledge/references/saas.specifications.application-document-release-set.contract.md +74 -0
- package/dist/knowledge/references/saas.specifications.assurance-control-markers.md +123 -0
- package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +88 -7
- package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +774 -53
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +211 -14
- package/dist/knowledge/references/saas.specifications.composite-view-specification.md +10 -0
- package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +364 -0
- package/dist/knowledge/references/saas.specifications.playbook-approval-and-failure-policies.md +96 -0
- package/dist/knowledge/references/saas.specifications.processor-register.md +333 -0
- package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +8 -0
- package/dist/knowledge/references/saas.specifications.resource-spec-config.md +22 -0
- package/dist/knowledge/references/saas.website.astro.bridge.md +64 -2
- package/dist/knowledge/references/saas.website.astro.head-renderer.md +32 -12
- package/dist/knowledge/references/saas.website.astro.label-loader.md +3 -0
- package/dist/knowledge/references/saas.website.astro.robots-renderer.md +14 -1
- package/dist/knowledge/references/saas.website.blog.bridge.md +21 -1
- package/dist/knowledge/references/saas.website.consent.banner.md +218 -0
- package/dist/knowledge/references/saas.website.consent.context.md +162 -0
- package/dist/knowledge/references/saas.website.consent.gate.md +38 -0
- package/dist/knowledge/references/saas.website.page-layout.component.md +67 -1
- package/dist/knowledge/references/saas.website.page.context.md +4 -3
- package/dist/knowledge/references/saas.website.runtime.context.md +43 -7
- package/dist/knowledge/references/saas.website.section.context.md +3 -2
- package/dist/knowledge/references/saas.website.sections.category-enum.md +19 -20
- package/dist/knowledge/references/vision.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/website-plan.config.md +205 -0
- package/dist/knowledge/references/workers.node.worker-init-contract.md +57 -0
- package/dist/knowledge/references/zod.decorators.chainable-runtime.md +43 -2
- package/dist/knowledge/references/zod.decorators.data-categories.md +197 -0
- package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +51 -4
- package/dist/knowledge/references/zod.decorators.display-edit-modes.md +54 -1
- package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +35 -0
- package/dist/knowledge/references/zod.decorators.field-spec-params.md +32 -5
- package/dist/knowledge/references/zod.decorators.file-nature-constraints.md +86 -0
- package/dist/knowledge/references/zod.decorators.file-readiness-metadata.md +67 -0
- package/dist/knowledge/references/zod.decorators.file-schema.md +90 -14
- package/dist/knowledge/references/zod.decorators.file-vocabularies.md +84 -0
- package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +140 -4
- package/dist/knowledge/references/zod.decorators.primitive-ui.md +3 -0
- package/dist/knowledge/references/zod.decorators.rag-source.md +6 -2
- package/dist/knowledge/references/zod.decorators.schema-metadata.md +24 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +35 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-params.md +46 -12
- package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +31 -12
- package/dist/knowledge/references/zod.factories.address.md +118 -0
- package/dist/knowledge/references/zod.factories.code.md +2 -0
- package/dist/knowledge/references/zod.factories.duration.md +2 -0
- package/dist/knowledge/references/zod.factories.money.md +2 -0
- package/dist/knowledge/references/zod.factories.phone.md +14 -1
- package/dist/knowledge/registries/assurance-authority-bases.json +3 -2
- package/dist/knowledge/registries/framework-topics.json +1215 -11
- package/dist/knowledge/registries/playbooks.json +454 -50
- package/dist/knowledge/registries/source-tags.json +3153 -1043
- package/dist/knowledge/rules/database-migration-obligation.md +110 -0
- package/dist/knowledge/rules/live-context-door.md +108 -0
- package/dist/knowledge/rules/resource-schema-awareness.md +75 -0
- package/dist/knowledge/skills/INDEX.md +46 -11
- package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +80 -37
- package/dist/knowledge/skills/application-consumer-documentation-authoring/references/framework-documentation-chapters-api.md +167 -0
- package/dist/knowledge/skills/application-consumer-documentation-authoring/references/source-and-ownership-routing.md +6 -3
- package/dist/knowledge/skills/application-database-migrations/SKILL.md +10 -3
- package/dist/knowledge/skills/application-database-migrations/references/framework-application-database-api.md +5 -2
- package/dist/knowledge/skills/application-database-migrations/references/migration-refusals.md +32 -0
- package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +94 -3
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +50 -0
- package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +26 -19
- package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +25 -1
- package/dist/knowledge/skills/backend-addon-wiring/references/framework-readiness-contributor-api.md +135 -0
- package/dist/knowledge/skills/backend-custom-operation/SKILL.md +75 -12
- package/dist/knowledge/skills/backend-custom-operation/references/framework-assurance-control-markers.md +137 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-error-user-guidance-api.md +112 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-operation-base-and-path-api.md +72 -1
- package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +207 -0
- package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +31 -1
- package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-asset-api.md +8 -16
- package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-snapshot-api.md +25 -9
- package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +135 -5
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +80 -17
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +369 -111
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +32 -10
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +103 -58
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-publication-contract.md +19 -13
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +142 -26
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +722 -23
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +348 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +123 -0
- package/dist/knowledge/skills/config-app-shell/SKILL.md +74 -11
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +85 -19
- package/dist/knowledge/skills/config-app-shell/references/framework-brand-identity-api.md +70 -0
- package/dist/knowledge/skills/config-app-shell/references/framework-public-shell-identity-api.md +124 -0
- package/dist/knowledge/skills/config-design-system/SKILL.md +43 -3
- package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +19 -10
- package/dist/knowledge/skills/config-design-system/references/loading-placeholder-authoring.md +47 -0
- package/dist/knowledge/skills/config-design-system/references/surface-policy-authoring.md +19 -10
- package/dist/knowledge/skills/config-navigation/SKILL.md +85 -2
- package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +98 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-layout-api.md +2 -2
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +54 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +232 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +172 -0
- package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +146 -0
- package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +141 -0
- package/dist/knowledge/skills/config-saas/SKILL.md +86 -9
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +199 -0
- package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +179 -0
- package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +493 -0
- package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +153 -0
- package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +242 -0
- package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +161 -0
- package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +93 -12
- package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +785 -0
- package/dist/knowledge/skills/config-saas/references/framework-value-moments-api.md +172 -0
- package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +261 -9
- package/dist/knowledge/skills/config-saas/references/saas-config-scope.md +9 -0
- package/dist/knowledge/skills/config-saas-backend/SKILL.md +58 -3
- package/dist/knowledge/skills/config-saas-backend/references/framework-application-owner-organization-codes-api.md +151 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-auth-methods-api.md +579 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-backend-authored-config-api.md +8 -2
- package/dist/knowledge/skills/config-saas-backend/references/framework-federated-identity-provider-private-networks-api.md +96 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +316 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-registration-config-api.md +221 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-tenant-teardown-api.md +121 -0
- package/dist/knowledge/skills/config-saas-backend/references/managed-startup-configuration.md +46 -0
- package/dist/knowledge/skills/configure-billing/SKILL.md +27 -22
- package/dist/knowledge/skills/configure-billing/references/config-chain-and-failure-map.md +27 -15
- package/dist/knowledge/skills/configure-billing/references/example-backend-billing-enable-block.md +41 -0
- package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +36 -17
- package/dist/knowledge/skills/configure-billing/references/framework-backend-provider-reachability-api.md +30 -28
- package/dist/knowledge/skills/configure-billing/references/framework-billing-frontend-api.md +169 -0
- package/dist/knowledge/skills/configure-billing/references/framework-billing-resolution-failure-api.md +44 -11
- package/dist/knowledge/skills/configure-billing/references/framework-product-catalog-api.md +187 -0
- package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +76 -0
- package/dist/knowledge/skills/configure-coding-agent/SKILL.md +280 -0
- package/dist/knowledge/skills/configure-coding-agent/references/agent-selection.md +168 -0
- package/dist/knowledge/skills/configure-coding-agent/references/framework-acp-execution-profile-api.md +504 -0
- package/dist/knowledge/skills/email-add-template/SKILL.md +41 -69
- package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +15 -7
- package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +120 -0
- package/dist/knowledge/skills/engine-component-registration/SKILL.md +19 -12
- package/dist/knowledge/skills/engine-product-definitions/SKILL.md +54 -31
- package/dist/knowledge/skills/engine-product-definitions/references/connected-feature-workflow.md +130 -0
- package/dist/knowledge/skills/engine-product-definitions/references/framework-engine-product-definitions-api.md +25 -0
- package/dist/knowledge/skills/engine-product-definitions/references/framework-feature-builders-api.md +215 -0
- package/dist/knowledge/skills/engine-product-definitions/references/framework-metered-usage-recording-api.md +78 -0
- package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +33 -24
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +121 -0
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +4 -3
- package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +10 -8
- package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +5 -4
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +46 -9
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +34 -7
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +151 -0
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +6 -10
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +54 -5
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-operation-and-model-api.md +75 -21
- package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +258 -0
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +480 -0
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +3983 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/SKILL.md +211 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-guidance-flow-api.md +165 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-elements-api.md +381 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-trigger-api.md +57 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-view-api.md +89 -0
- package/dist/knowledge/skills/i18n-label-generation/SKILL.md +13 -1
- package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +14 -0
- package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +14 -0
- package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +3 -1
- package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +14 -0
- package/dist/knowledge/skills/infra-environment-config/SKILL.md +237 -37
- package/dist/knowledge/skills/infra-environment-config/references/framework-application-database-api.md +5 -2
- package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +174 -21
- package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +206 -14
- package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +95 -0
- package/dist/knowledge/skills/journey-approve/SKILL.md +28 -8
- package/dist/knowledge/skills/journey-approve/references/specification-family-map.md +88 -0
- package/dist/knowledge/skills/journey-bootstrap-scope/SKILL.md +37 -2
- package/dist/knowledge/skills/journey-next/SKILL.md +41 -1
- package/dist/knowledge/skills/journey-report/SKILL.md +16 -3
- package/dist/knowledge/skills/journey-run/SKILL.md +92 -7
- package/dist/knowledge/skills/journey-run/references/expert-personas-and-deliberations.md +46 -0
- package/dist/knowledge/skills/journey-run/references/framework-playbook-approval-policy.md +108 -0
- package/dist/knowledge/skills/journey-status/SKILL.md +14 -4
- package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +153 -46
- package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +119 -0
- package/dist/knowledge/skills/local-environment-bootstrap/references/initialization-recovery-recipe.md +7 -4
- package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +253 -33
- package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +1 -1
- package/dist/knowledge/skills/market-add-feature-benefit/references/framework-feature-benefit-api.md +1 -1
- package/dist/knowledge/skills/market-alternatives/SKILL.md +1 -1
- package/dist/knowledge/skills/market-authoring-overview/references/framework-market-snapshot-api.md +12 -9
- package/dist/knowledge/skills/market-channels/SKILL.md +3 -3
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +226 -14
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +226 -14
- package/dist/knowledge/skills/market-generation-cli/SKILL.md +56 -9
- package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +32 -9
- package/dist/knowledge/skills/market-icp/SKILL.md +2 -2
- package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +3 -3
- package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +2 -2
- package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +17 -2
- package/dist/knowledge/skills/market-persona/SKILL.md +2 -2
- package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +2 -2
- package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +15 -0
- package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +15 -0
- package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +1 -1
- package/dist/knowledge/skills/market-triggers-and-journey/SKILL.md +1 -1
- package/dist/knowledge/skills/milestones-and-celebrations/SKILL.md +198 -0
- package/dist/knowledge/skills/milestones-and-celebrations/references/framework-celebration-overlay-contract.md +51 -0
- package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-celebration-api.md +79 -0
- package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-definition-api.md +220 -0
- package/dist/knowledge/skills/milestones-and-celebrations/references/framework-progression-tracker-api.md +86 -0
- package/dist/knowledge/skills/minion-authoring/SKILL.md +140 -0
- package/dist/knowledge/skills/minion-authoring/examples/contained-tick.example.md +84 -0
- package/dist/knowledge/skills/minion-authoring/references/framework-minion-tick-contract.md +91 -0
- package/dist/knowledge/skills/module-companion-exports/SKILL.md +38 -3
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +211 -14
- package/dist/knowledge/skills/module-registration/SKILL.md +50 -33
- package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +50 -1
- package/dist/knowledge/skills/module-registration/references/framework-notification-badges-api.md +142 -0
- package/dist/knowledge/skills/module-registration/references/registry-files.md +14 -5
- package/dist/knowledge/skills/module-relationships/SKILL.md +62 -0
- package/dist/knowledge/skills/module-relationships/references/framework-resource-relationship-authoring-api.md +26 -5
- package/dist/knowledge/skills/provider-backend-package/SKILL.md +279 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +80 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-loader-api.md +55 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-package-convention-api.md +48 -0
- package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +33 -6
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-file-provider-constraints-api.md +99 -47
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-module-api.md +241 -9
- package/dist/knowledge/skills/provider-operation-calls/SKILL.md +196 -0
- package/dist/knowledge/skills/provider-operation-calls/references/browser-door-answers.md +50 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-browser-operation-policy-api.md +80 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-frontend-execute-operation-api.md +71 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-operation-executor-api.md +58 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +275 -0
- package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +64 -11
- package/dist/knowledge/skills/rate-limit-authoring/references/fixed-window-and-environment-multiplier.md +27 -0
- package/dist/knowledge/skills/rate-limit-authoring/references/framework-rate-limit-policy-api.md +19 -6
- package/dist/knowledge/skills/resource-add-field/SKILL.md +12 -5
- package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +373 -23
- package/dist/knowledge/skills/resource-add-module/SKILL.md +116 -265
- package/dist/knowledge/skills/resource-add-module/references/framework-composition-scenarios-api.md +133 -0
- package/dist/knowledge/skills/resource-add-module/references/framework-new-module-wiring-api.md +25 -0
- package/dist/knowledge/skills/resource-add-module/references/module-scaffold-layout.md +12 -12
- package/dist/knowledge/skills/resource-add-resource/SKILL.md +26 -3
- package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +122 -4
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +25 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-administrative-continuity-codes-api.md +93 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-authority-audit-interpretation.md +136 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +85 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +133 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-idempotency-key-api.md +141 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-step-up-api.md +126 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +859 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-required-features-api.md +122 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +124 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +97 -2
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +457 -15
- package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +197 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +162 -46
- package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +452 -0
- package/dist/knowledge/skills/resource-custom-view/SKILL.md +5 -0
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +327 -11
- package/dist/knowledge/skills/resource-custom-view/references/framework-user-facing-error-message-api.md +50 -0
- package/dist/knowledge/skills/resource-external-data/SKILL.md +228 -15
- package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +54 -7
- package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +87 -113
- package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +13 -8
- package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +69 -26
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-file-upload-grant-contract.md +246 -0
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-resource-mcp-exposure-contract.md +7 -6
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-catalogue-withdrawal-and-verification.md +5 -3
- package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +43 -48
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +96 -14
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +47 -15
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-source-decorator-api.md +6 -2
- package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +32 -2
- package/dist/knowledge/skills/resource-schema-authoring/examples/basic-resource-schema.example.md +2 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/decorator-layer-map.md +17 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +75 -4
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-erasure-scrub-treatments-api.md +182 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +245 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +35 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +46 -12
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +480 -15
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-system-managed-fields-api.md +67 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +74 -14
- package/dist/knowledge/skills/resource-schema-authoring/references/polymorphic-per-scope-resources.md +28 -5
- package/dist/knowledge/skills/resource-schema-authoring/references/schema-variants-and-discriminators.md +25 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +1 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/special-factories.md +34 -0
- package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +236 -18
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +54 -1
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +35 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +327 -11
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +140 -4
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +3 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +155 -5
- package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +165 -0
- package/dist/knowledge/skills/seeding-authoring/SKILL.md +9 -1
- package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +4 -0
- package/dist/knowledge/skills/seeding-operations/SKILL.md +33 -29
- package/dist/knowledge/skills/seeding-operations/references/data-seeding-admin-runbook.md +13 -5
- package/dist/knowledge/skills/seeding-operations/references/data-seeding-cron-scheduler.md +67 -74
- package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +97 -24
- package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +205 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +205 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +229 -0
- package/dist/knowledge/skills/spec-companion-exports/SKILL.md +38 -3
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +211 -14
- package/dist/knowledge/skills/spec-component-update/SKILL.md +30 -11
- package/dist/knowledge/skills/spec-composite-view-update/references/framework-composite-view-specification-api.md +10 -0
- package/dist/knowledge/skills/spec-feature-update/SKILL.md +47 -9
- package/dist/knowledge/skills/spec-resource-update/SKILL.md +3 -0
- package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +32 -5
- package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +30 -0
- package/dist/knowledge/skills/views-add-composite-view/SKILL.md +1 -0
- package/dist/knowledge/skills/views-add-custom-view/SKILL.md +13 -2
- package/dist/knowledge/skills/views-add-custom-view/references/framework-view-scope-and-full-custom-api.md +24 -0
- package/dist/knowledge/skills/views-app-level/SKILL.md +1 -0
- package/dist/knowledge/skills/views-app-level/references/framework-view-scope-and-full-custom-api.md +24 -0
- package/dist/knowledge/skills/views-chart-authoring/SKILL.md +1 -0
- package/dist/knowledge/skills/views-composite-authoring/SKILL.md +1 -0
- package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +64 -0
- package/dist/knowledge/skills/views-execution-authoring/SKILL.md +3 -0
- package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +3 -3
- package/dist/knowledge/skills/views-execution-authoring/references/framework-user-facing-error-message-api.md +50 -0
- package/dist/knowledge/skills/website-anonymous-session/SKILL.md +43 -7
- package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +21 -1
- package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +21 -0
- package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +41 -1
- package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +735 -211
- package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +54 -7
- package/dist/knowledge/skills/website-layout-overrides/SKILL.md +67 -1
- package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +11 -0
- package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +19 -5
- package/dist/knowledge/skills/website-page-authoring/SKILL.md +94 -7
- package/dist/knowledge/skills/website-page-authoring/references/homepage-content-and-art-direction.md +126 -0
- package/dist/knowledge/skills/website-section-contact/SKILL.md +96 -146
- package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-cta/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-faq/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-hero/SKILL.md +37 -26
- package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-pricing/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-social-proof/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +14 -1
- package/dist/knowledge/skills/worker-authoring/SKILL.md +164 -0
- package/dist/knowledge/skills/worker-authoring/examples/worker-route.example.md +98 -0
- package/dist/knowledge/skills/worker-authoring/references/framework-worker-init-contract.md +65 -0
- package/dist/knowledge/topic-index.json +5335 -1010
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/dist/tsconfig.tsbuildinfo +1 -1
- package/package.json +4 -4
- package/dist/knowledge/references/example.provider.contribution.backend-billing.md +0 -12
- package/dist/knowledge/skills/configure-billing/references/example-provider-contribution-and-backend-config.md +0 -48
- /package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/structured-artifact-action.json +0 -0
|
@@ -41,10 +41,19 @@ to many concurrent coding agents and interleaves the companion generation steps.
|
|
|
41
41
|
|
|
42
42
|
The build plan is a typed family (`BuildPlanTaskGraph`): dispatch selects ONE
|
|
43
43
|
READY task (all declared prerequisite task refs have landed) and hands the
|
|
44
|
-
coding host exactly that task's `objective`, `target`, `
|
|
45
|
-
`skillRefs`. The host derives the physical
|
|
46
|
-
fixed verification from the target kind;
|
|
47
|
-
this method prose — authors a path, a
|
|
44
|
+
coding host exactly that task's `objective`, `target`, `produces`,
|
|
45
|
+
`functionalTopic` and `skillRefs`. The host derives the physical
|
|
46
|
+
allowed/prohibited paths and the fixed verification from the target kind;
|
|
47
|
+
nothing in the task — and nothing in this method prose — authors a path, a
|
|
48
|
+
command, a prompt or a runtime control.
|
|
49
|
+
|
|
50
|
+
`target` and `produces` answer two different questions, and a task needs both.
|
|
51
|
+
`target` is the WRITE SCOPE — where this run may edit, and several tasks
|
|
52
|
+
legitimately share one. `produces` is what the run is ACCOUNTABLE for: the
|
|
53
|
+
artifacts whose presence in the application proves the task done. A task has
|
|
54
|
+
landed when every artifact it declares is present and committed, so a run that
|
|
55
|
+
satisfies the objective's prose without delivering those artifacts is not
|
|
56
|
+
finished — the plan will offer the task again.
|
|
48
57
|
|
|
49
58
|
## Import Origins
|
|
50
59
|
|
|
@@ -80,8 +89,149 @@ export enum BuildPlanTaskTargetKind {
|
|
|
80
89
|
RESOURCE_STAGE = 'RESOURCE_STAGE',
|
|
81
90
|
/** One relationship between two resources. */
|
|
82
91
|
RELATIONSHIP = 'RELATIONSHIP',
|
|
83
|
-
/** A companion-owned deterministic generation step (labels,
|
|
92
|
+
/** A companion-owned deterministic generation step (labels, email templates, logo or database migrations) interleaved by the build loop, never a coding-agent run. */
|
|
84
93
|
COMPANION_GENERATION_STEP = 'COMPANION_GENERATION_STEP',
|
|
94
|
+
/**
|
|
95
|
+
* Authoring one SHELL SURFACE's placement configuration from the accepted
|
|
96
|
+
* placement plan — the settings rail, the sidebar, the user menu or the
|
|
97
|
+
* command palette.
|
|
98
|
+
*
|
|
99
|
+
* Its own kind rather than a reuse of the neighbours, because none of them is
|
|
100
|
+
* true of it: it is not a MODULE or a RESOURCE_STAGE (it is application-wide
|
|
101
|
+
* and belongs to no resource), not a RELATIONSHIP, and emphatically not a
|
|
102
|
+
* COMPANION_GENERATION_STEP — that kind is documented as "never a coding-agent
|
|
103
|
+
* run" and writing `settings-hub.config.ts` is exactly a coding-agent run.
|
|
104
|
+
* Borrowing one would hand the host the wrong mutation scope and the wrong
|
|
105
|
+
* verification, which is what the closed vocabulary exists to prevent.
|
|
106
|
+
*/
|
|
107
|
+
SHELL_PLACEMENT = 'SHELL_PLACEMENT',
|
|
108
|
+
/*
|
|
109
|
+
* THE NON-RESOURCE SURFACES (#1490). Until 2026-09-22 the five kinds above were the whole
|
|
110
|
+
* vocabulary, and every one of them is about a resource or the shell placement of one. The
|
|
111
|
+
* decompose method meanwhile told the planner to emit tasks for views, navigation, the design
|
|
112
|
+
* system, custom components, PDF templates, workers, minions, providers, the website and the
|
|
113
|
+
* documentation — surfaces the framework's own composition scenarios and 85 of its 111 skills
|
|
114
|
+
* already build. A task for any of them had no kind to declare, so it either declared none
|
|
115
|
+
* (landing as RAN-not-PROVEN forever) or borrowed `MODULE` with a product the module scope could
|
|
116
|
+
* not prove. The members below are those surfaces, one per write scope the host can derive.
|
|
117
|
+
*/
|
|
118
|
+
/**
|
|
119
|
+
* The FRONTEND and SPECIFICATION layers of one module — its composite, custom and chart views,
|
|
120
|
+
* its custom components and their specifications.
|
|
121
|
+
*
|
|
122
|
+
* Narrower than `MODULE` on purpose: a view task never touches `shared-lib` or `backend-api`, so
|
|
123
|
+
* handing it the four-layer scope also hands it four typechecks and the FK sweep for a change
|
|
124
|
+
* that can only break the frontend and the specifications package.
|
|
125
|
+
*/
|
|
126
|
+
MODULE_FRONTEND = 'MODULE_FRONTEND',
|
|
127
|
+
/**
|
|
128
|
+
* The BACKEND layer of one module beside its shared-lib declarations — PDF templates and their
|
|
129
|
+
* bindings, backend addons (services, controllers, flows-actors), email definitions.
|
|
130
|
+
*
|
|
131
|
+
* Shared-lib is in scope because a PDF template is bound to a resource FIELD the config declares
|
|
132
|
+
* (`generatedSummaryPdf`), and a backend addon usually declares its contract there first.
|
|
133
|
+
*/
|
|
134
|
+
MODULE_BACKEND = 'MODULE_BACKEND',
|
|
135
|
+
/**
|
|
136
|
+
* ONE application-wide frontend configuration surface — navigation, the design system, the app
|
|
137
|
+
* shell's composition, the global views — named by {@link FrontendConfigSurface}.
|
|
138
|
+
*
|
|
139
|
+
* Distinct from {@link SHELL_PLACEMENT}, which authors the placement plan's decisions into the
|
|
140
|
+
* shell files: a placement puts a decided subject in a decided group, while this kind COMPOSES
|
|
141
|
+
* the surface itself (which sidebar sections exist, which transitions the primary zone uses,
|
|
142
|
+
* which palette the product carries). Same file for `APP_SHELL`, different question.
|
|
143
|
+
*/
|
|
144
|
+
APPLICATION_FRONTEND_CONFIG = 'APPLICATION_FRONTEND_CONFIG',
|
|
145
|
+
/** The marketing website workspace (`website/`), composed by the `add-website` scenario. Pages and sections are its products. */
|
|
146
|
+
WEBSITE = 'WEBSITE',
|
|
147
|
+
/**
|
|
148
|
+
* The technical-documentation workspace (`technical-doc/`) and the specification package's
|
|
149
|
+
* `technical-documentation/` declarations that feed it. Its generated tree is never written by a
|
|
150
|
+
* task: the companion publishes into it, and the coding policy prohibits it by prefix.
|
|
151
|
+
*/
|
|
152
|
+
TECHNICAL_DOCUMENTATION = 'TECHNICAL_DOCUMENTATION',
|
|
153
|
+
/** One worker package (`workers/<workerRef>/`), Node or Rust, plus its declaration in the SaaS config. */
|
|
154
|
+
WORKER = 'WORKER',
|
|
155
|
+
/** One cron minion package (`minions/<minionRef>/`) plus its declaration in the SaaS config. */
|
|
156
|
+
MINION = 'MINION',
|
|
157
|
+
/**
|
|
158
|
+
* Declaring one provider in the application — the SaaS config's provider scopes, the backend
|
|
159
|
+
* package dependency, the frontend provider module and its companion contribution.
|
|
160
|
+
*
|
|
161
|
+
* Application-wide by construction: a provider binding names no module, and the four files it
|
|
162
|
+
* may touch are the same for every provider.
|
|
163
|
+
*/
|
|
164
|
+
PROVIDER_BINDING = 'PROVIDER_BINDING',
|
|
165
|
+
}
|
|
166
|
+
|
|
167
|
+
/**
|
|
168
|
+
* WHICH application-wide frontend configuration surface a task composes — one file each, in
|
|
169
|
+
* `frontend/src/config/`, and the coding policy resolves the member to that file exactly as
|
|
170
|
+
* `SHELL_PLACEMENT` resolves a `PlacementSurface`.
|
|
171
|
+
*
|
|
172
|
+
* Its own vocabulary rather than a reuse of `PlacementSurface`: a placement surface is WHERE a
|
|
173
|
+
* subject sits in the shell (settings hub, sidebar, user menu, command palette), and three of
|
|
174
|
+
* those live in one file. A configuration surface is WHICH FILE a composition task authors, and
|
|
175
|
+
* navigation and the design system are not places anything is placed.
|
|
176
|
+
*/
|
|
177
|
+
export enum FrontendConfigSurface {
|
|
178
|
+
/** `frontend/src/config/navigation.config.ts` — zones, transitions, overlay appearance. */
|
|
179
|
+
NAVIGATION = 'NAVIGATION',
|
|
180
|
+
/** `frontend/src/config/design-system.config.ts` — palette, typography, shell appearance from the brand's visual tone. */
|
|
181
|
+
DESIGN_SYSTEM = 'DESIGN_SYSTEM',
|
|
182
|
+
/** `frontend/src/config/app-shell.config.ts` — top bar, sidebar sections, quick switcher: the shell's COMPOSITION, not a placement into it. */
|
|
183
|
+
APP_SHELL = 'APP_SHELL',
|
|
184
|
+
/** `frontend/src/config/global-views.config.ts` — the application-level launcher and view registrations. */
|
|
185
|
+
GLOBAL_VIEWS = 'GLOBAL_VIEWS',
|
|
186
|
+
}
|
|
187
|
+
|
|
188
|
+
/**
|
|
189
|
+
* The two shapes of guidance an application gives a person, and the file each is declared in.
|
|
190
|
+
*
|
|
191
|
+
* They are distinct because they are found differently: an onboarding DOCUMENT is embedded in a
|
|
192
|
+
* screen (`EmbedOnboarding`) and is there whenever that screen is, while a guidance FLOW is started
|
|
193
|
+
* by an event and shows once. Both are listed on the owning frontend module — `onboardingViews` and
|
|
194
|
+
* `guidanceFlows`. Each kind has a CONVENTIONAL definitions file, which the authoring skill teaches
|
|
195
|
+
* and a landing probe reads for the declared ref (alongside the module's `index.ts`, where a small
|
|
196
|
+
* module may declare inline). A convention for generated applications: a hand-authored application
|
|
197
|
+
* may keep its declarations elsewhere, and then simply is not probed by a build plan.
|
|
198
|
+
*/
|
|
199
|
+
export enum ApplicationGuidanceKind {
|
|
200
|
+
/** `frontend/src/modules/<m>/app-level-views/onboarding-views.definitions.ts` — an embedded onboarding document. */
|
|
201
|
+
ONBOARDING_DOCUMENT = 'ONBOARDING_DOCUMENT',
|
|
202
|
+
/** `frontend/src/modules/<m>/app-level-views/guidance-flows.definitions.ts` — a triggered guidance flow. */
|
|
203
|
+
GUIDANCE_FLOW = 'GUIDANCE_FLOW',
|
|
204
|
+
}
|
|
205
|
+
|
|
206
|
+
/**
|
|
207
|
+
* The two worker runtimes the framework composes (`add-worker-node`, `add-worker-rust`). The
|
|
208
|
+
* runtime decides the entry file a landing probe reads and whether a typecheck exists to run: a
|
|
209
|
+
* Node worker is verified by its package typecheck, a Rust worker has no TypeScript to check and
|
|
210
|
+
* the policy says so rather than inventing a command.
|
|
211
|
+
*
|
|
212
|
+
* Not the SaaS config's `WorkerRuntime`, which is a free-form `{ type, language }` pair an
|
|
213
|
+
* application authors for deployment; this is the closed set a creation run can COMPOSE.
|
|
214
|
+
*/
|
|
215
|
+
export enum BuildPlanWorkerRuntime {
|
|
216
|
+
NODE = 'NODE',
|
|
217
|
+
RUST = 'RUST',
|
|
218
|
+
}
|
|
219
|
+
|
|
220
|
+
/**
|
|
221
|
+
* WHERE a provider is bound — which runtime owner's scope its declaration lands in. Each member
|
|
222
|
+
* is a different file, so a probe and a write grant both derive from it.
|
|
223
|
+
*
|
|
224
|
+
* Named after the SaaS config's own scope keys (`providers.scopes.backend`, `.companion`,
|
|
225
|
+
* `.frontendServices.app`, `.frontendServices.website`), which the `add-provider` and
|
|
226
|
+
* `add-file-picker-provider` scenarios write. Minion and worker scopes are deliberately absent:
|
|
227
|
+
* a provider reaching a minion is declared on that minion's own `providers` block and belongs to
|
|
228
|
+
* the {@link BuildPlanTaskTargetKind.MINION} task that builds it.
|
|
229
|
+
*/
|
|
230
|
+
export enum ProviderBindingScope {
|
|
231
|
+
BACKEND = 'BACKEND',
|
|
232
|
+
COMPANION = 'COMPANION',
|
|
233
|
+
FRONTEND_APP = 'FRONTEND_APP',
|
|
234
|
+
WEBSITE = 'WEBSITE',
|
|
85
235
|
}
|
|
86
236
|
|
|
87
237
|
/** The per-resource build stages, in their fixed order. */
|
|
@@ -93,6 +243,34 @@ export enum BuildPlanResourceStage {
|
|
|
93
243
|
}
|
|
94
244
|
|
|
95
245
|
const SlugSchema = z.string().regex(/^[a-z0-9]+(?:-[a-z0-9]+)*$/);
|
|
246
|
+
|
|
247
|
+
/**
|
|
248
|
+
* The governed document a task produces, named as a COMPLIANCE-DOCUMENT CANDIDATE names it:
|
|
249
|
+
* `document:<namespace>.<id>`, e.g. `document:public.privacy-notice`.
|
|
250
|
+
*
|
|
251
|
+
* **This field was `SlugSchema`, and a slug cannot name a governed document — so until 2026-09-16 no
|
|
252
|
+
* build plan in any application could declare a document the engine catalog defines.** A slug forbids
|
|
253
|
+
* the colon and the dot, the catalog's definitions are `document-definition:public.privacy-notice`,
|
|
254
|
+
* and `selectAssuranceDocumentBlueprintForDocumentRef` joins the two namespaces by exact suffix — so
|
|
255
|
+
* every authored `documentRef` resolved to NO blueprint, and a blueprint is what says which sections,
|
|
256
|
+
* facts and claim guards the document owes. The two vocabularies were disjoint by construction.
|
|
257
|
+
*
|
|
258
|
+
* The cost is measured rather than theoretical. Wonder CRM's plan declares two such products
|
|
259
|
+
* (`gdpr-data-handling-governance`, `terminal-access-governance`), neither of which names anything;
|
|
260
|
+
* the first was dispatched, and its agent spent a full turn establishing — with a positive control —
|
|
261
|
+
* that the document does not exist and could only be invented, which the authoring skill forbids.
|
|
262
|
+
*
|
|
263
|
+
* The bare slug is STILL ACCEPTED, and that is deliberate rather than tidiness left undone: tightening
|
|
264
|
+
* this to the namespaced form alone would make every already-accepted plan carrying one fail to parse,
|
|
265
|
+
* and a build plan that cannot be READ stops the whole lane — the gate
|
|
266
|
+
* `application-creation-directive.md` forbids, for a task nobody can fix by re-running anything. A slug
|
|
267
|
+
* simply resolves to no blueprint, so the dispatcher skips that task with a message naming the ref,
|
|
268
|
+
* and the rest of the plan proceeds.
|
|
269
|
+
*/
|
|
270
|
+
const DocumentProductRefSchema = z.union([
|
|
271
|
+
z.string().regex(/^document:[a-z0-9]+(?:-[a-z0-9]+)*\.[a-z0-9]+(?:-[a-z0-9]+)*$/),
|
|
272
|
+
SlugSchema,
|
|
273
|
+
]);
|
|
96
274
|
/**
|
|
97
275
|
* A skill ref is the skill's FOLDER id in the app-knowledge catalog, which is
|
|
98
276
|
* also its `SKILL.md` frontmatter `name` — one id, kebab-case. The host refuses
|
|
@@ -102,6 +280,283 @@ const SlugSchema = z.string().regex(/^[a-z0-9]+(?:-[a-z0-9]+)*$/);
|
|
|
102
280
|
const SkillRefSchema = z.string().regex(/^[a-z0-9]+(?:-[a-z0-9]+)*$/);
|
|
103
281
|
const NonEmptyStringSchema = z.string().trim().min(1);
|
|
104
282
|
|
|
283
|
+
/**
|
|
284
|
+
* WHAT a build task PRODUCES — the artifact whose presence in the application
|
|
285
|
+
* proves the task is done.
|
|
286
|
+
*
|
|
287
|
+
* **This is not `target`, and the difference is the whole reason it exists.**
|
|
288
|
+
* `target` is a WRITE SCOPE: the host turns it into the path prefixes a run may
|
|
289
|
+
* mutate, and several tasks legitimately share one. `produces` is a PRODUCT
|
|
290
|
+
* IDENTITY: it says which artifact this task, and no other, is accountable for.
|
|
291
|
+
*
|
|
292
|
+
* Measured 2026-09-10 on Wonder CRM (issue #597): `build-task-pipeline-view`
|
|
293
|
+
* and `build-task-deal-follow-through-operation` carry BYTE-IDENTICAL targets
|
|
294
|
+
* (`{ kind: MODULE, moduleRef: 'deals' }`), and 7 of that plan's 42 tasks share
|
|
295
|
+
* 3 targets. Landing had been answered by narrowing the target to a module
|
|
296
|
+
* DIRECTORY — which `wildo compose` commits on day one, and which cannot tell
|
|
297
|
+
* two tasks apart even in principle. The loop reported 40 of 42 tasks landed
|
|
298
|
+
* while no coding task had ever run, so `dispatch-next` skipped every one of
|
|
299
|
+
* them and the phase-advance gate read a build that was all but complete.
|
|
300
|
+
*
|
|
301
|
+
* Like `target`, this stays SEMANTIC: a product names a resource, a field, a
|
|
302
|
+
* relationship or a view — never a path, and never a command. The host owns the
|
|
303
|
+
* translation from a product to the physical question it asks of the working
|
|
304
|
+
* tree, exactly as it owns the translation from a target kind to path prefixes.
|
|
305
|
+
* A model that could author the path could author its own mutation scope.
|
|
306
|
+
*/
|
|
307
|
+
export enum BuildPlanTaskProductKind {
|
|
308
|
+
/**
|
|
309
|
+
* Named fields on one resource's schema.
|
|
310
|
+
*
|
|
311
|
+
* The shape an ENRICHMENT task needs, and the reason a product cannot always
|
|
312
|
+
* be "a file": every resource file already exists, written by the scaffold
|
|
313
|
+
* with its self-described STARTER shape, so file presence answers nothing.
|
|
314
|
+
* The FIELDS are what the task adds.
|
|
315
|
+
*/
|
|
316
|
+
RESOURCE_SCHEMA_FIELDS = 'RESOURCE_SCHEMA_FIELDS',
|
|
317
|
+
/**
|
|
318
|
+
* One resource's declared operations — its registry presence, named by the verbs it gains.
|
|
319
|
+
*
|
|
320
|
+
* The VERBS, not the config file: `<r>.resources-config.ts` is written by the scaffold, so its
|
|
321
|
+
* existence is satisfied before any task runs. That is the exact shape of the defect this
|
|
322
|
+
* vocabulary replaces, and a kind that reproduced it would be worse than no kind at all.
|
|
323
|
+
*/
|
|
324
|
+
RESOURCE_REGISTRATION = 'RESOURCE_REGISTRATION',
|
|
325
|
+
/** One resource's frontend ui-behavior. */
|
|
326
|
+
RESOURCE_UI_BEHAVIOR = 'RESOURCE_UI_BEHAVIOR',
|
|
327
|
+
/**
|
|
328
|
+
* One resource's specification, named by the fields it documents.
|
|
329
|
+
*
|
|
330
|
+
* The FIELDS, for the same reason as {@link RESOURCE_REGISTRATION}: every resource is scaffolded
|
|
331
|
+
* with a `*.resource.specification.ts` documenting only the starter shape, so file existence
|
|
332
|
+
* proves nothing about the task that was meant to enrich it.
|
|
333
|
+
*/
|
|
334
|
+
RESOURCE_SPECIFICATION = 'RESOURCE_SPECIFICATION',
|
|
335
|
+
/** One relationship edge between two resources, named by the domain plan's `relationshipRef`. */
|
|
336
|
+
RESOURCE_RELATIONSHIP = 'RESOURCE_RELATIONSHIP',
|
|
337
|
+
/** One named custom operation on one resource. */
|
|
338
|
+
RESOURCE_OPERATION = 'RESOURCE_OPERATION',
|
|
339
|
+
/** One named application-level view. */
|
|
340
|
+
APPLICATION_VIEW = 'APPLICATION_VIEW',
|
|
341
|
+
/** One named governed application document (a compliance notice, a governance statement). */
|
|
342
|
+
APPLICATION_DOCUMENT = 'APPLICATION_DOCUMENT',
|
|
343
|
+
/** One application module, registered across the layer registries under one module identity. */
|
|
344
|
+
APPLICATION_MODULE = 'APPLICATION_MODULE',
|
|
345
|
+
/*
|
|
346
|
+
* THE NON-RESOURCE PRODUCTS (#1490). Each names an artifact of a surface the five target kinds
|
|
347
|
+
* above `MODULE_FRONTEND` could not express, and each is probed by the host from committed bytes —
|
|
348
|
+
* a declaration in the one file that registers it, never a directory a scenario already wrote.
|
|
349
|
+
*/
|
|
350
|
+
/**
|
|
351
|
+
* Named declarations in ONE application-wide frontend configuration file — a sidebar section
|
|
352
|
+
* ref the app shell gains, a zone the navigation config declares, a token the design system sets.
|
|
353
|
+
*
|
|
354
|
+
* The DECLARATIONS, never the file: every `frontend/src/config/*.config.ts` is written by
|
|
355
|
+
* `wildo init`, so its presence is true before any task runs. Same reasoning as
|
|
356
|
+
* {@link RESOURCE_SCHEMA_FIELDS}, one level up.
|
|
357
|
+
*/
|
|
358
|
+
APPLICATION_FRONTEND_CONFIG = 'APPLICATION_FRONTEND_CONFIG',
|
|
359
|
+
/**
|
|
360
|
+
* One composite view of one resource — the cross-resource surface a resource's ui-behavior
|
|
361
|
+
* declares under `compositeViews`. Distinct from {@link APPLICATION_VIEW}, which is
|
|
362
|
+
* application-level and owned by a module rather than a resource.
|
|
363
|
+
*/
|
|
364
|
+
RESOURCE_COMPOSITE_VIEW = 'RESOURCE_COMPOSITE_VIEW',
|
|
365
|
+
/** One custom operation or execution view of one resource, bound in its ui-behavior. */
|
|
366
|
+
RESOURCE_CUSTOM_VIEW = 'RESOURCE_CUSTOM_VIEW',
|
|
367
|
+
/** One chart view of one resource, declared under its ui-behavior's `chartViews`. */
|
|
368
|
+
RESOURCE_CHART_VIEW = 'RESOURCE_CHART_VIEW',
|
|
369
|
+
/** One custom frontend component, registered by `componentRef` in the module's or the engine's registrations. */
|
|
370
|
+
CUSTOM_COMPONENT = 'CUSTOM_COMPONENT',
|
|
371
|
+
/**
|
|
372
|
+
* One milestone a module declares — the moment the application recognises and celebrates.
|
|
373
|
+
*
|
|
374
|
+
* Named by its identifier, which is what the module's `milestones.ts` declares
|
|
375
|
+
* (`first-project-created` is spelled `FIRST_PROJECT_CREATED` there). The module FILE is not the
|
|
376
|
+
* product: a module may carry milestones before this task runs, and only the identifier says this
|
|
377
|
+
* one landed.
|
|
378
|
+
*/
|
|
379
|
+
APPLICATION_MILESTONE = 'APPLICATION_MILESTONE',
|
|
380
|
+
/** One onboarding document or guidance flow a module declares, named by its ref. */
|
|
381
|
+
APPLICATION_GUIDANCE = 'APPLICATION_GUIDANCE',
|
|
382
|
+
/** One PDF template bound to one resource's generated-file field. */
|
|
383
|
+
PDF_TEMPLATE = 'PDF_TEMPLATE',
|
|
384
|
+
/**
|
|
385
|
+
* One worker's JOBS — the named handlers its entry file declares.
|
|
386
|
+
*
|
|
387
|
+
* The jobs, not the package: `add-worker-node` writes the package, so its directory proves
|
|
388
|
+
* nothing. What a coding task adds is behaviour, and behaviour is a symbol in the entry file.
|
|
389
|
+
*/
|
|
390
|
+
APPLICATION_WORKER = 'APPLICATION_WORKER',
|
|
391
|
+
/** One minion's BEHAVIOURS — the named tick handlers its entry file declares. Same reasoning as the worker. */
|
|
392
|
+
APPLICATION_MINION = 'APPLICATION_MINION',
|
|
393
|
+
/** One provider declared in one runtime owner's scope. */
|
|
394
|
+
PROVIDER_BINDING = 'PROVIDER_BINDING',
|
|
395
|
+
/** One website page, registered in the website root config by its manifest. */
|
|
396
|
+
WEBSITE_PAGE = 'WEBSITE_PAGE',
|
|
397
|
+
/** One section of one website page, declared in that page's sections file. */
|
|
398
|
+
WEBSITE_SECTION = 'WEBSITE_SECTION',
|
|
399
|
+
/**
|
|
400
|
+
* One authored documentation chapter — a consumer guide the specifications package declares
|
|
401
|
+
* for the documentation portal to publish (#874's publication input).
|
|
402
|
+
*/
|
|
403
|
+
DOCUMENTATION_CHAPTER = 'DOCUMENTATION_CHAPTER',
|
|
404
|
+
}
|
|
405
|
+
|
|
406
|
+
/**
|
|
407
|
+
* One artifact a task is accountable for. Closed by construction: a product the
|
|
408
|
+
* host cannot ask a question about is a product that can never be shown to have
|
|
409
|
+
* landed, so the vocabulary only grows alongside the resolver that answers it.
|
|
410
|
+
*/
|
|
411
|
+
export const BuildPlanTaskProductSchema = z.discriminatedUnion('kind', [
|
|
412
|
+
z.strictObject({
|
|
413
|
+
kind: z.literal(BuildPlanTaskProductKind.RESOURCE_SCHEMA_FIELDS).systemEnum('BuildPlanTaskProductKind'),
|
|
414
|
+
resourceRef: SlugSchema,
|
|
415
|
+
/**
|
|
416
|
+
* At least one field, because a task that enriches a schema with nothing is
|
|
417
|
+
* the vacuity this whole field exists to stop: it would land the moment the
|
|
418
|
+
* scaffold existed, which is the defect being fixed.
|
|
419
|
+
*/
|
|
420
|
+
fieldRefs: z.array(NonEmptyStringSchema).min(1),
|
|
421
|
+
}),
|
|
422
|
+
z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_REGISTRATION).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, operationRefs: z.array(NonEmptyStringSchema).min(1) }),
|
|
423
|
+
z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_UI_BEHAVIOR).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema }),
|
|
424
|
+
z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_SPECIFICATION).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, fieldRefs: z.array(NonEmptyStringSchema).min(1) }),
|
|
425
|
+
z.strictObject({
|
|
426
|
+
kind: z.literal(BuildPlanTaskProductKind.RESOURCE_RELATIONSHIP).systemEnum('BuildPlanTaskProductKind'),
|
|
427
|
+
relationshipRef: SlugSchema,
|
|
428
|
+
/*
|
|
429
|
+
* The two resources the edge relates, NAMED rather than parsed out of the ref.
|
|
430
|
+
*
|
|
431
|
+
* A ref is `<source>-<target>` by convention and that convention is not invertible:
|
|
432
|
+
* `next-step-deal` splits as (`next`, `step-deal`) or (`next-step`, `deal`) and only the domain
|
|
433
|
+
* plan knows which. The domain plan already carries both, so the plan passes them on instead of
|
|
434
|
+
* making the host guess — a host that guesses wrong probes for a resource that does not exist
|
|
435
|
+
* and reports the task permanently unlanded.
|
|
436
|
+
*/
|
|
437
|
+
sourceResourceRef: SlugSchema,
|
|
438
|
+
targetResourceRef: SlugSchema,
|
|
439
|
+
}),
|
|
440
|
+
z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_OPERATION).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, operationRef: SlugSchema }),
|
|
441
|
+
z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_VIEW).systemEnum('BuildPlanTaskProductKind'), viewRef: SlugSchema }),
|
|
442
|
+
z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_DOCUMENT).systemEnum('BuildPlanTaskProductKind'), documentRef: DocumentProductRefSchema }),
|
|
443
|
+
z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_MODULE).systemEnum('BuildPlanTaskProductKind'), moduleRef: SlugSchema }),
|
|
444
|
+
z.strictObject({
|
|
445
|
+
kind: z.literal(BuildPlanTaskProductKind.APPLICATION_FRONTEND_CONFIG).systemEnum('BuildPlanTaskProductKind'),
|
|
446
|
+
configSurface: z.enum(FrontendConfigSurface).systemEnum('FrontendConfigSurface'),
|
|
447
|
+
/** At least one, for the same vacuity reason as a schema's `fieldRefs`: the file exists on day one. */
|
|
448
|
+
declarationRefs: z.array(NonEmptyStringSchema).min(1),
|
|
449
|
+
}),
|
|
450
|
+
z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_COMPOSITE_VIEW).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, viewRef: SlugSchema }),
|
|
451
|
+
z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_CUSTOM_VIEW).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, viewRef: SlugSchema }),
|
|
452
|
+
z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_CHART_VIEW).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, chartRef: SlugSchema }),
|
|
453
|
+
z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.CUSTOM_COMPONENT).systemEnum('BuildPlanTaskProductKind'), componentRef: SlugSchema }),
|
|
454
|
+
z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_MILESTONE).systemEnum('BuildPlanTaskProductKind'), milestoneRef: SlugSchema }),
|
|
455
|
+
z.strictObject({
|
|
456
|
+
kind: z.literal(BuildPlanTaskProductKind.APPLICATION_GUIDANCE).systemEnum('BuildPlanTaskProductKind'),
|
|
457
|
+
/** Which definitions file carries it — a document and a flow live in different ones. */
|
|
458
|
+
guidanceKind: z.enum(ApplicationGuidanceKind).systemEnum('ApplicationGuidanceKind'),
|
|
459
|
+
guidanceRef: SlugSchema,
|
|
460
|
+
}),
|
|
461
|
+
z.strictObject({
|
|
462
|
+
kind: z.literal(BuildPlanTaskProductKind.PDF_TEMPLATE).systemEnum('BuildPlanTaskProductKind'),
|
|
463
|
+
resourceRef: SlugSchema,
|
|
464
|
+
/** The generated-file FIELD the template is bound to (`generatedSummaryPdf`) — a symbol, so any spelling. */
|
|
465
|
+
templateRef: NonEmptyStringSchema,
|
|
466
|
+
}),
|
|
467
|
+
z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_WORKER).systemEnum('BuildPlanTaskProductKind'), workerRef: SlugSchema, jobRefs: z.array(NonEmptyStringSchema).min(1) }),
|
|
468
|
+
z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_MINION).systemEnum('BuildPlanTaskProductKind'), minionRef: SlugSchema, behaviorRefs: z.array(NonEmptyStringSchema).min(1) }),
|
|
469
|
+
z.strictObject({
|
|
470
|
+
kind: z.literal(BuildPlanTaskProductKind.PROVIDER_BINDING).systemEnum('BuildPlanTaskProductKind'),
|
|
471
|
+
providerRef: SlugSchema,
|
|
472
|
+
scope: z.enum(ProviderBindingScope).systemEnum('ProviderBindingScope'),
|
|
473
|
+
}),
|
|
474
|
+
z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.WEBSITE_PAGE).systemEnum('BuildPlanTaskProductKind'), pageRef: SlugSchema }),
|
|
475
|
+
z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.WEBSITE_SECTION).systemEnum('BuildPlanTaskProductKind'), pageRef: SlugSchema, sectionRef: SlugSchema }),
|
|
476
|
+
z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.DOCUMENTATION_CHAPTER).systemEnum('BuildPlanTaskProductKind'), chapterRef: SlugSchema }),
|
|
477
|
+
]);
|
|
478
|
+
export type BuildPlanTaskProduct = z.infer<typeof BuildPlanTaskProductSchema>;
|
|
479
|
+
|
|
480
|
+
/**
|
|
481
|
+
* Every artifact identity a product claims — one string per artifact, not one
|
|
482
|
+
* per product, because a product may claim several.
|
|
483
|
+
*
|
|
484
|
+
* `RESOURCE_SCHEMA_FIELDS` is why this returns a list. Two tasks may both enrich
|
|
485
|
+
* one resource's schema (a domain shape and a billing concern, say), and that is
|
|
486
|
+
* legitimate; what must never overlap is the FIELDS. Comparing whole products
|
|
487
|
+
* would refuse the legitimate pair, and comparing only the resource would let two
|
|
488
|
+
* tasks claim one field and make landing ambiguous again.
|
|
489
|
+
*
|
|
490
|
+
* Derived from the product's own members rather than stored, and total over the
|
|
491
|
+
* vocabulary, so a kind added tomorrow must state its identity here or fail to
|
|
492
|
+
* compile — it cannot be silently treated as equal to its siblings.
|
|
493
|
+
*/
|
|
494
|
+
export function buildPlanTaskProductIdentities(product: BuildPlanTaskProduct): readonly string[] {
|
|
495
|
+
switch (product.kind) {
|
|
496
|
+
case BuildPlanTaskProductKind.RESOURCE_SCHEMA_FIELDS:
|
|
497
|
+
return product.fieldRefs.map((fieldRef) => `${product.kind}:${product.resourceRef}:${fieldRef}`);
|
|
498
|
+
case BuildPlanTaskProductKind.RESOURCE_REGISTRATION:
|
|
499
|
+
return product.operationRefs.map((operationRef) => `${product.kind}:${product.resourceRef}:${operationRef}`);
|
|
500
|
+
case BuildPlanTaskProductKind.RESOURCE_SPECIFICATION:
|
|
501
|
+
return product.fieldRefs.map((fieldRef) => `${product.kind}:${product.resourceRef}:${fieldRef}`);
|
|
502
|
+
case BuildPlanTaskProductKind.RESOURCE_UI_BEHAVIOR:
|
|
503
|
+
return [`${product.kind}:${product.resourceRef}`];
|
|
504
|
+
case BuildPlanTaskProductKind.RESOURCE_RELATIONSHIP:
|
|
505
|
+
return [`${product.kind}:${product.relationshipRef}`];
|
|
506
|
+
case BuildPlanTaskProductKind.RESOURCE_OPERATION:
|
|
507
|
+
return [`${product.kind}:${product.resourceRef}:${product.operationRef}`];
|
|
508
|
+
case BuildPlanTaskProductKind.APPLICATION_VIEW:
|
|
509
|
+
return [`${product.kind}:${product.viewRef}`];
|
|
510
|
+
case BuildPlanTaskProductKind.APPLICATION_DOCUMENT:
|
|
511
|
+
/*
|
|
512
|
+
* The ref AS AUTHORED, so a slug and a namespaced ref are different artifact identities even
|
|
513
|
+
* where they mean the same document — the duplicate-artifact refusal cannot see two tasks
|
|
514
|
+
* claiming one document if they spell it differently. Not normalisable: a slug carries no
|
|
515
|
+
* namespace, so nothing can recover `public.` from `privacy-notice`. It costs nothing today
|
|
516
|
+
* because a slug names no catalogued document at all, and the dispatcher skips such a task.
|
|
517
|
+
*/
|
|
518
|
+
return [`${product.kind}:${product.documentRef}`];
|
|
519
|
+
case BuildPlanTaskProductKind.APPLICATION_MODULE:
|
|
520
|
+
return [`${product.kind}:${product.moduleRef}`];
|
|
521
|
+
// One identity per DECLARATION, like schema fields: two tasks may compose one config file as
|
|
522
|
+
// long as they declare different things in it.
|
|
523
|
+
case BuildPlanTaskProductKind.APPLICATION_FRONTEND_CONFIG:
|
|
524
|
+
return product.declarationRefs.map((declarationRef) => `${product.kind}:${product.configSurface}:${declarationRef}`);
|
|
525
|
+
case BuildPlanTaskProductKind.RESOURCE_COMPOSITE_VIEW:
|
|
526
|
+
case BuildPlanTaskProductKind.RESOURCE_CUSTOM_VIEW:
|
|
527
|
+
return [`${product.kind}:${product.resourceRef}:${product.viewRef}`];
|
|
528
|
+
case BuildPlanTaskProductKind.RESOURCE_CHART_VIEW:
|
|
529
|
+
return [`${product.kind}:${product.resourceRef}:${product.chartRef}`];
|
|
530
|
+
case BuildPlanTaskProductKind.CUSTOM_COMPONENT:
|
|
531
|
+
return [`${product.kind}:${product.componentRef}`];
|
|
532
|
+
case BuildPlanTaskProductKind.APPLICATION_MILESTONE:
|
|
533
|
+
return [`${product.kind}:${product.milestoneRef}`];
|
|
534
|
+
// The ref alone: a document and a flow sharing one ref is still one guidance identity, and the
|
|
535
|
+
// runtime keys a person's saved state by it — two artifacts claiming it would collide there too.
|
|
536
|
+
case BuildPlanTaskProductKind.APPLICATION_GUIDANCE:
|
|
537
|
+
return [`${product.kind}:${product.guidanceRef}`];
|
|
538
|
+
case BuildPlanTaskProductKind.PDF_TEMPLATE:
|
|
539
|
+
return [`${product.kind}:${product.resourceRef}:${product.templateRef}`];
|
|
540
|
+
case BuildPlanTaskProductKind.APPLICATION_WORKER:
|
|
541
|
+
return product.jobRefs.map((jobRef) => `${product.kind}:${product.workerRef}:${jobRef}`);
|
|
542
|
+
case BuildPlanTaskProductKind.APPLICATION_MINION:
|
|
543
|
+
return product.behaviorRefs.map((behaviorRef) => `${product.kind}:${product.minionRef}:${behaviorRef}`);
|
|
544
|
+
// The SCOPE is part of the identity: one provider bound on the backend and on the website is two artifacts.
|
|
545
|
+
case BuildPlanTaskProductKind.PROVIDER_BINDING:
|
|
546
|
+
return [`${product.kind}:${product.scope}:${product.providerRef}`];
|
|
547
|
+
case BuildPlanTaskProductKind.WEBSITE_PAGE:
|
|
548
|
+
return [`${product.kind}:${product.pageRef}`];
|
|
549
|
+
case BuildPlanTaskProductKind.WEBSITE_SECTION:
|
|
550
|
+
return [`${product.kind}:${product.pageRef}:${product.sectionRef}`];
|
|
551
|
+
case BuildPlanTaskProductKind.DOCUMENTATION_CHAPTER:
|
|
552
|
+
return [`${product.kind}:${product.chapterRef}`];
|
|
553
|
+
default: {
|
|
554
|
+
const unhandled: never = product;
|
|
555
|
+
throw new Error(`Unhandled build-plan task product ${JSON.stringify(unhandled)}.`);
|
|
556
|
+
}
|
|
557
|
+
}
|
|
558
|
+
}
|
|
559
|
+
|
|
105
560
|
export const BuildPlanTaskTargetSchema = z.discriminatedUnion('kind', [
|
|
106
561
|
z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.MODULE), moduleRef: SlugSchema }),
|
|
107
562
|
z.strictObject({
|
|
@@ -117,9 +572,47 @@ export const BuildPlanTaskTargetSchema = z.discriminatedUnion('kind', [
|
|
|
117
572
|
}),
|
|
118
573
|
z.strictObject({
|
|
119
574
|
kind: z.literal(BuildPlanTaskTargetKind.COMPANION_GENERATION_STEP),
|
|
120
|
-
/** The companion generation step this task runs (e.g. labels,
|
|
575
|
+
/** The companion generation step this task runs (e.g. i18n-labels, email-templates); resolved by the companion, never by a coding agent. */
|
|
121
576
|
generationStepRef: SlugSchema,
|
|
122
577
|
}),
|
|
578
|
+
z.strictObject({
|
|
579
|
+
kind: z.literal(BuildPlanTaskTargetKind.SHELL_PLACEMENT),
|
|
580
|
+
/**
|
|
581
|
+
* Which shell surface this task authors — the placement family's OWN
|
|
582
|
+
* `PlacementSurface`, deliberately not a build-plan copy of it.
|
|
583
|
+
*
|
|
584
|
+
* A copy was written first and was a defect, caught by probing the landing
|
|
585
|
+
* renderer rather than by any test: `PlacementAddress` discriminates on
|
|
586
|
+
* `surface` with `z.literal(...)` per option, so only the VALUES survive into
|
|
587
|
+
* the schema, and the renderer resolves a discriminator by matching that value
|
|
588
|
+
* SET against the exported enums. Two enums with identical values made the
|
|
589
|
+
* match ambiguous, the renderer correctly refused to guess an owner, and the
|
|
590
|
+
* address discriminator became unnameable — a landed placement plan would have
|
|
591
|
+
* emitted `surface: "SETTINGS_HUB"` as a bare string instead of
|
|
592
|
+
* `PlacementSurface.SETTINGS_HUB`. One concept, one named source.
|
|
593
|
+
*/
|
|
594
|
+
surface: z.enum(PlacementSurface).systemEnum('PlacementSurface'),
|
|
595
|
+
}),
|
|
596
|
+
z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.MODULE_FRONTEND), moduleRef: SlugSchema }),
|
|
597
|
+
z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.MODULE_BACKEND), moduleRef: SlugSchema }),
|
|
598
|
+
z.strictObject({
|
|
599
|
+
kind: z.literal(BuildPlanTaskTargetKind.APPLICATION_FRONTEND_CONFIG),
|
|
600
|
+
configSurface: z.enum(FrontendConfigSurface).systemEnum('FrontendConfigSurface'),
|
|
601
|
+
}),
|
|
602
|
+
z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.WEBSITE) }),
|
|
603
|
+
z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.TECHNICAL_DOCUMENTATION) }),
|
|
604
|
+
z.strictObject({
|
|
605
|
+
kind: z.literal(BuildPlanTaskTargetKind.WORKER),
|
|
606
|
+
/** The worker's directory under `workers/` and its key in the SaaS config, in slug form. */
|
|
607
|
+
workerRef: SlugSchema,
|
|
608
|
+
runtime: z.enum(BuildPlanWorkerRuntime).systemEnum('BuildPlanWorkerRuntime'),
|
|
609
|
+
}),
|
|
610
|
+
z.strictObject({
|
|
611
|
+
kind: z.literal(BuildPlanTaskTargetKind.MINION),
|
|
612
|
+
/** The minion's directory under `minions/` and its key in the SaaS config, in slug form. */
|
|
613
|
+
minionRef: SlugSchema,
|
|
614
|
+
}),
|
|
615
|
+
z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.PROVIDER_BINDING), providerRef: SlugSchema }),
|
|
123
616
|
]);
|
|
124
617
|
export type BuildPlanTaskTarget = z.infer<typeof BuildPlanTaskTargetSchema>;
|
|
125
618
|
|
|
@@ -137,16 +630,69 @@ export type BuildPlanTaskTarget = z.infer<typeof BuildPlanTaskTargetSchema>;
|
|
|
137
630
|
export const BuildPlanTaskSchema = z.strictObject({
|
|
138
631
|
/** `build-task-<slug>`, stamped by the trusted runtime. */
|
|
139
632
|
taskRef: z.string().regex(new RegExp(`^${BUILD_PLAN_TASK_REF_PREFIX}[a-z0-9]+(?:-[a-z0-9]+)*$`)),
|
|
140
|
-
/**
|
|
141
|
-
|
|
633
|
+
/**
|
|
634
|
+
* One sentence of intent: what this task delivers.
|
|
635
|
+
*
|
|
636
|
+
* Its OWN instance, not the file's shared leaf, which `templateRef` and the product ref lists also
|
|
637
|
+
* hold. A display decorator mutates the instance it is applied to, and the workbench gives those
|
|
638
|
+
* refs a receding identifier look, which the objective sentence then took too.
|
|
639
|
+
*/
|
|
640
|
+
objective: z.string().trim().min(1),
|
|
142
641
|
target: BuildPlanTaskTargetSchema,
|
|
143
|
-
/**
|
|
144
|
-
|
|
642
|
+
/**
|
|
643
|
+
* The artifacts this task is accountable for — what proves it done.
|
|
644
|
+
*
|
|
645
|
+
* Coding tasks should declare at least one product that composition did not already
|
|
646
|
+
* write. A target is a shared mutation scope; its scaffolded file is not evidence
|
|
647
|
+
* that this task's intended work exists. Products identify the output to probe.
|
|
648
|
+
*
|
|
649
|
+
* Empty declarations remain representable and produce the advisory
|
|
650
|
+
* `TASK_DECLARES_NO_PRODUCT`. The host may advance after a COMPLETED durable run,
|
|
651
|
+
* while naming the task in `unverifiableLandedTaskRefs`: it ran, but its output
|
|
652
|
+
* cannot be proven from a product declaration. An unexecuted task is not landed.
|
|
653
|
+
* This distinction avoids repeatedly dispatching the same unprovable task without
|
|
654
|
+
* presenting execution history as evidence that the intended product is correct.
|
|
655
|
+
*
|
|
656
|
+
* The ONE hard exception is a `COMPANION_GENERATION_STEP`, which must declare NONE.
|
|
657
|
+
* That kind already carries its own typed landed condition, owned by the
|
|
658
|
+
* generation-step service — a set computed asynchronously (planner units x
|
|
659
|
+
* enabled locales), and for the migration step a STATE rather than files. A
|
|
660
|
+
* product declared beside it would be read by nothing, which is the inert
|
|
661
|
+
* declaration this field exists to avoid. Enforced on the graph below, in both
|
|
662
|
+
* directions.
|
|
663
|
+
*/
|
|
664
|
+
produces: z.array(BuildPlanTaskProductSchema).default([]),
|
|
665
|
+
/**
|
|
666
|
+
* Exactly ONE functional topic this task belongs to.
|
|
667
|
+
*
|
|
668
|
+
* **It does NOT drive ordering** — this said "drives cross-app ordering" until 2026-08-30 and
|
|
669
|
+
* nothing ever ordered by it. Sequencing is `prerequisiteTaskRefs`, resolved by the host, and it
|
|
670
|
+
* is the only thing that decides what may run next.
|
|
671
|
+
*
|
|
672
|
+
* What it DOES: the dispatch host stamps it into the coding-agent's task payload beside
|
|
673
|
+
* `skillRefs`, so the agent is told which phase of building the application this task belongs to.
|
|
674
|
+
* That is context an LLM reads, not a value the runtime branches on — the distinction matters,
|
|
675
|
+
* because a reader who believes it orders will look here for a scheduling bug that lives in the
|
|
676
|
+
* prerequisite graph. See issue #124.
|
|
677
|
+
*/
|
|
678
|
+
functionalTopic: z.enum(MetaWorkflow_FunctionalTopic).systemEnum('MetaWorkflow_FunctionalTopic'),
|
|
145
679
|
/** Installed app-knowledge skill folders that carry the technical HOW; resolved via the skills router at dispatch. */
|
|
146
680
|
skillRefs: z.array(SkillRefSchema).min(1),
|
|
147
681
|
/** Task refs that must have landed first; resolved by the host, not solved by the model. */
|
|
148
682
|
prerequisiteTaskRefs: z.array(z.string()).default([]),
|
|
149
|
-
/**
|
|
683
|
+
/**
|
|
684
|
+
* What this task is accountable to — traceability only, NEVER scope authority.
|
|
685
|
+
*
|
|
686
|
+
* The vocabulary is the five aspects `BUILD_PLAN_FAMILY_ASPECTS` declares as targets: functional
|
|
687
|
+
* and non-functional requirements, roadmap phases, and the vision's success criteria and
|
|
688
|
+
* constraints. It reads "Requirement / roadmap refs" until 2026-09-11, and the last two were added
|
|
689
|
+
* because the producer had been writing them all along (#629) — the generation contract asks for a
|
|
690
|
+
* plain string list, so nothing here has ever refused a key.
|
|
691
|
+
*
|
|
692
|
+
* A key outside those five is not rejected and must not be: this is traceability a human or a
|
|
693
|
+
* model wrote down, and dropping it loses the intent. The workbench renders such a key as visibly
|
|
694
|
+
* unresolved instead, which is what makes a producer drift legible rather than silent.
|
|
695
|
+
*/
|
|
150
696
|
servesRefs: z.array(NonEmptyStringSchema).default([]),
|
|
151
697
|
});
|
|
152
698
|
export type BuildPlanTask = z.infer<typeof BuildPlanTaskSchema>;
|
|
@@ -186,6 +732,43 @@ export const BuildPlanTaskGraphSchema = z.object({
|
|
|
186
732
|
}
|
|
187
733
|
refs.add(task.taskRef);
|
|
188
734
|
});
|
|
735
|
+
/*
|
|
736
|
+
* No two tasks claim the same artifact.
|
|
737
|
+
*
|
|
738
|
+
* This is what makes landing DECIDABLE, not a tidiness rule. If two tasks name
|
|
739
|
+
* one product, the host cannot tell which of them a present artifact proves —
|
|
740
|
+
* exactly the ambiguity that shared `target`s created, arriving through the
|
|
741
|
+
* field that replaced them. Enforced here rather than left to the validator
|
|
742
|
+
* because a graph that cannot answer "has this task landed?" is not a graph
|
|
743
|
+
* the loop may run at all.
|
|
744
|
+
*/
|
|
745
|
+
graph.tasks.forEach((task, index) => {
|
|
746
|
+
const isGenerationStep = task.target.kind === BuildPlanTaskTargetKind.COMPANION_GENERATION_STEP;
|
|
747
|
+
if (isGenerationStep && task.produces.length > 0) {
|
|
748
|
+
context.addIssue({
|
|
749
|
+
code: 'custom',
|
|
750
|
+
message: `build task "${task.taskRef}" is a companion generation step and must declare no products; its landing is the generation step's own condition`,
|
|
751
|
+
path: ['tasks', index, 'produces'],
|
|
752
|
+
});
|
|
753
|
+
}
|
|
754
|
+
});
|
|
755
|
+
const productOwners = new Map<string, string>();
|
|
756
|
+
graph.tasks.forEach((task, index) => {
|
|
757
|
+
task.produces.forEach((product, productIndex) => {
|
|
758
|
+
buildPlanTaskProductIdentities(product).forEach((identity) => {
|
|
759
|
+
const owner = productOwners.get(identity);
|
|
760
|
+
if (owner !== undefined) {
|
|
761
|
+
context.addIssue({
|
|
762
|
+
code: 'custom',
|
|
763
|
+
message: `build task "${task.taskRef}" claims the same artifact as "${owner}" (${identity}); an artifact is produced by exactly one task`,
|
|
764
|
+
path: ['tasks', index, 'produces', productIndex],
|
|
765
|
+
});
|
|
766
|
+
return;
|
|
767
|
+
}
|
|
768
|
+
productOwners.set(identity, task.taskRef);
|
|
769
|
+
});
|
|
770
|
+
});
|
|
771
|
+
});
|
|
189
772
|
graph.tasks.forEach((task, index) => {
|
|
190
773
|
task.prerequisiteTaskRefs.forEach((prerequisite, prerequisiteIndex) => {
|
|
191
774
|
if (prerequisite === task.taskRef) {
|
|
@@ -216,7 +799,7 @@ Most of the D4 dispatch contract is **runner mechanism**, not prose you re-imple
|
|
|
216
799
|
the runner composes the context pack, opens a coding session with the agent over the
|
|
217
800
|
Agent Client Protocol and sends one prompt turn, answers the agent's permission
|
|
218
801
|
requests within the declared ceiling, captures the change-set, runs the verify hook,
|
|
219
|
-
holds the single-flight lock
|
|
802
|
+
holds the single-flight lock and applies its configured execution limits. Your method here is the **declarative recipe** the runner interprets —
|
|
220
803
|
*which* task to dispatch next, *when* it is authorized, and *how* its outcome is
|
|
221
804
|
judged. Do not hand-compose a dispatch prompt or drive git yourself; let the runner
|
|
222
805
|
own composition and change-set capture.
|
|
@@ -248,12 +831,58 @@ Before dispatching anything:
|
|
|
248
831
|
depends on greenfield bring-up tooling (deferred). The dispatch contract is real and
|
|
249
832
|
runs against an **existing** app skeleton — the dogfood app already has one.
|
|
250
833
|
|
|
251
|
-
//
|
|
252
|
-
//
|
|
834
|
+
// Operator status: `wildo context journey` (eligibility board + runs in flight). Which tasks already
|
|
835
|
+
// landed is read from GIT by the runner itself — a task is landed when every file it produces is
|
|
836
|
+
// committed clean.
|
|
253
837
|
|
|
254
838
|
You **read** `build-plan`; you **write** no journey artifact
|
|
255
839
|
— the runner records the change-set + task status on the dispatched task's row.
|
|
256
840
|
|
|
841
|
+
## Precondition — the application must establish the agent's role, or dispatch stalls
|
|
842
|
+
|
|
843
|
+
Check this before the first dispatch of an application's life. It costs one look and it is the
|
|
844
|
+
difference between a working lane and one that burns model time producing nothing.
|
|
845
|
+
|
|
846
|
+
**The application needs a root `CLAUDE.md` stating that a task dispatched by its dev companion is
|
|
847
|
+
legitimate work.** Without it the agent is right to refuse, and refusing is what it does.
|
|
848
|
+
|
|
849
|
+
The reason is structural rather than a matter of tone. A dispatched task reaches the agent as an
|
|
850
|
+
ordinary prompt — a user turn carrying an objective, a mutation scope and skill refs. Nothing in
|
|
851
|
+
that turn proves where it came from. So the agent is being handed conversational content that
|
|
852
|
+
tells it to write files into a repository, which is indistinguishable from the thing every
|
|
853
|
+
careful agent is supposed to decline, and the more trustworthy the agent the more reliably it
|
|
854
|
+
declines. Measured on a real application with no such file: two dispatched runs stalled, one
|
|
855
|
+
answering *"content that arrives as conversational input doesn't get to reassign what I am"*.
|
|
856
|
+
|
|
857
|
+
The failure does not look like a missing file. It looks like an agent that deliberates well,
|
|
858
|
+
identifies exactly which files it would author, explains its reasoning, asks a human to confirm,
|
|
859
|
+
and ends its turn — `end_turn`, no error, no denial, an empty change set, and a bill for the
|
|
860
|
+
tokens. Read as "the agent chose not to work", which invites prompt-tuning that cannot fix it.
|
|
861
|
+
|
|
862
|
+
`wildo init` scaffolds this file. An application created before that, or one whose `CLAUDE.md`
|
|
863
|
+
covers only its own conventions, needs the section added. What it must establish:
|
|
864
|
+
|
|
865
|
+
- the task is **selected by the host** from the accepted build plan, not composed by a caller;
|
|
866
|
+
- its **file edits** are **confined before they arrive** — the host answers every permission request
|
|
867
|
+
against the declared mutation scope and refuses paths outside it;
|
|
868
|
+
- its **shell commands are NOT**, and the section must say so. A command declares no `locations`, so
|
|
869
|
+
the scope predicate never runs for one; telling an agent it "need not police itself" is true of its
|
|
870
|
+
edits and false of its commands, and that is the half a stray write comes through. Name the
|
|
871
|
+
compensations with it: the post-run change set and the companion's warning DETECT such a write,
|
|
872
|
+
they do not prevent it;
|
|
873
|
+
- it is **reversible** — every write is an uncommitted working edit until something commits it. Do
|
|
874
|
+
not state WHO commits as a property of the lane: that is the host's autonomy posture, it changes,
|
|
875
|
+
and an agent that reads "a human commits" from a scaffold written under a different posture is
|
|
876
|
+
working from a stale contract.
|
|
877
|
+
|
|
878
|
+
Two smaller things belong in the same section, because both were observed costing a run:
|
|
879
|
+
|
|
880
|
+
- **Say what `allowedPathPrefixes` are relative to.** The agent receives bare prefixes such as
|
|
881
|
+
`shared-lib/src/modules/<module>/` with no root, and cannot verify its own confinement against
|
|
882
|
+
them. One sentence naming the application root removes the ambiguity.
|
|
883
|
+
- **Do not name a task so it reads as a fixture.** An agent that concludes it is looking at a
|
|
884
|
+
smoke test will say so and stop. Name the task after the product change it makes.
|
|
885
|
+
|
|
257
886
|
## Step 1 — Select the next dispatchable task (single-flight)
|
|
258
887
|
|
|
259
888
|
Walk the build plan in its authored order and pick the **first** task that is not
|
|
@@ -284,29 +913,21 @@ empty build plan is the same: nothing to dispatch, stop.
|
|
|
284
913
|
those steps *concurrently* with coding runs at scale is the scale playbook's job —
|
|
285
914
|
here you simply run the ready one in its turn.
|
|
286
915
|
|
|
287
|
-
## Step 2 —
|
|
288
|
-
|
|
289
|
-
A coding
|
|
290
|
-
|
|
291
|
-
|
|
292
|
-
|
|
293
|
-
|
|
294
|
-
|
|
295
|
-
|
|
296
|
-
|
|
297
|
-
|
|
298
|
-
|
|
299
|
-
|
|
300
|
-
|
|
301
|
-
|
|
302
|
-
too (bounded by the run-count budget floor), rather than re-prompting per task. So
|
|
303
|
-
`approve_before` here means "the creator authorizes the **dispatch loop** before any
|
|
304
|
-
task mutates the workspace" — a real pre-mutation floor. A per-run, single-use gate
|
|
305
|
-
is a deferred runner posture; until it lands, the budget ceiling + the per-task
|
|
306
|
-
change-set capture + the verify gate are what bound the authorized loop.
|
|
307
|
-
- The floor still hard-gates regardless of preset: once the dispatch playbook's run
|
|
308
|
-
ceiling is reached, further dispatches are **refused** — that refusal is the
|
|
309
|
-
correct outcome; report it, do not work around it.
|
|
916
|
+
## Step 2 — Check the actual host authorization boundary
|
|
917
|
+
|
|
918
|
+
A coding dispatch writes the application workspace. Read its selected task, readiness,
|
|
919
|
+
mutation scope and the configured coding host's authorization policy before invoking it.
|
|
920
|
+
The single-flight mutation lock still applies to the current shared workspace.
|
|
921
|
+
|
|
922
|
+
The playbook's `approval` declaration and the journey autonomy presets express policy
|
|
923
|
+
intent. The current playbook runner does not interpret them as pre-dispatch gates,
|
|
924
|
+
automatic authorization, or a GUIDED/YOLO mapping. A declared `approve_before` does
|
|
925
|
+
not create a pending Authority Request. Use `journey-approve` only for an actual
|
|
926
|
+
request from an explicitly connected authority workflow; never invent one from an enum.
|
|
927
|
+
|
|
928
|
+
Likewise, do not infer enforced per-playbook or per-journey run ceilings from declared
|
|
929
|
+
budget fields. Respect the limits actually reported by the execution host. Inspect the
|
|
930
|
+
recorded changes and verification result after each task; no preset commits or accepts them.
|
|
310
931
|
|
|
311
932
|
## Step 3 — Dispatch the task through the coding-agent contract
|
|
312
933
|
|
|
@@ -332,7 +953,7 @@ dispatch contract for you (you do not hand-assemble any of it):
|
|
|
332
953
|
the run terminalises with its change-set intact instead of being killed — an
|
|
333
954
|
operator who stops a run still needs to know what it had already written.
|
|
334
955
|
- **Usage is reported.** Tokens and cost come back from the run itself rather than
|
|
335
|
-
being unavailable, which
|
|
956
|
+
being unavailable, which lets the host report a terminal timeout instead of leaving the run ambiguous.
|
|
336
957
|
3. **Change-set capture** — the runner captures a git worktree snapshot before and
|
|
337
958
|
after the run and attributes each touched file (the run's own edit vs. an
|
|
338
959
|
already-dirty parallel-session file vs. a file that appeared during the run),
|
|
@@ -340,8 +961,12 @@ dispatch contract for you (you do not hand-assemble any of it):
|
|
|
340
961
|
dirty-at-dispatch is the NORMAL state (parallel sessions), so the capture
|
|
341
962
|
*attributes* rather than assuming the run had the tree to itself.
|
|
342
963
|
|
|
343
|
-
//
|
|
344
|
-
//
|
|
964
|
+
// The trigger is the companion's run route (`POST /api/companion/playbooks/<ref>/run`, via the
|
|
965
|
+
// workbench or HTTP) — there is no CLI trigger yet. The runner composes the typed context pack,
|
|
966
|
+
// runs one ACP prompt turn, and captures the change-set.
|
|
967
|
+
// That route is MUTATING, so the call must carry `x-wildo-companion-token`, read from
|
|
968
|
+
// `./.wildo-saas/state/companion.token` (mode 0600). Without it the companion answers `401` with a
|
|
969
|
+
// body that names nothing — the explanation is in the companion's own log.
|
|
345
970
|
|
|
346
971
|
## Step 4 — Verify OUTSIDE the coding agent
|
|
347
972
|
|
|
@@ -370,7 +995,7 @@ so the agent cannot mark its own homework:
|
|
|
370
995
|
## Step 5 — Record the result and apply the failure disposition
|
|
371
996
|
|
|
372
997
|
The runner records the change-set + the task's terminal status on the task row. On a
|
|
373
|
-
**failed or timed-out** run,
|
|
998
|
+
**failed or timed-out** run, the current coding host retains its captured changes for inspection (the declaration describes this as **`keep_and_flag`**): the
|
|
374
999
|
captured change-set is **kept and flagged for human triage** — never silently
|
|
375
1000
|
reverted, and never left as an un-recorded half-applied state. The change-set capture
|
|
376
1001
|
*is* the flag: it attributes exactly which files the run touched, so a human can
|
|
@@ -410,7 +1035,7 @@ flagged for triage.
|
|
|
410
1035
|
- **Follow the plan's order.** If the build plan was refined upstream (a task added,
|
|
411
1036
|
an ordering corrected), respect the new order on the next selection — do not cache
|
|
412
1037
|
a stale work list across runs.
|
|
413
|
-
- **A
|
|
1038
|
+
- **A host execution refusal is a real stop.** When an actual execution limit is reported, stop dispatching
|
|
414
1039
|
and report what remains; do not do the coding work out-of-band to "finish the
|
|
415
1040
|
build" — that makes the journey's task history a lie.
|
|
416
1041
|
|
|
@@ -451,8 +1076,8 @@ authored by this playbook. That is deliberately not duplicated into a separate
|
|
|
451
1076
|
journey artifact family: the task row already *is* the dispatch record, and a second
|
|
452
1077
|
home for the same record would drift.
|
|
453
1078
|
|
|
454
|
-
|
|
455
|
-
|
|
1079
|
+
Dispatch uses the configured host's actual authorization boundary. The creator reviews
|
|
1080
|
+
the recorded change-set and verification outcome afterwards —
|
|
456
1081
|
one verified task at a time, until the build plan is fully dispatched.
|
|
457
1082
|
|
|
458
1083
|
## References
|
|
@@ -460,8 +1085,7 @@ one verified task at a time, until the build plan is fully dispatched.
|
|
|
460
1085
|
- `.claude/skills/journey-status/SKILL.md` — read the current journey state,
|
|
461
1086
|
scope, and budget; confirm the build plan is approved and the foundation ran, and
|
|
462
1087
|
see which tasks already dispatched.
|
|
463
|
-
- `.claude/skills/journey-
|
|
464
|
-
gate decision that authorizes the workspace-mutating dispatch (never self-approve).
|
|
1088
|
+
- `.claude/skills/journey-run/references/framework-playbook-approval-policy.md` — declaration semantics and the actual runner boundary.
|
|
465
1089
|
- `.claude/skills/journey-run/SKILL.md` — trigger the dispatch and monitor it; the
|
|
466
1090
|
runner composes the context pack, runs one prompt turn against the coding agent in
|
|
467
1091
|
the app workspace, captures the change-set, and runs the verify hook.
|
|
@@ -472,4 +1096,4 @@ one verified task at a time, until the build plan is fully dispatched.
|
|
|
472
1096
|
|
|
473
1097
|
Formerly authored as an `llm_judge` quality gate; the generic rubric-only gate kind was retired at the flexible-intelligence hard cut (judgment now runs only through a compiled Evaluation Treatment). The checklist itself is creator-facing review guidance and is kept here, verbatim (minus the retired runner's closing sentence, and with repository-specific wording made application-neutral):
|
|
474
1098
|
|
|
475
|
-
Judge whether ONE dispatched build-plan task ran soundly under the D4 dispatch contract — the trust-but-verify reviewer pass OUTSIDE the coding agent. Assess six invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) TASK ACCOMPLISHED — the change-set the run produced actually implements the dispatched task's target + stage (e.g. a schema task added the persisted shape; a ui-behavior task added field displays); a run whose change-set does not advance the task's stated target is a GAP (the dispatch produced nothing useful), and an empty change-set on a task that should have authored files is a GAP. (2) CHANGE-SET SCOPED TO THE TASK — the files touched belong to the task's target (its module / resource / stage) and the app workspace; edits sprawling into unrelated modules, Wildo package source outside the application workspace, or files no build-plan task owns are a CONCERN (scope creep the reviewer must flag).
|
|
1099
|
+
Judge whether ONE dispatched build-plan task ran soundly under the D4 dispatch contract — the trust-but-verify reviewer pass OUTSIDE the coding agent. Assess six invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) TASK ACCOMPLISHED — the change-set the run produced actually implements the dispatched task's target + stage (e.g. a schema task added the persisted shape; a ui-behavior task added field displays); a run whose change-set does not advance the task's stated target is a GAP (the dispatch produced nothing useful), and an empty change-set on a task that should have authored files is a GAP. (2) CHANGE-SET SCOPED TO THE TASK — the files touched belong to the task's target (its module / resource / stage) and the app workspace; edits sprawling into unrelated modules, Wildo package source outside the application workspace, or files no build-plan task owns are a CONCERN (scope creep the reviewer must flag). Files attributed BASELINE_DIRTY_AMBIGUOUS were already dirty and changed again during the run; this establishes uncertainty, not ownership by a parallel editor. Every changed path outside the declared scope — ambiguous or not, and including a parallel session's edits, which the capture cannot tell apart from the run's own — is RECORDED on the result as `outOfScopePaths`; nothing refuses the run for it. Treat each as a CONCERN and resolve its authorship during review, never as a GAP by itself. Committed-window entries and recognized concurrent host-lane paths are classified separately and left off that list. (3) VERIFY RAN + PASSED — the deterministic verify gate (typecheck) ran OUTSIDE the coding agent after the run and passed; a run recorded as succeeded whose typecheck the reviewer cannot confirm passed is a CONCERN, and a run whose typecheck FAILED but was recorded succeeded is a GAP. (4) ATTRIBUTION CLEAN (the single-flight signal) — the run's edits are cleanly attributable to it in the captured change-set (files classed RUN_EXCLUSIVE or APPEARED_DURING_RUN), consistent with the single-flight lock having held for this dispatch. A change-set the capture could NOT cleanly attribute to the run — dominated by BASELINE_DIRTY_AMBIGUOUS overlap, or captured across a HEAD that moved mid-run — is a CONCERN the reviewer must resolve by hand before accepting the run, not a clean pass (single-flight is a hard runner floor, so this invariant reads the attribution the run actually recorded rather than re-proving the lock). (5) FAILURE DISPOSITION CORRECT — a failed/timed-out run's captured change-set is KEPT + FLAGGED for human triage (keep_and_flag), never silently reverted nor silently left as an un-recorded half-applied state; a failed run with no recorded change-set flag is a GAP (F-5 workspace-safety violation). (6) BOUNDARY DISCIPLINE — the dispatch stays at single-task depth: it dispatches ONE task, captures + verifies + records it, and applies onFailure. It does NOT re-decompose the plan (the build-decompose playbook owns the task graph), does NOT run MANY coding agents concurrently / design a concurrency scheduler / interleave the companion generation steps at scale (the scale playbook), and does NOT itself author schemas / fields / code (the coding agent does that at dispatch time). Evidence of re-decomposition, multi-agent scale orchestration, or the dispatcher authoring code itself is a CONCERN (scope creep out of the single-flight dispatch lane). (The checklist is declarative: nothing executes it; the current host's deterministic checks apply; the approval enum alone adds no gate.)
|