@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
|
@@ -0,0 +1,236 @@
|
|
|
1
|
+
# Placement Plan — Where Each Thing Belongs in the Shell, and Why
|
|
2
|
+
|
|
3
|
+
### Target Application Framing
|
|
4
|
+
|
|
5
|
+
This knowledge is for configuring behavior in the target application.
|
|
6
|
+
Wildo is the framework surface being used, not the product being built.
|
|
7
|
+
|
|
8
|
+
Read and apply these patterns from the application-developer point of view:
|
|
9
|
+
|
|
10
|
+
- how the application should configure the relevant app-level file
|
|
11
|
+
- how the application should use framework-provided factories, enums, and helpers
|
|
12
|
+
- how the application should avoid mixing frontend, backend, and infrastructure concerns
|
|
13
|
+
|
|
14
|
+
|
|
15
|
+
> **This is a v1 methodology.** The criteria below are deliberately explicit so
|
|
16
|
+
> they can be tuned against real runs. What is NOT provisional is the shape of the
|
|
17
|
+
> output: a decision per subject, on a named surface, with a rationale.
|
|
18
|
+
|
|
19
|
+
## Where you are in the journey
|
|
20
|
+
|
|
21
|
+
You run in the **bottom-up phase**, after the **domain plan** exists and **before**
|
|
22
|
+
the build is decomposed. By now the application knows what its modules and resources
|
|
23
|
+
ARE; what nobody has decided is **where any of it appears**.
|
|
24
|
+
|
|
25
|
+
That order matters and was corrected during authoring. Placing things *after* the
|
|
26
|
+
build plan reads natural — you would know every task — but `bottom_up.build-decompose`
|
|
27
|
+
is what PRODUCES the build plan and it consumes this one to emit the placement tasks.
|
|
28
|
+
Requiring its output would be a cycle. It is also the better order on its own merits:
|
|
29
|
+
placement is a design decision that should INFORM the decomposition, not trail it. You
|
|
30
|
+
do not need the task graph to know that a `deals` resource will have a list.
|
|
31
|
+
|
|
32
|
+
That question used to have no owner. The framework shipped a placed settings rail,
|
|
33
|
+
so an application could not add, remove, reorder or rename a section without the
|
|
34
|
+
framework agreeing — and the application's own config file did not tell you what a
|
|
35
|
+
user would see. Placement is now the application's, which means somebody has to
|
|
36
|
+
decide it. That is this playbook.
|
|
37
|
+
|
|
38
|
+
## What this playbook does
|
|
39
|
+
|
|
40
|
+
You produce a **placement plan**: for every subject, one decision per surface.
|
|
41
|
+
|
|
42
|
+
A **subject** is one of three things:
|
|
43
|
+
|
|
44
|
+
- an **engine settings destination**, named by its ref from the engine catalog
|
|
45
|
+
(`profile`, `security`, `billing`, `sso`, …) — the engine owns what each MEANS
|
|
46
|
+
(its target, its required roles, its entitlement); it owns nothing about where it
|
|
47
|
+
goes;
|
|
48
|
+
- a **resource operation** — a resource's LIST, its READ, a custom verb;
|
|
49
|
+
- an **application view** — composite, chart, execution, full-custom.
|
|
50
|
+
|
|
51
|
+
A **surface** is one of four:
|
|
52
|
+
|
|
53
|
+
| surface | grouped by | authoring home |
|
|
54
|
+
|---|---|---|
|
|
55
|
+
| `SETTINGS_HUB` | a rail **category** | `frontend/src/config/settings-hub.config.ts` |
|
|
56
|
+
| `SIDEBAR` | a sidebar **section** | `appShellConfig[SIDEBAR].contentSections` |
|
|
57
|
+
| `USER_MENU` | flat | the user dropdown's settings entries |
|
|
58
|
+
| `COMMAND_MENU` | flat | the command palette |
|
|
59
|
+
|
|
60
|
+
A subject may legitimately be placed on **several** surfaces — billing is a settings
|
|
61
|
+
rail section AND answers to the command palette. One decision per (subject, surface);
|
|
62
|
+
two placements of one subject on ONE surface is a contradiction and the validator
|
|
63
|
+
refuses it.
|
|
64
|
+
|
|
65
|
+
**Not every surface can carry every kind of subject**, and the validator refuses a
|
|
66
|
+
placement that no configuration could realise (`SUBJECT_NOT_EXPRESSIBLE_ON_SURFACE`,
|
|
67
|
+
a hard floor):
|
|
68
|
+
|
|
69
|
+
| surface | engine destination | resource operation | application view |
|
|
70
|
+
|---|---|---|---|
|
|
71
|
+
| `SETTINGS_HUB` | yes | yes — as a settings section the application declares for it | **no** |
|
|
72
|
+
| `USER_MENU` | yes | yes — the same application settings section, opened from the dropdown | **no** |
|
|
73
|
+
| `SIDEBAR` | yes | yes | yes |
|
|
74
|
+
| `COMMAND_MENU` | yes | yes | yes |
|
|
75
|
+
|
|
76
|
+
The settings rail and the user dropdown hold settings SECTIONS. A section can show a
|
|
77
|
+
resource operation (a list of the team's members, say), a framework panel, or a
|
|
78
|
+
component the application registers; it cannot show an application view. A view
|
|
79
|
+
that people reach from settings belongs on the sidebar or the palette.
|
|
80
|
+
|
|
81
|
+
## Decline explicitly; never omit
|
|
82
|
+
|
|
83
|
+
Every decision is `PLACED` or `DECLINED`, and **both require a rationale**.
|
|
84
|
+
|
|
85
|
+
This is the rule most worth getting right. A subject recorded as `DECLINED` is a
|
|
86
|
+
decision a later reader can disagree with. A subject simply missing from the plan is
|
|
87
|
+
a **coverage gap** — nobody looked. If those two were the same thing, "we considered
|
|
88
|
+
the audit log and this app has no compliance audience" would be indistinguishable
|
|
89
|
+
from forgetting the audit log existed.
|
|
90
|
+
|
|
91
|
+
So: if a destination should not appear anywhere in this application, say so, and say
|
|
92
|
+
why.
|
|
93
|
+
|
|
94
|
+
## The criteria, in the order you apply them
|
|
95
|
+
|
|
96
|
+
1. **Scope correctness.** A thing that acts on the whole organization does not sit
|
|
97
|
+
among a person's own preferences, and the reverse. This is first because it is
|
|
98
|
+
the only criterion that is objectively *wrong* rather than debatable.
|
|
99
|
+
2. **Findability.** Would the user who wants this look here FIRST — unprompted?
|
|
100
|
+
Not "would they accept it once shown". Those are different tests and only the
|
|
101
|
+
first one predicts behaviour.
|
|
102
|
+
3. **Grouping coherence.** Everything in a group answers one question a user
|
|
103
|
+
actually asks. A group that needs "and other things" in its name is two groups.
|
|
104
|
+
4. **Convention fit.** Users arrive with expectations already formed by comparable
|
|
105
|
+
products. A novel arrangement must EARN the cost of surprising them.
|
|
106
|
+
5. **Depth discipline.** One more level of nesting must buy more than it costs. A
|
|
107
|
+
section reachable only after three guesses is not placed, it is hidden.
|
|
108
|
+
|
|
109
|
+
Reject placements justified by implementation convenience ("it renders there
|
|
110
|
+
already"), by the shape of the data model rather than the user's task, or by symmetry
|
|
111
|
+
for its own sake. Surfacing something everywhere is a **cost**, not thoroughness.
|
|
112
|
+
|
|
113
|
+
## Groups carry a purpose, and the purpose is load-bearing
|
|
114
|
+
|
|
115
|
+
When you declare a group, state its `purpose` in product terms. It is not decoration:
|
|
116
|
+
it is what grounds the generated `settings_hub.categories.<ref>.label` and
|
|
117
|
+
`sidebar_sections.<ref>.title` labels in authored intent. Without it a model invents
|
|
118
|
+
filler from the ref alone — which is exactly how a sidebar section came to be
|
|
119
|
+
described as "various tools and utilities".
|
|
120
|
+
|
|
121
|
+
## Placing an operator surface commits the application to an AUDIENCE — say which
|
|
122
|
+
|
|
123
|
+
Some subjects exist for whoever OPERATES the product rather than for the people who use it:
|
|
124
|
+
application-wide single sign-on, the application's own API keys and OAuth clients, the
|
|
125
|
+
entitlement state of every tenant, the plans and prices on sale, the application-wide audit
|
|
126
|
+
trail. The framework keeps them in a separate preset scope from the end-user surfaces, and it
|
|
127
|
+
keeps them separate ON PURPOSE — an application may legitimately never render them.
|
|
128
|
+
|
|
129
|
+
**So placing one is a decision about what this application IS, and the plan must state it.**
|
|
130
|
+
Two answers, both correct:
|
|
131
|
+
|
|
132
|
+
- **ONE application.** Operators and users share a frontend and are told apart by their roles.
|
|
133
|
+
Place the operator subjects in their own group — an `administration` category beside the
|
|
134
|
+
account and organization ones — and record that this application composes BOTH preset scopes.
|
|
135
|
+
- **TWO applications.** A separate operator frontend. Decline the operator subjects here, with
|
|
136
|
+
that as the rationale, and they belong to the other application's plan.
|
|
137
|
+
|
|
138
|
+
State the answer in the plan even when it is the obvious one, because the failure it prevents is
|
|
139
|
+
silent: an application that places operator subjects while composing only the end-user scope gets
|
|
140
|
+
rail entries that OPEN AND RENDER NOTHING. An operation no composed preset surfaces is
|
|
141
|
+
callable-from-code with no interface, so the section is not missing and does not error — it is
|
|
142
|
+
blank, and it reads as a slow load or a broken backend rather than as an application that was
|
|
143
|
+
assembled without an audience. Seventeen sections were in exactly that state on the dogfood
|
|
144
|
+
application before this was written down.
|
|
145
|
+
|
|
146
|
+
You are not choosing the composition here — that is a coding task the build lane dispatches
|
|
147
|
+
through `settings-placement-authoring`. You are stating WHICH audience the arrangement assumes,
|
|
148
|
+
so the task that follows has something to implement rather than a default to guess.
|
|
149
|
+
|
|
150
|
+
## What you do NOT do
|
|
151
|
+
|
|
152
|
+
- **You do not author configuration.** Turning a decision into
|
|
153
|
+
`settings-hub.config.ts` or `app-shell.config.ts` is a coding task the build lane
|
|
154
|
+
dispatches through the `settings-placement-authoring` skill. If you catch yourself
|
|
155
|
+
writing a config key, a file path or a label string, stop.
|
|
156
|
+
- **You do not invent destination refs.** The workspace-truth section lists every engine
|
|
157
|
+
settings destination under **"Settings destinations the engine ships"**, with what each
|
|
158
|
+
one shows and its role gating. That list is the whole universe: a ref outside it is an
|
|
159
|
+
`UNKNOWN_SUBJECT` and the validator REFUSES the plan — a hard floor, not a warning. Rule
|
|
160
|
+
on all of them where you can; a destination your plan says nothing about is reported
|
|
161
|
+
undecided.
|
|
162
|
+
- **You do not decide what a destination MEANS.** Its target, roles and entitlement
|
|
163
|
+
are the engine's. You decide only where it sits.
|
|
164
|
+
- **You do not re-open the build plan.** What is being built is settled.
|
|
165
|
+
|
|
166
|
+
## Verification
|
|
167
|
+
|
|
168
|
+
- Every subject the workspace offers is either PLACED or DECLINED — nothing omitted.
|
|
169
|
+
- No subject placed twice on one surface.
|
|
170
|
+
- No application view placed on the settings rail or the user dropdown.
|
|
171
|
+
- Every grouped placement names a group this plan declares, for that same surface.
|
|
172
|
+
- Every group has something in it.
|
|
173
|
+
- Every decision, both arms, carries a rationale that would satisfy a reader who
|
|
174
|
+
disagrees with it.
|
|
175
|
+
- The plan states which AUDIENCE it assumes — one application or two — whenever it places or
|
|
176
|
+
declines an operator subject.
|
|
177
|
+
|
|
178
|
+
## WHO decides — a panel, not you alone and not the creator
|
|
179
|
+
|
|
180
|
+
**The creator does not choose placement.** This playbook convenes an expert panel and
|
|
181
|
+
takes its winner.
|
|
182
|
+
|
|
183
|
+
Concretely, on every run: three candidate arrangements are generated independently
|
|
184
|
+
against this brief, each schema-valid before anyone sees it and each told to take a
|
|
185
|
+
genuinely different position; the **information-architect** derives the rubric (it
|
|
186
|
+
owns the domain); it and the **design-system-guardian** review every candidate; the
|
|
187
|
+
guardian coordinates, shortlists, and synthesises a winner. What lands is that winner.
|
|
188
|
+
|
|
189
|
+
Two consequences for how you write:
|
|
190
|
+
|
|
191
|
+
- **Take a position and commit to it.** You are one candidate among three, and the
|
|
192
|
+
panel cannot compare three hedged arrangements. State what your arrangement makes
|
|
193
|
+
WORSE — an arrangement with no cost has not been thought about, and the reviewers
|
|
194
|
+
are instructed to notice.
|
|
195
|
+
- **The rationale on each decision is the durable part.** It is what a creator asking
|
|
196
|
+
"why is Billing under Organization?" reads, and it is the only trace of the argument
|
|
197
|
+
once the winner has landed.
|
|
198
|
+
|
|
199
|
+
**Fail-closed on charters.** Every panel role needs a committed charter, and the
|
|
200
|
+
companion indexes agents at startup — a charter accepted after boot has no agent until
|
|
201
|
+
a restart, and the error says exactly that. The run does NOT quietly degrade to a
|
|
202
|
+
single generation: an artifact carrying a panel's authority over a decision no panel
|
|
203
|
+
saw is the worst outcome available here, so fewer than two usable candidates returns
|
|
204
|
+
to the ordinary retry instead.
|
|
205
|
+
|
|
206
|
+
## And when the placement is wrong
|
|
207
|
+
|
|
208
|
+
Two different things can change, and conflating them is how a plan starts lying.
|
|
209
|
+
|
|
210
|
+
**The config file** — `settings-hub.config.ts`, `app-shell.config.ts` — is what actually
|
|
211
|
+
renders. A creator who disagrees edits it directly. That works today, needs no companion,
|
|
212
|
+
and is a git commit, which is the accepted state.
|
|
213
|
+
|
|
214
|
+
**The plan** is the decision record, and it is what a later reader consults to ask why.
|
|
215
|
+
It can be changed two ways:
|
|
216
|
+
|
|
217
|
+
- **Re-run this playbook.** The panel deliberates again and the landing REPLACES the
|
|
218
|
+
existing file. Nothing refuses it; that is the design.
|
|
219
|
+
- **Edit the landed plan.** It is an application-owned source like any other.
|
|
220
|
+
|
|
221
|
+
Either way, a decision that no longer reflects the panel must say so. Set its `origin`
|
|
222
|
+
to `REVISED` and record what the panel had decided in `supersedes.rationale`. Both are
|
|
223
|
+
required together — the schema refuses a `REVISED` decision with nothing superseded, and
|
|
224
|
+
refuses a `DELIBERATED` one that supersedes something, because no panel run produces
|
|
225
|
+
either shape.
|
|
226
|
+
|
|
227
|
+
**Why the artifact carries this when git already records the change.** Git knows who
|
|
228
|
+
changed the line, when, and with what message, and that is not being duplicated here. What
|
|
229
|
+
git cannot tell someone READING the file — in an editor, asking "why is Billing under
|
|
230
|
+
Account?" — is that this particular decision is no longer the panel's. Without it, the
|
|
231
|
+
`rationale` field goes on asserting panel reasoning for a decision the panel never took,
|
|
232
|
+
and there is no way to notice.
|
|
233
|
+
|
|
234
|
+
Do not paraphrase the panel's rationale into the new one. A `supersedes.rationale` that
|
|
235
|
+
repeats the decision's own text word for word satisfies the schema and tells a reader
|
|
236
|
+
nothing; the validator reports it as an authoring warning.
|
|
@@ -0,0 +1,63 @@
|
|
|
1
|
+
{
|
|
2
|
+
"ref": "bottom_up.placement-plan",
|
|
3
|
+
"version": "0.1.0",
|
|
4
|
+
"phase": "bottom_up",
|
|
5
|
+
"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.",
|
|
6
|
+
"preconditions": [
|
|
7
|
+
{
|
|
8
|
+
"kind": "artifact_exists",
|
|
9
|
+
"selector": {
|
|
10
|
+
"family": "domain-plan"
|
|
11
|
+
}
|
|
12
|
+
}
|
|
13
|
+
],
|
|
14
|
+
"inputs": [
|
|
15
|
+
{
|
|
16
|
+
"family": "domain-plan"
|
|
17
|
+
},
|
|
18
|
+
{
|
|
19
|
+
"family": "requirements"
|
|
20
|
+
}
|
|
21
|
+
],
|
|
22
|
+
"outputs": [
|
|
23
|
+
{
|
|
24
|
+
"family": "placement-plan",
|
|
25
|
+
"schemaRef": "saas-specifications:PlacementPlan",
|
|
26
|
+
"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."
|
|
27
|
+
}
|
|
28
|
+
],
|
|
29
|
+
"stepOutputs": [],
|
|
30
|
+
"method": {
|
|
31
|
+
"guidance": "# Placement Plan — Where Each Thing Belongs in the Shell, and Why\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 methodology.** The criteria below are deliberately explicit so\n> they can be tuned against real runs. What is NOT provisional is the shape of the\n> output: a decision per subject, on a named surface, with a rationale.\n\n## Where you are in the journey\n\nYou run in the **bottom-up phase**, after the **domain plan** exists and **before**\nthe build is decomposed. By now the application knows what its modules and resources\nARE; what nobody has decided is **where any of it appears**.\n\nThat order matters and was corrected during authoring. Placing things *after* the\nbuild plan reads natural — you would know every task — but `bottom_up.build-decompose`\nis what PRODUCES the build plan and it consumes this one to emit the placement tasks.\nRequiring its output would be a cycle. It is also the better order on its own merits:\nplacement is a design decision that should INFORM the decomposition, not trail it. You\ndo not need the task graph to know that a `deals` resource will have a list.\n\nThat question used to have no owner. The framework shipped a placed settings rail,\nso an application could not add, remove, reorder or rename a section without the\nframework agreeing — and the application's own config file did not tell you what a\nuser would see. Placement is now the application's, which means somebody has to\ndecide it. That is this playbook.\n\n## What this playbook does\n\nYou produce a **placement plan**: for every subject, one decision per surface.\n\nA **subject** is one of three things:\n\n- an **engine settings destination**, named by its ref from the engine catalog\n (`profile`, `security`, `billing`, `sso`, …) — the engine owns what each MEANS\n (its target, its required roles, its entitlement); it owns nothing about where it\n goes;\n- a **resource operation** — a resource's LIST, its READ, a custom verb;\n- an **application view** — composite, chart, execution, full-custom.\n\nA **surface** is one of four:\n\n| surface | grouped by | authoring home |\n|---|---|---|\n| `SETTINGS_HUB` | a rail **category** | `frontend/src/config/settings-hub.config.ts` |\n| `SIDEBAR` | a sidebar **section** | `appShellConfig[SIDEBAR].contentSections` |\n| `USER_MENU` | flat | the user dropdown's settings entries |\n| `COMMAND_MENU` | flat | the command palette |\n\nA subject may legitimately be placed on **several** surfaces — billing is a settings\nrail section AND answers to the command palette. One decision per (subject, surface);\ntwo placements of one subject on ONE surface is a contradiction and the validator\nrefuses it.\n\n**Not every surface can carry every kind of subject**, and the validator refuses a\nplacement that no configuration could realise (`SUBJECT_NOT_EXPRESSIBLE_ON_SURFACE`,\na hard floor):\n\n| surface | engine destination | resource operation | application view |\n|---|---|---|---|\n| `SETTINGS_HUB` | yes | yes — as a settings section the application declares for it | **no** |\n| `USER_MENU` | yes | yes — the same application settings section, opened from the dropdown | **no** |\n| `SIDEBAR` | yes | yes | yes |\n| `COMMAND_MENU` | yes | yes | yes |\n\nThe settings rail and the user dropdown hold settings SECTIONS. A section can show a\nresource operation (a list of the team's members, say), a framework panel, or a\ncomponent the application registers; it cannot show an application view. A view\nthat people reach from settings belongs on the sidebar or the palette.\n\n## Decline explicitly; never omit\n\nEvery decision is `PLACED` or `DECLINED`, and **both require a rationale**.\n\nThis is the rule most worth getting right. A subject recorded as `DECLINED` is a\ndecision a later reader can disagree with. A subject simply missing from the plan is\na **coverage gap** — nobody looked. If those two were the same thing, \"we considered\nthe audit log and this app has no compliance audience\" would be indistinguishable\nfrom forgetting the audit log existed.\n\nSo: if a destination should not appear anywhere in this application, say so, and say\nwhy.\n\n## The criteria, in the order you apply them\n\n1. **Scope correctness.** A thing that acts on the whole organization does not sit\n among a person's own preferences, and the reverse. This is first because it is\n the only criterion that is objectively *wrong* rather than debatable.\n2. **Findability.** Would the user who wants this look here FIRST — unprompted?\n Not \"would they accept it once shown\". Those are different tests and only the\n first one predicts behaviour.\n3. **Grouping coherence.** Everything in a group answers one question a user\n actually asks. A group that needs \"and other things\" in its name is two groups.\n4. **Convention fit.** Users arrive with expectations already formed by comparable\n products. A novel arrangement must EARN the cost of surprising them.\n5. **Depth discipline.** One more level of nesting must buy more than it costs. A\n section reachable only after three guesses is not placed, it is hidden.\n\nReject placements justified by implementation convenience (\"it renders there\nalready\"), by the shape of the data model rather than the user's task, or by symmetry\nfor its own sake. Surfacing something everywhere is a **cost**, not thoroughness.\n\n## Groups carry a purpose, and the purpose is load-bearing\n\nWhen you declare a group, state its `purpose` in product terms. It is not decoration:\nit is what grounds the generated `settings_hub.categories.<ref>.label` and\n`sidebar_sections.<ref>.title` labels in authored intent. Without it a model invents\nfiller from the ref alone — which is exactly how a sidebar section came to be\ndescribed as \"various tools and utilities\".\n\n## Placing an operator surface commits the application to an AUDIENCE — say which\n\nSome subjects exist for whoever OPERATES the product rather than for the people who use it:\napplication-wide single sign-on, the application's own API keys and OAuth clients, the\nentitlement state of every tenant, the plans and prices on sale, the application-wide audit\ntrail. The framework keeps them in a separate preset scope from the end-user surfaces, and it\nkeeps them separate ON PURPOSE — an application may legitimately never render them.\n\n**So placing one is a decision about what this application IS, and the plan must state it.**\nTwo answers, both correct:\n\n- **ONE application.** Operators and users share a frontend and are told apart by their roles.\n Place the operator subjects in their own group — an `administration` category beside the\n account and organization ones — and record that this application composes BOTH preset scopes.\n- **TWO applications.** A separate operator frontend. Decline the operator subjects here, with\n that as the rationale, and they belong to the other application's plan.\n\nState the answer in the plan even when it is the obvious one, because the failure it prevents is\nsilent: an application that places operator subjects while composing only the end-user scope gets\nrail entries that OPEN AND RENDER NOTHING. An operation no composed preset surfaces is\ncallable-from-code with no interface, so the section is not missing and does not error — it is\nblank, and it reads as a slow load or a broken backend rather than as an application that was\nassembled without an audience. Seventeen sections were in exactly that state on the dogfood\napplication before this was written down.\n\nYou are not choosing the composition here — that is a coding task the build lane dispatches\nthrough `settings-placement-authoring`. You are stating WHICH audience the arrangement assumes,\nso the task that follows has something to implement rather than a default to guess.\n\n## What you do NOT do\n\n- **You do not author configuration.** Turning a decision into\n `settings-hub.config.ts` or `app-shell.config.ts` is a coding task the build lane\n dispatches through the `settings-placement-authoring` skill. If you catch yourself\n writing a config key, a file path or a label string, stop.\n- **You do not invent destination refs.** The workspace-truth section lists every engine\n settings destination under **\"Settings destinations the engine ships\"**, with what each\n one shows and its role gating. That list is the whole universe: a ref outside it is an\n `UNKNOWN_SUBJECT` and the validator REFUSES the plan — a hard floor, not a warning. Rule\n on all of them where you can; a destination your plan says nothing about is reported\n undecided.\n- **You do not decide what a destination MEANS.** Its target, roles and entitlement\n are the engine's. You decide only where it sits.\n- **You do not re-open the build plan.** What is being built is settled.\n\n## Verification\n\n- Every subject the workspace offers is either PLACED or DECLINED — nothing omitted.\n- No subject placed twice on one surface.\n- No application view placed on the settings rail or the user dropdown.\n- Every grouped placement names a group this plan declares, for that same surface.\n- Every group has something in it.\n- Every decision, both arms, carries a rationale that would satisfy a reader who\n disagrees with it.\n- The plan states which AUDIENCE it assumes — one application or two — whenever it places or\n declines an operator subject.\n\n## WHO decides — a panel, not you alone and not the creator\n\n**The creator does not choose placement.** This playbook convenes an expert panel and\ntakes its winner.\n\nConcretely, on every run: three candidate arrangements are generated independently\nagainst this brief, each schema-valid before anyone sees it and each told to take a\ngenuinely different position; the **information-architect** derives the rubric (it\nowns the domain); it and the **design-system-guardian** review every candidate; the\nguardian coordinates, shortlists, and synthesises a winner. What lands is that winner.\n\nTwo consequences for how you write:\n\n- **Take a position and commit to it.** You are one candidate among three, and the\n panel cannot compare three hedged arrangements. State what your arrangement makes\n WORSE — an arrangement with no cost has not been thought about, and the reviewers\n are instructed to notice.\n- **The rationale on each decision is the durable part.** It is what a creator asking\n \"why is Billing under Organization?\" reads, and it is the only trace of the argument\n once the winner has landed.\n\n**Fail-closed on charters.** Every panel role needs a committed charter, and the\ncompanion indexes agents at startup — a charter accepted after boot has no agent until\na restart, and the error says exactly that. The run does NOT quietly degrade to a\nsingle generation: an artifact carrying a panel's authority over a decision no panel\nsaw is the worst outcome available here, so fewer than two usable candidates returns\nto the ordinary retry instead.\n\n## And when the placement is wrong\n\nTwo different things can change, and conflating them is how a plan starts lying.\n\n**The config file** — `settings-hub.config.ts`, `app-shell.config.ts` — is what actually\nrenders. A creator who disagrees edits it directly. That works today, needs no companion,\nand is a git commit, which is the accepted state.\n\n**The plan** is the decision record, and it is what a later reader consults to ask why.\nIt can be changed two ways:\n\n- **Re-run this playbook.** The panel deliberates again and the landing REPLACES the\n existing file. Nothing refuses it; that is the design.\n- **Edit the landed plan.** It is an application-owned source like any other.\n\nEither way, a decision that no longer reflects the panel must say so. Set its `origin`\nto `REVISED` and record what the panel had decided in `supersedes.rationale`. Both are\nrequired together — the schema refuses a `REVISED` decision with nothing superseded, and\nrefuses a `DELIBERATED` one that supersedes something, because no panel run produces\neither shape.\n\n**Why the artifact carries this when git already records the change.** Git knows who\nchanged the line, when, and with what message, and that is not being duplicated here. What\ngit cannot tell someone READING the file — in an editor, asking \"why is Billing under\nAccount?\" — is that this particular decision is no longer the panel's. Without it, the\n`rationale` field goes on asserting panel reasoning for a decision the panel never took,\nand there is no way to notice.\n\nDo not paraphrase the panel's rationale into the new one. A `supersedes.rationale` that\nrepeats the decision's own text word for word satisfies the schema and tells a reader\nnothing; the validator reports it as an authoring warning.\n",
|
|
32
|
+
"skillRefs": [
|
|
33
|
+
"settings-placement-authoring",
|
|
34
|
+
"config-app-shell",
|
|
35
|
+
"config-navigation",
|
|
36
|
+
"journey-status"
|
|
37
|
+
],
|
|
38
|
+
"skillBodyRefs": [],
|
|
39
|
+
"contextSources": [
|
|
40
|
+
"workspace_truth"
|
|
41
|
+
],
|
|
42
|
+
"draftableDocumentDefinitionRefs": [],
|
|
43
|
+
"suspendsForClarification": false,
|
|
44
|
+
"briefAdequacyGate": false,
|
|
45
|
+
"briefAdequacyExcludedSources": [],
|
|
46
|
+
"deliberation": {
|
|
47
|
+
"workDomain": "information_architecture",
|
|
48
|
+
"reviewerRoleRefs": [
|
|
49
|
+
"information-architect",
|
|
50
|
+
"design-system-guardian"
|
|
51
|
+
],
|
|
52
|
+
"coordinatorRoleRef": "design-system-guardian",
|
|
53
|
+
"rubricDeriverRoleRef": "information-architect",
|
|
54
|
+
"candidateCount": 3
|
|
55
|
+
}
|
|
56
|
+
},
|
|
57
|
+
"executor": "companion_agent",
|
|
58
|
+
"approval": "approve_result",
|
|
59
|
+
"budget": {
|
|
60
|
+
"maxRuns": 3
|
|
61
|
+
},
|
|
62
|
+
"onFailure": "keep_and_flag"
|
|
63
|
+
}
|
|
@@ -0,0 +1,116 @@
|
|
|
1
|
+
# Website Plan — What the Marketing Site Says
|
|
2
|
+
|
|
3
|
+
### Target Application Framing
|
|
4
|
+
|
|
5
|
+
This knowledge is for configuring behavior in the target application.
|
|
6
|
+
Wildo is the framework surface being used, not the product being built.
|
|
7
|
+
|
|
8
|
+
Read and apply these patterns from the application-developer point of view:
|
|
9
|
+
|
|
10
|
+
- how the application should configure the relevant app-level file
|
|
11
|
+
- how the application should use framework-provided factories, enums, and helpers
|
|
12
|
+
- how the application should avoid mixing frontend, backend, and infrastructure concerns
|
|
13
|
+
|
|
14
|
+
|
|
15
|
+
## Where you are in the journey
|
|
16
|
+
|
|
17
|
+
The top-down lane has produced a market snapshot — ICPs, jobs, pains, gains, benefits with their
|
|
18
|
+
weighting, positioning per ICP, tones of voice, proofs and objections — and a brand. The capability
|
|
19
|
+
composition has decided whether this application has a marketing website. You decide **what that
|
|
20
|
+
site says**: its pages, and the sections that carry each page's argument.
|
|
21
|
+
|
|
22
|
+
You do not write the site. `bottom_up.build-decompose` turns each page and each section into a
|
|
23
|
+
build task, and a coding agent authors it against the shipped `website-*` skills. The `website/`
|
|
24
|
+
workspace itself is composed by the `add-website` scenario, which the foundation applies from the
|
|
25
|
+
same capability composition you read here.
|
|
26
|
+
|
|
27
|
+
## Step 1 — Read the capability composition FIRST
|
|
28
|
+
|
|
29
|
+
Find the `add-website` decision.
|
|
30
|
+
|
|
31
|
+
- **Declined** (or owned by nothing, or absent from the record): land a plan with
|
|
32
|
+
`disposition: NOT_APPLICABLE`, no pages, and a `rationale` naming what the composition said. That
|
|
33
|
+
is a complete answer. Do not plan a site the application will never compose — the pages would
|
|
34
|
+
become tasks with nowhere to write.
|
|
35
|
+
- **Needed**: `disposition: PLANNED`, and continue.
|
|
36
|
+
|
|
37
|
+
## Step 2 — Decide the pages, from what the product actually declares
|
|
38
|
+
|
|
39
|
+
A page exists because something the application declared needs a place to be said. Derive first,
|
|
40
|
+
and invent nothing:
|
|
41
|
+
|
|
42
|
+
| page | exists when |
|
|
43
|
+
|---|---|
|
|
44
|
+
| the landing page | always — it is the origin every canonical URL derives from |
|
|
45
|
+
| a pricing page | the business model declares pricing plans |
|
|
46
|
+
| a features page | the market snapshot carries benefits worth arguing one at a time |
|
|
47
|
+
| a contact page | the product's audience buys through a conversation (an inbound channel, a legal-entity ICP) |
|
|
48
|
+
|
|
49
|
+
Each page names the ICPs it is **written for** and the tone of voice it speaks in, both by their
|
|
50
|
+
market-snapshot refs. A page written for everybody is written for nobody: the positioning the
|
|
51
|
+
market pass produced is per ICP, and a page that names none cannot use it.
|
|
52
|
+
|
|
53
|
+
## Step 3 — Compose each page's sections, in reading order
|
|
54
|
+
|
|
55
|
+
Order is the plan's substance. A page opens on a **HERO** — the promise, before any detail — and
|
|
56
|
+
argues from there. The section kinds are closed, and each one names the skill that authors it:
|
|
57
|
+
|
|
58
|
+
| kind | what it does |
|
|
59
|
+
|---|---|
|
|
60
|
+
| `HERO` | the opening promise: headline, sub-headline, primary call to action |
|
|
61
|
+
| `FEATURE_BENEFIT_SUMMARY` | the benefits in one line each, for a reader who will not read the detail |
|
|
62
|
+
| `FEATURE_DETAIL` | one benefit argued: the job it advances, the pain it relieves, what the product does |
|
|
63
|
+
| `PRICING` | the plans, as the business model declares them |
|
|
64
|
+
| `SOCIAL_PROOF` | the proofs the market pass authored |
|
|
65
|
+
| `FAQ` | the objections, answered |
|
|
66
|
+
| `CTA` | a call to action inside the page's flow |
|
|
67
|
+
| `FOOTER_CTA` | the closing call to action |
|
|
68
|
+
| `CONTACT` | a way to reach a human |
|
|
69
|
+
|
|
70
|
+
**Every section names the market entries it draws on** (`drawsOnRefs`) — the benefit, proof,
|
|
71
|
+
objection, job, pain, ICP or tone refs, exactly as the snapshot authored them. That is what makes a
|
|
72
|
+
claim checkable: a reader opens the snapshot and finds the entry. A section that draws on nothing is
|
|
73
|
+
a section somebody invented, and the validator reports a page where no section names anything.
|
|
74
|
+
|
|
75
|
+
Lead with fit. The brief carries the computed fit matrix beside each benefit's authored Kano
|
|
76
|
+
category; a page for an ICP argues the benefits that score for THAT ICP first, rather than the ones
|
|
77
|
+
the model finds most interesting.
|
|
78
|
+
|
|
79
|
+
## Refine, don't re-author
|
|
80
|
+
|
|
81
|
+
Your own prior plan is an input. Keep every page ref that still has a reason to exist — build tasks
|
|
82
|
+
name them, and a ref that moves orphans the task that produced its page. Add, sharpen and reorder;
|
|
83
|
+
do not renumber.
|
|
84
|
+
|
|
85
|
+
## What you emit
|
|
86
|
+
|
|
87
|
+
- The **website plan** at `specifications/src/website-plan/index.ts` — a disposition with its
|
|
88
|
+
rationale, and the pages in navigation order, each with its purpose, audience, tone and ordered
|
|
89
|
+
sections.
|
|
90
|
+
|
|
91
|
+
## Verification
|
|
92
|
+
|
|
93
|
+
- Every `drawsOnRefs` entry names an entry that exists in the market snapshot.
|
|
94
|
+
- Every page opens on a `HERO`, and exactly one page reads as the landing page.
|
|
95
|
+
- `rg -n "sectionRef" specifications/src/website-plan/index.ts | wc -l` — the number of website
|
|
96
|
+
section tasks the build lane will emit.
|
|
97
|
+
|
|
98
|
+
## References — named by REF, because this step cannot open a file
|
|
99
|
+
|
|
100
|
+
A structured generation has no filesystem: naming a path here would be an instruction answered from
|
|
101
|
+
recollection (#1435). So each skill is named by its REF, and only `website-page-authoring` reaches
|
|
102
|
+
this step as a BODY (`method.skillBodyRefs`) — it is the one contract the plan must not contradict,
|
|
103
|
+
because it says what a page IS in this engine: a manifest, a route adapter, a sections file and a
|
|
104
|
+
label pack that fails the build closed on a missing key. A page planned against anything else is a
|
|
105
|
+
page the build lane cannot author.
|
|
106
|
+
|
|
107
|
+
The others below are the contracts the CODING AGENT opens when it builds each task, listed so a
|
|
108
|
+
reader knows the plan's decisions land somewhere:
|
|
109
|
+
|
|
110
|
+
- `website-navigation-authoring` — how pages reach each other, which bounds how many top-level pages are worth planning.
|
|
111
|
+
- `website-seo-aeo-geo` — what a page owes a search engine and an answer engine.
|
|
112
|
+
- `website-label-pack` — every string a section renders is a label key, and the build fails closed on a missing one.
|
|
113
|
+
- `website-marketing-metadata-extension` — the metadata a page carries beyond its sections.
|
|
114
|
+
- `website-section-*` — one per section KIND, bound to the emitted task by `WEBSITE_SECTION_SKILL_REF`.
|
|
115
|
+
- `market-positioning-authoring`, `market-tone-of-voice`, `market-proof-and-objection` — the market
|
|
116
|
+
vocabularies a section draws on, which arrive here as the market snapshot itself rather than as prose.
|
|
@@ -0,0 +1,79 @@
|
|
|
1
|
+
{
|
|
2
|
+
"ref": "bottom_up.website-plan",
|
|
3
|
+
"version": "0.1.0",
|
|
4
|
+
"phase": "bottom_up",
|
|
5
|
+
"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.",
|
|
6
|
+
"preconditions": [
|
|
7
|
+
{
|
|
8
|
+
"kind": "artifact_exists",
|
|
9
|
+
"selector": {
|
|
10
|
+
"family": "capability-composition"
|
|
11
|
+
}
|
|
12
|
+
},
|
|
13
|
+
{
|
|
14
|
+
"kind": "artifact_exists",
|
|
15
|
+
"selector": {
|
|
16
|
+
"family": "market-snapshot"
|
|
17
|
+
}
|
|
18
|
+
}
|
|
19
|
+
],
|
|
20
|
+
"inputs": [
|
|
21
|
+
{
|
|
22
|
+
"family": "capability-composition"
|
|
23
|
+
},
|
|
24
|
+
{
|
|
25
|
+
"family": "market-snapshot"
|
|
26
|
+
},
|
|
27
|
+
{
|
|
28
|
+
"family": "brand-brief",
|
|
29
|
+
"render": "map"
|
|
30
|
+
},
|
|
31
|
+
{
|
|
32
|
+
"family": "business-model"
|
|
33
|
+
},
|
|
34
|
+
{
|
|
35
|
+
"family": "vision-brief"
|
|
36
|
+
},
|
|
37
|
+
{
|
|
38
|
+
"family": "website-plan"
|
|
39
|
+
}
|
|
40
|
+
],
|
|
41
|
+
"outputs": [
|
|
42
|
+
{
|
|
43
|
+
"family": "website-plan",
|
|
44
|
+
"schemaRef": "saas-specifications:WebsitePlan",
|
|
45
|
+
"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."
|
|
46
|
+
}
|
|
47
|
+
],
|
|
48
|
+
"stepOutputs": [],
|
|
49
|
+
"method": {
|
|
50
|
+
"guidance": "# Website Plan — What the Marketing Site Says\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## Where you are in the journey\n\nThe top-down lane has produced a market snapshot — ICPs, jobs, pains, gains, benefits with their\nweighting, positioning per ICP, tones of voice, proofs and objections — and a brand. The capability\ncomposition has decided whether this application has a marketing website. You decide **what that\nsite says**: its pages, and the sections that carry each page's argument.\n\nYou do not write the site. `bottom_up.build-decompose` turns each page and each section into a\nbuild task, and a coding agent authors it against the shipped `website-*` skills. The `website/`\nworkspace itself is composed by the `add-website` scenario, which the foundation applies from the\nsame capability composition you read here.\n\n## Step 1 — Read the capability composition FIRST\n\nFind the `add-website` decision.\n\n- **Declined** (or owned by nothing, or absent from the record): land a plan with\n `disposition: NOT_APPLICABLE`, no pages, and a `rationale` naming what the composition said. That\n is a complete answer. Do not plan a site the application will never compose — the pages would\n become tasks with nowhere to write.\n- **Needed**: `disposition: PLANNED`, and continue.\n\n## Step 2 — Decide the pages, from what the product actually declares\n\nA page exists because something the application declared needs a place to be said. Derive first,\nand invent nothing:\n\n| page | exists when |\n|---|---|\n| the landing page | always — it is the origin every canonical URL derives from |\n| a pricing page | the business model declares pricing plans |\n| a features page | the market snapshot carries benefits worth arguing one at a time |\n| a contact page | the product's audience buys through a conversation (an inbound channel, a legal-entity ICP) |\n\nEach page names the ICPs it is **written for** and the tone of voice it speaks in, both by their\nmarket-snapshot refs. A page written for everybody is written for nobody: the positioning the\nmarket pass produced is per ICP, and a page that names none cannot use it.\n\n## Step 3 — Compose each page's sections, in reading order\n\nOrder is the plan's substance. A page opens on a **HERO** — the promise, before any detail — and\nargues from there. The section kinds are closed, and each one names the skill that authors it:\n\n| kind | what it does |\n|---|---|\n| `HERO` | the opening promise: headline, sub-headline, primary call to action |\n| `FEATURE_BENEFIT_SUMMARY` | the benefits in one line each, for a reader who will not read the detail |\n| `FEATURE_DETAIL` | one benefit argued: the job it advances, the pain it relieves, what the product does |\n| `PRICING` | the plans, as the business model declares them |\n| `SOCIAL_PROOF` | the proofs the market pass authored |\n| `FAQ` | the objections, answered |\n| `CTA` | a call to action inside the page's flow |\n| `FOOTER_CTA` | the closing call to action |\n| `CONTACT` | a way to reach a human |\n\n**Every section names the market entries it draws on** (`drawsOnRefs`) — the benefit, proof,\nobjection, job, pain, ICP or tone refs, exactly as the snapshot authored them. That is what makes a\nclaim checkable: a reader opens the snapshot and finds the entry. A section that draws on nothing is\na section somebody invented, and the validator reports a page where no section names anything.\n\nLead with fit. The brief carries the computed fit matrix beside each benefit's authored Kano\ncategory; a page for an ICP argues the benefits that score for THAT ICP first, rather than the ones\nthe model finds most interesting.\n\n## Refine, don't re-author\n\nYour own prior plan is an input. Keep every page ref that still has a reason to exist — build tasks\nname them, and a ref that moves orphans the task that produced its page. Add, sharpen and reorder;\ndo not renumber.\n\n## What you emit\n\n- The **website plan** at `specifications/src/website-plan/index.ts` — a disposition with its\n rationale, and the pages in navigation order, each with its purpose, audience, tone and ordered\n sections.\n\n## Verification\n\n- Every `drawsOnRefs` entry names an entry that exists in the market snapshot.\n- Every page opens on a `HERO`, and exactly one page reads as the landing page.\n- `rg -n \"sectionRef\" specifications/src/website-plan/index.ts | wc -l` — the number of website\n section tasks the build lane will emit.\n\n## References — named by REF, because this step cannot open a file\n\nA structured generation has no filesystem: naming a path here would be an instruction answered from\nrecollection (#1435). So each skill is named by its REF, and only `website-page-authoring` reaches\nthis step as a BODY (`method.skillBodyRefs`) — it is the one contract the plan must not contradict,\nbecause it says what a page IS in this engine: a manifest, a route adapter, a sections file and a\nlabel pack that fails the build closed on a missing key. A page planned against anything else is a\npage the build lane cannot author.\n\nThe others below are the contracts the CODING AGENT opens when it builds each task, listed so a\nreader knows the plan's decisions land somewhere:\n\n- `website-navigation-authoring` — how pages reach each other, which bounds how many top-level pages are worth planning.\n- `website-seo-aeo-geo` — what a page owes a search engine and an answer engine.\n- `website-label-pack` — every string a section renders is a label key, and the build fails closed on a missing one.\n- `website-marketing-metadata-extension` — the metadata a page carries beyond its sections.\n- `website-section-*` — one per section KIND, bound to the emitted task by `WEBSITE_SECTION_SKILL_REF`.\n- `market-positioning-authoring`, `market-tone-of-voice`, `market-proof-and-objection` — the market\n vocabularies a section draws on, which arrive here as the market snapshot itself rather than as prose.\n",
|
|
51
|
+
"skillRefs": [
|
|
52
|
+
"journey-status",
|
|
53
|
+
"website-page-authoring",
|
|
54
|
+
"website-navigation-authoring",
|
|
55
|
+
"website-seo-aeo-geo",
|
|
56
|
+
"website-label-pack",
|
|
57
|
+
"website-marketing-metadata-extension",
|
|
58
|
+
"market-positioning-authoring",
|
|
59
|
+
"market-tone-of-voice",
|
|
60
|
+
"market-proof-and-objection"
|
|
61
|
+
],
|
|
62
|
+
"skillBodyRefs": [
|
|
63
|
+
"website-page-authoring"
|
|
64
|
+
],
|
|
65
|
+
"contextSources": [
|
|
66
|
+
"market_fit_scores"
|
|
67
|
+
],
|
|
68
|
+
"draftableDocumentDefinitionRefs": [],
|
|
69
|
+
"suspendsForClarification": false,
|
|
70
|
+
"briefAdequacyGate": false,
|
|
71
|
+
"briefAdequacyExcludedSources": []
|
|
72
|
+
},
|
|
73
|
+
"executor": "companion_agent",
|
|
74
|
+
"approval": "approve_result",
|
|
75
|
+
"budget": {
|
|
76
|
+
"maxRuns": 3
|
|
77
|
+
},
|
|
78
|
+
"onFailure": "keep_and_flag"
|
|
79
|
+
}
|
|
@@ -0,0 +1,71 @@
|
|
|
1
|
+
# Creating the application — the root
|
|
2
|
+
|
|
3
|
+
### Target Application Framing
|
|
4
|
+
|
|
5
|
+
This knowledge is for configuring behavior in the target application.
|
|
6
|
+
Wildo is the framework surface being used, not the product being built.
|
|
7
|
+
|
|
8
|
+
Read and apply these patterns from the application-developer point of view:
|
|
9
|
+
|
|
10
|
+
- how the application should configure the relevant app-level file
|
|
11
|
+
- how the application should use framework-provided factories, enums, and helpers
|
|
12
|
+
- how the application should avoid mixing frontend, backend, and infrastructure concerns
|
|
13
|
+
|
|
14
|
+
|
|
15
|
+
This playbook IS the creation of the application. It produces nothing itself: it drives
|
|
16
|
+
four lanes, each of which drives its own leaves, and it ends on a reading of how mature
|
|
17
|
+
the application is against its own requirements — a stage, never a "done".
|
|
18
|
+
|
|
19
|
+
## The lanes, and why the order is not written here
|
|
20
|
+
|
|
21
|
+
- **`top_down.definition`** — what the application IS: the vision, the market and its
|
|
22
|
+
evidence, the value proposition, the requirements, the capability map, the business
|
|
23
|
+
model, the roadmap, and the phase gate that judges their coherence. Brand identity and
|
|
24
|
+
the risk register run beside the chain. Opens on an empty application.
|
|
25
|
+
- **`cross_cutting.compliance`** — which regimes apply and what the application must be
|
|
26
|
+
able to say: the posture from researched evidence, the assurance programme, the facts
|
|
27
|
+
read from the product, and the drafted governed documents. Opens on a valid vision, so
|
|
28
|
+
it runs beside the definition rather than after it.
|
|
29
|
+
- **`bottom_up.conception`** — the structure: the domain plan, the expert charters that
|
|
30
|
+
staff the panels, the composed foundation, the placement plan. Opens once the
|
|
31
|
+
requirements and the market snapshot are on record.
|
|
32
|
+
- **`bottom_up.build`** — the application itself: the build plan, the dispatch of its
|
|
33
|
+
tasks, the assembly check, and the maturity reading it ends on. Opens once the domain
|
|
34
|
+
and placement plans are on record.
|
|
35
|
+
|
|
36
|
+
Nothing above is a sequence. Each lane declares what it needs and the runtime re-reads
|
|
37
|
+
the tree after every round; that is the waterfall, and it is why this playbook can be
|
|
38
|
+
run again on an application at any stage — whatever is on record satisfies the gates of
|
|
39
|
+
whatever is not.
|
|
40
|
+
|
|
41
|
+
## Selecting the next lane
|
|
42
|
+
|
|
43
|
+
- **One lane per round.** A lane is a long run of its own. The definition and compliance
|
|
44
|
+
lanes both write the vision, so they cannot share a round; the rest are sequential.
|
|
45
|
+
- **Furthest first.** Choose the lane that can advance the application most from what is
|
|
46
|
+
on record, and prefer a lane waiting on nothing to one waiting on the creator.
|
|
47
|
+
- **Do not re-select a lane that has just landed.** The round history says what ran.
|
|
48
|
+
- **A lane that stopped because the creator owes it an answer is a real stop.** Say so
|
|
49
|
+
in the rationale rather than re-selecting it.
|
|
50
|
+
|
|
51
|
+
## Composing an objective for a lane
|
|
52
|
+
|
|
53
|
+
Name what the application already holds and what this lane should add — "the vision and
|
|
54
|
+
market are on record, the requirements are not; take the definition through to the phase
|
|
55
|
+
gate". A later round names what changed: "the domain plan moved; re-open the document
|
|
56
|
+
facts that were derived from it".
|
|
57
|
+
|
|
58
|
+
## When to stop
|
|
59
|
+
|
|
60
|
+
Stop when no lane can advance the application from what is on record. **That is a
|
|
61
|
+
STAGE, not a finished application** — the maturity reading is what names it, measured
|
|
62
|
+
against the application's own requirements, and it moves every time a later run lands
|
|
63
|
+
something. Stop also when every remaining lane is waiting on the creator, and say which
|
|
64
|
+
answers are owed.
|
|
65
|
+
|
|
66
|
+
## What the creator reviews
|
|
67
|
+
|
|
68
|
+
One decision at the end: the work every lane kept, to accept, to revise with a note, or
|
|
69
|
+
to discard. Under the current posture it is notified rather than awaited. Each lane has
|
|
70
|
+
already ended on its own decision, and each leaf's own review guide still applies to
|
|
71
|
+
what it landed.
|