@wildo-ai/framework-knowledge 1.1.4 → 1.1.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
- package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.definitions.js +227 -6
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/framework-knowledge.loader.d.ts +19 -0
- package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.loader.js +47 -1
- package/dist/esm/framework-knowledge.loader.js.map +1 -1
- package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.schemas.js.map +1 -1
- package/dist/esm/index.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts +125 -0
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +177 -0
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +213 -7
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +326 -8
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +5 -3
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +21 -14
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts +57 -0
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js +63 -0
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +132 -0
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +179 -0
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts +67 -0
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js +76 -0
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +5 -4
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +10 -5
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +67 -0
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +82 -0
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +25 -9
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +124 -7
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts +67 -0
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +83 -0
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts +69 -0
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js +71 -0
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +71 -0
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +88 -0
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts +97 -0
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js +156 -0
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts +115 -0
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +152 -0
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +188 -8
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +167 -9
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +171 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +146 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts +248 -0
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js +248 -0
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +157 -4
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +172 -4
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +5 -4
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +8 -7
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +3 -2
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +22 -3
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +5 -3
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +21 -12
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +192 -27
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +172 -33
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +2 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +6 -2
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +182 -5
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +191 -5
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts +2 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +3 -2
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +154 -0
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js +214 -0
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +44 -0
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +51 -0
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +2 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +2 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts +2 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +6 -2
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts +2 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.js +2 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +2 -2
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +7 -3
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +32 -4
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +27 -3
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -2
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +4 -2
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +199 -0
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +227 -0
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +5 -3
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +18 -4
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +155 -4
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +187 -4
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +6 -5
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +18 -17
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -0
- package/dist/knowledge/manifest.json +9 -8
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +75 -0
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +43 -0
- package/dist/knowledge/playbooks/bottom_up.build/method.md +79 -0
- package/dist/knowledge/playbooks/bottom_up.build/playbook.json +65 -0
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +1122 -76
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +49 -13
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +671 -47
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +10 -16
- package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +31 -35
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +10 -16
- package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +95 -0
- package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +62 -0
- package/dist/knowledge/playbooks/bottom_up.conception/method.md +80 -0
- package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +90 -0
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +107 -0
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +70 -0
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +8 -8
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +14 -13
- package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +165 -0
- package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +74 -0
- package/dist/knowledge/playbooks/bottom_up.foundation/method.md +219 -140
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +55 -22
- package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +138 -0
- package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +70 -0
- package/dist/knowledge/playbooks/bottom_up.maturity-reading/method.md +87 -0
- package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +69 -0
- package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +236 -0
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +63 -0
- package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +116 -0
- package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +79 -0
- package/dist/knowledge/playbooks/cross_cutting.application-creation/method.md +71 -0
- package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +70 -0
- package/dist/knowledge/playbooks/cross_cutting.compliance/method.md +83 -0
- package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +68 -0
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +873 -15
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +19 -12
- package/dist/knowledge/playbooks/refinement.document-facts/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/refinement.document-facts/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +186 -21
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +12 -16
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/method.md +343 -0
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +54 -0
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.brand-identity/method.md +28 -11
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +15 -17
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +8 -15
- package/dist/knowledge/playbooks/top_down.capability-map/method.md +25 -49
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +14 -17
- package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +41 -0
- package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +101 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +209 -0
- package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +68 -0
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +61 -0
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +42 -0
- package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +39 -12
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +18 -66
- package/dist/knowledge/playbooks/top_down.compliance-research/method.md +78 -0
- package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +43 -0
- package/dist/knowledge/playbooks/top_down.definition/method.md +103 -0
- package/dist/knowledge/playbooks/top_down.definition/playbook.json +75 -0
- package/dist/knowledge/playbooks/top_down.expert-personas/method.md +56 -0
- package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +48 -0
- package/dist/knowledge/playbooks/top_down.market-analysis/method.md +51 -165
- package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +25 -44
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +56 -0
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +43 -0
- package/dist/knowledge/playbooks/top_down.market-research/method.md +68 -0
- package/dist/knowledge/playbooks/top_down.market-research/playbook.json +45 -0
- package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +247 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +71 -0
- package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.phase-gate/method.md +36 -69
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +12 -9
- package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +11 -7
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +12 -16
- package/dist/knowledge/playbooks/top_down.risk-register/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.risk-register/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.risk-register/method.md +46 -0
- package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +59 -0
- package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +12 -5
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +15 -17
- package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.value-proposition/method.md +23 -14
- package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +12 -17
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +7 -3
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +13 -17
- package/dist/knowledge/references/acp.execution-profile.md +266 -0
- package/dist/knowledge/references/acp.host-configuration-inheritance.md +29 -0
- package/dist/knowledge/references/acp.permission-ceiling.md +105 -0
- package/dist/knowledge/references/acp.permission-escalation.md +37 -0
- package/dist/knowledge/references/application-documentation-chapters.config.md +152 -0
- package/dist/knowledge/references/application-documentation-plan.config.md +136 -0
- package/dist/knowledge/references/application-maturity.config.md +319 -0
- package/dist/knowledge/references/assertions.authored-metadata.config.md +1 -1
- package/dist/knowledge/references/assertions.specification.config.md +1 -1
- package/dist/knowledge/references/brand.asset.config.md +8 -16
- package/dist/knowledge/references/brand.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/brand.logo-direction.config.md +9 -7
- package/dist/knowledge/references/brand.snapshot.config.md +16 -2
- package/dist/knowledge/references/brand.snapshot.validation.md +0 -7
- package/dist/knowledge/references/build-plan.task-graph.config.md +581 -7
- package/dist/knowledge/references/business-model.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/business-model.pricing-plan.config.md +1 -1
- package/dist/knowledge/references/business-model.snapshot.validation.md +15 -0
- package/dist/knowledge/references/capability-composition.config.md +155 -0
- package/dist/knowledge/references/cli.market.utils.md +1 -0
- package/dist/knowledge/references/companion.technical-doc.service.md +453 -98
- package/dist/knowledge/references/engine.client-bundle.allow-list.md +21 -0
- package/dist/knowledge/references/engine.client-bundle.external-connectors-public.discipline.md +20 -1
- package/dist/knowledge/references/engine.saas-technical-doc.config.md +8 -4
- package/dist/knowledge/references/engine.saas-website.config.md +22 -10
- package/dist/knowledge/references/example.backend.addon-wiring.module.md +8 -12
- package/dist/knowledge/references/example.config.app-shell.full.md +42 -7
- package/dist/knowledge/references/example.config.backend.required-floors.md +4 -0
- package/dist/knowledge/references/example.config.design-system.full.md +3 -0
- package/dist/knowledge/references/example.engine.product-definitions.feature-and-profiles.md +19 -7
- package/dist/knowledge/references/example.features.connected-feature.declaration.md +66 -0
- package/dist/knowledge/references/example.features.connected-feature.surface.md +42 -0
- package/dist/knowledge/references/example.flows-actors.chat-assistant.md +4 -3
- package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +6 -10
- package/dist/knowledge/references/example.guidance.bound-survey-flow.md +82 -0
- package/dist/knowledge/references/example.infra.environment-config.local.md +88 -11
- package/dist/knowledge/references/example.milestones.module-definitions.md +73 -0
- package/dist/knowledge/references/example.minion.contained-tick.md +79 -0
- package/dist/knowledge/references/example.module.companion-exports.full.md +38 -3
- package/dist/knowledge/references/example.provider.backend-module-shape.md +31 -13
- package/dist/knowledge/references/example.provider.frontend-app.module.md +103 -0
- package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +20 -0
- package/dist/knowledge/references/example.provider.frontend-file-picker.module.md +7 -3
- package/dist/knowledge/references/example.provider.operation.backend-typed-client.md +30 -0
- package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +11 -0
- package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +3 -0
- package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +94 -10
- package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +79 -0
- package/dist/knowledge/references/example.spec.frontend-component.prop-vocabulary.md +18 -0
- package/dist/knowledge/references/example.worker.node-route.md +94 -0
- package/dist/knowledge/references/experience-plan.config.md +311 -0
- package/dist/knowledge/references/external-connectors.app.frontend-provider-module.md +132 -9
- package/dist/knowledge/references/external-connectors.backend.provider-package-convention.md +36 -0
- package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +269 -0
- package/dist/knowledge/references/integration-plan.config.md +185 -0
- package/dist/knowledge/references/market.alternative.config.md +1 -1
- package/dist/knowledge/references/market.authored-metadata.config.md +12 -9
- package/dist/knowledge/references/market.channel.config.md +3 -3
- package/dist/knowledge/references/market.feature-benefit.config.md +1 -1
- package/dist/knowledge/references/market.gain.config.md +1 -1
- package/dist/knowledge/references/market.icp.config.md +2 -2
- package/dist/knowledge/references/market.job.config.md +1 -1
- package/dist/knowledge/references/market.message-template.config.md +2 -2
- package/dist/knowledge/references/market.objection.config.md +1 -1
- package/dist/knowledge/references/market.pain.config.md +1 -1
- package/dist/knowledge/references/market.persona.config.md +2 -2
- package/dist/knowledge/references/market.proof.config.md +1 -1
- package/dist/knowledge/references/market.snapshot.validation.md +15 -0
- package/dist/knowledge/references/market.tone-of-voice.config.md +1 -1
- package/dist/knowledge/references/market.trigger.config.md +1 -1
- package/dist/knowledge/references/minions.tick-contract.md +83 -0
- package/dist/knowledge/references/placement-plan.config.md +369 -0
- package/dist/knowledge/references/platform.config.application-database.md +5 -2
- package/dist/knowledge/references/platform.config.backing-services.md +0 -21
- package/dist/knowledge/references/platform.config.environment.deployment.md +206 -14
- package/dist/knowledge/references/platform.config.infra-provider-resolution.md +170 -0
- package/dist/knowledge/references/platform.config.infrastructure-host.md +87 -0
- package/dist/knowledge/references/platform.config.saas.md +261 -9
- package/dist/knowledge/references/presets.models.labelling.sections.md +14 -0
- package/dist/knowledge/references/presets.models.surface-policy.md +19 -10
- package/dist/knowledge/references/requirements.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/requirements.snapshot.validation.md +15 -0
- package/dist/knowledge/references/roadmap.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/roadmap.snapshot.validation.md +15 -7
- package/dist/knowledge/references/saas.backend.a2a.token-budget.md +71 -0
- package/dist/knowledge/references/saas.backend.app-config.backend-authored.md +1 -2
- package/dist/knowledge/references/saas.backend.auth.federated-identity-provider-private-networks.md +62 -0
- package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +86 -0
- package/dist/knowledge/references/saas.backend.billing.catalog-sync-result.md +37 -0
- package/dist/knowledge/references/saas.backend.billing.resolution-failure-reasons.md +24 -5
- package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +187 -0
- package/dist/knowledge/references/saas.backend.domain-module.md +25 -1
- package/dist/knowledge/references/saas.backend.error-builder.user-guidance.md +82 -0
- package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +6 -0
- package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +22 -4
- package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +17 -4
- package/dist/knowledge/references/saas.backend.flows-actors.tool-dispatch-obligations.md +84 -0
- package/dist/knowledge/references/saas.backend.health-readiness-contributor.md +73 -0
- package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +200 -0
- package/dist/knowledge/references/saas.backend.providers.operation-executor.md +51 -0
- package/dist/knowledge/references/saas.backend.providers.optional-runtime-peers.md +71 -0
- package/dist/knowledge/references/saas.backend.queue.worker-topology.md +39 -0
- package/dist/knowledge/references/saas.backend.system-access-service.md +51 -42
- package/dist/knowledge/references/saas.composition.scenario-apply.md +51 -0
- package/dist/knowledge/references/saas.config.content-security-policy.md +97 -0
- package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +91 -21
- package/dist/knowledge/references/saas.data-seeding.definition-input.md +4 -0
- package/dist/knowledge/references/saas.external-providers.backend-provider-loader.md +38 -0
- package/dist/knowledge/references/saas.external-providers.backend-provider-registry.runtime-filter.md +27 -27
- package/dist/knowledge/references/saas.external-providers.llm.model-configuration.md +65 -16
- package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +41 -11
- package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +44 -8
- package/dist/knowledge/references/saas.frontend.billing-context.md +108 -0
- package/dist/knowledge/references/saas.frontend.brand-identity.md +38 -0
- package/dist/knowledge/references/saas.frontend.celebration-overlay-contract.md +41 -0
- package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +64 -0
- package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +34 -0
- package/dist/knowledge/references/saas.frontend.errors.user-facing-error-message.md +47 -0
- package/dist/knowledge/references/saas.frontend.execution-view.action-status-contract.per-action-retry-loop.md +7 -1
- package/dist/knowledge/references/saas.frontend.execution-view.definition.md +3 -3
- package/dist/knowledge/references/saas.frontend.flows-actors-view.md +7 -4
- package/dist/knowledge/references/saas.frontend.form-fields.file-provider-constraints.md +30 -48
- package/dist/knowledge/references/saas.frontend.full-custom-view.definition.md +24 -0
- package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +45 -0
- package/dist/knowledge/references/saas.frontend.onboarding-view.md +84 -0
- package/dist/knowledge/references/saas.frontend.providers.execute-operation.md +65 -0
- package/dist/knowledge/references/saas.frontend.public-shell.identity-mode.md +65 -0
- package/dist/knowledge/references/saas.frontend.resource-header-title.md +28 -4
- package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +127 -1
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +327 -11
- package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +198 -0
- package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +220 -0
- package/dist/knowledge/references/saas.market.generation-agent.md +26 -9
- package/dist/knowledge/references/saas.models.analytics.value-moments.md +132 -0
- package/dist/knowledge/references/saas.models.audit.trail-config.md +155 -0
- package/dist/knowledge/references/saas.models.auth.methods.md +513 -0
- package/dist/knowledge/references/saas.models.authorization.administrative-continuity-codes.md +82 -0
- package/dist/knowledge/references/saas.models.billing.catalog-vocabularies.md +77 -0
- package/dist/knowledge/references/saas.models.config.organization-types.md +192 -0
- package/dist/knowledge/references/saas.models.config.registration.md +188 -0
- package/dist/knowledge/references/saas.models.config.tenant-teardown.md +81 -0
- package/dist/knowledge/references/saas.models.data-mode-read-list.md +173 -3
- package/dist/knowledge/references/saas.models.email.template-type.md +40 -0
- package/dist/knowledge/references/saas.models.engine-capabilities.md +85 -7
- package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +61 -0
- package/dist/knowledge/references/saas.models.external-data-pipeline.md +43 -4
- package/dist/knowledge/references/saas.models.features.definition-builders.md +162 -0
- package/dist/knowledge/references/saas.models.file-upload-grant.md +222 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-definition.md +54 -5
- package/dist/knowledge/references/saas.models.governed-document-acceptance-mode.md +116 -0
- package/dist/knowledge/references/saas.models.guidance-flow.md +160 -0
- package/dist/knowledge/references/saas.models.http-api-binding.md +76 -110
- package/dist/knowledge/references/saas.models.milestone-celebration.md +69 -0
- package/dist/knowledge/references/saas.models.milestone-definition.md +209 -0
- package/dist/knowledge/references/saas.models.navigation.layout.md +2 -2
- package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +124 -0
- package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +99 -0
- package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +150 -0
- package/dist/knowledge/references/saas.models.notifications.badge-vocabularies.md +70 -0
- package/dist/knowledge/references/saas.models.notifications.targets.md +138 -0
- package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +256 -0
- package/dist/knowledge/references/saas.models.onboarding-elements.md +375 -0
- package/dist/knowledge/references/saas.models.onboarding-trigger.md +52 -0
- package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +50 -0
- package/dist/knowledge/references/saas.models.organizations.application-owner-codes.md +129 -0
- package/dist/knowledge/references/saas.models.privacy.client-instance-id-scope.md +49 -0
- package/dist/knowledge/references/saas.models.privacy.redaction-treatments.md +106 -0
- package/dist/knowledge/references/saas.models.progression-tracker-variant.md +76 -0
- package/dist/knowledge/references/saas.models.provider-capabilities.md +8 -5
- package/dist/knowledge/references/saas.models.providers.browser-operation-policy.md +72 -0
- package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +50 -0
- package/dist/knowledge/references/saas.models.providers.capability-surface.md +58 -0
- package/dist/knowledge/references/saas.models.providers.compliance-choice.md +111 -0
- package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +156 -0
- package/dist/knowledge/references/saas.models.rate-limit-configuration.md +11 -1
- package/dist/knowledge/references/saas.models.relationship-handling-settings.md +23 -1
- package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +122 -4
- package/dist/knowledge/references/saas.models.resource-config.forwarded-label.md +5 -4
- package/dist/knowledge/references/saas.models.resource-config.metered-usage-recording.md +69 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +15 -2
- package/dist/knowledge/references/saas.models.resource-config.operation-auditable-event.md +66 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-base.md +24 -1
- package/dist/knowledge/references/saas.models.resource-config.operation-cron-job.md +59 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-idempotency-key.md +55 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-mcp-exposure.md +5 -4
- package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +158 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-step-up.md +77 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +42 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-variant-for-key.md +6 -1
- package/dist/knowledge/references/saas.models.resource-config.queue-policy.md +49 -0
- package/dist/knowledge/references/saas.models.resource-config.required-features.md +84 -0
- package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +10 -0
- package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +14 -0
- package/dist/knowledge/references/saas.models.resource-config.system-access-policy.md +111 -4
- package/dist/knowledge/references/saas.models.resource-config.system-managed-fields.md +39 -0
- package/dist/knowledge/references/saas.models.resource-operation-display-risk.md +48 -0
- package/dist/knowledge/references/saas.models.resource-operation-variant-runtime.md +38 -0
- package/dist/knowledge/references/saas.models.resource-primary-scope.md +11 -2
- package/dist/knowledge/references/saas.models.scope-membership.md +3 -4
- package/dist/knowledge/references/saas.models.shared-saas-module.md +25 -0
- package/dist/knowledge/references/saas.models.systems-of-record.md +635 -0
- package/dist/knowledge/references/saas.public-runtime.contract.md +198 -1
- package/dist/knowledge/references/saas.rag.retrieval-result.md +19 -8
- package/dist/knowledge/references/saas.specifications.application-authored-document-fact-specification.contract.md +29 -0
- package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +15 -36
- package/dist/knowledge/references/saas.specifications.application-document-publication.contract.md +9 -5
- package/dist/knowledge/references/saas.specifications.application-document-publication.generation.md +63 -0
- package/dist/knowledge/references/saas.specifications.application-document-release-set.contract.md +74 -0
- package/dist/knowledge/references/saas.specifications.assurance-control-markers.md +123 -0
- package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +88 -7
- package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +774 -53
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +211 -14
- package/dist/knowledge/references/saas.specifications.composite-view-specification.md +10 -0
- package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +364 -0
- package/dist/knowledge/references/saas.specifications.playbook-approval-and-failure-policies.md +96 -0
- package/dist/knowledge/references/saas.specifications.processor-register.md +333 -0
- package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +8 -0
- package/dist/knowledge/references/saas.specifications.resource-spec-config.md +22 -0
- package/dist/knowledge/references/saas.website.astro.bridge.md +64 -2
- package/dist/knowledge/references/saas.website.astro.head-renderer.md +32 -12
- package/dist/knowledge/references/saas.website.astro.label-loader.md +3 -0
- package/dist/knowledge/references/saas.website.astro.robots-renderer.md +14 -1
- package/dist/knowledge/references/saas.website.blog.bridge.md +21 -1
- package/dist/knowledge/references/saas.website.consent.banner.md +218 -0
- package/dist/knowledge/references/saas.website.consent.context.md +162 -0
- package/dist/knowledge/references/saas.website.consent.gate.md +38 -0
- package/dist/knowledge/references/saas.website.page-layout.component.md +67 -1
- package/dist/knowledge/references/saas.website.page.context.md +4 -3
- package/dist/knowledge/references/saas.website.runtime.context.md +43 -7
- package/dist/knowledge/references/saas.website.section.context.md +3 -2
- package/dist/knowledge/references/saas.website.sections.category-enum.md +19 -20
- package/dist/knowledge/references/vision.authored-metadata.config.md +2 -2
- package/dist/knowledge/references/website-plan.config.md +205 -0
- package/dist/knowledge/references/workers.node.worker-init-contract.md +57 -0
- package/dist/knowledge/references/zod.decorators.chainable-runtime.md +43 -2
- package/dist/knowledge/references/zod.decorators.data-categories.md +197 -0
- package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +51 -4
- package/dist/knowledge/references/zod.decorators.display-edit-modes.md +54 -1
- package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +35 -0
- package/dist/knowledge/references/zod.decorators.field-spec-params.md +32 -5
- package/dist/knowledge/references/zod.decorators.file-nature-constraints.md +86 -0
- package/dist/knowledge/references/zod.decorators.file-readiness-metadata.md +67 -0
- package/dist/knowledge/references/zod.decorators.file-schema.md +90 -14
- package/dist/knowledge/references/zod.decorators.file-vocabularies.md +84 -0
- package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +140 -4
- package/dist/knowledge/references/zod.decorators.primitive-ui.md +3 -0
- package/dist/knowledge/references/zod.decorators.rag-source.md +6 -2
- package/dist/knowledge/references/zod.decorators.schema-metadata.md +24 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +35 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-params.md +46 -12
- package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +31 -12
- package/dist/knowledge/references/zod.factories.address.md +118 -0
- package/dist/knowledge/references/zod.factories.code.md +2 -0
- package/dist/knowledge/references/zod.factories.duration.md +2 -0
- package/dist/knowledge/references/zod.factories.money.md +2 -0
- package/dist/knowledge/references/zod.factories.phone.md +14 -1
- package/dist/knowledge/registries/assurance-authority-bases.json +3 -2
- package/dist/knowledge/registries/framework-topics.json +1215 -11
- package/dist/knowledge/registries/playbooks.json +454 -50
- package/dist/knowledge/registries/source-tags.json +3153 -1043
- package/dist/knowledge/rules/database-migration-obligation.md +110 -0
- package/dist/knowledge/rules/live-context-door.md +108 -0
- package/dist/knowledge/rules/resource-schema-awareness.md +75 -0
- package/dist/knowledge/skills/INDEX.md +46 -11
- package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +80 -37
- package/dist/knowledge/skills/application-consumer-documentation-authoring/references/framework-documentation-chapters-api.md +167 -0
- package/dist/knowledge/skills/application-consumer-documentation-authoring/references/source-and-ownership-routing.md +6 -3
- package/dist/knowledge/skills/application-database-migrations/SKILL.md +10 -3
- package/dist/knowledge/skills/application-database-migrations/references/framework-application-database-api.md +5 -2
- package/dist/knowledge/skills/application-database-migrations/references/migration-refusals.md +32 -0
- package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +94 -3
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +50 -0
- package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +26 -19
- package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +25 -1
- package/dist/knowledge/skills/backend-addon-wiring/references/framework-readiness-contributor-api.md +135 -0
- package/dist/knowledge/skills/backend-custom-operation/SKILL.md +75 -12
- package/dist/knowledge/skills/backend-custom-operation/references/framework-assurance-control-markers.md +137 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-error-user-guidance-api.md +112 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-operation-base-and-path-api.md +72 -1
- package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +207 -0
- package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +31 -1
- package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-asset-api.md +8 -16
- package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-snapshot-api.md +25 -9
- package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +135 -5
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +80 -17
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +369 -111
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +32 -10
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +103 -58
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-publication-contract.md +19 -13
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +142 -26
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +722 -23
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +348 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +123 -0
- package/dist/knowledge/skills/config-app-shell/SKILL.md +74 -11
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +85 -19
- package/dist/knowledge/skills/config-app-shell/references/framework-brand-identity-api.md +70 -0
- package/dist/knowledge/skills/config-app-shell/references/framework-public-shell-identity-api.md +124 -0
- package/dist/knowledge/skills/config-design-system/SKILL.md +43 -3
- package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +19 -10
- package/dist/knowledge/skills/config-design-system/references/loading-placeholder-authoring.md +47 -0
- package/dist/knowledge/skills/config-design-system/references/surface-policy-authoring.md +19 -10
- package/dist/knowledge/skills/config-navigation/SKILL.md +85 -2
- package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +98 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-layout-api.md +2 -2
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +54 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +232 -0
- package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +172 -0
- package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +146 -0
- package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +141 -0
- package/dist/knowledge/skills/config-saas/SKILL.md +86 -9
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +199 -0
- package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +179 -0
- package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +493 -0
- package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +153 -0
- package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +242 -0
- package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +161 -0
- package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +93 -12
- package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +785 -0
- package/dist/knowledge/skills/config-saas/references/framework-value-moments-api.md +172 -0
- package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +261 -9
- package/dist/knowledge/skills/config-saas/references/saas-config-scope.md +9 -0
- package/dist/knowledge/skills/config-saas-backend/SKILL.md +58 -3
- package/dist/knowledge/skills/config-saas-backend/references/framework-application-owner-organization-codes-api.md +151 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-auth-methods-api.md +579 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-backend-authored-config-api.md +8 -2
- package/dist/knowledge/skills/config-saas-backend/references/framework-federated-identity-provider-private-networks-api.md +96 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +316 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-registration-config-api.md +221 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-tenant-teardown-api.md +121 -0
- package/dist/knowledge/skills/config-saas-backend/references/managed-startup-configuration.md +46 -0
- package/dist/knowledge/skills/configure-billing/SKILL.md +27 -22
- package/dist/knowledge/skills/configure-billing/references/config-chain-and-failure-map.md +27 -15
- package/dist/knowledge/skills/configure-billing/references/example-backend-billing-enable-block.md +41 -0
- package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +36 -17
- package/dist/knowledge/skills/configure-billing/references/framework-backend-provider-reachability-api.md +30 -28
- package/dist/knowledge/skills/configure-billing/references/framework-billing-frontend-api.md +169 -0
- package/dist/knowledge/skills/configure-billing/references/framework-billing-resolution-failure-api.md +44 -11
- package/dist/knowledge/skills/configure-billing/references/framework-product-catalog-api.md +187 -0
- package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +76 -0
- package/dist/knowledge/skills/configure-coding-agent/SKILL.md +280 -0
- package/dist/knowledge/skills/configure-coding-agent/references/agent-selection.md +168 -0
- package/dist/knowledge/skills/configure-coding-agent/references/framework-acp-execution-profile-api.md +504 -0
- package/dist/knowledge/skills/email-add-template/SKILL.md +41 -69
- package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +15 -7
- package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +120 -0
- package/dist/knowledge/skills/engine-component-registration/SKILL.md +19 -12
- package/dist/knowledge/skills/engine-product-definitions/SKILL.md +54 -31
- package/dist/knowledge/skills/engine-product-definitions/references/connected-feature-workflow.md +130 -0
- package/dist/knowledge/skills/engine-product-definitions/references/framework-engine-product-definitions-api.md +25 -0
- package/dist/knowledge/skills/engine-product-definitions/references/framework-feature-builders-api.md +215 -0
- package/dist/knowledge/skills/engine-product-definitions/references/framework-metered-usage-recording-api.md +78 -0
- package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +33 -24
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +121 -0
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +4 -3
- package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +10 -8
- package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +5 -4
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +46 -9
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +34 -7
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +151 -0
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +6 -10
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +54 -5
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-operation-and-model-api.md +75 -21
- package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +258 -0
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +480 -0
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +3983 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/SKILL.md +211 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-guidance-flow-api.md +165 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-elements-api.md +381 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-trigger-api.md +57 -0
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-view-api.md +89 -0
- package/dist/knowledge/skills/i18n-label-generation/SKILL.md +13 -1
- package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +14 -0
- package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +14 -0
- package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +3 -1
- package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +14 -0
- package/dist/knowledge/skills/infra-environment-config/SKILL.md +237 -37
- package/dist/knowledge/skills/infra-environment-config/references/framework-application-database-api.md +5 -2
- package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +174 -21
- package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +206 -14
- package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +95 -0
- package/dist/knowledge/skills/journey-approve/SKILL.md +28 -8
- package/dist/knowledge/skills/journey-approve/references/specification-family-map.md +88 -0
- package/dist/knowledge/skills/journey-bootstrap-scope/SKILL.md +37 -2
- package/dist/knowledge/skills/journey-next/SKILL.md +41 -1
- package/dist/knowledge/skills/journey-report/SKILL.md +16 -3
- package/dist/knowledge/skills/journey-run/SKILL.md +92 -7
- package/dist/knowledge/skills/journey-run/references/expert-personas-and-deliberations.md +46 -0
- package/dist/knowledge/skills/journey-run/references/framework-playbook-approval-policy.md +108 -0
- package/dist/knowledge/skills/journey-status/SKILL.md +14 -4
- package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +153 -46
- package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +119 -0
- package/dist/knowledge/skills/local-environment-bootstrap/references/initialization-recovery-recipe.md +7 -4
- package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +253 -33
- package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +1 -1
- package/dist/knowledge/skills/market-add-feature-benefit/references/framework-feature-benefit-api.md +1 -1
- package/dist/knowledge/skills/market-alternatives/SKILL.md +1 -1
- package/dist/knowledge/skills/market-authoring-overview/references/framework-market-snapshot-api.md +12 -9
- package/dist/knowledge/skills/market-channels/SKILL.md +3 -3
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +226 -14
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +226 -14
- package/dist/knowledge/skills/market-generation-cli/SKILL.md +56 -9
- package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +32 -9
- package/dist/knowledge/skills/market-icp/SKILL.md +2 -2
- package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +3 -3
- package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +2 -2
- package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +17 -2
- package/dist/knowledge/skills/market-persona/SKILL.md +2 -2
- package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +2 -2
- package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +15 -0
- package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +15 -0
- package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +1 -1
- package/dist/knowledge/skills/market-triggers-and-journey/SKILL.md +1 -1
- package/dist/knowledge/skills/milestones-and-celebrations/SKILL.md +198 -0
- package/dist/knowledge/skills/milestones-and-celebrations/references/framework-celebration-overlay-contract.md +51 -0
- package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-celebration-api.md +79 -0
- package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-definition-api.md +220 -0
- package/dist/knowledge/skills/milestones-and-celebrations/references/framework-progression-tracker-api.md +86 -0
- package/dist/knowledge/skills/minion-authoring/SKILL.md +140 -0
- package/dist/knowledge/skills/minion-authoring/examples/contained-tick.example.md +84 -0
- package/dist/knowledge/skills/minion-authoring/references/framework-minion-tick-contract.md +91 -0
- package/dist/knowledge/skills/module-companion-exports/SKILL.md +38 -3
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +211 -14
- package/dist/knowledge/skills/module-registration/SKILL.md +50 -33
- package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +50 -1
- package/dist/knowledge/skills/module-registration/references/framework-notification-badges-api.md +142 -0
- package/dist/knowledge/skills/module-registration/references/registry-files.md +14 -5
- package/dist/knowledge/skills/module-relationships/SKILL.md +62 -0
- package/dist/knowledge/skills/module-relationships/references/framework-resource-relationship-authoring-api.md +26 -5
- package/dist/knowledge/skills/provider-backend-package/SKILL.md +279 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +80 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-loader-api.md +55 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-package-convention-api.md +48 -0
- package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +33 -6
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-file-provider-constraints-api.md +99 -47
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-module-api.md +241 -9
- package/dist/knowledge/skills/provider-operation-calls/SKILL.md +196 -0
- package/dist/knowledge/skills/provider-operation-calls/references/browser-door-answers.md +50 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-browser-operation-policy-api.md +80 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-frontend-execute-operation-api.md +71 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-operation-executor-api.md +58 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +275 -0
- package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +64 -11
- package/dist/knowledge/skills/rate-limit-authoring/references/fixed-window-and-environment-multiplier.md +27 -0
- package/dist/knowledge/skills/rate-limit-authoring/references/framework-rate-limit-policy-api.md +19 -6
- package/dist/knowledge/skills/resource-add-field/SKILL.md +12 -5
- package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +373 -23
- package/dist/knowledge/skills/resource-add-module/SKILL.md +116 -265
- package/dist/knowledge/skills/resource-add-module/references/framework-composition-scenarios-api.md +133 -0
- package/dist/knowledge/skills/resource-add-module/references/framework-new-module-wiring-api.md +25 -0
- package/dist/knowledge/skills/resource-add-module/references/module-scaffold-layout.md +12 -12
- package/dist/knowledge/skills/resource-add-resource/SKILL.md +26 -3
- package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +122 -4
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +25 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-administrative-continuity-codes-api.md +93 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-authority-audit-interpretation.md +136 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +85 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +133 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-idempotency-key-api.md +141 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-step-up-api.md +126 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +859 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-required-features-api.md +122 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +124 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +97 -2
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +457 -15
- package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +197 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +162 -46
- package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +452 -0
- package/dist/knowledge/skills/resource-custom-view/SKILL.md +5 -0
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +327 -11
- package/dist/knowledge/skills/resource-custom-view/references/framework-user-facing-error-message-api.md +50 -0
- package/dist/knowledge/skills/resource-external-data/SKILL.md +228 -15
- package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +54 -7
- package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +87 -113
- package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +13 -8
- package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +69 -26
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-file-upload-grant-contract.md +246 -0
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-resource-mcp-exposure-contract.md +7 -6
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-catalogue-withdrawal-and-verification.md +5 -3
- package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +43 -48
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +96 -14
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +47 -15
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-source-decorator-api.md +6 -2
- package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +32 -2
- package/dist/knowledge/skills/resource-schema-authoring/examples/basic-resource-schema.example.md +2 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/decorator-layer-map.md +17 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +75 -4
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-erasure-scrub-treatments-api.md +182 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +245 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +35 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +46 -12
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +480 -15
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-system-managed-fields-api.md +67 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +74 -14
- package/dist/knowledge/skills/resource-schema-authoring/references/polymorphic-per-scope-resources.md +28 -5
- package/dist/knowledge/skills/resource-schema-authoring/references/schema-variants-and-discriminators.md +25 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +1 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/special-factories.md +34 -0
- package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +236 -18
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +54 -1
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +35 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +327 -11
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +140 -4
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +3 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +155 -5
- package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +165 -0
- package/dist/knowledge/skills/seeding-authoring/SKILL.md +9 -1
- package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +4 -0
- package/dist/knowledge/skills/seeding-operations/SKILL.md +33 -29
- package/dist/knowledge/skills/seeding-operations/references/data-seeding-admin-runbook.md +13 -5
- package/dist/knowledge/skills/seeding-operations/references/data-seeding-cron-scheduler.md +67 -74
- package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +97 -24
- package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +205 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +205 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +229 -0
- package/dist/knowledge/skills/spec-companion-exports/SKILL.md +38 -3
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +211 -14
- package/dist/knowledge/skills/spec-component-update/SKILL.md +30 -11
- package/dist/knowledge/skills/spec-composite-view-update/references/framework-composite-view-specification-api.md +10 -0
- package/dist/knowledge/skills/spec-feature-update/SKILL.md +47 -9
- package/dist/knowledge/skills/spec-resource-update/SKILL.md +3 -0
- package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +32 -5
- package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +30 -0
- package/dist/knowledge/skills/views-add-composite-view/SKILL.md +1 -0
- package/dist/knowledge/skills/views-add-custom-view/SKILL.md +13 -2
- package/dist/knowledge/skills/views-add-custom-view/references/framework-view-scope-and-full-custom-api.md +24 -0
- package/dist/knowledge/skills/views-app-level/SKILL.md +1 -0
- package/dist/knowledge/skills/views-app-level/references/framework-view-scope-and-full-custom-api.md +24 -0
- package/dist/knowledge/skills/views-chart-authoring/SKILL.md +1 -0
- package/dist/knowledge/skills/views-composite-authoring/SKILL.md +1 -0
- package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +64 -0
- package/dist/knowledge/skills/views-execution-authoring/SKILL.md +3 -0
- package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +3 -3
- package/dist/knowledge/skills/views-execution-authoring/references/framework-user-facing-error-message-api.md +50 -0
- package/dist/knowledge/skills/website-anonymous-session/SKILL.md +43 -7
- package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +21 -1
- package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +21 -0
- package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +41 -1
- package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +735 -211
- package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +54 -7
- package/dist/knowledge/skills/website-layout-overrides/SKILL.md +67 -1
- package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +11 -0
- package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +19 -5
- package/dist/knowledge/skills/website-page-authoring/SKILL.md +94 -7
- package/dist/knowledge/skills/website-page-authoring/references/homepage-content-and-art-direction.md +126 -0
- package/dist/knowledge/skills/website-section-contact/SKILL.md +96 -146
- package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-cta/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-faq/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-hero/SKILL.md +37 -26
- package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-pricing/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-section-social-proof/SKILL.md +19 -20
- package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +19 -20
- package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +14 -1
- package/dist/knowledge/skills/worker-authoring/SKILL.md +164 -0
- package/dist/knowledge/skills/worker-authoring/examples/worker-route.example.md +98 -0
- package/dist/knowledge/skills/worker-authoring/references/framework-worker-init-contract.md +65 -0
- package/dist/knowledge/topic-index.json +5335 -1010
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/dist/tsconfig.tsbuildinfo +1 -1
- package/package.json +4 -4
- package/dist/knowledge/references/example.provider.contribution.backend-billing.md +0 -12
- package/dist/knowledge/skills/configure-billing/references/example-provider-contribution-and-backend-config.md +0 -48
- /package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/structured-artifact-action.json +0 -0
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../src/playbooks/bottom_up.foundation/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAC/B;IACE,KAAK,EAAE,sBAAsB;IAC7B,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,WAAW;IACpB,QAAQ,EAAE,87CAA87C;IACx8C,eAAe,EAAE;QACf,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,aAAa,EAAE,EAAE;QACtE,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,cAAc,EAAE,EAAE;KACxE;IACD,QAAQ,EAAE;QACR,EAAE,QAAQ,EAAE,aAAa,EAAE;QAC3B,EAAE,QAAQ,EAAE,cAAc,EAAE;QAC5B,EAAE,QAAQ,EAAE,iBAAiB,EAAE;QAC/B,EAAE,QAAQ,EAAE,gBAAgB,EAAE;QAC9B,EAAE,QAAQ,EAAE,cAAc,EAAE;QAC5B,EAAE,QAAQ,EAAE,SAAS,EAAE;KACxB;IACD,SAAS,EAAE,EAAE;IACb,QAAQ,EAAE;QACR,WAAW,EAAE;YACX,gBAAgB;YAChB,aAAa;YACb,qBAAqB;YACrB,0BAA0B;YAC1B,6BAA6B;YAC7B,iCAAiC;SAClC;QACD,aAAa,EAAE;YACb,WAAW,EAAE;gBACX;;;;;;;;;mBASG;gBACH;oBACE,KAAK,EAAE,eAAe;oBACtB,UAAU,EAAE,2NAA2N;oBACvO,MAAM,EAAE,QAAQ;oBAChB,SAAS,EAAE,CAAC,eAAe,EAAE,OAAO,CAAC;iBACtC;gBACD;;;;;;;;;;;mBAWG;gBACH;oBACE,KAAK,EAAE,kBAAkB;oBACzB,UAAU,EAAE,ogBAAogB;oBAChhB,MAAM,EAAE,WAAW;iBACpB;gBACD;oBACE,KAAK,EAAE,yBAAyB;oBAChC,UAAU,EAAE,6XAA6X;oBACzY,MAAM,EAAE,WAAW;iBACpB;aACF;SACF;KACF;IACC,UAAU,EAAE,gBAAgB;IAC9B,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 * The structured method remains intentionally rich: its intent, inputs, output\n * contracts, elicitation, deterministic verification and skill routing are the\n * application knowledge a later generic assessment loop composes. This source\n * intentionally omits the superseded per-playbook evaluation-treatment object;\n * generation records that absence rather than fabricating legacy judge behavior.\n */\nexport const playbookDefinition =\n{\n \"ref\": \"bottom_up.foundation\",\n \"version\": \"0.2.1\",\n \"phase\": \"bottom_up\",\n \"intent\": \"Bottom-up foundation — turn the approved domain plan + the top-down definition set into a configured, bootable application skeleton. Reads the domain-plan (the module decomposition + per-module resource inventory) and the vision-brief (whose compliance/vision constraints drive which engine capabilities to enable), then: (1) authors ./wildo.saas.config.ts for real — the engine capabilities (derived from compliance/vision), the modules (from the domain plan), and the providers (matched to the declared capabilities); (2) materializes the app skeleton (app/ shared-lib/ backend-api/ specifications/ + the module registries); (3) installs app-knowledge; (4) runs the deterministic bring-up — wildo setup --non-interactive, then wildo local init. This is a v1 SCAFFOLD METHOD describing the foundation SEQUENCE: skeleton materialization and app-knowledge installation remain deferred greenfield tooling, while headless setup and verified local initialization are registered commands once the app structure exists. It emits NO artifact: the deliverable is the app itself (the authored config + materialized skeleton + verified initialization), and the reasons behind each capability/module/provider choice are recorded as comments in the config the next reader opens. The foundation-manifest family it used to emit was retired 2026-08-25 with the app-creation verification/digest aspect. Runs after the domain plan is approved and the journey is in the bottom_up phase.\",\n \"preconditions\": [\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"domain-plan\" } },\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"vision-brief\" } }\n ],\n \"inputs\": [\n { \"family\": \"domain-plan\" },\n { \"family\": \"vision-brief\" },\n { \"family\": \"market-snapshot\" },\n { \"family\": \"business-model\" },\n { \"family\": \"requirements\" },\n { \"family\": \"roadmap\" }\n ],\n \"outputs\": [],\n \"method\": {\n \"skillRefs\": [\n \"journey-status\",\n \"config-saas\",\n \"module-registration\",\n \"infra-environment-config\",\n \"local-environment-bootstrap\",\n \"application-database-migrations\"\n ],\n \"elicitation\": {\n \"questions\": [\n /*\n * THE FALLBACK, since 2026-08-28. `bottom_up.domain-plan` now asks this and carries the\n * answer in the committed plan (`DomainPlanOutputSet.tenancy`), because the plan MODELS\n * tenancy — wonder-crm's invented a workspace module and a membership before anyone was\n * asked — so asking after the model is shaped lets a second answer contradict it.\n *\n * The executor reads the plan first and reaches this question only for a plan authored\n * before the field existed. Keep it: those plans are real (wonder-crm, wonder-todos) and\n * must stay composable.\n */\n {\n \"ref\": \"primary-scope\",\n \"question\": \"What is the application's tenancy model? Answer `organizations` when users collaborate inside shared workspaces/teams (this enables the ORGANIZATIONS engine capability), or `users` when every user's data is their own.\",\n \"kind\": \"choice\",\n \"options\": [\"organizations\", \"users\"]\n },\n /*\n * The operator's own legal identity (issue #235), asked HERE because this is the playbook that\n * writes `wildo.saas.config.ts` and already carries the `config-saas` skill — an answer\n * elicited anywhere else would have nowhere to land, since a companion-agent playbook produces\n * an artifact and writes no files.\n *\n * Both questions are deliberately ANSWERABLE IN PART. Every part of\n * `operatorComplianceIdentity` is independently declarable (#228), so a creator who knows the\n * registered name and not the lawful bases records the name — and Paul's decision (#225) is\n * explicit that filling the entity must never block. A question that demanded the whole thing\n * would reintroduce the blocking this lane just removed, one layer up.\n */\n {\n \"ref\": \"operating-entity\",\n \"question\": \"Which legal entity operates this service? Give the registered company name, its registered address, and the route a person uses to reach you about privacy (an email, a URL or a postal address). Answer only the parts you actually know today — anything you leave out is recorded as outstanding and nothing is blocked by it. Do NOT supply a placeholder or a plausible-looking value: a produced privacy notice quotes these as fact, and the address is what a person would use to serve a legal request on a real company.\",\n \"kind\": \"free_text\"\n },\n {\n \"ref\": \"operating-jurisdictions\",\n \"question\": \"Which jurisdictions does this application operate in, and why does each one reach it — are you established there, do you sell there, or do you hold data about people there? Use country codes (`fr`, `us`), the supranational `eu`, or a subdivision (`us-ca`). Answer \\\"not decided\\\" if the market is genuinely unsettled; an absent answer is read as unanswered, never as \\\"nowhere\\\".\",\n \"kind\": \"free_text\"\n }\n ]\n }\n },\n \"approval\": \"approve_result\",\n \"budget\": {\n \"maxRuns\": 3\n },\n \"onFailure\": \"keep_and_flag\"\n} as const;\n"]}
|
|
1
|
+
{"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.foundation/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAC/B;IACE,KAAK,EAAE,sBAAsB;IAC7B,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,WAAW;IACpB,QAAQ,EAAE,gsCAAgsC;IAC1sC,eAAe,EAAE;QACf,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,aAAa,EAAE,EAAE;QACtE;;;;;;;;;;;;WAYG;QACH,EAAE,MAAM,EAAE,mBAAmB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,cAAc,EAAE,EAAE;QACzE;;;;;;;;;;;;;;;;;;;;;;;;WAwBG;QACH,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,kBAAkB,EAAE,EAAE;QAC3E;;;;;;WAMG;QACH,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,wBAAwB,EAAE,EAAE;KAClF;IACD;;;;;;;;;;;;;;;OAeG;IACH,QAAQ,EAAE;QACR,EAAE,QAAQ,EAAE,aAAa,EAAE;QAC3B,EAAE,QAAQ,EAAE,gBAAgB,EAAE;QAC9B;;;;;;WAMG;QACH,EAAE,QAAQ,EAAE,wBAAwB,EAAE;QACtC;;;;;;WAMG;QACH,EAAE,QAAQ,EAAE,kBAAkB,EAAE;KACjC;IACD,SAAS,EAAE,EAAE;IACb,QAAQ,EAAE;QACR,WAAW,EAAE;YACX,gBAAgB;YAChB,aAAa;YACb,qBAAqB;YACrB,0BAA0B;YAC1B,6BAA6B;YAC7B,iCAAiC;SAClC;QACD,aAAa,EAAE;YACb,WAAW,EAAE;gBACX;;;;;;;;;mBASG;gBACH;oBACE,KAAK,EAAE,eAAe;oBACtB,UAAU,EAAE,2NAA2N;oBACvO,MAAM,EAAE,QAAQ;oBAChB,SAAS,EAAE,CAAC,eAAe,EAAE,OAAO,CAAC;iBACtC;gBACD;;;;;;;;;;;;;;;;;;;;;;;;;mBAyBG;gBACH;oBACE,KAAK,EAAE,kBAAkB;oBACzB,UAAU,EAAE,ogBAAogB;oBAChhB,MAAM,EAAE,WAAW;iBACpB;gBACD;oBACE,KAAK,EAAE,yBAAyB;oBAChC,UAAU,EAAE,6XAA6X;oBACzY,MAAM,EAAE,WAAW;iBACpB;gBACD;;;;;;;;;;;;;;;mBAeG;gBACH;oBACE,KAAK,EAAE,kBAAkB;oBACzB,UAAU,EAAE,8JAA8J;oBAC1K,MAAM,EAAE,QAAQ;oBAChB,SAAS,EAAE,CAAC,QAAQ,EAAE,MAAM,CAAC;iBAC9B;gBACD;oBACE,KAAK,EAAE,cAAc;oBACrB,UAAU,EAAE,+KAA+K;oBAC3L,MAAM,EAAE,QAAQ;oBAChB,SAAS,EAAE,CAAC,QAAQ,EAAE,MAAM,CAAC;iBAC9B;aACF;SACF;KACF;IACC,UAAU,EAAE,gBAAgB;IAC9B,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 * The structured method remains intentionally rich: its intent, inputs, output\n * contracts, elicitation, deterministic verification and skill routing are the\n * application knowledge a later generic assessment loop composes. This source\n * intentionally omits the superseded per-playbook evaluation-treatment object;\n * generation records that absence rather than fabricating legacy judge behavior.\n */\nexport const playbookDefinition =\n{\n \"ref\": \"bottom_up.foundation\",\n \"version\": \"0.2.4\",\n \"phase\": \"bottom_up\",\n \"intent\": \"Bottom-up foundation \\u2014 turn the approved domain plan and top-down definitions into a configured, bootable application skeleton. For a fresh application, use wildo init in an empty destination before refining its generated configuration; preserve existing projects and use their repair/composition paths. Author capabilities, modules and providers from the approved plan, verify application knowledge delivery (wildo assets sync refreshes installed assets), then run wildo setup --non-interactive and wildo local init with their prerequisites. These tools exist; their successful invocation and postconditions must be observed in the current run. The registered foundation executor composes module/resource shells and tenancy configuration; it does not run this full init/assets/setup sequence. This methodology states the prerequisites and postconditions to fulfil around that execution. It emits no artifact: the deliverable is the application source, configured module registrations and verified initialization. Record the reasons for configuration choices beside those choices. Runs after the domain plan is approved in the bottom_up phase; business resource implementation belongs to the later build work.\",\n \"preconditions\": [\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"domain-plan\" } },\n /*\n * SEQUENCING, not readiness (#1434). `artifact_exists` asserts this playbook needs the vision's\n * CONTENT, and it does not read a word of it: the run short-circuits into the foundation\n * executor before any brief is composed, and the executor reads the domain plan and the landed\n * business model. The audit rule that reports a readiness gate whose family is undeclared named\n * both remedies — declare it, or weaken the gate \"if the order is all that matters\" — and here\n * the order is all that matters.\n *\n * Nothing is lost by weakening it. The vision is enforced TRANSITIVELY and harder than this gate\n * ever did: `top_down.market-snapshot-produce` and `top_down.requirements-definition` both gate\n * on `vision-brief` at readiness, and `bottom_up.domain-plan` gates on both of those — so an\n * approved domain plan, which this playbook DOES require at readiness, cannot exist without one.\n */\n { \"kind\": \"artifact_expected\", \"selector\": { \"family\": \"vision-brief\" } },\n /*\n * CONTENT, not sequencing — and this gate is why (#1544).\n *\n * `appendBackgroundExecutionScenarios` composes one `add-worker-node` / `add-worker-rust` /\n * `add-minion` per surface the INTEGRATION PLAN declares, deriving every variable from that\n * declaration. It reads the plan leniently on purpose: absent or unparseable means the\n * application declares nothing to run beside its backend, which is the ordinary case. That\n * leniency is correct and stays — what it cannot do is tell \"declares nothing\" from \"has not\n * been produced yet\", and both come back as silence.\n *\n * Measured on the first end-to-end run: this playbook ran at 06:58:03 and concluded three\n * seconds later; `bottom_up.integration-plan` started at 06:58:47 — 44 seconds AFTER — and\n * declared one minion, `minion-compose-weekly-team-digest`. Nothing was composed. The build\n * decomposer then emitted `build-task-weekly-digest-minion` against a package that no step\n * would ever create, and nine hours later there was still no `minions/` directory and\n * `applicationMinions = {}`.\n *\n * `artifact_exists` rather than `artifact_expected`, by the distinction the vision gate above\n * draws: this playbook reads the plan's CONTENT, not merely its position in the order.\n *\n * Safe to gate on. The integration-plan playbook produces a plan for every application,\n * `workers: []` and `minions: []` included — an application with no background execution is a\n * plan that says so, not an absent one. So this cannot make the foundation permanently\n * ineligible; it can only hold it until the answer exists.\n */\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"integration-plan\" } },\n /*\n * The same gate for the same reason, one input over. `capability-composition` decides which\n * scenarios are NEEDED — the loop above it throws when a scenario is marked needed and the\n * foundation has no invocation for it — so composing before it lands composes from an empty\n * decision set, silently and with the same shape. Not measured failing; gated because it is the\n * same invariant at its other site (`invariant-call-site-enumeration.md`).\n */\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"capability-composition\" } }\n ],\n /*\n * TWO, measured rather than aspirational (#1434) — THREE since #1491, see the third entry.\n *\n * This playbook does not compose a brief at all: `executePlaybookRun` short-circuits it into the\n * foundation executor before any section is composed, so a declared input reaches no model. The\n * executor reads the domain plan (handed to it) and the landed business model (read itself), and\n * derives the three capabilities that are derivable from those two values.\n *\n * `vision-brief`, `market-snapshot`, `requirements` and `roadmap` were declared and reached\n * nothing — while the method told a reader that the vision's compliance constraints were \"the\n * primary driver of capability selection\". A declaration nothing reads is a promise nothing\n * keeps, and four of the six were exactly that.\n *\n * `vision-brief` stays a PRECONDITION, which is a different statement: the foundation must not run\n * before a vision exists, and that gate is real whether or not anything reads its content here.\n */\n \"inputs\": [\n { \"family\": \"domain-plan\" },\n { \"family\": \"business-model\" },\n /*\n * THIRD, since #1491: which optional packages (the website, the documentation portal) this\n * application needs, decided by `bottom_up.capability-composition` and applied here after the\n * domain scenarios. An INPUT, not a precondition, for the same reason as the business model: a\n * foundation run with no composition yet composes the domain and applies no optional package,\n * and the executor reads it through the `capabilityComposition` slot rather than a brief.\n */\n { \"family\": \"capability-composition\" },\n /*\n * FOURTH, since #1495: what runs beside the backend. The executor fans one `add-worker-node`,\n * `add-worker-rust` or `add-minion` out of this plan per surface it declares — the same shape as\n * the module and resource fan-out, and an INPUT for the same reason as the two above: a run with\n * no integration plan composes no background package, and a plan landing later re-stales this\n * step rather than gating it.\n */\n { \"family\": \"integration-plan\" }\n ],\n \"outputs\": [],\n \"method\": {\n \"skillRefs\": [\n \"journey-status\",\n \"config-saas\",\n \"module-registration\",\n \"infra-environment-config\",\n \"local-environment-bootstrap\",\n \"application-database-migrations\"\n ],\n \"elicitation\": {\n \"questions\": [\n /*\n * THE FALLBACK, since 2026-08-28. `bottom_up.domain-plan` now asks this and carries the\n * answer in the committed plan (`DomainPlanOutputSet.tenancy`), because the plan MODELS\n * tenancy — wonder-crm's invented a workspace module and a membership before anyone was\n * asked — so asking after the model is shaped lets a second answer contradict it.\n *\n * The executor reads the plan first and reaches this question only for a plan authored\n * before the field existed. Keep it: those plans are real (wonder-crm, wonder-todos) and\n * must stay composable.\n */\n {\n \"ref\": \"primary-scope\",\n \"question\": \"What is the application's tenancy model? Answer `organizations` when users collaborate inside shared workspaces/teams (this enables the ORGANIZATIONS engine capability), or `users` when every user's data is their own.\",\n \"kind\": \"choice\",\n \"options\": [\"organizations\", \"users\"]\n },\n /*\n * The operator's own legal identity (issue #235), asked HERE because this is the playbook that\n * writes `wildo.saas.config.ts` and already carries the `config-saas` skill — an answer\n * elicited anywhere else would have nowhere to land, since a companion-agent playbook produces\n * an artifact and writes no files.\n *\n * KEPT on 2026-09-22 (#1454, Step 5), after \"bind them to the typed config keys, or stop\n * asking\" was weighed. The executor reads neither answer — it reads only `primary-scope` —\n * and the questions are nonetheless the elicitation path into a typed, committed key, which\n * is what `compliance-is-derived-from-the-product.md` rule 2 asks for (never a form that\n * stays a form). What changed is where the answers LIVE: the DOSSIER keeps them, so they are\n * asked once and read by every run that needs them.\n *\n * CORRECTED 2026-09-22 (#1434), same day: that reasoning originally said \"this is a\n * CODING-AGENT playbook, and the agent's brief carries the rendered interview\". This playbook\n * composes NO BRIEF — `executePlaybookRun` short-circuits it into the foundation executor\n * before any section is composed — so no agent reads `method.md` Step 4 here. The decision to\n * keep the questions stands on the dossier, which is a real reader; the delivery path named\n * beside it was not.\n *\n * Both questions are deliberately ANSWERABLE IN PART. Every part of\n * `operatorComplianceIdentity` is independently declarable (#228), so a creator who knows the\n * registered name and not the lawful bases records the name — and Paul's decision (#225) is\n * explicit that filling the entity must never block. A question that demanded the whole thing\n * would reintroduce the blocking this lane just removed, one layer up.\n */\n {\n \"ref\": \"operating-entity\",\n \"question\": \"Which legal entity operates this service? Give the registered company name, its registered address, and the route a person uses to reach you about privacy (an email, a URL or a postal address). Answer only the parts you actually know today — anything you leave out is recorded as outstanding and nothing is blocked by it. Do NOT supply a placeholder or a plausible-looking value: a produced privacy notice quotes these as fact, and the address is what a person would use to serve a legal request on a real company.\",\n \"kind\": \"free_text\"\n },\n {\n \"ref\": \"operating-jurisdictions\",\n \"question\": \"Which jurisdictions does this application operate in, and why does each one reach it — are you established there, do you sell there, or do you hold data about people there? Use country codes (`fr`, `us`), the supranational `eu`, or a subdivision (`us-ca`). Answer \\\"not decided\\\" if the market is genuinely unsettled; an absent answer is read as unanswered, never as \\\"nowhere\\\".\",\n \"kind\": \"free_text\"\n },\n /*\n * The creator's PROVIDER choices (#1488). Which vendor an application charges or texts through is\n * a class-3 product decision — the field does not converge on one answer — so it is asked, as a\n * typed CHOICE, and the answer is kept in the dossier and read by the foundation executor, which\n * declares the provider, selects it as primary and enables the capability. The credentials the\n * provider needs are recorded as OWED on the run result: the boot floor reads declaration and\n * selection, never secrets, so the application boots and the provider answers once they are set.\n *\n * The OPTIONS are the engine providers serving the capability (ENGINE origin, backend scope), and\n * `foundation-executor.companion.service.test.ts` pins these authored lists to that derivation plus the\n * `none` member, so a vendor added to the catalogue fails the pin until it is offered here.\n *\n * `none` is an OPTION, not an absence: the elicitation contract refuses a run whose interview is not\n * fully answered, and a CHOICE accepts only its options, so \"decide later\" has to be sayable. It leaves\n * the capability owed exactly as before (#1272).\n */\n {\n \"ref\": \"billing-provider\",\n \"question\": \"Which billing provider should this application charge its users through? Answer `none` to decide later; the capability stays off until a provider is chosen.\",\n \"kind\": \"choice\",\n \"options\": [\"stripe\", \"none\"]\n },\n {\n \"ref\": \"sms-provider\",\n \"question\": \"Which SMS provider should this application send text messages through (phone verification, SMS second factor)? Answer `none` if the product sends no SMS, or to decide later.\",\n \"kind\": \"choice\",\n \"options\": [\"twilio\", \"none\"]\n }\n ]\n }\n },\n \"approval\": \"approve_result\",\n \"budget\": {\n \"maxRuns\": 3\n },\n \"onFailure\": \"keep_and_flag\"\n} as const;\n"]}
|
|
@@ -0,0 +1,67 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* Canonical native declaration for this reusable application-creation method.
|
|
3
|
+
*
|
|
4
|
+
* The background-execution and external-reach leaf (#1495). `add-minion`, `add-worker-node`,
|
|
5
|
+
* `add-worker-rust`, `add-provider` and `add-file-picker-provider` all shipped as scenarios, and
|
|
6
|
+
* the decomposer was told to plan "workers / minions and other auxiliary execution surfaces" and
|
|
7
|
+
* "providers, external connectors, billing wiring" — with no product kind for any of them and,
|
|
8
|
+
* measured 2026-09-22, ZERO worker and minion skills in the catalog. Nothing in the journey could
|
|
9
|
+
* give an application a background worker, a cron minion or a provider binding.
|
|
10
|
+
*
|
|
11
|
+
* It produces the integration plan. Two consumers read it, and the split is the point:
|
|
12
|
+
*
|
|
13
|
+
* - `bottom_up.foundation` composes the PACKAGE — one `add-worker-node`, `add-worker-rust` or
|
|
14
|
+
* `add-minion` per surface, fanned out exactly as modules and resources are fanned out of the
|
|
15
|
+
* domain plan. That is why the capability composition reports those three scenarios as owned by
|
|
16
|
+
* the foundation rather than as undecidable, which is what they read until this family existed.
|
|
17
|
+
* - `bottom_up.build-decompose` emits the WORK — one task per worker, minion and provider binding,
|
|
18
|
+
* each bound to its skill through the three total maps in `_core`.
|
|
19
|
+
*
|
|
20
|
+
* The build plan keeps ONE producer, which is what makes landing decidable (#895).
|
|
21
|
+
*/
|
|
22
|
+
export declare const playbookDefinition: {
|
|
23
|
+
readonly ref: "bottom_up.integration-plan";
|
|
24
|
+
readonly version: "0.1.0";
|
|
25
|
+
readonly phase: "bottom_up";
|
|
26
|
+
readonly intent: "Background execution and external reach — decide WHAT RUNS BESIDE THE BACKEND and WHAT THIS APPLICATION REACHES OUT TO: which workers exist and on which runtime, which cron minions wake on their own and exactly which resources each one may read and write, and which providers are bound into which runtime owner's scope. Reads the requirements and feature drafts (what somebody asked for, including the work that cannot happen inside a request), the domain plan (the resources a minion's containment whitelist names) and the roadmap (what is owed when). Every surface names what it is accountable to, because a process nobody asked for is a process nobody maintains. Produces the plan; the foundation composes each package and the decomposer emits the work, each task bound to the skill its runtime or scope names.";
|
|
27
|
+
readonly preconditions: readonly [{
|
|
28
|
+
readonly kind: "artifact_exists";
|
|
29
|
+
readonly selector: {
|
|
30
|
+
readonly family: "domain-plan";
|
|
31
|
+
};
|
|
32
|
+
}];
|
|
33
|
+
readonly inputs: readonly [{
|
|
34
|
+
readonly family: "requirements";
|
|
35
|
+
readonly "//": "What somebody asked the application to do — including the work that cannot happen inside a request, which is the only honest reason a worker exists.";
|
|
36
|
+
}, {
|
|
37
|
+
readonly family: "feature-drafts";
|
|
38
|
+
readonly "//": "The drafted features whose work a background surface carries.";
|
|
39
|
+
}, {
|
|
40
|
+
readonly family: "domain-plan";
|
|
41
|
+
readonly "//": "The resources a minion's containment whitelist names, and the modules a worker serves.";
|
|
42
|
+
}, {
|
|
43
|
+
readonly family: "roadmap";
|
|
44
|
+
readonly render: "map";
|
|
45
|
+
readonly "//": "When each phase is owed, so a surface is planned against the phase that needs it. A MAP: the phases' own rationale is not this method's input (#1424).";
|
|
46
|
+
}, {
|
|
47
|
+
readonly family: "integration-plan";
|
|
48
|
+
readonly "//": "Its own family: its method refines its own prior output and keeps its worker and minion refs, which build tasks name (#1430). Input, not precondition: a first run stays eligible.";
|
|
49
|
+
}];
|
|
50
|
+
readonly outputs: readonly [{
|
|
51
|
+
readonly family: "integration-plan";
|
|
52
|
+
readonly schemaRef: "saas-specifications:IntegrationPlan";
|
|
53
|
+
readonly description: "What this application runs beside its backend and what it reaches out to: its workers (each with its runtime, what the backend delegates to it, the routes it registers and what it is accountable to), its cron minions (each with what happens because time passed, its named behaviours, and exactly which resources its tick reads and writes), and the providers it binds into each runtime owner's scope. Every collection may be empty, and saying so is an answer.";
|
|
54
|
+
}];
|
|
55
|
+
readonly method: {
|
|
56
|
+
readonly contextSources: readonly ["workspace_truth"];
|
|
57
|
+
readonly skillBodyRefs: readonly ["worker-authoring", "minion-authoring"];
|
|
58
|
+
readonly skillRefs: readonly ["journey-status", "worker-authoring", "minion-authoring", "provider-backend-package", "provider-frontend-file-picker", "provider-operation-calls", "resource-external-data", "configure-billing"];
|
|
59
|
+
};
|
|
60
|
+
readonly executor: "companion_agent";
|
|
61
|
+
readonly approval: "approve_result";
|
|
62
|
+
readonly budget: {
|
|
63
|
+
readonly maxRuns: 3;
|
|
64
|
+
};
|
|
65
|
+
readonly onFailure: "keep_and_flag";
|
|
66
|
+
};
|
|
67
|
+
//# sourceMappingURL=playbook.definition.d.ts.map
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.integration-plan/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;GAoBG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA4DrB,CAAC"}
|
|
@@ -0,0 +1,83 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* Canonical native declaration for this reusable application-creation method.
|
|
3
|
+
*
|
|
4
|
+
* The background-execution and external-reach leaf (#1495). `add-minion`, `add-worker-node`,
|
|
5
|
+
* `add-worker-rust`, `add-provider` and `add-file-picker-provider` all shipped as scenarios, and
|
|
6
|
+
* the decomposer was told to plan "workers / minions and other auxiliary execution surfaces" and
|
|
7
|
+
* "providers, external connectors, billing wiring" — with no product kind for any of them and,
|
|
8
|
+
* measured 2026-09-22, ZERO worker and minion skills in the catalog. Nothing in the journey could
|
|
9
|
+
* give an application a background worker, a cron minion or a provider binding.
|
|
10
|
+
*
|
|
11
|
+
* It produces the integration plan. Two consumers read it, and the split is the point:
|
|
12
|
+
*
|
|
13
|
+
* - `bottom_up.foundation` composes the PACKAGE — one `add-worker-node`, `add-worker-rust` or
|
|
14
|
+
* `add-minion` per surface, fanned out exactly as modules and resources are fanned out of the
|
|
15
|
+
* domain plan. That is why the capability composition reports those three scenarios as owned by
|
|
16
|
+
* the foundation rather than as undecidable, which is what they read until this family existed.
|
|
17
|
+
* - `bottom_up.build-decompose` emits the WORK — one task per worker, minion and provider binding,
|
|
18
|
+
* each bound to its skill through the three total maps in `_core`.
|
|
19
|
+
*
|
|
20
|
+
* The build plan keeps ONE producer, which is what makes landing decidable (#895).
|
|
21
|
+
*/
|
|
22
|
+
export const playbookDefinition = {
|
|
23
|
+
"ref": "bottom_up.integration-plan",
|
|
24
|
+
"version": "0.1.0",
|
|
25
|
+
"phase": "bottom_up",
|
|
26
|
+
"intent": "Background execution and external reach — decide WHAT RUNS BESIDE THE BACKEND and WHAT THIS APPLICATION REACHES OUT TO: which workers exist and on which runtime, which cron minions wake on their own and exactly which resources each one may read and write, and which providers are bound into which runtime owner's scope. Reads the requirements and feature drafts (what somebody asked for, including the work that cannot happen inside a request), the domain plan (the resources a minion's containment whitelist names) and the roadmap (what is owed when). Every surface names what it is accountable to, because a process nobody asked for is a process nobody maintains. Produces the plan; the foundation composes each package and the decomposer emits the work, each task bound to the skill its runtime or scope names.",
|
|
27
|
+
"preconditions": [
|
|
28
|
+
/*
|
|
29
|
+
* The DOMAIN PLAN is what a minion's containment is OVER: `readsResourceRefs` and
|
|
30
|
+
* `writesResourceRefs` name decided resources, and a whitelist naming resources nobody decided
|
|
31
|
+
* contains nothing. Its CONTENT is read, so `artifact_exists` is the honest strength (#1434).
|
|
32
|
+
*/
|
|
33
|
+
{ "kind": "artifact_exists", "selector": { "family": "domain-plan" } }
|
|
34
|
+
],
|
|
35
|
+
"inputs": [
|
|
36
|
+
{ "family": "requirements", "//": "What somebody asked the application to do — including the work that cannot happen inside a request, which is the only honest reason a worker exists." },
|
|
37
|
+
{ "family": "feature-drafts", "//": "The drafted features whose work a background surface carries." },
|
|
38
|
+
{ "family": "domain-plan", "//": "The resources a minion's containment whitelist names, and the modules a worker serves." },
|
|
39
|
+
{ "family": "roadmap", "render": "map", "//": "When each phase is owed, so a surface is planned against the phase that needs it. A MAP: the phases' own rationale is not this method's input (#1424)." },
|
|
40
|
+
{ "family": "integration-plan", "//": "Its own family: its method refines its own prior output and keeps its worker and minion refs, which build tasks name (#1430). Input, not precondition: a first run stays eligible." }
|
|
41
|
+
],
|
|
42
|
+
"outputs": [
|
|
43
|
+
{
|
|
44
|
+
"family": "integration-plan",
|
|
45
|
+
"schemaRef": "saas-specifications:IntegrationPlan",
|
|
46
|
+
"description": "What this application runs beside its backend and what it reaches out to: its workers (each with its runtime, what the backend delegates to it, the routes it registers and what it is accountable to), its cron minions (each with what happens because time passed, its named behaviours, and exactly which resources its tick reads and writes), and the providers it binds into each runtime owner's scope. Every collection may be empty, and saying so is an answer."
|
|
47
|
+
}
|
|
48
|
+
],
|
|
49
|
+
"method": {
|
|
50
|
+
/*
|
|
51
|
+
* WORKSPACE_TRUTH — this method plans against CODE as well as against decisions: which workers
|
|
52
|
+
* and minions the application ALREADY carries (its `applicationWorkers` / `applicationMinions`
|
|
53
|
+
* buckets), and which providers its scopes already name. A plan proposing a worker the tree
|
|
54
|
+
* already has emits a task that composes a package twice.
|
|
55
|
+
*/
|
|
56
|
+
"contextSources": ["workspace_truth"],
|
|
57
|
+
/*
|
|
58
|
+
* TWO bodies reach this step (#1435), and they are the two the plan's central decisions depend
|
|
59
|
+
* on: whether a surface is a worker or a minion, and what a minion's containment must name.
|
|
60
|
+
* Both are impossible to decide from recollection — the difference is a runtime contract, and
|
|
61
|
+
* the containment chain has three parts of which two are outside the minion's own package.
|
|
62
|
+
* Every other skill is a contract the CODING AGENT opens when it builds the task.
|
|
63
|
+
*/
|
|
64
|
+
"skillBodyRefs": ["worker-authoring", "minion-authoring"],
|
|
65
|
+
"skillRefs": [
|
|
66
|
+
"journey-status",
|
|
67
|
+
"worker-authoring",
|
|
68
|
+
"minion-authoring",
|
|
69
|
+
"provider-backend-package",
|
|
70
|
+
"provider-frontend-file-picker",
|
|
71
|
+
"provider-operation-calls",
|
|
72
|
+
"resource-external-data",
|
|
73
|
+
"configure-billing"
|
|
74
|
+
]
|
|
75
|
+
},
|
|
76
|
+
"executor": "companion_agent",
|
|
77
|
+
"approval": "approve_result",
|
|
78
|
+
"budget": {
|
|
79
|
+
"maxRuns": 3
|
|
80
|
+
},
|
|
81
|
+
"onFailure": "keep_and_flag"
|
|
82
|
+
};
|
|
83
|
+
//# sourceMappingURL=playbook.definition.js.map
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.integration-plan/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;GAoBG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG;IAChC,KAAK,EAAE,4BAA4B;IACnC,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,WAAW;IACpB,QAAQ,EAAE,+yBAA+yB;IACzzB,eAAe,EAAE;QACf;;;;WAIG;QACH,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,aAAa,EAAE,EAAE;KACvE;IACD,QAAQ,EAAE;QACR,EAAE,QAAQ,EAAE,cAAc,EAAE,IAAI,EAAE,sJAAsJ,EAAE;QAC1L,EAAE,QAAQ,EAAE,gBAAgB,EAAE,IAAI,EAAE,+DAA+D,EAAE;QACrG,EAAE,QAAQ,EAAE,aAAa,EAAE,IAAI,EAAE,wFAAwF,EAAE;QAC3H,EAAE,QAAQ,EAAE,SAAS,EAAE,QAAQ,EAAE,KAAK,EAAE,IAAI,EAAE,wJAAwJ,EAAE;QACxM,EAAE,QAAQ,EAAE,kBAAkB,EAAE,IAAI,EAAE,oLAAoL,EAAE;KAC7N;IACD,SAAS,EAAE;QACT;YACE,QAAQ,EAAE,kBAAkB;YAC5B,WAAW,EAAE,qCAAqC;YAClD,aAAa,EAAE,4cAA4c;SAC5d;KACF;IACD,QAAQ,EAAE;QACR;;;;;WAKG;QACH,gBAAgB,EAAE,CAAC,iBAAiB,CAAC;QACrC;;;;;;WAMG;QACH,eAAe,EAAE,CAAC,kBAAkB,EAAE,kBAAkB,CAAC;QACzD,WAAW,EAAE;YACX,gBAAgB;YAChB,kBAAkB;YAClB,kBAAkB;YAClB,0BAA0B;YAC1B,+BAA+B;YAC/B,0BAA0B;YAC1B,wBAAwB;YACxB,mBAAmB;SACpB;KACF;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 * The background-execution and external-reach leaf (#1495). `add-minion`, `add-worker-node`,\n * `add-worker-rust`, `add-provider` and `add-file-picker-provider` all shipped as scenarios, and\n * the decomposer was told to plan \"workers / minions and other auxiliary execution surfaces\" and\n * \"providers, external connectors, billing wiring\" — with no product kind for any of them and,\n * measured 2026-09-22, ZERO worker and minion skills in the catalog. Nothing in the journey could\n * give an application a background worker, a cron minion or a provider binding.\n *\n * It produces the integration plan. Two consumers read it, and the split is the point:\n *\n * - `bottom_up.foundation` composes the PACKAGE — one `add-worker-node`, `add-worker-rust` or\n * `add-minion` per surface, fanned out exactly as modules and resources are fanned out of the\n * domain plan. That is why the capability composition reports those three scenarios as owned by\n * the foundation rather than as undecidable, which is what they read until this family existed.\n * - `bottom_up.build-decompose` emits the WORK — one task per worker, minion and provider binding,\n * each bound to its skill through the three total maps in `_core`.\n *\n * The build plan keeps ONE producer, which is what makes landing decidable (#895).\n */\nexport const playbookDefinition = {\n \"ref\": \"bottom_up.integration-plan\",\n \"version\": \"0.1.0\",\n \"phase\": \"bottom_up\",\n \"intent\": \"Background execution and external reach — decide WHAT RUNS BESIDE THE BACKEND and WHAT THIS APPLICATION REACHES OUT TO: which workers exist and on which runtime, which cron minions wake on their own and exactly which resources each one may read and write, and which providers are bound into which runtime owner's scope. Reads the requirements and feature drafts (what somebody asked for, including the work that cannot happen inside a request), the domain plan (the resources a minion's containment whitelist names) and the roadmap (what is owed when). Every surface names what it is accountable to, because a process nobody asked for is a process nobody maintains. Produces the plan; the foundation composes each package and the decomposer emits the work, each task bound to the skill its runtime or scope names.\",\n \"preconditions\": [\n /*\n * The DOMAIN PLAN is what a minion's containment is OVER: `readsResourceRefs` and\n * `writesResourceRefs` name decided resources, and a whitelist naming resources nobody decided\n * contains nothing. Its CONTENT is read, so `artifact_exists` is the honest strength (#1434).\n */\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"domain-plan\" } }\n ],\n \"inputs\": [\n { \"family\": \"requirements\", \"//\": \"What somebody asked the application to do — including the work that cannot happen inside a request, which is the only honest reason a worker exists.\" },\n { \"family\": \"feature-drafts\", \"//\": \"The drafted features whose work a background surface carries.\" },\n { \"family\": \"domain-plan\", \"//\": \"The resources a minion's containment whitelist names, and the modules a worker serves.\" },\n { \"family\": \"roadmap\", \"render\": \"map\", \"//\": \"When each phase is owed, so a surface is planned against the phase that needs it. A MAP: the phases' own rationale is not this method's input (#1424).\" },\n { \"family\": \"integration-plan\", \"//\": \"Its own family: its method refines its own prior output and keeps its worker and minion refs, which build tasks name (#1430). Input, not precondition: a first run stays eligible.\" }\n ],\n \"outputs\": [\n {\n \"family\": \"integration-plan\",\n \"schemaRef\": \"saas-specifications:IntegrationPlan\",\n \"description\": \"What this application runs beside its backend and what it reaches out to: its workers (each with its runtime, what the backend delegates to it, the routes it registers and what it is accountable to), its cron minions (each with what happens because time passed, its named behaviours, and exactly which resources its tick reads and writes), and the providers it binds into each runtime owner's scope. Every collection may be empty, and saying so is an answer.\"\n }\n ],\n \"method\": {\n /*\n * WORKSPACE_TRUTH — this method plans against CODE as well as against decisions: which workers\n * and minions the application ALREADY carries (its `applicationWorkers` / `applicationMinions`\n * buckets), and which providers its scopes already name. A plan proposing a worker the tree\n * already has emits a task that composes a package twice.\n */\n \"contextSources\": [\"workspace_truth\"],\n /*\n * TWO bodies reach this step (#1435), and they are the two the plan's central decisions depend\n * on: whether a surface is a worker or a minion, and what a minion's containment must name.\n * Both are impossible to decide from recollection — the difference is a runtime contract, and\n * the containment chain has three parts of which two are outside the minion's own package.\n * Every other skill is a contract the CODING AGENT opens when it builds the task.\n */\n \"skillBodyRefs\": [\"worker-authoring\", \"minion-authoring\"],\n \"skillRefs\": [\n \"journey-status\",\n \"worker-authoring\",\n \"minion-authoring\",\n \"provider-backend-package\",\n \"provider-frontend-file-picker\",\n \"provider-operation-calls\",\n \"resource-external-data\",\n \"configure-billing\"\n ]\n },\n \"executor\": \"companion_agent\",\n \"approval\": \"approve_result\",\n \"budget\": {\n \"maxRuns\": 3\n },\n \"onFailure\": \"keep_and_flag\"\n} as const;\n"]}
|
|
@@ -0,0 +1,69 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* Canonical native declaration for this reusable application-creation method.
|
|
3
|
+
*
|
|
4
|
+
* A RUNNER-OWNED step, like `bottom_up.capability-composition` and `bottom_up.foundation` (#1496):
|
|
5
|
+
* the run short-circuits into the companion's maturity executor before any brief is composed,
|
|
6
|
+
* because the reading is a PURE FUNCTION — `deriveApplicationMaturity` walks the requirements
|
|
7
|
+
* family, the decided-element graph's inbound links and the build plan's landing probe. A model
|
|
8
|
+
* asked where an application stands would ANSWER, and nothing could check the answer, which is the
|
|
9
|
+
* one thing this family exists to prevent.
|
|
10
|
+
*
|
|
11
|
+
* It declares its `outputs` because the family IS landed through the generic renderer, so the
|
|
12
|
+
* coherence report and the workbench have a producer to read. It carries no evaluation treatment:
|
|
13
|
+
* there is no judgement in it to judge, only a measurement whose validator reports what the
|
|
14
|
+
* APPLICATION lacks rather than what the artifact got wrong.
|
|
15
|
+
*
|
|
16
|
+
* **Not a gate, and nothing downstream may treat it as one.** Paul, 2026-09-22: *"there are no
|
|
17
|
+
* 'Done' for an app, there are a measurement face to requirements, with some stage."* The highest
|
|
18
|
+
* stage says only that every requirement currently has the strongest evidence this framework can
|
|
19
|
+
* produce; the next requirement lowers it again.
|
|
20
|
+
*/
|
|
21
|
+
export declare const playbookDefinition: {
|
|
22
|
+
readonly ref: "bottom_up.maturity-reading";
|
|
23
|
+
readonly version: "0.1.0";
|
|
24
|
+
readonly phase: "bottom_up";
|
|
25
|
+
readonly intent: "Maturity reading — measure WHERE THIS APPLICATION STANDS against its own requirements, and record it as the `application-maturity` family: one row per requirement the application declares, the evidence that exists for it, and the stage that follows. DERIVED, never judged. Each row's level is reached by a measurement — a decided element that points at the requirement (a feature draft, an experience surface, a worker, a build task), a build task addressing it that has LANDED in committed bytes, a landed task whose declared product was PROVEN, or a runtime observation of the running application. The denominator is the requirements family itself, total and in its own order, so a requirement nothing addresses is a row rather than an omission and adding one lowers the reading with no code change. This is a MEASUREMENT and never a gate: there is no 'done' for an application, and the stage moves in both directions as the application and its requirements change.";
|
|
26
|
+
readonly preconditions: readonly [{
|
|
27
|
+
readonly kind: "artifact_exists";
|
|
28
|
+
readonly selector: {
|
|
29
|
+
readonly family: "requirements";
|
|
30
|
+
};
|
|
31
|
+
}];
|
|
32
|
+
readonly inputs: readonly [{
|
|
33
|
+
readonly family: "requirements";
|
|
34
|
+
readonly render: "map";
|
|
35
|
+
}, {
|
|
36
|
+
readonly family: "feature-drafts";
|
|
37
|
+
readonly render: "map";
|
|
38
|
+
}, {
|
|
39
|
+
readonly family: "build-plan";
|
|
40
|
+
readonly render: "map";
|
|
41
|
+
}, {
|
|
42
|
+
readonly family: "experience-plan";
|
|
43
|
+
readonly render: "map";
|
|
44
|
+
}, {
|
|
45
|
+
readonly family: "integration-plan";
|
|
46
|
+
readonly render: "map";
|
|
47
|
+
}, {
|
|
48
|
+
readonly family: "roadmap";
|
|
49
|
+
readonly render: "map";
|
|
50
|
+
}, {
|
|
51
|
+
readonly family: "application-maturity";
|
|
52
|
+
readonly render: "map";
|
|
53
|
+
readonly "//": "Its own family: the reading it replaces. Input, not precondition — a first run, with no prior reading, stays eligible.";
|
|
54
|
+
}];
|
|
55
|
+
readonly outputs: readonly [{
|
|
56
|
+
readonly family: "application-maturity";
|
|
57
|
+
readonly schemaRef: "saas-specifications:ApplicationMaturity";
|
|
58
|
+
readonly description: "Where the application stands against its own requirements: one row per requirement with the evidence level it has reached and the elements, landed tasks, proven tasks and runtime observations that carry it, the thresholds the reading was scored against, and the stage that follows. A reading, never a verdict.";
|
|
59
|
+
}];
|
|
60
|
+
readonly method: {
|
|
61
|
+
readonly skillRefs: readonly ["journey-status"];
|
|
62
|
+
};
|
|
63
|
+
readonly approval: "approve_result";
|
|
64
|
+
readonly budget: {
|
|
65
|
+
readonly maxRuns: 5;
|
|
66
|
+
};
|
|
67
|
+
readonly onFailure: "keep_and_flag";
|
|
68
|
+
};
|
|
69
|
+
//# sourceMappingURL=playbook.definition.d.ts.map
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.maturity-reading/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;GAmBG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAiDrB,CAAC"}
|
|
@@ -0,0 +1,71 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* Canonical native declaration for this reusable application-creation method.
|
|
3
|
+
*
|
|
4
|
+
* A RUNNER-OWNED step, like `bottom_up.capability-composition` and `bottom_up.foundation` (#1496):
|
|
5
|
+
* the run short-circuits into the companion's maturity executor before any brief is composed,
|
|
6
|
+
* because the reading is a PURE FUNCTION — `deriveApplicationMaturity` walks the requirements
|
|
7
|
+
* family, the decided-element graph's inbound links and the build plan's landing probe. A model
|
|
8
|
+
* asked where an application stands would ANSWER, and nothing could check the answer, which is the
|
|
9
|
+
* one thing this family exists to prevent.
|
|
10
|
+
*
|
|
11
|
+
* It declares its `outputs` because the family IS landed through the generic renderer, so the
|
|
12
|
+
* coherence report and the workbench have a producer to read. It carries no evaluation treatment:
|
|
13
|
+
* there is no judgement in it to judge, only a measurement whose validator reports what the
|
|
14
|
+
* APPLICATION lacks rather than what the artifact got wrong.
|
|
15
|
+
*
|
|
16
|
+
* **Not a gate, and nothing downstream may treat it as one.** Paul, 2026-09-22: *"there are no
|
|
17
|
+
* 'Done' for an app, there are a measurement face to requirements, with some stage."* The highest
|
|
18
|
+
* stage says only that every requirement currently has the strongest evidence this framework can
|
|
19
|
+
* produce; the next requirement lowers it again.
|
|
20
|
+
*/
|
|
21
|
+
export const playbookDefinition = {
|
|
22
|
+
"ref": "bottom_up.maturity-reading",
|
|
23
|
+
"version": "0.1.0",
|
|
24
|
+
"phase": "bottom_up",
|
|
25
|
+
"intent": "Maturity reading — measure WHERE THIS APPLICATION STANDS against its own requirements, and record it as the `application-maturity` family: one row per requirement the application declares, the evidence that exists for it, and the stage that follows. DERIVED, never judged. Each row's level is reached by a measurement — a decided element that points at the requirement (a feature draft, an experience surface, a worker, a build task), a build task addressing it that has LANDED in committed bytes, a landed task whose declared product was PROVEN, or a runtime observation of the running application. The denominator is the requirements family itself, total and in its own order, so a requirement nothing addresses is a row rather than an omission and adding one lowers the reading with no code change. This is a MEASUREMENT and never a gate: there is no 'done' for an application, and the stage moves in both directions as the application and its requirements change.",
|
|
26
|
+
"preconditions": [
|
|
27
|
+
/*
|
|
28
|
+
* The REQUIREMENTS are the denominator, and a reading with no denominator is not a weaker
|
|
29
|
+
* reading — it is a different statement ("nothing has been asked of this application yet").
|
|
30
|
+
* `artifact_exists` because the CONTENT is read: the rows ARE its entries (#1434).
|
|
31
|
+
*/
|
|
32
|
+
{ "kind": "artifact_exists", "selector": { "family": "requirements" } }
|
|
33
|
+
],
|
|
34
|
+
/*
|
|
35
|
+
* Every family the derivation reads, declared so derived-staleness compares them: the reading goes
|
|
36
|
+
* stale when any decided element that could address a requirement changes. `render: 'map'` on each
|
|
37
|
+
* — the executor reads the VALUES itself through the artifact state, and no brief is composed for
|
|
38
|
+
* this step, so a full render would reach nothing (#1434's lesson).
|
|
39
|
+
*
|
|
40
|
+
* The list is the families that declare an edge to a requirement TODAY. It is not how the
|
|
41
|
+
* derivation finds them — that is the decided-element graph, which a family declaring such an edge
|
|
42
|
+
* tomorrow joins without this file changing — so a missing entry costs staleness, never coverage.
|
|
43
|
+
*/
|
|
44
|
+
"inputs": [
|
|
45
|
+
{ "family": "requirements", "render": "map" },
|
|
46
|
+
{ "family": "feature-drafts", "render": "map" },
|
|
47
|
+
{ "family": "build-plan", "render": "map" },
|
|
48
|
+
{ "family": "experience-plan", "render": "map" },
|
|
49
|
+
{ "family": "integration-plan", "render": "map" },
|
|
50
|
+
{ "family": "roadmap", "render": "map" },
|
|
51
|
+
{ "family": "application-maturity", "render": "map", "//": "Its own family: the reading it replaces. Input, not precondition — a first run, with no prior reading, stays eligible." }
|
|
52
|
+
],
|
|
53
|
+
"outputs": [
|
|
54
|
+
{
|
|
55
|
+
"family": "application-maturity",
|
|
56
|
+
"schemaRef": "saas-specifications:ApplicationMaturity",
|
|
57
|
+
"description": "Where the application stands against its own requirements: one row per requirement with the evidence level it has reached and the elements, landed tasks, proven tasks and runtime observations that carry it, the thresholds the reading was scored against, and the stage that follows. A reading, never a verdict."
|
|
58
|
+
}
|
|
59
|
+
],
|
|
60
|
+
"method": {
|
|
61
|
+
"skillRefs": [
|
|
62
|
+
"journey-status"
|
|
63
|
+
]
|
|
64
|
+
},
|
|
65
|
+
"approval": "approve_result",
|
|
66
|
+
"budget": {
|
|
67
|
+
"maxRuns": 5
|
|
68
|
+
},
|
|
69
|
+
"onFailure": "keep_and_flag"
|
|
70
|
+
};
|
|
71
|
+
//# sourceMappingURL=playbook.definition.js.map
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.maturity-reading/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;GAmBG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG;IAChC,KAAK,EAAE,4BAA4B;IACnC,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,WAAW;IACpB,QAAQ,EAAE,y8BAAy8B;IACn9B,eAAe,EAAE;QACf;;;;WAIG;QACH,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,cAAc,EAAE,EAAE;KACxE;IACD;;;;;;;;;OASG;IACH,QAAQ,EAAE;QACR,EAAE,QAAQ,EAAE,cAAc,EAAE,QAAQ,EAAE,KAAK,EAAE;QAC7C,EAAE,QAAQ,EAAE,gBAAgB,EAAE,QAAQ,EAAE,KAAK,EAAE;QAC/C,EAAE,QAAQ,EAAE,YAAY,EAAE,QAAQ,EAAE,KAAK,EAAE;QAC3C,EAAE,QAAQ,EAAE,iBAAiB,EAAE,QAAQ,EAAE,KAAK,EAAE;QAChD,EAAE,QAAQ,EAAE,kBAAkB,EAAE,QAAQ,EAAE,KAAK,EAAE;QACjD,EAAE,QAAQ,EAAE,SAAS,EAAE,QAAQ,EAAE,KAAK,EAAE;QACxC,EAAE,QAAQ,EAAE,sBAAsB,EAAE,QAAQ,EAAE,KAAK,EAAE,IAAI,EAAE,wHAAwH,EAAE;KACtL;IACD,SAAS,EAAE;QACT;YACE,QAAQ,EAAE,sBAAsB;YAChC,WAAW,EAAE,yCAAyC;YACtD,aAAa,EAAE,uTAAuT;SACvU;KACF;IACD,QAAQ,EAAE;QACR,WAAW,EAAE;YACX,gBAAgB;SACjB;KACF;IACD,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.capability-composition` and `bottom_up.foundation` (#1496):\n * the run short-circuits into the companion's maturity executor before any brief is composed,\n * because the reading is a PURE FUNCTION — `deriveApplicationMaturity` walks the requirements\n * family, the decided-element graph's inbound links and the build plan's landing probe. A model\n * asked where an application stands would ANSWER, and nothing could check the answer, which is the\n * one thing this family exists to prevent.\n *\n * It declares its `outputs` because the family IS landed through the generic renderer, so the\n * coherence report and the workbench have a producer to read. It carries no evaluation treatment:\n * there is no judgement in it to judge, only a measurement whose validator reports what the\n * APPLICATION lacks rather than what the artifact got wrong.\n *\n * **Not a gate, and nothing downstream may treat it as one.** Paul, 2026-09-22: *\"there are no\n * 'Done' for an app, there are a measurement face to requirements, with some stage.\"* The highest\n * stage says only that every requirement currently has the strongest evidence this framework can\n * produce; the next requirement lowers it again.\n */\nexport const playbookDefinition = {\n \"ref\": \"bottom_up.maturity-reading\",\n \"version\": \"0.1.0\",\n \"phase\": \"bottom_up\",\n \"intent\": \"Maturity reading — measure WHERE THIS APPLICATION STANDS against its own requirements, and record it as the `application-maturity` family: one row per requirement the application declares, the evidence that exists for it, and the stage that follows. DERIVED, never judged. Each row's level is reached by a measurement — a decided element that points at the requirement (a feature draft, an experience surface, a worker, a build task), a build task addressing it that has LANDED in committed bytes, a landed task whose declared product was PROVEN, or a runtime observation of the running application. The denominator is the requirements family itself, total and in its own order, so a requirement nothing addresses is a row rather than an omission and adding one lowers the reading with no code change. This is a MEASUREMENT and never a gate: there is no 'done' for an application, and the stage moves in both directions as the application and its requirements change.\",\n \"preconditions\": [\n /*\n * The REQUIREMENTS are the denominator, and a reading with no denominator is not a weaker\n * reading — it is a different statement (\"nothing has been asked of this application yet\").\n * `artifact_exists` because the CONTENT is read: the rows ARE its entries (#1434).\n */\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"requirements\" } }\n ],\n /*\n * Every family the derivation reads, declared so derived-staleness compares them: the reading goes\n * stale when any decided element that could address a requirement changes. `render: 'map'` on each\n * — the executor reads the VALUES itself through the artifact state, and no brief is composed for\n * this step, so a full render would reach nothing (#1434's lesson).\n *\n * The list is the families that declare an edge to a requirement TODAY. It is not how the\n * derivation finds them — that is the decided-element graph, which a family declaring such an edge\n * tomorrow joins without this file changing — so a missing entry costs staleness, never coverage.\n */\n \"inputs\": [\n { \"family\": \"requirements\", \"render\": \"map\" },\n { \"family\": \"feature-drafts\", \"render\": \"map\" },\n { \"family\": \"build-plan\", \"render\": \"map\" },\n { \"family\": \"experience-plan\", \"render\": \"map\" },\n { \"family\": \"integration-plan\", \"render\": \"map\" },\n { \"family\": \"roadmap\", \"render\": \"map\" },\n { \"family\": \"application-maturity\", \"render\": \"map\", \"//\": \"Its own family: the reading it replaces. Input, not precondition — a first run, with no prior reading, stays eligible.\" }\n ],\n \"outputs\": [\n {\n \"family\": \"application-maturity\",\n \"schemaRef\": \"saas-specifications:ApplicationMaturity\",\n \"description\": \"Where the application stands against its own requirements: one row per requirement with the evidence level it has reached and the elements, landed tasks, proven tasks and runtime observations that carry it, the thresholds the reading was scored against, and the stage that follows. A reading, never a verdict.\"\n }\n ],\n \"method\": {\n \"skillRefs\": [\n \"journey-status\"\n ]\n },\n \"approval\": \"approve_result\",\n \"budget\": {\n \"maxRuns\": 5\n },\n \"onFailure\": \"keep_and_flag\"\n} as const;\n"]}
|
|
@@ -24,7 +24,7 @@ export declare const playbookDefinition: {
|
|
|
24
24
|
readonly outputs: readonly [{
|
|
25
25
|
readonly family: "placement-plan";
|
|
26
26
|
readonly schemaRef: "saas-specifications:PlacementPlan";
|
|
27
|
-
readonly description: "The placement decision — `groups[]` (the containers that should exist on the grouped surfaces, each with the product purpose behind it) plus `decisions[]` (one per subject PER SURFACE: a stable `decisionRef`, the `PlacementSubject` being placed — an engine settings destination by ref, a resource operation, or an app view — a `PlacementDisposition` of PLACED or DECLINED, the surface-discriminated `PlacementAddress` when placed, and a REQUIRED `rationale` on both arms). Each decision also carries a REQUIRED `origin` — `DELIBERATED` or `REVISED` — which the trusted runtime stamps `DELIBERATED`; it is not representable in the provider-facing generation shape, because a panel run IS the panel's judgement and a model cannot declare its own output a human revision. A later edit that changes a decision sets `origin: REVISED` and records the panel's own reasoning in `supersedes.rationale`, so the artifact stops asserting panel reasoning for a decision the panel never took. Typed by the `_core` `placement-plan` family (`PlacementPlan`); the provider answers the strict `PlacementPlanGeneration` shape and the trusted runtime stamps refs and version. `validatePlacementPlan` is the deterministic validator: one subject placed twice on the SAME surface is a hard floor (the plan contradicts itself), while an empty group and an order collision are authoring warnings. Its coverage checks run per SUBJECT KIND and only for the kinds a caller supplies a catalog for,
|
|
27
|
+
readonly description: "The placement decision — `groups[]` (the containers that should exist on the grouped surfaces, each with the product purpose behind it) plus `decisions[]` (one per subject PER SURFACE: a stable `decisionRef`, the `PlacementSubject` being placed — an engine settings destination by ref, a resource operation, or an app view — a `PlacementDisposition` of PLACED or DECLINED, the surface-discriminated `PlacementAddress` when placed, and a REQUIRED `rationale` on both arms). Each decision also carries a REQUIRED `origin` — `DELIBERATED` or `REVISED` — which the trusted runtime stamps `DELIBERATED`; it is not representable in the provider-facing generation shape, because a panel run IS the panel's judgement and a model cannot declare its own output a human revision. A later edit that changes a decision sets `origin: REVISED` and records the panel's own reasoning in `supersedes.rationale`, so the artifact stops asserting panel reasoning for a decision the panel never took. Typed by the `_core` `placement-plan` family (`PlacementPlan`); the provider answers the strict `PlacementPlanGeneration` shape and the trusted runtime stamps refs and version. `validatePlacementPlan` is the deterministic validator: one subject placed twice on the SAME surface is a hard floor (the plan contradicts itself), while an empty group and an order collision are authoring warnings. Its coverage checks run per SUBJECT KIND and only for the kinds a caller supplies a catalog for, and the semantic authority currently supplies ENGINE_SETTINGS_DESTINATION_REFS for ENGINE_SETTINGS_DESTINATION. Unknown settings references are errors and missing settings decisions are warnings. This does not establish coverage for resource operations or application views: those kinds need their own supplied catalogues. A caller supplying no catalogue receives no coverage result, not a clean coverage result. The plan carries no file path, config key or label string — those belong to the coding task that authors the config.";
|
|
28
28
|
}];
|
|
29
29
|
readonly method: {
|
|
30
30
|
readonly "//contextSources": "WORKSPACE_TRUTH — placement is decided against what EXISTS: the real engine settings destinations, the real resources and their operations, and the shell surfaces the application already has. A planner working from the definition artifacts alone invents destination refs that resolve to nothing, and every decision it emits is unplaceable.";
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["
|
|
1
|
+
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.placement-plan/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA4CrB,CAAC"}
|
|
@@ -21,7 +21,7 @@ export const playbookDefinition = {
|
|
|
21
21
|
{
|
|
22
22
|
"family": "placement-plan",
|
|
23
23
|
"schemaRef": "saas-specifications:PlacementPlan",
|
|
24
|
-
"description": "The placement decision — `groups[]` (the containers that should exist on the grouped surfaces, each with the product purpose behind it) plus `decisions[]` (one per subject PER SURFACE: a stable `decisionRef`, the `PlacementSubject` being placed — an engine settings destination by ref, a resource operation, or an app view — a `PlacementDisposition` of PLACED or DECLINED, the surface-discriminated `PlacementAddress` when placed, and a REQUIRED `rationale` on both arms). Each decision also carries a REQUIRED `origin` — `DELIBERATED` or `REVISED` — which the trusted runtime stamps `DELIBERATED`; it is not representable in the provider-facing generation shape, because a panel run IS the panel's judgement and a model cannot declare its own output a human revision. A later edit that changes a decision sets `origin: REVISED` and records the panel's own reasoning in `supersedes.rationale`, so the artifact stops asserting panel reasoning for a decision the panel never took. Typed by the `_core` `placement-plan` family (`PlacementPlan`); the provider answers the strict `PlacementPlanGeneration` shape and the trusted runtime stamps refs and version. `validatePlacementPlan` is the deterministic validator: one subject placed twice on the SAME surface is a hard floor (the plan contradicts itself), while an empty group and an order collision are authoring warnings. Its coverage checks run per SUBJECT KIND and only for the kinds a caller supplies a catalog for,
|
|
24
|
+
"description": "The placement decision — `groups[]` (the containers that should exist on the grouped surfaces, each with the product purpose behind it) plus `decisions[]` (one per subject PER SURFACE: a stable `decisionRef`, the `PlacementSubject` being placed — an engine settings destination by ref, a resource operation, or an app view — a `PlacementDisposition` of PLACED or DECLINED, the surface-discriminated `PlacementAddress` when placed, and a REQUIRED `rationale` on both arms). Each decision also carries a REQUIRED `origin` — `DELIBERATED` or `REVISED` — which the trusted runtime stamps `DELIBERATED`; it is not representable in the provider-facing generation shape, because a panel run IS the panel's judgement and a model cannot declare its own output a human revision. A later edit that changes a decision sets `origin: REVISED` and records the panel's own reasoning in `supersedes.rationale`, so the artifact stops asserting panel reasoning for a decision the panel never took. Typed by the `_core` `placement-plan` family (`PlacementPlan`); the provider answers the strict `PlacementPlanGeneration` shape and the trusted runtime stamps refs and version. `validatePlacementPlan` is the deterministic validator: one subject placed twice on the SAME surface is a hard floor (the plan contradicts itself), while an empty group and an order collision are authoring warnings. Its coverage checks run per SUBJECT KIND and only for the kinds a caller supplies a catalog for, and the semantic authority currently supplies ENGINE_SETTINGS_DESTINATION_REFS for ENGINE_SETTINGS_DESTINATION. Unknown settings references are errors and missing settings decisions are warnings. This does not establish coverage for resource operations or application views: those kinds need their own supplied catalogues. A caller supplying no catalogue receives no coverage result, not a clean coverage result. The plan carries no file path, config key or label string — those belong to the coding task that authors the config."
|
|
25
25
|
}
|
|
26
26
|
],
|
|
27
27
|
"method": {
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["
|
|
1
|
+
{"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.placement-plan/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAC/B;IACE,KAAK,EAAE,0BAA0B;IACjC,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,WAAW;IACpB,QAAQ,EAAE,2+CAA2+C;IACr/C,eAAe,EAAE;QACf,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,aAAa,EAAE,EAAE;KACvE;IACD,QAAQ,EAAE;QACR,EAAE,QAAQ,EAAE,aAAa,EAAE;QAC3B,EAAE,QAAQ,EAAE,cAAc,EAAE;KAC7B;IACD,SAAS,EAAE;QACT;YACE,QAAQ,EAAE,gBAAgB;YAC1B,WAAW,EAAE,mCAAmC;YAChD,aAAa,EAAE,g9DAAg9D;SACh+D;KACF;IACD,QAAQ,EAAE;QACR,kBAAkB,EAAE,qVAAqV;QACzW,gBAAgB,EAAE,CAAC,iBAAiB,CAAC;QACrC,WAAW,EAAE;YACX,8BAA8B;YAC9B,kBAAkB;YAClB,mBAAmB;YACnB,gBAAgB;SACjB;QACD,gBAAgB,EAAE,4pBAA4pB;QAC9qB,cAAc,EAAE;YACd,YAAY,EAAE,0BAA0B;YACxC,kBAAkB,EAAE,CAAC,uBAAuB,EAAE,wBAAwB,CAAC;YACvE,oBAAoB,EAAE,wBAAwB;YAC9C,sBAAsB,EAAE,uBAAuB;YAC/C,gBAAgB,EAAE,CAAC;SACpB;KACF;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 * Placement is a DECISION the creator should not have to make. This playbook\n * produces it as an artifact, with a per-decision rationale, so a later reader\n * can ask \"why is this here?\" without re-deriving the answer.\n */\nexport const playbookDefinition =\n{\n \"ref\": \"bottom_up.placement-plan\",\n \"version\": \"0.1.0\",\n \"phase\": \"bottom_up\",\n \"intent\": \"Decide WHERE every settings destination, resource operation and application view sits in the application shell, and WHY. Reads the domain plan (the modules, their resources and what they mean) and the requirements (which tasks matter), and produces a PLACEMENT PLAN: for each subject, either a PLACED decision naming one surface (the settings hub rail, the sidebar, the user menu, the command palette) and its address on that surface, or an explicit DECLINED decision with a reason. Both carry a rationale. It also declares the GROUPS that should exist on the grouped surfaces (settings rail categories, sidebar sections) with the product purpose behind each, which is what grounds their generated labels in authored intent instead of filler. This playbook DECIDES placement; it does NOT author configuration — turning a decision into `frontend/src/config/settings-hub.config.ts` and `app-shell.config.ts` is a coding task the build lane dispatches through the `settings-placement-authoring` skill. It runs BEFORE build-decompose, which consumes the plan and emits those tasks — the reverse order would be a cycle, since build-decompose is what produces the build plan. It writes no TypeScript, invents no destination refs, and authors no labels. It exists because the alternative is the framework defaulting placement, which is what made an application's settings rail unauthorable: nothing is placed implicitly, so a subject nobody decided about is a visible coverage gap rather than a silent framework default.\",\n \"preconditions\": [\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"domain-plan\" } }\n ],\n \"inputs\": [\n { \"family\": \"domain-plan\" },\n { \"family\": \"requirements\" }\n ],\n \"outputs\": [\n {\n \"family\": \"placement-plan\",\n \"schemaRef\": \"saas-specifications:PlacementPlan\",\n \"description\": \"The placement decision — `groups[]` (the containers that should exist on the grouped surfaces, each with the product purpose behind it) plus `decisions[]` (one per subject PER SURFACE: a stable `decisionRef`, the `PlacementSubject` being placed — an engine settings destination by ref, a resource operation, or an app view — a `PlacementDisposition` of PLACED or DECLINED, the surface-discriminated `PlacementAddress` when placed, and a REQUIRED `rationale` on both arms). Each decision also carries a REQUIRED `origin` — `DELIBERATED` or `REVISED` — which the trusted runtime stamps `DELIBERATED`; it is not representable in the provider-facing generation shape, because a panel run IS the panel's judgement and a model cannot declare its own output a human revision. A later edit that changes a decision sets `origin: REVISED` and records the panel's own reasoning in `supersedes.rationale`, so the artifact stops asserting panel reasoning for a decision the panel never took. Typed by the `_core` `placement-plan` family (`PlacementPlan`); the provider answers the strict `PlacementPlanGeneration` shape and the trusted runtime stamps refs and version. `validatePlacementPlan` is the deterministic validator: one subject placed twice on the SAME surface is a hard floor (the plan contradicts itself), while an empty group and an order collision are authoring warnings. Its coverage checks run per SUBJECT KIND and only for the kinds a caller supplies a catalog for, and the semantic authority currently supplies ENGINE_SETTINGS_DESTINATION_REFS for ENGINE_SETTINGS_DESTINATION. Unknown settings references are errors and missing settings decisions are warnings. This does not establish coverage for resource operations or application views: those kinds need their own supplied catalogues. A caller supplying no catalogue receives no coverage result, not a clean coverage result. The plan carries no file path, config key or label string — those belong to the coding task that authors the config.\"\n }\n ],\n \"method\": {\n \"//contextSources\": \"WORKSPACE_TRUTH — placement is decided against what EXISTS: the real engine settings destinations, the real resources and their operations, and the shell surfaces the application already has. A planner working from the definition artifacts alone invents destination refs that resolve to nothing, and every decision it emits is unplaceable.\",\n \"contextSources\": [\"workspace_truth\"],\n \"skillRefs\": [\n \"settings-placement-authoring\",\n \"config-app-shell\",\n \"config-navigation\",\n \"journey-status\"\n ],\n \"//deliberation\": \"Placement is DECIDED BY A PANEL, not elicited from the creator: the arrangement that is right for an application has several defensible answers, and the creator is the person least equipped to choose between them before the app exists. The information-architect OWNS the domain (so it derives the rubric); the design-system-guardian sits as the coherence memory, because where a thing goes must not fork the pattern the shipped surfaces already taught users. Three candidates, because the criteria trade off against each other — first-run discoverability, the daily-use path, and category convention pull in different directions and a single pass silently picks one.\",\n \"deliberation\": {\n \"workDomain\": \"information_architecture\",\n \"reviewerRoleRefs\": [\"information-architect\", \"design-system-guardian\"],\n \"coordinatorRoleRef\": \"design-system-guardian\",\n \"rubricDeriverRoleRef\": \"information-architect\",\n \"candidateCount\": 3\n }\n },\n \"executor\": \"companion_agent\",\n \"approval\": \"approve_result\",\n \"budget\": {\n \"maxRuns\": 3\n },\n \"onFailure\": \"keep_and_flag\"\n} as const;\n"]}
|
|
@@ -0,0 +1,71 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* Canonical native declaration for this reusable application-creation method.
|
|
3
|
+
*
|
|
4
|
+
* The website lane's one leaf (#1492). It reads the market snapshot the top-down lane produced —
|
|
5
|
+
* positioning, ICPs, tones of voice, proofs, objections, benefits — the brand brief and the
|
|
6
|
+
* business model's pricing plans, and decides WHAT THE MARKETING SITE SAYS: its pages, their
|
|
7
|
+
* sections in reading order, and the market entries each section draws on.
|
|
8
|
+
*
|
|
9
|
+
* It does NOT write the site. `bottom_up.build-decompose` turns each page into a `WEBSITE_PAGE`
|
|
10
|
+
* task and each section into a `WEBSITE_SECTION` task bound to the skill that section's KIND names,
|
|
11
|
+
* because the build plan has ONE producer and a second would destroy the first's output (#895).
|
|
12
|
+
*
|
|
13
|
+
* The 23 `website-*` skills the framework ships were named by NO playbook until this one — the
|
|
14
|
+
* largest finished asset in the catalog with no door. The site-level ones are this method's
|
|
15
|
+
* `skillRefs`; the nine section skills are reached through `WEBSITE_SECTION_SKILL_REF`, which is
|
|
16
|
+
* total over the section vocabulary, so a kind added without its skill does not compile.
|
|
17
|
+
*/
|
|
18
|
+
export declare const playbookDefinition: {
|
|
19
|
+
readonly ref: "bottom_up.website-plan";
|
|
20
|
+
readonly version: "0.1.0";
|
|
21
|
+
readonly phase: "bottom_up";
|
|
22
|
+
readonly intent: "Website plan — decide WHAT THE MARKETING WEBSITE SAYS for this application: which pages it has, what each page is for and who it is written for, and the sections that carry each page's argument in reading order, each drawing on the market entries the top-down lane authored (benefits, proofs, objections, jobs, pains, ICPs, tones of voice). Reads the capability composition FIRST: an application whose composition declined a website lands a NOT_APPLICABLE plan stating why, which is a complete answer rather than an empty artifact. A section's KIND (hero, benefits summary, benefit in detail, pricing, proof, objections answered, call to action, closing call to action, contact) names the shipped `website-section-*` skill that authors it, so the build lane can bind each emitted task to its skill without a model naming folders. Produces the plan; `bottom_up.build-decompose` turns it into the page and section tasks a coding agent runs, and the `add-website` composition scenario is what creates the `website/` workspace they write in.";
|
|
23
|
+
readonly preconditions: readonly [{
|
|
24
|
+
readonly kind: "artifact_exists";
|
|
25
|
+
readonly selector: {
|
|
26
|
+
readonly family: "capability-composition";
|
|
27
|
+
};
|
|
28
|
+
}, {
|
|
29
|
+
readonly kind: "artifact_exists";
|
|
30
|
+
readonly selector: {
|
|
31
|
+
readonly family: "market-snapshot";
|
|
32
|
+
};
|
|
33
|
+
}];
|
|
34
|
+
readonly inputs: readonly [{
|
|
35
|
+
readonly family: "capability-composition";
|
|
36
|
+
readonly "//": "Whether this application has a website, and the declaration that decided it.";
|
|
37
|
+
}, {
|
|
38
|
+
readonly family: "market-snapshot";
|
|
39
|
+
readonly "//": "The substance of every section: benefits, proofs, objections, jobs, pains, ICPs, tones of voice, positioning.";
|
|
40
|
+
}, {
|
|
41
|
+
readonly family: "brand-brief";
|
|
42
|
+
readonly render: "map";
|
|
43
|
+
readonly "//": "Whether the product has a name and a visual tone to present. The plan needs to know it EXISTS and who it addresses; the site's own chrome is authored by the build tasks (#1424's reading).";
|
|
44
|
+
}, {
|
|
45
|
+
readonly family: "business-model";
|
|
46
|
+
readonly "//": "The pricing plans a PRICING section presents — a pricing page with no plan behind it is a page about nothing.";
|
|
47
|
+
}, {
|
|
48
|
+
readonly family: "vision-brief";
|
|
49
|
+
readonly "//": "The product's own one-liner and differentiation, which a hero states before any market entry qualifies it.";
|
|
50
|
+
}, {
|
|
51
|
+
readonly family: "website-plan";
|
|
52
|
+
readonly "//": "Its own family: its method refines its own prior output and keeps its page refs, so it must be GIVEN that output (#1430). Input, not precondition: a first run stays eligible.";
|
|
53
|
+
}];
|
|
54
|
+
readonly outputs: readonly [{
|
|
55
|
+
readonly family: "website-plan";
|
|
56
|
+
readonly schemaRef: "saas-specifications:WebsitePlan";
|
|
57
|
+
readonly description: "What the marketing site says: a disposition (PLANNED, or NOT_APPLICABLE when the capability composition declined a website) with its rationale, and — when planned — the pages in navigation order, each with its purpose, the ICPs it is written for, its tone of voice, and its sections in reading order. Each section carries its KIND (which names the skill that authors it), what it does for the reader, and the market entries it draws on.";
|
|
58
|
+
}];
|
|
59
|
+
readonly method: {
|
|
60
|
+
readonly contextSources: readonly ["market_fit_scores"];
|
|
61
|
+
readonly skillBodyRefs: readonly ["website-page-authoring"];
|
|
62
|
+
readonly skillRefs: readonly ["journey-status", "website-page-authoring", "website-navigation-authoring", "website-seo-aeo-geo", "website-label-pack", "website-marketing-metadata-extension", "market-positioning-authoring", "market-tone-of-voice", "market-proof-and-objection"];
|
|
63
|
+
};
|
|
64
|
+
readonly executor: "companion_agent";
|
|
65
|
+
readonly approval: "approve_result";
|
|
66
|
+
readonly budget: {
|
|
67
|
+
readonly maxRuns: 3;
|
|
68
|
+
};
|
|
69
|
+
readonly onFailure: "keep_and_flag";
|
|
70
|
+
};
|
|
71
|
+
//# sourceMappingURL=playbook.definition.d.ts.map
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.website-plan/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;GAgBG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAqErB,CAAC"}
|