@wildo-ai/framework-knowledge 1.1.3 → 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 +349 -17
- 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/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +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.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.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
|
@@ -0,0 +1,154 @@
|
|
|
1
|
+
import { MetaWorkflow_ApprovalPolicy, MetaWorkflow_FailurePolicy } from '@wildo-ai/saas-models/meta-workflows';
|
|
2
|
+
import { MetaWorkflow_InputRender, MetaWorkflow_Phase } from '@wildo-ai/saas-specifications/application-creation';
|
|
3
|
+
/**
|
|
4
|
+
* The DEFINITION LANE — the first of the lanes that drive the creation of the application (#1499,
|
|
5
|
+
* epic #1506), and the first composite whose deliverable is not one family but a coherent SET of them.
|
|
6
|
+
*
|
|
7
|
+
* Paul, 2026-09-22: *"we need playbooks that drive the application creation itself. So we have
|
|
8
|
+
* leaves, with lot missing, but we need to build the lanes that will make the application coherent."*
|
|
9
|
+
*
|
|
10
|
+
* Until this existed the top-down half was ten leaves the unattended loop picked among freely and a
|
|
11
|
+
* human drove one card at a time (#1273). Nothing was wrong with any leaf; what was missing was the
|
|
12
|
+
* thing that IS the definition of the application — vision → market → requirements → capability map →
|
|
13
|
+
* value proposition → business model → roadmap → phase gate, with brand identity and the risk register
|
|
14
|
+
* beside the chain, ending on one decision a person can see.
|
|
15
|
+
*
|
|
16
|
+
* ## Order is nowhere in this file — the waterfall is the leaves' own preconditions
|
|
17
|
+
*
|
|
18
|
+
* `admits` is a set. `market-research` needs only a valid vision; `requirements-definition` needs a
|
|
19
|
+
* valid vision AND a valid market snapshot; `scope-roadmap` needs feature drafts, which
|
|
20
|
+
* `capability-map` lands; `phase-gate` needs the roadmap. Re-evaluated against the working tree after
|
|
21
|
+
* every round, that IS the waterfall — and it is also what lets the lane be re-run on an application
|
|
22
|
+
* where most of it already exists: whatever is on record satisfies the gates of whatever is not, and
|
|
23
|
+
* the selector's job is to pick what is missing rather than to walk a list from the top.
|
|
24
|
+
*
|
|
25
|
+
* ## The market umbrella is a NESTED LANE — un-flattened 2026-09-22, when #1497 landed
|
|
26
|
+
*
|
|
27
|
+
* This lane admitted `market-research`, `market-evidence-adequacy` and `market-snapshot-produce`
|
|
28
|
+
* directly for one day, because a composite could not admit a composite. It now admits
|
|
29
|
+
* `top_down.market-analysis` itself: `runPlaybookChoreography` recurses, the umbrella's landings come
|
|
30
|
+
* back as the child's `landed` (so it is marked delivered and never re-offered), its checkpoint rides
|
|
31
|
+
* inside this run's, and its INTERNAL step scope — `market-evidence`, `evidence-adequacy` — stays its
|
|
32
|
+
* own. That isolation is the point of running it as a lane rather than as three siblings: the
|
|
33
|
+
* evidence loop's re-search rounds are the umbrella's business, and this lane sees only that a market
|
|
34
|
+
* snapshot landed.
|
|
35
|
+
*
|
|
36
|
+
* `maximumDepth: 2` is what admits it — a composite child is WITHHELD when `depth + 1` reaches the
|
|
37
|
+
* ceiling, so the schema's default of `1` would have offered this lane a child it could never run.
|
|
38
|
+
* Under the root (`application-creation`, depth 0) this lane runs at depth 1 and the umbrella at
|
|
39
|
+
* depth 2, which the root's own `maximumDepth: 3` permits; the tightest ancestor's ceiling wins.
|
|
40
|
+
*
|
|
41
|
+
* **The compliance lane was, for one day, NOT un-flattened, and the asymmetry was a mechanism fact.**
|
|
42
|
+
* `top_down.compliance-analysis` carries an INTERVIEW, and a nested composite's own elicitation did not
|
|
43
|
+
* reach its children: the companion bound `runChild` ONCE, in `runChoreography`, with the OUTERMOST
|
|
44
|
+
* composite's rendered section, and `runNestedLane` forwarded that closure unchanged. That is fixed:
|
|
45
|
+
* `runChild` names the dispatching composite (#1513), and so does each round's selector (#1577), so a
|
|
46
|
+
* nested lane's children AND its selector receive that lane's own interview. `cross_cutting.compliance`
|
|
47
|
+
* now nests the umbrella too. `top_down.market-analysis` declares no elicitation, so this lane never
|
|
48
|
+
* depended on the fix.
|
|
49
|
+
*
|
|
50
|
+
* ## The interviews are answered in the DOSSIER, not here
|
|
51
|
+
*
|
|
52
|
+
* Four of the leaves interview the creator (`vision-elicitation`, `business-model`, `scope-roadmap`,
|
|
53
|
+
* `brand-identity`). The compliance umbrella moved its children's questions onto itself; this lane
|
|
54
|
+
* does NOT, because a child's eligibility inside a composite is `unansweredQuestionRefs.length === 0`
|
|
55
|
+
* computed against the `creator-inputs` family for THAT child's ref (#1454, Step 5) — the umbrella's
|
|
56
|
+
* questions would be asked twice and the child's copy would still gate. A leaf whose interview the
|
|
57
|
+
* dossier does not answer is simply not eligible in this run, the lane runs everything else it can,
|
|
58
|
+
* and the board reports the leaf as waiting for the creator. That is the "human input only at the
|
|
59
|
+
* interviews" contract stated as a mechanism rather than as a hope.
|
|
60
|
+
*
|
|
61
|
+
* ## The lane ENDS on a decision
|
|
62
|
+
*
|
|
63
|
+
* `phase-gate` is the closing move: five criteria over the coherence report, an advisory verdict, and
|
|
64
|
+
* — under the current posture — auto-accepted and notified. `approval: APPROVE_RESULT` is where the
|
|
65
|
+
* lane's boundary decision attaches, and it is LIVE since #111 landed. Note that `phase-gate` lands nothing and returns no step value, so the runner never
|
|
66
|
+
* marks it delivered — the intent below tells the selector to stop once it has run, and the round
|
|
67
|
+
* history shows that it has.
|
|
68
|
+
*
|
|
69
|
+
* ## Loop-back — the criterion → leaf table, and why nothing declares it YET
|
|
70
|
+
*
|
|
71
|
+
* The mechanism arrived (#1498): `runChoreographyChild` forwards an assessing leaf's verdict, the
|
|
72
|
+
* choreography stores it under `judge:top_down.phase-gate`, and any child gated on that ref is handed
|
|
73
|
+
* the per-criterion detail. The table below is this lane's mapping from a faulted criterion to the
|
|
74
|
+
* artifact that can be wrong.
|
|
75
|
+
*
|
|
76
|
+
* | phase-gate criterion (`application-creation:criterion/…`) | re-opens | why that leaf |
|
|
77
|
+
* |---|---|---|
|
|
78
|
+
* | `requirement-coverage` — a functional requirement no roadmap phase delivers or defers | `top_down.scope-roadmap` | the roadmap owns delivery and deferral; the requirement is not wrong for being unplanned |
|
|
79
|
+
* | `success-criterion-coverage` — a vision success criterion no phase delivers | `top_down.scope-roadmap` | same owner, the vision's other half |
|
|
80
|
+
* | `capability-completeness` — a market benefit wired to no delivering feature | `top_down.capability-map` | it authors the benefit → feature edges and the feature drafts |
|
|
81
|
+
* | `positioning-icp-coherence` — pillars that miss the core ICPs or centre an anti-target | `top_down.value-proposition` | positioning and the ICP classifications live in its slice of the snapshot |
|
|
82
|
+
* | `compliance-presence` — regulated data with no declared compliance constraint | the COMPLIANCE lane (#1502), through the root | the constraint is landed on the vision by `compliance-posture`, which belongs to another lane |
|
|
83
|
+
*
|
|
84
|
+
* **The mapping lives HERE, on the lane, and that is where it belongs.** The judge's routable verdict
|
|
85
|
+
* is keyed by criterion ref precisely so a lane author can name the criterion a revise child answers —
|
|
86
|
+
* `toRoutableJudgeVerdict` says so at its own site: the mapping is the AUTHOR's declaration, never the
|
|
87
|
+
* function's inference. The phase gate's TREATMENT cannot carry it either: an evaluation criterion is a
|
|
88
|
+
* `strictObject` of ref, instruction, evidence requirements and verdict guidance, with no routing
|
|
89
|
+
* field — and adding one would be a schema with no consumer, since the revise child it would point at
|
|
90
|
+
* does not exist yet. So the declaration is this table until a revise child declares it executably.
|
|
91
|
+
*
|
|
92
|
+
* A GAP on `requirement-coverage` therefore re-runs `scope-roadmap`, not `requirements-definition`:
|
|
93
|
+
* the criterion reads the roadmap against the requirements, and the roadmap is the artifact that can
|
|
94
|
+
* be wrong. A requirements gap the gate cannot see (a requirement that should exist and does not) is
|
|
95
|
+
* a coherence finding, not a gate verdict, and re-opens `requirements-definition` through #57.
|
|
96
|
+
*
|
|
97
|
+
* **What the table does NOT do yet is gate anything, and that is a decision rather than a gap.** The
|
|
98
|
+
* child that declares the gate cannot be one of the leaves it would revise — a leaf must run in the
|
|
99
|
+
* waterfall BEFORE the gate exists, and a leaf that landed is in the run's `delivered` set and is
|
|
100
|
+
* never re-offered — so it is a new playbook, and the shape forks three ways with real costs on each
|
|
101
|
+
* (three narrow revise children that restate three leaves; one broad one that re-derives three
|
|
102
|
+
* families when one faulted; a runtime that clears `delivered` on a verdict, needing a composite
|
|
103
|
+
* field whose only consumer is a loop nobody has run). `application-creation-directive.md` settles
|
|
104
|
+
* it: *"The system must WORK first. Restrictions come later, when a real incident shows the need."*
|
|
105
|
+
* This lane has never been driven live, so choosing now is choosing between three guesses about what a
|
|
106
|
+
* real gap looks like. The choice waits for the first live run (#1264); the mapping is ready for it.
|
|
107
|
+
*
|
|
108
|
+
* The other two mechanisms this lane was authored to adopt are ADOPTED, and both cost zero edits:
|
|
109
|
+
*
|
|
110
|
+
* - **The decision boundary (#111)** — by already declaring `approval`, which the runtime now reads at
|
|
111
|
+
* the end of every composite run.
|
|
112
|
+
* - **The staleness gate (#57)** — `ARTIFACT_STALE` reads the DECLARING playbook's own `inputs[]`, so
|
|
113
|
+
* its consumer is a child that re-derives a family, never a lane: a composite gating itself on
|
|
114
|
+
* staleness would refuse the first run of every application. Inside a lane it is SEQUENCING and is
|
|
115
|
+
* bypassed, so what it buys here is the selector's attention rather than a filter.
|
|
116
|
+
*
|
|
117
|
+
* ## Inputs are declared for the SELECTOR, not for a generation
|
|
118
|
+
*
|
|
119
|
+
* A composite generates nothing, so its `inputs` reach exactly one reader: the round selector's
|
|
120
|
+
* prompt, which renders the declared families that exist and omits the ones that do not. That is how
|
|
121
|
+
* the selector tells a missing family from a landed one — the only way it can, since an eligible
|
|
122
|
+
* child carries no "already landed" mark. The vision is read whole (it is small and it is the product);
|
|
123
|
+
* everything else is read as a MAP so the selector knows WHAT exists without paying for its content.
|
|
124
|
+
* `risk-register` has no aspect index, so a map of it would read as empty; it is read whole.
|
|
125
|
+
*/
|
|
126
|
+
export declare const playbookDefinition: {
|
|
127
|
+
ref: string;
|
|
128
|
+
version: string;
|
|
129
|
+
phase: MetaWorkflow_Phase.TOP_DOWN;
|
|
130
|
+
intent: string;
|
|
131
|
+
preconditions: any[];
|
|
132
|
+
inputs: ({
|
|
133
|
+
family: string;
|
|
134
|
+
render?: undefined;
|
|
135
|
+
} | {
|
|
136
|
+
family: string;
|
|
137
|
+
render: MetaWorkflow_InputRender.MAP;
|
|
138
|
+
})[];
|
|
139
|
+
outputs: any[];
|
|
140
|
+
method: {
|
|
141
|
+
skillRefs: string[];
|
|
142
|
+
choreography: {
|
|
143
|
+
admits: string[];
|
|
144
|
+
maximumIterations: number;
|
|
145
|
+
maximumLanesPerIteration: number;
|
|
146
|
+
maximumDepth: number;
|
|
147
|
+
maximumDurationMs: number;
|
|
148
|
+
};
|
|
149
|
+
};
|
|
150
|
+
approval: MetaWorkflow_ApprovalPolicy.APPROVE_RESULT;
|
|
151
|
+
budget: {};
|
|
152
|
+
onFailure: MetaWorkflow_FailurePolicy.KEEP_AND_FLAG;
|
|
153
|
+
};
|
|
154
|
+
//# sourceMappingURL=playbook.definition.d.ts.map
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.definition/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,0BAA0B,EAC3B,MAAM,sCAAsC,CAAC;AAC9C,OAAO,EACL,wBAAwB,EACxB,kBAAkB,EAEnB,MAAM,oDAAoD,CAAC;AAE5D;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA0HG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;CA0F9B,CAAC"}
|
|
@@ -0,0 +1,214 @@
|
|
|
1
|
+
import { MetaWorkflow_ApprovalPolicy, MetaWorkflow_FailurePolicy, } from '@wildo-ai/saas-models/meta-workflows';
|
|
2
|
+
import { MetaWorkflow_InputRender, MetaWorkflow_Phase, } from '@wildo-ai/saas-specifications/application-creation';
|
|
3
|
+
/**
|
|
4
|
+
* The DEFINITION LANE — the first of the lanes that drive the creation of the application (#1499,
|
|
5
|
+
* epic #1506), and the first composite whose deliverable is not one family but a coherent SET of them.
|
|
6
|
+
*
|
|
7
|
+
* Paul, 2026-09-22: *"we need playbooks that drive the application creation itself. So we have
|
|
8
|
+
* leaves, with lot missing, but we need to build the lanes that will make the application coherent."*
|
|
9
|
+
*
|
|
10
|
+
* Until this existed the top-down half was ten leaves the unattended loop picked among freely and a
|
|
11
|
+
* human drove one card at a time (#1273). Nothing was wrong with any leaf; what was missing was the
|
|
12
|
+
* thing that IS the definition of the application — vision → market → requirements → capability map →
|
|
13
|
+
* value proposition → business model → roadmap → phase gate, with brand identity and the risk register
|
|
14
|
+
* beside the chain, ending on one decision a person can see.
|
|
15
|
+
*
|
|
16
|
+
* ## Order is nowhere in this file — the waterfall is the leaves' own preconditions
|
|
17
|
+
*
|
|
18
|
+
* `admits` is a set. `market-research` needs only a valid vision; `requirements-definition` needs a
|
|
19
|
+
* valid vision AND a valid market snapshot; `scope-roadmap` needs feature drafts, which
|
|
20
|
+
* `capability-map` lands; `phase-gate` needs the roadmap. Re-evaluated against the working tree after
|
|
21
|
+
* every round, that IS the waterfall — and it is also what lets the lane be re-run on an application
|
|
22
|
+
* where most of it already exists: whatever is on record satisfies the gates of whatever is not, and
|
|
23
|
+
* the selector's job is to pick what is missing rather than to walk a list from the top.
|
|
24
|
+
*
|
|
25
|
+
* ## The market umbrella is a NESTED LANE — un-flattened 2026-09-22, when #1497 landed
|
|
26
|
+
*
|
|
27
|
+
* This lane admitted `market-research`, `market-evidence-adequacy` and `market-snapshot-produce`
|
|
28
|
+
* directly for one day, because a composite could not admit a composite. It now admits
|
|
29
|
+
* `top_down.market-analysis` itself: `runPlaybookChoreography` recurses, the umbrella's landings come
|
|
30
|
+
* back as the child's `landed` (so it is marked delivered and never re-offered), its checkpoint rides
|
|
31
|
+
* inside this run's, and its INTERNAL step scope — `market-evidence`, `evidence-adequacy` — stays its
|
|
32
|
+
* own. That isolation is the point of running it as a lane rather than as three siblings: the
|
|
33
|
+
* evidence loop's re-search rounds are the umbrella's business, and this lane sees only that a market
|
|
34
|
+
* snapshot landed.
|
|
35
|
+
*
|
|
36
|
+
* `maximumDepth: 2` is what admits it — a composite child is WITHHELD when `depth + 1` reaches the
|
|
37
|
+
* ceiling, so the schema's default of `1` would have offered this lane a child it could never run.
|
|
38
|
+
* Under the root (`application-creation`, depth 0) this lane runs at depth 1 and the umbrella at
|
|
39
|
+
* depth 2, which the root's own `maximumDepth: 3` permits; the tightest ancestor's ceiling wins.
|
|
40
|
+
*
|
|
41
|
+
* **The compliance lane was, for one day, NOT un-flattened, and the asymmetry was a mechanism fact.**
|
|
42
|
+
* `top_down.compliance-analysis` carries an INTERVIEW, and a nested composite's own elicitation did not
|
|
43
|
+
* reach its children: the companion bound `runChild` ONCE, in `runChoreography`, with the OUTERMOST
|
|
44
|
+
* composite's rendered section, and `runNestedLane` forwarded that closure unchanged. That is fixed:
|
|
45
|
+
* `runChild` names the dispatching composite (#1513), and so does each round's selector (#1577), so a
|
|
46
|
+
* nested lane's children AND its selector receive that lane's own interview. `cross_cutting.compliance`
|
|
47
|
+
* now nests the umbrella too. `top_down.market-analysis` declares no elicitation, so this lane never
|
|
48
|
+
* depended on the fix.
|
|
49
|
+
*
|
|
50
|
+
* ## The interviews are answered in the DOSSIER, not here
|
|
51
|
+
*
|
|
52
|
+
* Four of the leaves interview the creator (`vision-elicitation`, `business-model`, `scope-roadmap`,
|
|
53
|
+
* `brand-identity`). The compliance umbrella moved its children's questions onto itself; this lane
|
|
54
|
+
* does NOT, because a child's eligibility inside a composite is `unansweredQuestionRefs.length === 0`
|
|
55
|
+
* computed against the `creator-inputs` family for THAT child's ref (#1454, Step 5) — the umbrella's
|
|
56
|
+
* questions would be asked twice and the child's copy would still gate. A leaf whose interview the
|
|
57
|
+
* dossier does not answer is simply not eligible in this run, the lane runs everything else it can,
|
|
58
|
+
* and the board reports the leaf as waiting for the creator. That is the "human input only at the
|
|
59
|
+
* interviews" contract stated as a mechanism rather than as a hope.
|
|
60
|
+
*
|
|
61
|
+
* ## The lane ENDS on a decision
|
|
62
|
+
*
|
|
63
|
+
* `phase-gate` is the closing move: five criteria over the coherence report, an advisory verdict, and
|
|
64
|
+
* — under the current posture — auto-accepted and notified. `approval: APPROVE_RESULT` is where the
|
|
65
|
+
* lane's boundary decision attaches, and it is LIVE since #111 landed. Note that `phase-gate` lands nothing and returns no step value, so the runner never
|
|
66
|
+
* marks it delivered — the intent below tells the selector to stop once it has run, and the round
|
|
67
|
+
* history shows that it has.
|
|
68
|
+
*
|
|
69
|
+
* ## Loop-back — the criterion → leaf table, and why nothing declares it YET
|
|
70
|
+
*
|
|
71
|
+
* The mechanism arrived (#1498): `runChoreographyChild` forwards an assessing leaf's verdict, the
|
|
72
|
+
* choreography stores it under `judge:top_down.phase-gate`, and any child gated on that ref is handed
|
|
73
|
+
* the per-criterion detail. The table below is this lane's mapping from a faulted criterion to the
|
|
74
|
+
* artifact that can be wrong.
|
|
75
|
+
*
|
|
76
|
+
* | phase-gate criterion (`application-creation:criterion/…`) | re-opens | why that leaf |
|
|
77
|
+
* |---|---|---|
|
|
78
|
+
* | `requirement-coverage` — a functional requirement no roadmap phase delivers or defers | `top_down.scope-roadmap` | the roadmap owns delivery and deferral; the requirement is not wrong for being unplanned |
|
|
79
|
+
* | `success-criterion-coverage` — a vision success criterion no phase delivers | `top_down.scope-roadmap` | same owner, the vision's other half |
|
|
80
|
+
* | `capability-completeness` — a market benefit wired to no delivering feature | `top_down.capability-map` | it authors the benefit → feature edges and the feature drafts |
|
|
81
|
+
* | `positioning-icp-coherence` — pillars that miss the core ICPs or centre an anti-target | `top_down.value-proposition` | positioning and the ICP classifications live in its slice of the snapshot |
|
|
82
|
+
* | `compliance-presence` — regulated data with no declared compliance constraint | the COMPLIANCE lane (#1502), through the root | the constraint is landed on the vision by `compliance-posture`, which belongs to another lane |
|
|
83
|
+
*
|
|
84
|
+
* **The mapping lives HERE, on the lane, and that is where it belongs.** The judge's routable verdict
|
|
85
|
+
* is keyed by criterion ref precisely so a lane author can name the criterion a revise child answers —
|
|
86
|
+
* `toRoutableJudgeVerdict` says so at its own site: the mapping is the AUTHOR's declaration, never the
|
|
87
|
+
* function's inference. The phase gate's TREATMENT cannot carry it either: an evaluation criterion is a
|
|
88
|
+
* `strictObject` of ref, instruction, evidence requirements and verdict guidance, with no routing
|
|
89
|
+
* field — and adding one would be a schema with no consumer, since the revise child it would point at
|
|
90
|
+
* does not exist yet. So the declaration is this table until a revise child declares it executably.
|
|
91
|
+
*
|
|
92
|
+
* A GAP on `requirement-coverage` therefore re-runs `scope-roadmap`, not `requirements-definition`:
|
|
93
|
+
* the criterion reads the roadmap against the requirements, and the roadmap is the artifact that can
|
|
94
|
+
* be wrong. A requirements gap the gate cannot see (a requirement that should exist and does not) is
|
|
95
|
+
* a coherence finding, not a gate verdict, and re-opens `requirements-definition` through #57.
|
|
96
|
+
*
|
|
97
|
+
* **What the table does NOT do yet is gate anything, and that is a decision rather than a gap.** The
|
|
98
|
+
* child that declares the gate cannot be one of the leaves it would revise — a leaf must run in the
|
|
99
|
+
* waterfall BEFORE the gate exists, and a leaf that landed is in the run's `delivered` set and is
|
|
100
|
+
* never re-offered — so it is a new playbook, and the shape forks three ways with real costs on each
|
|
101
|
+
* (three narrow revise children that restate three leaves; one broad one that re-derives three
|
|
102
|
+
* families when one faulted; a runtime that clears `delivered` on a verdict, needing a composite
|
|
103
|
+
* field whose only consumer is a loop nobody has run). `application-creation-directive.md` settles
|
|
104
|
+
* it: *"The system must WORK first. Restrictions come later, when a real incident shows the need."*
|
|
105
|
+
* This lane has never been driven live, so choosing now is choosing between three guesses about what a
|
|
106
|
+
* real gap looks like. The choice waits for the first live run (#1264); the mapping is ready for it.
|
|
107
|
+
*
|
|
108
|
+
* The other two mechanisms this lane was authored to adopt are ADOPTED, and both cost zero edits:
|
|
109
|
+
*
|
|
110
|
+
* - **The decision boundary (#111)** — by already declaring `approval`, which the runtime now reads at
|
|
111
|
+
* the end of every composite run.
|
|
112
|
+
* - **The staleness gate (#57)** — `ARTIFACT_STALE` reads the DECLARING playbook's own `inputs[]`, so
|
|
113
|
+
* its consumer is a child that re-derives a family, never a lane: a composite gating itself on
|
|
114
|
+
* staleness would refuse the first run of every application. Inside a lane it is SEQUENCING and is
|
|
115
|
+
* bypassed, so what it buys here is the selector's attention rather than a filter.
|
|
116
|
+
*
|
|
117
|
+
* ## Inputs are declared for the SELECTOR, not for a generation
|
|
118
|
+
*
|
|
119
|
+
* A composite generates nothing, so its `inputs` reach exactly one reader: the round selector's
|
|
120
|
+
* prompt, which renders the declared families that exist and omits the ones that do not. That is how
|
|
121
|
+
* the selector tells a missing family from a landed one — the only way it can, since an eligible
|
|
122
|
+
* child carries no "already landed" mark. The vision is read whole (it is small and it is the product);
|
|
123
|
+
* everything else is read as a MAP so the selector knows WHAT exists without paying for its content.
|
|
124
|
+
* `risk-register` has no aspect index, so a map of it would read as empty; it is read whole.
|
|
125
|
+
*/
|
|
126
|
+
export const playbookDefinition = {
|
|
127
|
+
ref: 'top_down.definition',
|
|
128
|
+
version: '0.1.0',
|
|
129
|
+
phase: MetaWorkflow_Phase.TOP_DOWN,
|
|
130
|
+
intent: 'Drive the top-down DEFINITION of the application as one lane: from an answered vision through market evidence, the market snapshot, the value proposition, the requirements, the capability map, the business model and the roadmap, to the phase gate — with the brand identity and the risk register beside the chain. An umbrella: it authors nothing itself; every child declares what it needs and the runtime recomputes what may run after each round, so the order is the leaves\' preconditions and never a list. Select what is MISSING from the accepted truth shown to you: a family already on record is not re-derived unless a family it was derived from has been re-derived in this run. Run independent children in the same round (brand identity and the risk register beside the chain; several research lanes with different objectives). Run the phase gate once the roadmap is on record, and STOP after it has run — its verdict is this lane\'s closing decision, and it is not re-run in the same run. A child whose interview the creator has not answered is not offered; run everything else and stop when nothing eligible advances the definition.',
|
|
131
|
+
// None. The lane STARTS at the vision interview, which has no precondition of its own, so a fresh
|
|
132
|
+
// application is exactly where this composite must be eligible. Every later gate is a child's.
|
|
133
|
+
preconditions: [],
|
|
134
|
+
inputs: [
|
|
135
|
+
{ family: 'vision-brief' },
|
|
136
|
+
{ family: 'market-snapshot', render: MetaWorkflow_InputRender.MAP },
|
|
137
|
+
{ family: 'requirements', render: MetaWorkflow_InputRender.MAP },
|
|
138
|
+
{ family: 'feature-drafts', render: MetaWorkflow_InputRender.MAP },
|
|
139
|
+
{ family: 'business-model', render: MetaWorkflow_InputRender.MAP },
|
|
140
|
+
{ family: 'roadmap', render: MetaWorkflow_InputRender.MAP },
|
|
141
|
+
{ family: 'brand-brief', render: MetaWorkflow_InputRender.MAP },
|
|
142
|
+
{ family: 'risk-register' },
|
|
143
|
+
],
|
|
144
|
+
// Nothing, for the market umbrella's recorded reason: a composite's deliverable is what its children
|
|
145
|
+
// land, and the loop resolves this lane's write scope TRANSITIVELY through `admits` — every family
|
|
146
|
+
// above except the vision's compliance slice, which the compliance lane owns.
|
|
147
|
+
outputs: [],
|
|
148
|
+
method: {
|
|
149
|
+
skillRefs: ['journey-status', 'journey-report'],
|
|
150
|
+
choreography: {
|
|
151
|
+
/*
|
|
152
|
+
* UNORDERED. Listed closing-move-first on purpose, the umbrellas' own trap check: if anything
|
|
153
|
+
* ever read this array as a sequence the lane would try to judge a definition before any of it
|
|
154
|
+
* existed, and the run would fail loudly rather than silently degrading.
|
|
155
|
+
*/
|
|
156
|
+
admits: [
|
|
157
|
+
'top_down.phase-gate',
|
|
158
|
+
'top_down.scope-roadmap',
|
|
159
|
+
'top_down.business-model',
|
|
160
|
+
'top_down.capability-map',
|
|
161
|
+
'top_down.value-proposition',
|
|
162
|
+
'top_down.requirements-definition',
|
|
163
|
+
// A NESTED LANE, not three siblings — see the un-flattening note above. Its evidence loop is its own.
|
|
164
|
+
'top_down.market-analysis',
|
|
165
|
+
'top_down.vision-elicitation',
|
|
166
|
+
// Beside the chain, not on it: each needs the vision (and the business model, for the register)
|
|
167
|
+
// and nothing downstream needs them.
|
|
168
|
+
'top_down.brand-identity',
|
|
169
|
+
'top_down.risk-register',
|
|
170
|
+
],
|
|
171
|
+
/*
|
|
172
|
+
* The schema's ceiling. Derived, not guessed: one round per chain leaf (vision, produce,
|
|
173
|
+
* value proposition, requirements, capability map, business model, roadmap, phase gate = 8) plus
|
|
174
|
+
* the market's evidence loop, which consumed FIVE of six iterations on its first measured run
|
|
175
|
+
* (`top_down.market-analysis`, wonder-crm run 5), plus brand and risk running beside the chain at
|
|
176
|
+
* no extra round when the selector pairs them. Fifteen on a fresh application if nothing loops;
|
|
177
|
+
* twenty is the headroom for one re-search cycle and one re-run of a chain leaf. A breaker, not a
|
|
178
|
+
* budget: it stops a loop spinning, it never refuses work for want of spend.
|
|
179
|
+
*/
|
|
180
|
+
maximumIterations: 20,
|
|
181
|
+
// The journey loop's own width. Research is breadth-first, and the chain's side leaves ride beside it.
|
|
182
|
+
maximumLanesPerIteration: 3,
|
|
183
|
+
/*
|
|
184
|
+
* Two levels below this one: the market umbrella, and the umbrella's own leaves. A composite
|
|
185
|
+
* child is WITHHELD when `depth + 1` reaches the ceiling, so the default `1` would offer this
|
|
186
|
+
* lane a nested lane it could never run — an eligible-looking card that stops before its first
|
|
187
|
+
* iteration.
|
|
188
|
+
*/
|
|
189
|
+
maximumDepth: 2,
|
|
190
|
+
/*
|
|
191
|
+
* Three hours. The market loop measured ~168s per iteration and the compliance loop ~280s; a
|
|
192
|
+
* chain generation with a full brief (requirements, capability map, roadmap) is in the same range,
|
|
193
|
+
* and twenty iterations at the slower figure is ~95 minutes. The companion's HTTP request ceiling
|
|
194
|
+
* (30 min) is SHORTER than this — submit the lane with `async: true` and read the outcome from
|
|
195
|
+
* `/playbooks/runs`, as the compliance umbrella's own comment already warns. Literal: the
|
|
196
|
+
* definition evaluator computes no expressions.
|
|
197
|
+
*/
|
|
198
|
+
maximumDurationMs: 10_800_000,
|
|
199
|
+
},
|
|
200
|
+
},
|
|
201
|
+
/*
|
|
202
|
+
* The lane's closing decision — accept the definition, or send it back.
|
|
203
|
+
*
|
|
204
|
+
* LIVE since #111 landed: `derivePlaybookChoreographyBoundary` reads this field at the end of every
|
|
205
|
+
* composite run and the companion projects ONE `approve_result` decision onto the human-decision
|
|
206
|
+
* plane — approve / revise / discard, over the paths this lane's children kept. The POSTURE decides
|
|
207
|
+
* what it does: under YOLO it notifies and the run concludes; GUIDED's hold is the marked gate,
|
|
208
|
+
* armed at Gate 3. `onFailure` below is read at the same boundary.
|
|
209
|
+
*/
|
|
210
|
+
approval: MetaWorkflow_ApprovalPolicy.APPROVE_RESULT,
|
|
211
|
+
budget: {},
|
|
212
|
+
onFailure: MetaWorkflow_FailurePolicy.KEEP_AND_FLAG,
|
|
213
|
+
};
|
|
214
|
+
//# sourceMappingURL=playbook.definition.js.map
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.definition/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,0BAA0B,GAC3B,MAAM,sCAAsC,CAAC;AAC9C,OAAO,EACL,wBAAwB,EACxB,kBAAkB,GAEnB,MAAM,oDAAoD,CAAC;AAE5D;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA0HG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG;IAChC,GAAG,EAAE,qBAAqB;IAC1B,OAAO,EAAE,OAAO;IAChB,KAAK,EAAE,kBAAkB,CAAC,QAAQ;IAClC,MAAM,EACJ,onCAAonC;IACtnC,kGAAkG;IAClG,+FAA+F;IAC/F,aAAa,EAAE,EAAE;IACjB,MAAM,EAAE;QACN,EAAE,MAAM,EAAE,cAAc,EAAE;QAC1B,EAAE,MAAM,EAAE,iBAAiB,EAAE,MAAM,EAAE,wBAAwB,CAAC,GAAG,EAAE;QACnE,EAAE,MAAM,EAAE,cAAc,EAAE,MAAM,EAAE,wBAAwB,CAAC,GAAG,EAAE;QAChE,EAAE,MAAM,EAAE,gBAAgB,EAAE,MAAM,EAAE,wBAAwB,CAAC,GAAG,EAAE;QAClE,EAAE,MAAM,EAAE,gBAAgB,EAAE,MAAM,EAAE,wBAAwB,CAAC,GAAG,EAAE;QAClE,EAAE,MAAM,EAAE,SAAS,EAAE,MAAM,EAAE,wBAAwB,CAAC,GAAG,EAAE;QAC3D,EAAE,MAAM,EAAE,aAAa,EAAE,MAAM,EAAE,wBAAwB,CAAC,GAAG,EAAE;QAC/D,EAAE,MAAM,EAAE,eAAe,EAAE;KAC5B;IACD,qGAAqG;IACrG,mGAAmG;IACnG,8EAA8E;IAC9E,OAAO,EAAE,EAAE;IACX,MAAM,EAAE;QACN,SAAS,EAAE,CAAC,gBAAgB,EAAE,gBAAgB,CAAC;QAC/C,YAAY,EAAE;YACZ;;;;eAIG;YACH,MAAM,EAAE;gBACN,qBAAqB;gBACrB,wBAAwB;gBACxB,yBAAyB;gBACzB,yBAAyB;gBACzB,4BAA4B;gBAC5B,kCAAkC;gBAClC,sGAAsG;gBACtG,0BAA0B;gBAC1B,6BAA6B;gBAC7B,gGAAgG;gBAChG,qCAAqC;gBACrC,yBAAyB;gBACzB,wBAAwB;aACzB;YACD;;;;;;;;eAQG;YACH,iBAAiB,EAAE,EAAE;YACrB,uGAAuG;YACvG,wBAAwB,EAAE,CAAC;YAC3B;;;;;eAKG;YACH,YAAY,EAAE,CAAC;YACf;;;;;;;eAOG;YACH,iBAAiB,EAAE,UAAU;SAC9B;KACF;IACD;;;;;;;;OAQG;IACH,QAAQ,EAAE,2BAA2B,CAAC,cAAc;IACpD,MAAM,EAAE,EAAE;IACV,SAAS,EAAE,0BAA0B,CAAC,aAAa;CAGpD,CAAC","sourcesContent":["import {\n MetaWorkflow_ApprovalPolicy,\n MetaWorkflow_FailurePolicy,\n} from '@wildo-ai/saas-models/meta-workflows';\nimport {\n MetaWorkflow_InputRender,\n MetaWorkflow_Phase,\n type MetaWorkflowPlaybookAuthoring,\n} from '@wildo-ai/saas-specifications/application-creation';\n\n/**\n * The DEFINITION LANE — the first of the lanes that drive the creation of the application (#1499,\n * epic #1506), and the first composite whose deliverable is not one family but a coherent SET of them.\n *\n * Paul, 2026-09-22: *\"we need playbooks that drive the application creation itself. So we have\n * leaves, with lot missing, but we need to build the lanes that will make the application coherent.\"*\n *\n * Until this existed the top-down half was ten leaves the unattended loop picked among freely and a\n * human drove one card at a time (#1273). Nothing was wrong with any leaf; what was missing was the\n * thing that IS the definition of the application — vision → market → requirements → capability map →\n * value proposition → business model → roadmap → phase gate, with brand identity and the risk register\n * beside the chain, ending on one decision a person can see.\n *\n * ## Order is nowhere in this file — the waterfall is the leaves' own preconditions\n *\n * `admits` is a set. `market-research` needs only a valid vision; `requirements-definition` needs a\n * valid vision AND a valid market snapshot; `scope-roadmap` needs feature drafts, which\n * `capability-map` lands; `phase-gate` needs the roadmap. Re-evaluated against the working tree after\n * every round, that IS the waterfall — and it is also what lets the lane be re-run on an application\n * where most of it already exists: whatever is on record satisfies the gates of whatever is not, and\n * the selector's job is to pick what is missing rather than to walk a list from the top.\n *\n * ## The market umbrella is a NESTED LANE — un-flattened 2026-09-22, when #1497 landed\n *\n * This lane admitted `market-research`, `market-evidence-adequacy` and `market-snapshot-produce`\n * directly for one day, because a composite could not admit a composite. It now admits\n * `top_down.market-analysis` itself: `runPlaybookChoreography` recurses, the umbrella's landings come\n * back as the child's `landed` (so it is marked delivered and never re-offered), its checkpoint rides\n * inside this run's, and its INTERNAL step scope — `market-evidence`, `evidence-adequacy` — stays its\n * own. That isolation is the point of running it as a lane rather than as three siblings: the\n * evidence loop's re-search rounds are the umbrella's business, and this lane sees only that a market\n * snapshot landed.\n *\n * `maximumDepth: 2` is what admits it — a composite child is WITHHELD when `depth + 1` reaches the\n * ceiling, so the schema's default of `1` would have offered this lane a child it could never run.\n * Under the root (`application-creation`, depth 0) this lane runs at depth 1 and the umbrella at\n * depth 2, which the root's own `maximumDepth: 3` permits; the tightest ancestor's ceiling wins.\n *\n * **The compliance lane was, for one day, NOT un-flattened, and the asymmetry was a mechanism fact.**\n * `top_down.compliance-analysis` carries an INTERVIEW, and a nested composite's own elicitation did not\n * reach its children: the companion bound `runChild` ONCE, in `runChoreography`, with the OUTERMOST\n * composite's rendered section, and `runNestedLane` forwarded that closure unchanged. That is fixed:\n * `runChild` names the dispatching composite (#1513), and so does each round's selector (#1577), so a\n * nested lane's children AND its selector receive that lane's own interview. `cross_cutting.compliance`\n * now nests the umbrella too. `top_down.market-analysis` declares no elicitation, so this lane never\n * depended on the fix.\n *\n * ## The interviews are answered in the DOSSIER, not here\n *\n * Four of the leaves interview the creator (`vision-elicitation`, `business-model`, `scope-roadmap`,\n * `brand-identity`). The compliance umbrella moved its children's questions onto itself; this lane\n * does NOT, because a child's eligibility inside a composite is `unansweredQuestionRefs.length === 0`\n * computed against the `creator-inputs` family for THAT child's ref (#1454, Step 5) — the umbrella's\n * questions would be asked twice and the child's copy would still gate. A leaf whose interview the\n * dossier does not answer is simply not eligible in this run, the lane runs everything else it can,\n * and the board reports the leaf as waiting for the creator. That is the \"human input only at the\n * interviews\" contract stated as a mechanism rather than as a hope.\n *\n * ## The lane ENDS on a decision\n *\n * `phase-gate` is the closing move: five criteria over the coherence report, an advisory verdict, and\n * — under the current posture — auto-accepted and notified. `approval: APPROVE_RESULT` is where the\n * lane's boundary decision attaches, and it is LIVE since #111 landed. Note that `phase-gate` lands nothing and returns no step value, so the runner never\n * marks it delivered — the intent below tells the selector to stop once it has run, and the round\n * history shows that it has.\n *\n * ## Loop-back — the criterion → leaf table, and why nothing declares it YET\n *\n * The mechanism arrived (#1498): `runChoreographyChild` forwards an assessing leaf's verdict, the\n * choreography stores it under `judge:top_down.phase-gate`, and any child gated on that ref is handed\n * the per-criterion detail. The table below is this lane's mapping from a faulted criterion to the\n * artifact that can be wrong.\n *\n * | phase-gate criterion (`application-creation:criterion/…`) | re-opens | why that leaf |\n * |---|---|---|\n * | `requirement-coverage` — a functional requirement no roadmap phase delivers or defers | `top_down.scope-roadmap` | the roadmap owns delivery and deferral; the requirement is not wrong for being unplanned |\n * | `success-criterion-coverage` — a vision success criterion no phase delivers | `top_down.scope-roadmap` | same owner, the vision's other half |\n * | `capability-completeness` — a market benefit wired to no delivering feature | `top_down.capability-map` | it authors the benefit → feature edges and the feature drafts |\n * | `positioning-icp-coherence` — pillars that miss the core ICPs or centre an anti-target | `top_down.value-proposition` | positioning and the ICP classifications live in its slice of the snapshot |\n * | `compliance-presence` — regulated data with no declared compliance constraint | the COMPLIANCE lane (#1502), through the root | the constraint is landed on the vision by `compliance-posture`, which belongs to another lane |\n *\n * **The mapping lives HERE, on the lane, and that is where it belongs.** The judge's routable verdict\n * is keyed by criterion ref precisely so a lane author can name the criterion a revise child answers —\n * `toRoutableJudgeVerdict` says so at its own site: the mapping is the AUTHOR's declaration, never the\n * function's inference. The phase gate's TREATMENT cannot carry it either: an evaluation criterion is a\n * `strictObject` of ref, instruction, evidence requirements and verdict guidance, with no routing\n * field — and adding one would be a schema with no consumer, since the revise child it would point at\n * does not exist yet. So the declaration is this table until a revise child declares it executably.\n *\n * A GAP on `requirement-coverage` therefore re-runs `scope-roadmap`, not `requirements-definition`:\n * the criterion reads the roadmap against the requirements, and the roadmap is the artifact that can\n * be wrong. A requirements gap the gate cannot see (a requirement that should exist and does not) is\n * a coherence finding, not a gate verdict, and re-opens `requirements-definition` through #57.\n *\n * **What the table does NOT do yet is gate anything, and that is a decision rather than a gap.** The\n * child that declares the gate cannot be one of the leaves it would revise — a leaf must run in the\n * waterfall BEFORE the gate exists, and a leaf that landed is in the run's `delivered` set and is\n * never re-offered — so it is a new playbook, and the shape forks three ways with real costs on each\n * (three narrow revise children that restate three leaves; one broad one that re-derives three\n * families when one faulted; a runtime that clears `delivered` on a verdict, needing a composite\n * field whose only consumer is a loop nobody has run). `application-creation-directive.md` settles\n * it: *\"The system must WORK first. Restrictions come later, when a real incident shows the need.\"*\n * This lane has never been driven live, so choosing now is choosing between three guesses about what a\n * real gap looks like. The choice waits for the first live run (#1264); the mapping is ready for it.\n *\n * The other two mechanisms this lane was authored to adopt are ADOPTED, and both cost zero edits:\n *\n * - **The decision boundary (#111)** — by already declaring `approval`, which the runtime now reads at\n * the end of every composite run.\n * - **The staleness gate (#57)** — `ARTIFACT_STALE` reads the DECLARING playbook's own `inputs[]`, so\n * its consumer is a child that re-derives a family, never a lane: a composite gating itself on\n * staleness would refuse the first run of every application. Inside a lane it is SEQUENCING and is\n * bypassed, so what it buys here is the selector's attention rather than a filter.\n *\n * ## Inputs are declared for the SELECTOR, not for a generation\n *\n * A composite generates nothing, so its `inputs` reach exactly one reader: the round selector's\n * prompt, which renders the declared families that exist and omits the ones that do not. That is how\n * the selector tells a missing family from a landed one — the only way it can, since an eligible\n * child carries no \"already landed\" mark. The vision is read whole (it is small and it is the product);\n * everything else is read as a MAP so the selector knows WHAT exists without paying for its content.\n * `risk-register` has no aspect index, so a map of it would read as empty; it is read whole.\n */\nexport const playbookDefinition = {\n ref: 'top_down.definition',\n version: '0.1.0',\n phase: MetaWorkflow_Phase.TOP_DOWN,\n intent:\n 'Drive the top-down DEFINITION of the application as one lane: from an answered vision through market evidence, the market snapshot, the value proposition, the requirements, the capability map, the business model and the roadmap, to the phase gate — with the brand identity and the risk register beside the chain. An umbrella: it authors nothing itself; every child declares what it needs and the runtime recomputes what may run after each round, so the order is the leaves\\' preconditions and never a list. Select what is MISSING from the accepted truth shown to you: a family already on record is not re-derived unless a family it was derived from has been re-derived in this run. Run independent children in the same round (brand identity and the risk register beside the chain; several research lanes with different objectives). Run the phase gate once the roadmap is on record, and STOP after it has run — its verdict is this lane\\'s closing decision, and it is not re-run in the same run. A child whose interview the creator has not answered is not offered; run everything else and stop when nothing eligible advances the definition.',\n // None. The lane STARTS at the vision interview, which has no precondition of its own, so a fresh\n // application is exactly where this composite must be eligible. Every later gate is a child's.\n preconditions: [],\n inputs: [\n { family: 'vision-brief' },\n { family: 'market-snapshot', render: MetaWorkflow_InputRender.MAP },\n { family: 'requirements', render: MetaWorkflow_InputRender.MAP },\n { family: 'feature-drafts', render: MetaWorkflow_InputRender.MAP },\n { family: 'business-model', render: MetaWorkflow_InputRender.MAP },\n { family: 'roadmap', render: MetaWorkflow_InputRender.MAP },\n { family: 'brand-brief', render: MetaWorkflow_InputRender.MAP },\n { family: 'risk-register' },\n ],\n // Nothing, for the market umbrella's recorded reason: a composite's deliverable is what its children\n // land, and the loop resolves this lane's write scope TRANSITIVELY through `admits` — every family\n // above except the vision's compliance slice, which the compliance lane owns.\n outputs: [],\n method: {\n skillRefs: ['journey-status', 'journey-report'],\n choreography: {\n /*\n * UNORDERED. Listed closing-move-first on purpose, the umbrellas' own trap check: if anything\n * ever read this array as a sequence the lane would try to judge a definition before any of it\n * existed, and the run would fail loudly rather than silently degrading.\n */\n admits: [\n 'top_down.phase-gate',\n 'top_down.scope-roadmap',\n 'top_down.business-model',\n 'top_down.capability-map',\n 'top_down.value-proposition',\n 'top_down.requirements-definition',\n // A NESTED LANE, not three siblings — see the un-flattening note above. Its evidence loop is its own.\n 'top_down.market-analysis',\n 'top_down.vision-elicitation',\n // Beside the chain, not on it: each needs the vision (and the business model, for the register)\n // and nothing downstream needs them.\n 'top_down.brand-identity',\n 'top_down.risk-register',\n ],\n /*\n * The schema's ceiling. Derived, not guessed: one round per chain leaf (vision, produce,\n * value proposition, requirements, capability map, business model, roadmap, phase gate = 8) plus\n * the market's evidence loop, which consumed FIVE of six iterations on its first measured run\n * (`top_down.market-analysis`, wonder-crm run 5), plus brand and risk running beside the chain at\n * no extra round when the selector pairs them. Fifteen on a fresh application if nothing loops;\n * twenty is the headroom for one re-search cycle and one re-run of a chain leaf. A breaker, not a\n * budget: it stops a loop spinning, it never refuses work for want of spend.\n */\n maximumIterations: 20,\n // The journey loop's own width. Research is breadth-first, and the chain's side leaves ride beside it.\n maximumLanesPerIteration: 3,\n /*\n * Two levels below this one: the market umbrella, and the umbrella's own leaves. A composite\n * child is WITHHELD when `depth + 1` reaches the ceiling, so the default `1` would offer this\n * lane a nested lane it could never run — an eligible-looking card that stops before its first\n * iteration.\n */\n maximumDepth: 2,\n /*\n * Three hours. The market loop measured ~168s per iteration and the compliance loop ~280s; a\n * chain generation with a full brief (requirements, capability map, roadmap) is in the same range,\n * and twenty iterations at the slower figure is ~95 minutes. The companion's HTTP request ceiling\n * (30 min) is SHORTER than this — submit the lane with `async: true` and read the outcome from\n * `/playbooks/runs`, as the compliance umbrella's own comment already warns. Literal: the\n * definition evaluator computes no expressions.\n */\n maximumDurationMs: 10_800_000,\n },\n },\n /*\n * The lane's closing decision — accept the definition, or send it back.\n *\n * LIVE since #111 landed: `derivePlaybookChoreographyBoundary` reads this field at the end of every\n * composite run and the companion projects ONE `approve_result` decision onto the human-decision\n * plane — approve / revise / discard, over the paths this lane's children kept. The POSTURE decides\n * what it does: under YOLO it notifies and the run concludes; GUIDED's hold is the marked gate,\n * armed at Gate 3. `onFailure` below is read at the same boundary.\n */\n approval: MetaWorkflow_ApprovalPolicy.APPROVE_RESULT,\n budget: {},\n onFailure: MetaWorkflow_FailurePolicy.KEEP_AND_FLAG,\n} satisfies Omit<MetaWorkflowPlaybookAuthoring, 'method'> & {\n method: Omit<NonNullable<MetaWorkflowPlaybookAuthoring['method']>, 'guidance'>;\n};\n"]}
|
|
@@ -0,0 +1,44 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* Canonical native declaration for this reusable application-creation method.
|
|
3
|
+
*
|
|
4
|
+
* A RUNNER-OWNED step, like `bottom_up.foundation`: the run short-circuits into the companion's
|
|
5
|
+
* expert-persona derive → accept services before any brief is composed, so this declaration's
|
|
6
|
+
* `inputs` are what the derivation READS through introspection (never a composed brief — #1434's lesson) and it has no `outputs` (the family it lands,
|
|
7
|
+
* `expert-personas`, is written by those services as per-role modules plus an aggregator, a shape the
|
|
8
|
+
* generic landing renderer must not replace; see the landing placement's own comment). It carries no
|
|
9
|
+
* evaluation treatment either: each charter is critiqued by the derivation's own multi-pass
|
|
10
|
+
* DRAFT → CRITIQUE → FINALIZE protocol, whose report is persisted beside the proposal.
|
|
11
|
+
*/
|
|
12
|
+
export declare const playbookDefinition: {
|
|
13
|
+
readonly ref: "top_down.expert-personas";
|
|
14
|
+
readonly version: "0.1.0";
|
|
15
|
+
readonly phase: "top_down";
|
|
16
|
+
readonly intent: "Staff every expert panel the catalog convenes: derive and accept an application-specific charter for each framework expert role that a deliberated playbook (`method.deliberation`) or a companion generation step (the logo panel) seats, grounded in the application's own vision, market, requirements, business model and brand. Idempotent: a role whose charter is committed is left alone (a human-edited charter is never overwritten), and a role whose shaping inputs have not landed yet is REPORTED as waiting rather than failing the run. Before this step existed the panel's staffing was not a journey step at all — every deliberated playbook failed closed at bind time on an application whose charters nobody had curled in by hand (#572).";
|
|
17
|
+
readonly preconditions: readonly [{
|
|
18
|
+
readonly kind: "artifact_exists";
|
|
19
|
+
readonly selector: {
|
|
20
|
+
readonly family: "vision-brief";
|
|
21
|
+
};
|
|
22
|
+
}, {
|
|
23
|
+
readonly kind: "artifact_exists";
|
|
24
|
+
readonly selector: {
|
|
25
|
+
readonly family: "market-snapshot";
|
|
26
|
+
};
|
|
27
|
+
}];
|
|
28
|
+
readonly inputs: readonly [{
|
|
29
|
+
readonly family: "vision-brief";
|
|
30
|
+
}, {
|
|
31
|
+
readonly family: "market-snapshot";
|
|
32
|
+
}];
|
|
33
|
+
readonly outputs: readonly [];
|
|
34
|
+
readonly method: {
|
|
35
|
+
readonly skillRefs: readonly ["journey-status"];
|
|
36
|
+
};
|
|
37
|
+
readonly executor: "companion_agent";
|
|
38
|
+
readonly approval: "approve_result";
|
|
39
|
+
readonly budget: {
|
|
40
|
+
readonly maxRuns: 5;
|
|
41
|
+
};
|
|
42
|
+
readonly onFailure: "keep_and_flag";
|
|
43
|
+
};
|
|
44
|
+
//# sourceMappingURL=playbook.definition.d.ts.map
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.expert-personas/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAsCrB,CAAC"}
|
|
@@ -0,0 +1,51 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* Canonical native declaration for this reusable application-creation method.
|
|
3
|
+
*
|
|
4
|
+
* A RUNNER-OWNED step, like `bottom_up.foundation`: the run short-circuits into the companion's
|
|
5
|
+
* expert-persona derive → accept services before any brief is composed, so this declaration's
|
|
6
|
+
* `inputs` are what the derivation READS through introspection (never a composed brief — #1434's lesson) and it has no `outputs` (the family it lands,
|
|
7
|
+
* `expert-personas`, is written by those services as per-role modules plus an aggregator, a shape the
|
|
8
|
+
* generic landing renderer must not replace; see the landing placement's own comment). It carries no
|
|
9
|
+
* evaluation treatment either: each charter is critiqued by the derivation's own multi-pass
|
|
10
|
+
* DRAFT → CRITIQUE → FINALIZE protocol, whose report is persisted beside the proposal.
|
|
11
|
+
*/
|
|
12
|
+
export const playbookDefinition = {
|
|
13
|
+
"ref": "top_down.expert-personas",
|
|
14
|
+
"version": "0.1.0",
|
|
15
|
+
"phase": "top_down",
|
|
16
|
+
"intent": "Staff every expert panel the catalog convenes: derive and accept an application-specific charter for each framework expert role that a deliberated playbook (`method.deliberation`) or a companion generation step (the logo panel) seats, grounded in the application's own vision, market, requirements, business model and brand. Idempotent: a role whose charter is committed is left alone (a human-edited charter is never overwritten), and a role whose shaping inputs have not landed yet is REPORTED as waiting rather than failing the run. Before this step existed the panel's staffing was not a journey step at all — every deliberated playbook failed closed at bind time on an application whose charters nobody had curled in by hand (#572).",
|
|
17
|
+
"preconditions": [
|
|
18
|
+
/*
|
|
19
|
+
* READINESS on the two families FOUR of the five role templates read (`shapingInputKinds` measured over
|
|
20
|
+
* `EXPERT_ROLE_TEMPLATES` on 2026-09-22: information-architect, art-director, brand-strategist and
|
|
21
|
+
* copy-chief all name VISION and MARKET; design-system-guardian names BRAND and DESIGN_SYSTEM only). The
|
|
22
|
+
* gate is a convenience, not a necessity: without it the step would be eligible on an empty application
|
|
23
|
+
* and derive nothing, since every other shaping input is checked PER ROLE at run time and a role whose
|
|
24
|
+
* inputs are missing is reported as waiting. The guardian waits on the brand, which lands after both.
|
|
25
|
+
*/
|
|
26
|
+
{ "kind": "artifact_exists", "selector": { "family": "vision-brief" } },
|
|
27
|
+
{ "kind": "artifact_exists", "selector": { "family": "market-snapshot" } }
|
|
28
|
+
],
|
|
29
|
+
/*
|
|
30
|
+
* The two families EVERY role's derivation reads (the derivation agent's shaping briefs are rendered
|
|
31
|
+
* from them through introspection, not through a composed brief) — declared so the readiness gates
|
|
32
|
+
* above are honest and derived-staleness compares them (audit: readiness-gated-family-not-declared).
|
|
33
|
+
* The role-specific inputs (requirements, business model, brand) are read the same way and are NOT
|
|
34
|
+
* gates: a role missing one is reported as waiting.
|
|
35
|
+
*/
|
|
36
|
+
"inputs": [
|
|
37
|
+
{ "family": "vision-brief" },
|
|
38
|
+
{ "family": "market-snapshot" }
|
|
39
|
+
],
|
|
40
|
+
"outputs": [],
|
|
41
|
+
"method": {
|
|
42
|
+
"skillRefs": ["journey-status"]
|
|
43
|
+
},
|
|
44
|
+
"executor": "companion_agent",
|
|
45
|
+
"approval": "approve_result",
|
|
46
|
+
"budget": {
|
|
47
|
+
"maxRuns": 5
|
|
48
|
+
},
|
|
49
|
+
"onFailure": "keep_and_flag"
|
|
50
|
+
};
|
|
51
|
+
//# sourceMappingURL=playbook.definition.js.map
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.expert-personas/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG;IAChC,KAAK,EAAE,0BAA0B;IACjC,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,UAAU;IACnB,QAAQ,EAAE,muBAAmuB;IAC7uB,eAAe,EAAE;QACf;;;;;;;WAOG;QACH,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,cAAc,EAAE,EAAE;QACvE,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,iBAAiB,EAAE,EAAE;KAC3E;IACD;;;;;;OAMG;IACH,QAAQ,EAAE;QACR,EAAE,QAAQ,EAAE,cAAc,EAAE;QAC5B,EAAE,QAAQ,EAAE,iBAAiB,EAAE;KAChC;IACD,SAAS,EAAE,EAAE;IACb,QAAQ,EAAE;QACR,WAAW,EAAE,CAAC,gBAAgB,CAAC;KAChC;IACD,UAAU,EAAE,iBAAiB;IAC7B,UAAU,EAAE,gBAAgB;IAC5B,QAAQ,EAAE;QACR,SAAS,EAAE,CAAC;KACb;IACD,WAAW,EAAE,eAAe;CACpB,CAAC","sourcesContent":["/**\n * Canonical native declaration for this reusable application-creation method.\n *\n * A RUNNER-OWNED step, like `bottom_up.foundation`: the run short-circuits into the companion's\n * expert-persona derive → accept services before any brief is composed, so this declaration's\n * `inputs` are what the derivation READS through introspection (never a composed brief — #1434's lesson) and it has no `outputs` (the family it lands,\n * `expert-personas`, is written by those services as per-role modules plus an aggregator, a shape the\n * generic landing renderer must not replace; see the landing placement's own comment). It carries no\n * evaluation treatment either: each charter is critiqued by the derivation's own multi-pass\n * DRAFT → CRITIQUE → FINALIZE protocol, whose report is persisted beside the proposal.\n */\nexport const playbookDefinition = {\n \"ref\": \"top_down.expert-personas\",\n \"version\": \"0.1.0\",\n \"phase\": \"top_down\",\n \"intent\": \"Staff every expert panel the catalog convenes: derive and accept an application-specific charter for each framework expert role that a deliberated playbook (`method.deliberation`) or a companion generation step (the logo panel) seats, grounded in the application's own vision, market, requirements, business model and brand. Idempotent: a role whose charter is committed is left alone (a human-edited charter is never overwritten), and a role whose shaping inputs have not landed yet is REPORTED as waiting rather than failing the run. Before this step existed the panel's staffing was not a journey step at all — every deliberated playbook failed closed at bind time on an application whose charters nobody had curled in by hand (#572).\",\n \"preconditions\": [\n /*\n * READINESS on the two families FOUR of the five role templates read (`shapingInputKinds` measured over\n * `EXPERT_ROLE_TEMPLATES` on 2026-09-22: information-architect, art-director, brand-strategist and\n * copy-chief all name VISION and MARKET; design-system-guardian names BRAND and DESIGN_SYSTEM only). The\n * gate is a convenience, not a necessity: without it the step would be eligible on an empty application\n * and derive nothing, since every other shaping input is checked PER ROLE at run time and a role whose\n * inputs are missing is reported as waiting. The guardian waits on the brand, which lands after both.\n */\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"vision-brief\" } },\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"market-snapshot\" } }\n ],\n /*\n * The two families EVERY role's derivation reads (the derivation agent's shaping briefs are rendered\n * from them through introspection, not through a composed brief) — declared so the readiness gates\n * above are honest and derived-staleness compares them (audit: readiness-gated-family-not-declared).\n * The role-specific inputs (requirements, business model, brand) are read the same way and are NOT\n * gates: a role missing one is reported as waiting.\n */\n \"inputs\": [\n { \"family\": \"vision-brief\" },\n { \"family\": \"market-snapshot\" }\n ],\n \"outputs\": [],\n \"method\": {\n \"skillRefs\": [\"journey-status\"]\n },\n \"executor\": \"companion_agent\",\n \"approval\": \"approve_result\",\n \"budget\": {\n \"maxRuns\": 5\n },\n \"onFailure\": \"keep_and_flag\"\n} as const;\n"]}
|
|
@@ -1,4 +1,5 @@
|
|
|
1
|
-
import { MetaWorkflow_ApprovalPolicy, MetaWorkflow_FailurePolicy,
|
|
1
|
+
import { MetaWorkflow_ApprovalPolicy, MetaWorkflow_FailurePolicy, MetaWorkflow_PredicateKind } from '@wildo-ai/saas-models/meta-workflows';
|
|
2
|
+
import { MetaWorkflow_Phase } from '@wildo-ai/saas-specifications/application-creation';
|
|
2
3
|
/**
|
|
3
4
|
* The market-analysis UMBRELLA — a composite, not a producer.
|
|
4
5
|
*
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.market-analysis/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,0BAA0B,EAC1B,
|
|
1
|
+
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.market-analysis/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,0BAA0B,EAC1B,0BAA0B,EAC3B,MAAM,sCAAsC,CAAC;AAC9C,OAAO,EACL,kBAAkB,EAEnB,MAAM,oDAAoD,CAAC;AAE5D;;;;;;;;;;;;;;;;;;GAkBG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;CA6D9B,CAAC"}
|
|
@@ -1,4 +1,5 @@
|
|
|
1
|
-
import { MetaWorkflow_ApprovalPolicy, MetaWorkflow_FailurePolicy,
|
|
1
|
+
import { MetaWorkflow_ApprovalPolicy, MetaWorkflow_FailurePolicy, MetaWorkflow_PredicateKind, } from '@wildo-ai/saas-models/meta-workflows';
|
|
2
|
+
import { MetaWorkflow_Phase, } from '@wildo-ai/saas-specifications/application-creation';
|
|
2
3
|
/**
|
|
3
4
|
* The market-analysis UMBRELLA — a composite, not a producer.
|
|
4
5
|
*
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.market-analysis/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,0BAA0B,EAC1B,
|
|
1
|
+
{"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.market-analysis/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,0BAA0B,EAC1B,0BAA0B,GAC3B,MAAM,sCAAsC,CAAC;AAC9C,OAAO,EACL,kBAAkB,GAEnB,MAAM,oDAAoD,CAAC;AAE5D;;;;;;;;;;;;;;;;;;GAkBG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG;IAChC,GAAG,EAAE,0BAA0B;IAC/B,OAAO,EAAE,OAAO;IAChB,KAAK,EAAE,kBAAkB,CAAC,QAAQ;IAClC,MAAM,EACJ,6SAA6S;IAC/S,aAAa,EAAE;QACb,EAAE,IAAI,EAAE,0BAA0B,CAAC,cAAc,EAAE,QAAQ,EAAE,EAAE,MAAM,EAAE,cAAc,EAAE,EAAE;KAC1F;IACD,MAAM,EAAE,CAAC,EAAE,MAAM,EAAE,cAAc,EAAE,CAAC;IACpC,kGAAkG;IAClG,qGAAqG;IACrG,qBAAqB;IACrB,EAAE;IACF,oGAAoG;IACpG,oGAAoG;IACpG,mFAAmF;IACnF,kGAAkG;IAClG,8FAA8F;IAC9F,sEAAsE;IACtE,OAAO,EAAE,EAAE;IACX,MAAM,EAAE;QACN,SAAS,EAAE,CAAC,gBAAgB,EAAE,2BAA2B,CAAC;QAC1D,YAAY,EAAE;YACZ;;;;eAIG;YACH,MAAM,EAAE;gBACN,kCAAkC;gBAClC,0BAA0B;gBAC1B,mCAAmC;aACpC;YACD;;;;;;;;;;eAUG;YACH,iBAAiB,EAAE,EAAE;YACrB,6FAA6F;YAC7F,mFAAmF;YACnF,wBAAwB,EAAE,CAAC;YAC3B,6FAA6F;YAC7F,6EAA6E;YAC7E,4FAA4F;YAC5F,mFAAmF;YACnF,iBAAiB,EAAE,SAAS;SAC7B;KACF;IACD,QAAQ,EAAE,2BAA2B,CAAC,cAAc;IACpD,MAAM,EAAE,EAAE;IACV,SAAS,EAAE,0BAA0B,CAAC,aAAa;CAGpD,CAAC","sourcesContent":["import {\n MetaWorkflow_ApprovalPolicy,\n MetaWorkflow_FailurePolicy,\n MetaWorkflow_PredicateKind,\n} from '@wildo-ai/saas-models/meta-workflows';\nimport {\n MetaWorkflow_Phase,\n type MetaWorkflowPlaybookAuthoring,\n} from '@wildo-ai/saas-specifications/application-creation';\n\n/**\n * The market-analysis UMBRELLA — a composite, not a producer.\n *\n * It keeps the `top_down.market-analysis` ref deliberately: downstream gates on the FAMILY\n * (`top_down.phase-gate` requires `artifact_valid: market-snapshot`), never on a playbook ref, so the\n * producing work could move to a child without a single downstream edit. The ref is also what a\n * creator asks for by name.\n *\n * ## What changed, and why it is not a workflow\n *\n * This playbook used to be a single generation call whose intent claimed derivation from \"sealed\n * research evidence\" while nothing anywhere supplied evidence and its own method admitted it. It is\n * now three children — gather, judge, produce — and the ORDER between them is nowhere in this file.\n * `admits` is a set. Order comes from the children's own preconditions, re-evaluated every iteration\n * against the tree and against what siblings have returned, plus the model's choice among whatever is\n * eligible. That is what makes re-search possible at all: when the gate returns INSUFFICIENT, produce\n * stays ineligible and research becomes the reasonable choice again — with an objective aimed at the\n * gaps the gate named, not a repeat of the first one.\n */\nexport const playbookDefinition = {\n ref: 'top_down.market-analysis',\n version: '0.2.0',\n phase: MetaWorkflow_Phase.TOP_DOWN,\n intent:\n 'Produce the market snapshot by gathering EVIDENCE, judging whether it is enough, and deriving the snapshot only once it is. An umbrella: it authors nothing itself — its deliverable is what its children land, and the order between them is decided by their own preconditions rather than declared here.',\n preconditions: [\n { kind: MetaWorkflow_PredicateKind.ARTIFACT_VALID, selector: { family: 'vision-brief' } },\n ],\n inputs: [{ family: 'vision-brief' }],\n // Nothing. A composite's deliverable is what its children land; declaring its child's output here\n // would be two playbooks claiming one family and a landing path expecting THIS run to produce a file\n // it never produces.\n //\n // It stays empty, and the loop no longer reads that emptiness as \"writes nothing\": the disjointness\n // admission resolves a lane's write scope TRANSITIVELY through `admits`, so this playbook is scoped\n // to `market-snapshot` and cannot be admitted beside `top_down.value-proposition`,\n // `top_down.capability-map` or its own producing child. An earlier version of this comment argued\n // that declaring the output would force the admission to \"choose between a parent and its own\n // child\" — which is precisely the choice it must make, and could not.\n outputs: [],\n method: {\n skillRefs: ['journey-status', 'market-authoring-overview'],\n choreography: {\n /*\n * UNORDERED. Listed produce-first on purpose: if anything ever read this array as a sequence\n * the composite would try to author a snapshot before any evidence existed, and the run would\n * fail loudly rather than silently degrading.\n */\n admits: [\n 'top_down.market-snapshot-produce',\n 'top_down.market-research',\n 'top_down.market-evidence-adequacy',\n ],\n /*\n * MEASURED, not guessed (wonder-crm run 5, 2026-08-29). That run needed\n * research → judge(INSUFFICIENT) → research → research → judge(ADEQUATE) → produce: the\n * adequacy loop consumed FIVE of six iterations and produce landed on the last one, stopping on\n * the ceiling rather than on a decision. A run needing one more re-search cycle would have spent\n * the evidence gathering and landed nothing.\n *\n * At ~168s per iteration the WALL CLOCK was the real constraint, not this count — eight\n * iterations would have exceeded the old 20-minute breaker, so raising one without the other\n * would have changed nothing. Both moved together.\n */\n maximumIterations: 10,\n // Breadth-first: research is the case where several lanes with DIFFERENT invented objectives\n // (category, competitors, pricing, buyers) beat one lane asked everything at once.\n maximumLanesPerIteration: 3,\n // A literal: playbook definitions are read by an effect-free evaluator that does not compute\n // expressions, so `20 * 60_000` is not something it can resolve. 20 minutes.\n // 40 minutes: ~10 iterations at the measured 168s, with headroom. A breaker, not a budget —\n // it exists to stop a loop spinning, never to refuse work for want of spend (D11).\n maximumDurationMs: 2_400_000,\n },\n },\n approval: MetaWorkflow_ApprovalPolicy.APPROVE_RESULT,\n budget: {},\n onFailure: MetaWorkflow_FailurePolicy.KEEP_AND_FLAG,\n} satisfies Omit<MetaWorkflowPlaybookAuthoring, 'method'> & {\n method: Omit<NonNullable<MetaWorkflowPlaybookAuthoring['method']>, 'guidance'>;\n};\n"]}
|
|
@@ -1,4 +1,5 @@
|
|
|
1
|
-
import { MetaWorkflow_ApprovalPolicy, MetaWorkflow_Executor, MetaWorkflow_FailurePolicy,
|
|
1
|
+
import { MetaWorkflow_ApprovalPolicy, MetaWorkflow_Executor, MetaWorkflow_FailurePolicy, MetaWorkflow_PredicateKind } from '@wildo-ai/saas-models/meta-workflows';
|
|
2
|
+
import { MetaWorkflow_Phase } from '@wildo-ai/saas-specifications/application-creation';
|
|
2
3
|
export declare const playbookDefinition: {
|
|
3
4
|
ref: string;
|
|
4
5
|
version: string;
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.market-evidence-adequacy/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,qBAAqB,EACrB,0BAA0B,EAC1B,
|
|
1
|
+
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/top_down.market-evidence-adequacy/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,qBAAqB,EACrB,0BAA0B,EAC1B,0BAA0B,EAC3B,MAAM,sCAAsC,CAAC;AAC9C,OAAO,EACL,kBAAkB,EAEnB,MAAM,oDAAoD,CAAC;AAE5D,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;CA6B9B,CAAC"}
|