@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
|
@@ -115,13 +115,22 @@ export function nextState(status: number): SubmitState {
|
|
|
115
115
|
* contract the SaaS app now uses, instead of inventing a website-only
|
|
116
116
|
* metadata seam.
|
|
117
117
|
*
|
|
118
|
-
* **Why
|
|
119
|
-
*
|
|
120
|
-
*
|
|
121
|
-
*
|
|
122
|
-
*
|
|
123
|
-
* `
|
|
124
|
-
*
|
|
118
|
+
* **Why the hook lives in a separate file**: React Fast Refresh only
|
|
119
|
+
* preserves state for a module whose every export is a component, so
|
|
120
|
+
* a module mixing components with plain functions loses its HMR
|
|
121
|
+
* boundary. This file holds the two things that must be identical
|
|
122
|
+
* objects at runtime — the context and the provider component that
|
|
123
|
+
* writes it — while `useWebsiteRuntime` sits alone in
|
|
124
|
+
* `useWebsiteRuntime.ts`. A section author editing a component that
|
|
125
|
+
* merely READS the runtime therefore never remounts the provider.
|
|
126
|
+
*
|
|
127
|
+
* Until 2026-09-09 this paragraph described a different arrangement:
|
|
128
|
+
* that only the bare context was kept here and the provider lived in
|
|
129
|
+
* a file of its own. No such file has ever existed — the provider is
|
|
130
|
+
* exported below — and splitting it out would be the wrong shape
|
|
131
|
+
* anyway, since `useContext` matches on object identity.
|
|
132
|
+
* prose-referent-waiver: the retired file name is quoted only to retire it.
|
|
133
|
+
* The claim named `WebsiteRuntimeContextProvider.tsx`.
|
|
125
134
|
*/
|
|
126
135
|
export interface WebsiteRuntimeContextValue {
|
|
127
136
|
/**
|
|
@@ -141,6 +150,26 @@ export interface WebsiteRuntimeContextValue {
|
|
|
141
150
|
* paths.
|
|
142
151
|
*/
|
|
143
152
|
defaultLocale: AvailableLanguage;
|
|
153
|
+
/**
|
|
154
|
+
* Origin of the application this marketing site sends visitors INTO — the
|
|
155
|
+
* marketing → product handoff target, authored once as
|
|
156
|
+
* `WildoMarketingWebsiteConfig.appOrigin` (#493).
|
|
157
|
+
*
|
|
158
|
+
* Carried here for exactly the reason `defaultLocale` above is: a
|
|
159
|
+
* `wildo.website.config.ts` is Node-loaded and therefore invisible to a
|
|
160
|
+
* client island, so before this a site resolved the app origin a SECOND
|
|
161
|
+
* time from a public build-time environment variable it could read in the
|
|
162
|
+
* browser — one host authored twice, in two files, with no mechanical link
|
|
163
|
+
* between the copies. That is how a marketing site comes to point at the
|
|
164
|
+
* wrong environment: a defect nobody notices until a customer follows the
|
|
165
|
+
* link.
|
|
166
|
+
*
|
|
167
|
+
* Threading it through the runtime keeps the handoff a framework-internal
|
|
168
|
+
* concern, the same way threading `defaultLocale` kept locale-prefixing one:
|
|
169
|
+
* section authors never hand-assemble the product URL, and there is one
|
|
170
|
+
* place to change it.
|
|
171
|
+
*/
|
|
172
|
+
appOrigin?: string;
|
|
144
173
|
/**
|
|
145
174
|
* Flat `Record<string, string>` label pack for the active locale.
|
|
146
175
|
* Lookup keys MUST be fully-composed `website.<page>.<section>.<slot>`
|
|
@@ -187,6 +216,13 @@ export interface WebsiteRuntimeContextValue {
|
|
|
187
216
|
* catalog for analytics / captcha / browser-monitoring slices.
|
|
188
217
|
*/
|
|
189
218
|
frontendProviderRegistry?: FrontendWebsiteProviderRegistry;
|
|
219
|
+
/**
|
|
220
|
+
* Replaces the framework's visitor consent panel (#534). Reads `useWebsiteConsent()`; see
|
|
221
|
+
* `WebsiteConsentBanner` for the three properties a replacement must keep. Absent uses the default.
|
|
222
|
+
* Closed over by the bridge rather than passed as an island prop, like `navigation`, because a
|
|
223
|
+
* component cannot cross Astro's serialization boundary.
|
|
224
|
+
*/
|
|
225
|
+
consentBannerComponent?: ComponentType;
|
|
190
226
|
/**
|
|
191
227
|
* Backend API origin (WITHOUT a trailing slash) that anonymous-capture
|
|
192
228
|
* sections POST to when constructing a `WebsiteAnonymousSessionClient`
|
|
@@ -258,6 +294,17 @@ WebsiteRuntimeContextProvider.displayName = 'WebsiteRuntimeContextProvider';
|
|
|
258
294
|
requestsPerMinute: 5,
|
|
259
295
|
requestsPerHour: 30,
|
|
260
296
|
},
|
|
297
|
+
// The lead's marketing opt-in is a consent DECISION: the server stamps its instant (#534).
|
|
298
|
+
basicPrefixOperation: ({ inputDto }) => buildConsentDecisionPatch(inputDto, undefined),
|
|
299
|
+
authoritativeFields: ['privacy'],
|
|
300
|
+
// …and a decision the server stamps must leave a row. LOW sits below the automatic
|
|
301
|
+
// HIGH/CRITICAL floor, so without this the one consent a LEAD ever gives us was the one
|
|
302
|
+
// consent nothing recorded. The declaration rather than a raised risk level, for the reason
|
|
303
|
+
// the api-key reissue records: buying the row by mis-declaring the verb's danger corrupts the
|
|
304
|
+
// risk vocabulary every other control reads. Only the marked decision leaves enter the
|
|
305
|
+
// evidence, so the row carries the choice and not the lead's contact details.
|
|
306
|
+
// assurance-control: WILDO.PRIVACY.CONSENT_RECORD — the lead's own decision is recordable.
|
|
307
|
+
auditableEvent: { auditBelowRiskFloor: true },
|
|
261
308
|
},
|
|
262
309
|
```
|
|
263
310
|
|
|
@@ -108,6 +108,14 @@ export function MarketingLayout({ children }: { children: React.ReactNode }) {
|
|
|
108
108
|
* captcha so non-React tooling can detect the configured vendor
|
|
109
109
|
* without reverse-engineering app code.
|
|
110
110
|
*
|
|
111
|
+
* 4. **Provides the visitor's consent state and enforces it** (#534) —
|
|
112
|
+
* mounts `WebsiteConsentProvider`, starts a provider SDK or script only
|
|
113
|
+
* once the purpose it rests on is granted (and stops the SDK when it is
|
|
114
|
+
* withdrawn), and renders the consent panel when the site runs a
|
|
115
|
+
* consent-based provider and the visitor has not decided. Here rather
|
|
116
|
+
* than in each bridge because every page — including every blog post —
|
|
117
|
+
* renders through this layout, so no page can be mounted without it.
|
|
118
|
+
*
|
|
111
119
|
* **Why semantic `<header>` / `<main>` / `<footer>` elements**:
|
|
112
120
|
* marketing-site SEO scoring penalizes pages that ship a single
|
|
113
121
|
* unstructured `<div>` tree. Using semantic landmarks costs nothing
|
|
@@ -153,6 +161,17 @@ export interface WebsitePageLayoutProps {
|
|
|
153
161
|
* vertical-rhythm overrides on long-scroll landing pages.
|
|
154
162
|
*/
|
|
155
163
|
mainClassName?: string;
|
|
164
|
+
/**
|
|
165
|
+
* OPTIONAL anonymous-session client. When supplied, a visitor's consent decision is ALSO recorded
|
|
166
|
+
* server-side against their session, which is what lets it follow them into the account they go on
|
|
167
|
+
* to create (#1258). Pass the SAME instance the page's capture sections use, so one `uuidRef`
|
|
168
|
+
* carries the decision, the lead and the draft note together.
|
|
169
|
+
*
|
|
170
|
+
* Absent keeps today's behaviour exactly: the decision lives in this browser and nowhere else.
|
|
171
|
+
* The engine cannot construct the client here — it needs the application's own
|
|
172
|
+
* `frontendServiceName` — which is why it arrives as a prop rather than off the runtime context.
|
|
173
|
+
*/
|
|
174
|
+
consentRecorder?: WebsiteConsentRecorder;
|
|
156
175
|
/**
|
|
157
176
|
* The page's section composition. Typically a sequence of
|
|
158
177
|
* `<WebsiteSection>` wrappers around concrete section components.
|
|
@@ -160,7 +179,21 @@ export interface WebsitePageLayoutProps {
|
|
|
160
179
|
children: ReactNode;
|
|
161
180
|
}
|
|
162
181
|
|
|
163
|
-
export function WebsitePageLayout({
|
|
182
|
+
export function WebsitePageLayout(props: WebsitePageLayoutProps): ReactNode {
|
|
183
|
+
const runtime = useWebsiteRuntime();
|
|
184
|
+
// Derived from the LIVE providers, so the panel asks about exactly what this site processes.
|
|
185
|
+
const purposesInUse = useMemo(
|
|
186
|
+
() => consentPurposesInUseByProviders(runtime.frontendProviderRegistry?.modules.values()),
|
|
187
|
+
[runtime.frontendProviderRegistry],
|
|
188
|
+
);
|
|
189
|
+
return (
|
|
190
|
+
<WebsiteConsentProvider purposesInUse={purposesInUse} recorder={props.consentRecorder}>
|
|
191
|
+
<WebsitePageLayoutContent {...props} />
|
|
192
|
+
</WebsiteConsentProvider>
|
|
193
|
+
);
|
|
194
|
+
}
|
|
195
|
+
|
|
196
|
+
function WebsitePageLayoutContent({
|
|
164
197
|
pageRef,
|
|
165
198
|
header,
|
|
166
199
|
footer,
|
|
@@ -169,6 +202,7 @@ export function WebsitePageLayout({
|
|
|
169
202
|
children,
|
|
170
203
|
}: WebsitePageLayoutProps): ReactNode {
|
|
171
204
|
const runtime = useWebsiteRuntime();
|
|
205
|
+
const consent = useWebsiteConsent();
|
|
172
206
|
|
|
173
207
|
/**
|
|
174
208
|
* Defensive parse: callers should pass a `WebsitePageManifest.ref`
|
|
@@ -211,6 +245,16 @@ export function WebsitePageLayout({
|
|
|
211
245
|
return <FooterComponent />;
|
|
212
246
|
}, [footer, runtime.navigation.footerComponent]);
|
|
213
247
|
|
|
248
|
+
// Load whatever the live providers declared. Until this landed, the surface
|
|
249
|
+
// resolved provider refs and stamped them into the attributes below and
|
|
250
|
+
// stopped there — a provider could be declared, enabled and hydrated without
|
|
251
|
+
// anything of it ever running.
|
|
252
|
+
//
|
|
253
|
+
// Consent-based providers start only once their purpose is granted (#534). Before the stored decision is
|
|
254
|
+
// read, nothing is granted — the static HTML and the first render start nothing optional.
|
|
255
|
+
useWebsiteProviderScripts(runtime.frontendProviderRegistry, consent.grantedPurposes);
|
|
256
|
+
useWebsiteProviderSdks(runtime.frontendProviderRegistry, consent.grantedPurposes);
|
|
257
|
+
|
|
214
258
|
const providerRootAttributes = useMemo<Record<string, string>>(() => {
|
|
215
259
|
const attrs: Record<string, string> = {};
|
|
216
260
|
const productAnalyticsProviderRef = runtime.frontendProviderRegistry
|
|
@@ -282,11 +326,33 @@ export function WebsitePageLayout({
|
|
|
282
326
|
{children}
|
|
283
327
|
</main>
|
|
284
328
|
{resolvedFooter !== null ? <footer>{resolvedFooter}</footer> : null}
|
|
329
|
+
{renderConsentSurface(consent, runtime.consentBannerComponent)}
|
|
285
330
|
</div>
|
|
286
331
|
</WebsitePageContextProvider>
|
|
287
332
|
);
|
|
288
333
|
}
|
|
289
334
|
WebsitePageLayout.displayName = 'WebsitePageLayout';
|
|
335
|
+
|
|
336
|
+
/**
|
|
337
|
+
* The panel while a decision is owed (or re-opened), the reopen button once one is made, and nothing at
|
|
338
|
+
* all on a site whose live providers rest on no consent. Nothing renders before the stored decision is
|
|
339
|
+
* read, so a visitor who already decided never sees the panel flash.
|
|
340
|
+
*/
|
|
341
|
+
function renderConsentSurface(
|
|
342
|
+
consent: ReturnType<typeof useWebsiteConsent>,
|
|
343
|
+
BannerOverride: React.ComponentType | undefined,
|
|
344
|
+
): ReactNode {
|
|
345
|
+
if (!consent.isResolved || consent.purposesInUse.length === 0) return null;
|
|
346
|
+
if (consent.status === WebsiteConsentStatus.UNDECIDED || consent.isSettingsOpen) {
|
|
347
|
+
const Banner = BannerOverride ?? WebsiteConsentBanner;
|
|
348
|
+
return <Banner />;
|
|
349
|
+
}
|
|
350
|
+
return (
|
|
351
|
+
<div data-website-consent-settings="">
|
|
352
|
+
<WebsiteConsentSettingsButton />
|
|
353
|
+
</div>
|
|
354
|
+
);
|
|
355
|
+
}
|
|
290
356
|
```
|
|
291
357
|
|
|
292
358
|
## Import Origins
|
|
@@ -222,6 +222,17 @@ export function composeWebsiteSiteContext(
|
|
|
222
222
|
requestsPerMinute: 5,
|
|
223
223
|
requestsPerHour: 30,
|
|
224
224
|
},
|
|
225
|
+
// The lead's marketing opt-in is a consent DECISION: the server stamps its instant (#534).
|
|
226
|
+
basicPrefixOperation: ({ inputDto }) => buildConsentDecisionPatch(inputDto, undefined),
|
|
227
|
+
authoritativeFields: ['privacy'],
|
|
228
|
+
// …and a decision the server stamps must leave a row. LOW sits below the automatic
|
|
229
|
+
// HIGH/CRITICAL floor, so without this the one consent a LEAD ever gives us was the one
|
|
230
|
+
// consent nothing recorded. The declaration rather than a raised risk level, for the reason
|
|
231
|
+
// the api-key reissue records: buying the row by mis-declaring the verb's danger corrupts the
|
|
232
|
+
// risk vocabulary every other control reads. Only the marked decision leaves enter the
|
|
233
|
+
// evidence, so the row carries the choice and not the lead's contact details.
|
|
234
|
+
// assurance-control: WILDO.PRIVACY.CONSENT_RECORD — the lead's own decision is recordable.
|
|
235
|
+
auditableEvent: { auditBelowRiskFloor: true },
|
|
225
236
|
},
|
|
226
237
|
```
|
|
227
238
|
|
|
@@ -45,6 +45,13 @@ consequences flow from that:
|
|
|
45
45
|
hosts the page's sections. Header/footer therefore do NOT have a
|
|
46
46
|
`WebsitePageContext` or `WebsiteSectionContext` ambient — they
|
|
47
47
|
read site-wide state from `WebsiteRuntimeContext` directly.
|
|
48
|
+
3. **They render the CONTENTS of the landmark, never the landmark.**
|
|
49
|
+
Because the layout already supplies the `<header>` and `<footer>`,
|
|
50
|
+
your `HeaderComponent`'s root is a `<div>` (or a fragment), not a
|
|
51
|
+
second `<header>`. A nested `<header>` puts a banner inside the
|
|
52
|
+
banner and gives the page two of them — three accessibility
|
|
53
|
+
violations at once, and a screen reader lists the site header twice.
|
|
54
|
+
The same holds for the footer and `<footer>`.
|
|
48
55
|
|
|
49
56
|
The framework decision (D19) is that navigation lives on
|
|
50
57
|
`WebsiteRuntimeContextValue` (alongside `locale`, `labelPack`,
|
|
@@ -262,9 +269,10 @@ destination.
|
|
|
262
269
|
- Keep the handoff URL constant per build (one site-wide CTA target);
|
|
263
270
|
per-campaign variations belong on `website-section-cta` with their
|
|
264
271
|
own `?intent=…` query param.
|
|
265
|
-
-
|
|
266
|
-
|
|
267
|
-
|
|
272
|
+
- The header CTA is essential navigation the visitor asked for, so it is
|
|
273
|
+
never consent-gated. To give visitors a way back to their privacy choice,
|
|
274
|
+
add a footer link that calls `useWebsiteConsent().openSettings()` — see
|
|
275
|
+
`website-consent-gate-overrides`.
|
|
268
276
|
- The full anonymous-session contract (parent-domain cookie name,
|
|
269
277
|
TTL, transposition on sign-up) is documented in
|
|
270
278
|
`website-anonymous-session`.
|
|
@@ -335,6 +343,8 @@ automatically.
|
|
|
335
343
|
on the active locale.
|
|
336
344
|
- Header sign-up CTA targets the cross-frontend handoff route
|
|
337
345
|
(per `website-anonymous-session`), not the raw sign-up URL.
|
|
346
|
+
- Header and footer components render a `<div>` (or fragment) at their root, never
|
|
347
|
+
`<header>` / `<footer>` — the layout supplies the landmark.
|
|
338
348
|
- Per-page override (when used) passes `header={null}` for
|
|
339
349
|
explicit suppression OR a concrete `ReactNode` for replacement
|
|
340
350
|
— never `header={undefined}` (use the omission spelling: just
|
|
@@ -350,6 +360,7 @@ don't pass the prop).
|
|
|
350
360
|
| Header CTA targets the handoff route | `rg -n "primaryCtaHref:" website/src/website-root.config.ts` (must reference `/auth/handoff` or the consumer's documented handoff path) |
|
|
351
361
|
| Locale switcher uses `hrefLang` | `rg -n "hrefLang" website/src/chrome/SiteFooter.tsx` (must return ≥1) |
|
|
352
362
|
| External social links are flagged | `rg -n "<WebsiteLink href=\"https" website/src/chrome/SiteFooter.tsx` (every match must also have `external`) |
|
|
363
|
+
| Chrome never re-declares the landmark | `rg -n "<header\b\|<footer\b" website/src/components/ website/src/chrome/` (must return empty — the layout already emits both) |
|
|
353
364
|
|
|
354
365
|
|
|
355
366
|
## Common Rationalizations
|
|
@@ -359,6 +370,7 @@ don't pass the prop).
|
|
|
359
370
|
| ---------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
|
360
371
|
| "I'll wrap the header in `<WebsiteSection>` for analytics consistency" | Chrome is not a section. The framework emits `data-website-chrome="header"` on the runtime layout's `<header>` element; analytics that needs the chrome distinction reads that, not `data-section-ref`. Wrapping in `<WebsiteSection>` would corrupt the page's section context and break label-key derivation in chrome's children. |
|
|
361
372
|
| "I'll author header/footer once via `defineWebsiteSection` so they get the SEO contract" | Chrome doesn't have an SEO category. There is no `WebsiteSectionCategory.HEADER` for a reason — chrome doesn't emit JSON-LD; the page sections do. Trying to force chrome into the section vocabulary breaks the 1:1 invariant the SEO dispatcher relies on. |
|
|
373
|
+
| "My header is the site's banner, so its root should be `<header>`" | It already is one: `WebsitePageLayout` renders `<header>{HeaderComponent}</header>`. A second `<header>` inside it is a banner nested in the banner and a page with two, which axe reports three ways and a screen reader lists twice. The layout owns the landmark; the component owns its contents. |
|
|
362
374
|
| "I'll register the header per page so each page can override it" | Per-page override IS supported (`header={…}` prop on `<WebsitePageLayout>`). Site-wide registration is the common case; per-page is the escape hatch. Using per-page registration as the default forces every page module to repeat the registration and loses the runtime-context single source of truth. |
|
|
363
375
|
| "Header CTA can target `https://app.example.com/signup` directly" | Direct URLs lose the parent-domain anonymous-session UUID at the cross-frontend boundary. The app-side cannot match the marketing-site visitor to the new sign-up. Use the handoff route (D16). |
|
|
364
376
|
| "I'll inline the locale switcher labels in JSX, they're just two-letter codes" | `EN` / `FR` is the right user-visible token, but the surrounding strings (a11y label on the `<nav>`, `aria-current` semantics) need locale-aware copy — and the tokens themselves may need locale-specific casing for some scripts. Keep them in the label pack from the start. |
|
|
@@ -366,6 +378,8 @@ don't pass the prop).
|
|
|
366
378
|
|
|
367
379
|
## Red Flags
|
|
368
380
|
|
|
381
|
+
- **A `<header>` or `<footer>` element at the root of a chrome component** — the layout
|
|
382
|
+
already emits that landmark, so the page gets two (catch with the **landmark** grep above).
|
|
369
383
|
- **Hardcoded `<a href="https://...">` in chrome that targets the SaaS
|
|
370
384
|
app shell** — the parent-domain anonymous-session UUID is dropped.
|
|
371
385
|
Route through the handoff URL (D16).
|
|
@@ -405,8 +419,8 @@ used inside chrome.
|
|
|
405
419
|
namespace entries.
|
|
406
420
|
- `website-anonymous-session` — parent-domain cookie + cross-
|
|
407
421
|
frontend handoff route the header CTA targets.
|
|
408
|
-
- `website-consent-gate-overrides` —
|
|
409
|
-
|
|
422
|
+
- `website-consent-gate-overrides` — the visitor consent panel, and a
|
|
423
|
+
footer link that reopens it.
|
|
410
424
|
- `website-section-footer-cta` — the in-`<main>` last-impression CTA
|
|
411
425
|
band, distinct from this site footer.
|
|
412
426
|
- `website-seo-aeo-geo` — `hreflang` semantics the locale switcher
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: website-page-authoring
|
|
3
|
-
description:
|
|
3
|
+
description: Create or improve an application homepage or marketing page: establish its product message and visual direction, compose sections, declare the page manifest, route it, and verify its labels and discovery representation. Use for "create the homepage", "rewrite our homepage", "make the landing page punchier", "choose homepage illustrations", "add a new website page", "compose a landing page", or "create a new marketing route".
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# Website Page Authoring
|
|
@@ -24,6 +24,15 @@ sections, labels, navigation, structured data and discovery summary must agree
|
|
|
24
24
|
on its audience, claim and next action. Compose the page from the smallest
|
|
25
25
|
sections that preserve those responsibilities.
|
|
26
26
|
|
|
27
|
+
## Homepage message and visual direction
|
|
28
|
+
|
|
29
|
+
For a homepage or landing-page content/design task, read
|
|
30
|
+
[Homepage content and art direction](references/homepage-content-and-art-direction.md)
|
|
31
|
+
before composing sections. It covers product evidence, scannable copy, meaningful
|
|
32
|
+
visual analogies, incremental image refinement and responsive review. Apply it to
|
|
33
|
+
this application's audience and brand; do not import another product's section
|
|
34
|
+
names, claims, metaphors or layout as defaults.
|
|
35
|
+
|
|
27
36
|
## App Paths
|
|
28
37
|
|
|
29
38
|
| Surface | Application-relative location |
|
|
@@ -36,8 +45,10 @@ sections that preserve those responsibilities.
|
|
|
36
45
|
|
|
37
46
|
## Workflow
|
|
38
47
|
|
|
39
|
-
1. Define the visitor, purpose,
|
|
40
|
-
composing visuals.
|
|
48
|
+
1. Define the visitor, purpose, deliberate action policy and canonical route
|
|
49
|
+
before composing visuals. For a homepage, use the content/art-direction
|
|
50
|
+
reference to connect the opening promise to product evidence. A description-only
|
|
51
|
+
section need not contain a CTA.
|
|
41
52
|
2. Read the installed page-manifest contract and create the page’s stable ref,
|
|
42
53
|
locale/variant policy and section composition.
|
|
43
54
|
3. Select section categories based on the information journey: orientation,
|
|
@@ -68,6 +79,9 @@ export const pricingPageIntent = {
|
|
|
68
79
|
|
|
69
80
|
## References
|
|
70
81
|
|
|
82
|
+
- [Homepage content and art direction](references/homepage-content-and-art-direction.md) — application-facing editorial workflow, visual briefs and acceptance checks.
|
|
83
|
+
|
|
84
|
+
|
|
71
85
|
## Import Origins
|
|
72
86
|
|
|
73
87
|
- `@wildo-ai/saas-website`
|
|
@@ -200,6 +214,14 @@ export function defineWebsitePageManifest<TProps = Record<string, never>>(
|
|
|
200
214
|
* captcha so non-React tooling can detect the configured vendor
|
|
201
215
|
* without reverse-engineering app code.
|
|
202
216
|
*
|
|
217
|
+
* 4. **Provides the visitor's consent state and enforces it** (#534) —
|
|
218
|
+
* mounts `WebsiteConsentProvider`, starts a provider SDK or script only
|
|
219
|
+
* once the purpose it rests on is granted (and stops the SDK when it is
|
|
220
|
+
* withdrawn), and renders the consent panel when the site runs a
|
|
221
|
+
* consent-based provider and the visitor has not decided. Here rather
|
|
222
|
+
* than in each bridge because every page — including every blog post —
|
|
223
|
+
* renders through this layout, so no page can be mounted without it.
|
|
224
|
+
*
|
|
203
225
|
* **Why semantic `<header>` / `<main>` / `<footer>` elements**:
|
|
204
226
|
* marketing-site SEO scoring penalizes pages that ship a single
|
|
205
227
|
* unstructured `<div>` tree. Using semantic landmarks costs nothing
|
|
@@ -245,6 +267,17 @@ export interface WebsitePageLayoutProps {
|
|
|
245
267
|
* vertical-rhythm overrides on long-scroll landing pages.
|
|
246
268
|
*/
|
|
247
269
|
mainClassName?: string;
|
|
270
|
+
/**
|
|
271
|
+
* OPTIONAL anonymous-session client. When supplied, a visitor's consent decision is ALSO recorded
|
|
272
|
+
* server-side against their session, which is what lets it follow them into the account they go on
|
|
273
|
+
* to create (#1258). Pass the SAME instance the page's capture sections use, so one `uuidRef`
|
|
274
|
+
* carries the decision, the lead and the draft note together.
|
|
275
|
+
*
|
|
276
|
+
* Absent keeps today's behaviour exactly: the decision lives in this browser and nowhere else.
|
|
277
|
+
* The engine cannot construct the client here — it needs the application's own
|
|
278
|
+
* `frontendServiceName` — which is why it arrives as a prop rather than off the runtime context.
|
|
279
|
+
*/
|
|
280
|
+
consentRecorder?: WebsiteConsentRecorder;
|
|
248
281
|
/**
|
|
249
282
|
* The page's section composition. Typically a sequence of
|
|
250
283
|
* `<WebsiteSection>` wrappers around concrete section components.
|
|
@@ -252,7 +285,21 @@ export interface WebsitePageLayoutProps {
|
|
|
252
285
|
children: ReactNode;
|
|
253
286
|
}
|
|
254
287
|
|
|
255
|
-
export function WebsitePageLayout({
|
|
288
|
+
export function WebsitePageLayout(props: WebsitePageLayoutProps): ReactNode {
|
|
289
|
+
const runtime = useWebsiteRuntime();
|
|
290
|
+
// Derived from the LIVE providers, so the panel asks about exactly what this site processes.
|
|
291
|
+
const purposesInUse = useMemo(
|
|
292
|
+
() => consentPurposesInUseByProviders(runtime.frontendProviderRegistry?.modules.values()),
|
|
293
|
+
[runtime.frontendProviderRegistry],
|
|
294
|
+
);
|
|
295
|
+
return (
|
|
296
|
+
<WebsiteConsentProvider purposesInUse={purposesInUse} recorder={props.consentRecorder}>
|
|
297
|
+
<WebsitePageLayoutContent {...props} />
|
|
298
|
+
</WebsiteConsentProvider>
|
|
299
|
+
);
|
|
300
|
+
}
|
|
301
|
+
|
|
302
|
+
function WebsitePageLayoutContent({
|
|
256
303
|
pageRef,
|
|
257
304
|
header,
|
|
258
305
|
footer,
|
|
@@ -261,6 +308,7 @@ export function WebsitePageLayout({
|
|
|
261
308
|
children,
|
|
262
309
|
}: WebsitePageLayoutProps): ReactNode {
|
|
263
310
|
const runtime = useWebsiteRuntime();
|
|
311
|
+
const consent = useWebsiteConsent();
|
|
264
312
|
|
|
265
313
|
/**
|
|
266
314
|
* Defensive parse: callers should pass a `WebsitePageManifest.ref`
|
|
@@ -303,6 +351,16 @@ export function WebsitePageLayout({
|
|
|
303
351
|
return <FooterComponent />;
|
|
304
352
|
}, [footer, runtime.navigation.footerComponent]);
|
|
305
353
|
|
|
354
|
+
// Load whatever the live providers declared. Until this landed, the surface
|
|
355
|
+
// resolved provider refs and stamped them into the attributes below and
|
|
356
|
+
// stopped there — a provider could be declared, enabled and hydrated without
|
|
357
|
+
// anything of it ever running.
|
|
358
|
+
//
|
|
359
|
+
// Consent-based providers start only once their purpose is granted (#534). Before the stored decision is
|
|
360
|
+
// read, nothing is granted — the static HTML and the first render start nothing optional.
|
|
361
|
+
useWebsiteProviderScripts(runtime.frontendProviderRegistry, consent.grantedPurposes);
|
|
362
|
+
useWebsiteProviderSdks(runtime.frontendProviderRegistry, consent.grantedPurposes);
|
|
363
|
+
|
|
306
364
|
const providerRootAttributes = useMemo<Record<string, string>>(() => {
|
|
307
365
|
const attrs: Record<string, string> = {};
|
|
308
366
|
const productAnalyticsProviderRef = runtime.frontendProviderRegistry
|
|
@@ -374,11 +432,33 @@ export function WebsitePageLayout({
|
|
|
374
432
|
{children}
|
|
375
433
|
</main>
|
|
376
434
|
{resolvedFooter !== null ? <footer>{resolvedFooter}</footer> : null}
|
|
435
|
+
{renderConsentSurface(consent, runtime.consentBannerComponent)}
|
|
377
436
|
</div>
|
|
378
437
|
</WebsitePageContextProvider>
|
|
379
438
|
);
|
|
380
439
|
}
|
|
381
440
|
WebsitePageLayout.displayName = 'WebsitePageLayout';
|
|
441
|
+
|
|
442
|
+
/**
|
|
443
|
+
* The panel while a decision is owed (or re-opened), the reopen button once one is made, and nothing at
|
|
444
|
+
* all on a site whose live providers rest on no consent. Nothing renders before the stored decision is
|
|
445
|
+
* read, so a visitor who already decided never sees the panel flash.
|
|
446
|
+
*/
|
|
447
|
+
function renderConsentSurface(
|
|
448
|
+
consent: ReturnType<typeof useWebsiteConsent>,
|
|
449
|
+
BannerOverride: React.ComponentType | undefined,
|
|
450
|
+
): ReactNode {
|
|
451
|
+
if (!consent.isResolved || consent.purposesInUse.length === 0) return null;
|
|
452
|
+
if (consent.status === WebsiteConsentStatus.UNDECIDED || consent.isSettingsOpen) {
|
|
453
|
+
const Banner = BannerOverride ?? WebsiteConsentBanner;
|
|
454
|
+
return <Banner />;
|
|
455
|
+
}
|
|
456
|
+
return (
|
|
457
|
+
<div data-website-consent-settings="">
|
|
458
|
+
<WebsiteConsentSettingsButton />
|
|
459
|
+
</div>
|
|
460
|
+
);
|
|
461
|
+
}
|
|
382
462
|
```
|
|
383
463
|
|
|
384
464
|
These source-backed contracts are the page-manifest and structural composition
|
|
@@ -389,8 +469,8 @@ authority for the workflow below.
|
|
|
389
469
|
- The route, page ref, navigation label and canonical discovery entry agree.
|
|
390
470
|
- Every rendered section appears in the page manifest and its expected labels
|
|
391
471
|
are available for supported locales.
|
|
392
|
-
- The page has a
|
|
393
|
-
data claim.
|
|
472
|
+
- The page has a deliberate next-step policy (including any requested
|
|
473
|
+
description-only sections) and no duplicate/conflicting structured data claim.
|
|
394
474
|
|
|
395
475
|
Run `rg -n "defineWebsitePageManifest" website/src/pages-impl/` and confirm
|
|
396
476
|
the new page is represented by an explicit manifest declaration.
|
|
@@ -411,10 +491,17 @@ the new page is represented by an explicit manifest declaration.
|
|
|
411
491
|
|
|
412
492
|
## Red Flags
|
|
413
493
|
|
|
414
|
-
- A page has route code but no declared visitor
|
|
494
|
+
- A page has route code but no declared visitor, purpose or action policy.
|
|
495
|
+
- A homepage exposes framework taxonomy, generic slogans or an unverified claim
|
|
496
|
+
instead of explaining this application to its own customers.
|
|
497
|
+
- The headline is readable at one width only, or generated artwork contradicts
|
|
498
|
+
the product behavior it is meant to explain.
|
|
415
499
|
- Sections or labels are manually assembled outside their owning contracts.
|
|
416
500
|
|
|
417
501
|
## Related Skills
|
|
418
502
|
|
|
419
503
|
- `website-page-variants` for audience-specific page variation.
|
|
420
504
|
- `website-navigation-authoring` for site navigation changes.
|
|
505
|
+
|
|
506
|
+
For homepage changes, also complete the reference’s editorial and rendered-page
|
|
507
|
+
review; a valid manifest alone does not establish readable content or usable layout.
|
|
@@ -0,0 +1,126 @@
|
|
|
1
|
+
# Homepage content and art direction
|
|
2
|
+
|
|
3
|
+
Use for a new application homepage, a homepage rewrite, or a request to make its message and visual presentation clearer. Apply this alongside the page-manifest and section contracts in the parent skill. The homepage introduces the application being built, not the framework used to build it.
|
|
4
|
+
|
|
5
|
+
## 1. Establish what the visitor should understand
|
|
6
|
+
|
|
7
|
+
Read the application's product specifications, audience and positioning decisions, brand voice, existing public pages, and relevant implementation before writing. Inspect configured application behavior when a claim depends on it. Record a compact working brief:
|
|
8
|
+
|
|
9
|
+
| Decision | Required answer |
|
|
10
|
+
| --- | --- |
|
|
11
|
+
| Visitor | Who is evaluating the product, and what work are they trying to accomplish? |
|
|
12
|
+
| Product | What is it, in words this visitor already understands? |
|
|
13
|
+
| Value | What useful outcome becomes easier or possible? |
|
|
14
|
+
| Difference | Which connected behavior makes the outcome credible? |
|
|
15
|
+
| Responsibility | What does the product provide, and what does its user still decide or do? |
|
|
16
|
+
| Evidence | Which current configuration, behavior, example or verified measurement supports the statement? |
|
|
17
|
+
| Next step | What may the visitor do next, if a conversion action is in scope? |
|
|
18
|
+
|
|
19
|
+
Identify the main value before selecting the most visually convenient feature. A strong subsystem can still be the wrong homepage story. Explain the combination that matters to the buyer: what works together, what it changes in their work, and why it is useful.
|
|
20
|
+
|
|
21
|
+
Product intent, available implementation and executed proof are different evidence. Do not turn a roadmap into present-tense delivery. Do not promise automatic compliance, universal compatibility, guaranteed autonomous completion or percentage improvements without applicable evidence. For a count, establish exactly what is counted and how it was measured. A framework capability count does not establish that the application configures or exposes all those capabilities.
|
|
22
|
+
|
|
23
|
+
## 2. Structure from the top; write from the evidence upward
|
|
24
|
+
|
|
25
|
+
First map the page's sections and the question each answers. Then investigate the underlying product behavior, write the useful details, consolidate the section's strongest points, and finally sharpen the opening promise. This prevents an attractive headline from setting a promise the product cannot explain.
|
|
26
|
+
|
|
27
|
+
Use the existing site navigation as an information source, not an automatic template. If the brief calls for one homepage section per menu group, preserve that correspondence. Otherwise group by visitor questions and outcomes. Do not expose source-code organization or internal taxonomy as the public story. There is no universal five-section recipe.
|
|
28
|
+
|
|
29
|
+
Each section needs one reason to exist: a distinct message, a small set of useful supporting points, and an appropriate visual. Read the section headings alone: they should tell a coherent product story without repeating the same claim. Keep a coverage note linking the detailed topics to their public homes, so depth stays discoverable without becoming a homepage enumeration.
|
|
30
|
+
|
|
31
|
+
The homepage carries the main understanding in visible content. Essential value must not require opening accordions. Put contracts, extensive configuration, code samples and exhaustive catalogs on the appropriate detailed pages. Use technical disclosure on the homepage only when it helps the intended reader answer a specific question.
|
|
32
|
+
|
|
33
|
+
If the hero is deferred or already approved, preserve it while working on the body. When the whole homepage is in scope, refine the hero after the supporting content establishes its promise.
|
|
34
|
+
|
|
35
|
+
## 3. Make the information stand out
|
|
36
|
+
|
|
37
|
+
Be confident through concrete meaning and direct verbs. Put the product category, audience or useful outcome early. Prefer short claims that work independently, each followed by a short explanation of the mechanism or consequence. Remove filler before adding emphasis.
|
|
38
|
+
|
|
39
|
+
A practical hierarchy is:
|
|
40
|
+
|
|
41
|
+
- **Headline:** the central proposition, understandable without surrounding copy.
|
|
42
|
+
- **Supporting line:** what the application is and who it serves.
|
|
43
|
+
- **Section opening:** the change in the visitor's work.
|
|
44
|
+
- **Two to four scan points:** short meaningful headings with one concise explanation each.
|
|
45
|
+
|
|
46
|
+
This is a writing aid, not a requirement to render every level. Avoid saying the same thing in the headline, subtitle, paragraph and highlights. A keyword such as “Powerful” adds little; name the useful behavior. A visitor scanning only the prominent text should still understand the point.
|
|
47
|
+
|
|
48
|
+
**Illustrative editorial example, subject to the application's actual behavior:**
|
|
49
|
+
|
|
50
|
+
| Weak draft | More informative direction |
|
|
51
|
+
| --- | --- |
|
|
52
|
+
| “A new era of powerful operations.” | “Keep every inspection ready for sign-off.” |
|
|
53
|
+
| “Flexible. Connected. Intelligent.” | “Capture evidence on site.” / “Route findings to the right team.” / “Review the work in one place.” |
|
|
54
|
+
| A paragraph explaining the example before the general value | Explain the general behavior first; put the scenario below in a smaller, clearly marked Example block. |
|
|
55
|
+
|
|
56
|
+
Use typography, placement and concise wording to establish hierarchy. Do not make whole paragraphs bold, oversized or high-contrast to simulate punch. Supporting text should remain readable and visually consistent across ordinary text, examples and any disclosures.
|
|
57
|
+
|
|
58
|
+
Eyebrows and category labels are optional; omit those that merely repeat navigation or the heading. CTAs are deliberate conversion decisions, not decoration. An explanatory section can contain no CTA. If a user asks for a description-only pass, omit section CTAs and preserve the agreed action scope. When a next step is appropriate, avoid duplicating it after every block.
|
|
59
|
+
|
|
60
|
+
## 4. Design the image's meaning before its style
|
|
61
|
+
|
|
62
|
+
Inspect the application's approved images, not just their filenames. If no visual direction or approved imagery exists, derive a provisional direction from the audience, product subject, brand decisions and available design tokens. Mark it as proposed, choose or create a small set of relevant references/concepts within the authorized scope, and record the selected direction before refining it. Do not invent a prior approval or import another application's style to fill the gap.
|
|
63
|
+
|
|
64
|
+
Separate these decisions:
|
|
65
|
+
|
|
66
|
+
| Layer | What to decide |
|
|
67
|
+
| --- | --- |
|
|
68
|
+
| Meaning | What one relationship or action must the reader grasp? |
|
|
69
|
+
| Subject | What must unmistakably remain the product being sold? |
|
|
70
|
+
| Analogy | Which familiar scene explains the relationship without replacing the product? |
|
|
71
|
+
| Composition | What is supplied, who acts, what changes, and what is produced? |
|
|
72
|
+
| Style | Palette, medium, texture, detail, contrast and visual weight already established for the brand. |
|
|
73
|
+
|
|
74
|
+
An analogy succeeds when its relationships fit the product. A small craft scene can make substantial business software look like a toy. A grand architectural scene can communicate ambition while explaining nothing. A literal aircraft can make the image about aircraft rather than software. Conversely, a software-factory analogy may fit a developer tool but would be inappropriate as a default illustration for an inspection or invoicing application.
|
|
75
|
+
|
|
76
|
+
Show the real product category and the right sense of scale. Distinguish a shared supplier from an item being manufactured; a person directing work from someone manually doing every step; and an illustrative control station from an actual product screenshot. Avoid visuals that imply an instant or automatic outcome the copy cannot support.
|
|
77
|
+
|
|
78
|
+
Use one dominant scene and a small number of supporting elements. If the image needs many labels, arrows, slogans and fake interface details to explain itself, simplify its composition. Real screenshots are useful when they prove the behavior. Conceptual images should be identifiable as illustrations; mark explicit scenarios as examples where needed. Never present a generated interface or fabricated metrics as product evidence.
|
|
79
|
+
|
|
80
|
+
### Image iteration workflow
|
|
81
|
+
|
|
82
|
+
1. Write a short semantic brief: central subject, actors, supplied foundation, action, output, control and responsibilities. Name the elements that must remain clear.
|
|
83
|
+
2. Select approved style references, or establish the provisional direction described above, and specify each reference’s role. Describe the intended medium and detail level; do not substitute an HTML/SVG mockup when raster artwork was requested.
|
|
84
|
+
3. Generate a small set of genuinely different interpretations when requested. Vary composition, relationships and emphasis, not merely colors or object counts. Label proposals consistently before showing each one.
|
|
85
|
+
4. Inspect the result before presenting it: wrong text, extra slogans, anatomical glitches, object overlap, inconsistent perspective, misplaced inputs and outputs, and misleading product claims.
|
|
86
|
+
5. Once the composition is selected, lock it. A style refinement preserves the story; a local correction preserves everything outside the affected region. Do not silently replace the concept during polishing.
|
|
87
|
+
6. Keep the selected original and use a versioned project asset. Apply the configured website image pipeline for responsive sizes and compression. Verify the actual delivered image; do not assume importing a file optimizes it automatically.
|
|
88
|
+
|
|
89
|
+
A generation brief should state the subject and relationships first, then composition, medium/palette, any exact short text, and specific exclusions. It must also distinguish an edit target from a style reference. Do not reuse one product's metaphor or fixed palette across unrelated applications.
|
|
90
|
+
|
|
91
|
+
## 5. Implement within the application's website system
|
|
92
|
+
|
|
93
|
+
Use the installed page manifests, section definitions, labels, design tokens and layout contracts. Reuse or extend the existing components before introducing parallel styling or page infrastructure. Keep message, image selection and reusable presentation responsibilities clear.
|
|
94
|
+
|
|
95
|
+
Use semantic headings in order. An intentional headline break can mark two phrases, but both phrases must wrap naturally on narrow screens. Avoid nowrap, fixed character widths, manual space padding or a desktop-only screenshot as proof. Verify alternate locales and longer text where supported.
|
|
96
|
+
|
|
97
|
+
Give text and image a deliberate relationship. For explanatory pairs, align their starts unless the chosen composition calls for another alignment. A main header may need a stacked composition even when detailed sections use two columns. Do not impose a two-column layout everywhere.
|
|
98
|
+
|
|
99
|
+
Keep section spacing proportional to its content. Repeated full-viewport padding, large empty bands, forced scroll sequences and color alternation alone do not create a strong hierarchy. Prefer ordinary scrolling, distinct but coherent section compositions, and restrained movement. Core information must remain available without animation or JavaScript where the website supports static rendering. Honor reduced motion and keyboard access.
|
|
100
|
+
|
|
101
|
+
For in-page links into collapsed details, preserve the destination and open the necessary disclosure on both same-page navigation and a fresh page load. Verify the real interaction; a matching fragment identifier alone is insufficient. Do not require a disclosure to read the primary marketing message.
|
|
102
|
+
|
|
103
|
+
## 6. Review the page, not just the source
|
|
104
|
+
|
|
105
|
+
Before declaring the homepage ready:
|
|
106
|
+
|
|
107
|
+
- Read only the title, supporting line and scan headings. Can the reader identify the product, its value and its difference? This is an editorial check, not user research.
|
|
108
|
+
- Ask a reader unfamiliar with the product to explain it when that feedback is available. Do not invent feedback or infer understanding from a screenshot check.
|
|
109
|
+
- Check every public claim against its named evidence, including numbers, availability and responsibility boundaries.
|
|
110
|
+
- Inspect the page in light and dark themes where supported, at narrow mobile, tablet, ordinary desktop and wide desktop widths. Check the responsive headline, section spacing, image detail and absence of horizontal overflow.
|
|
111
|
+
- Check that every image loads at an appropriate resolution, has useful alternative text, and retains its subject at the actual displayed size. Decorative images should follow the site's decorative-image policy.
|
|
112
|
+
- Exercise the real links, keyboard interactions, disclosures, reduced-motion behavior and relevant static/no-JavaScript rendering. Preserve the configured security policy rather than weakening it for an effect.
|
|
113
|
+
- Run the application's permitted type, label, manifest and discovery checks. Separate development-render verification from production-build and deployment evidence.
|
|
114
|
+
- Confirm a focused revision did not change the approved hero, other sections, selected image or action policy outside its scope.
|
|
115
|
+
|
|
116
|
+
Deliver the changed page and a concise account of what was checked. Preserve concrete user decisions between iterations; do not repeatedly restart the art direction or rewrite already approved meaning.
|
|
117
|
+
|
|
118
|
+
## Research behind the writing guidance
|
|
119
|
+
|
|
120
|
+
These sources support readable structure; they do not establish conversion uplift for a particular application:
|
|
121
|
+
|
|
122
|
+
- [Nielsen Norman Group: Microcontent](https://www.nngroup.com/articles/microcontent-how-to-write-headlines-page-titles-and-subject-lines/) — useful, specific headings; short copy that conveys meaning without surrounding text.
|
|
123
|
+
- [Nielsen Norman Group: Concise, Scannable, and Objective](https://www.nngroup.com/articles/concise-scannable-and-objective-how-to-write-for-the-web/) — tested benefits of concise, scannable writing; distinguish the study's usability measures from marketing conversion claims.
|
|
124
|
+
- [Office for National Statistics: Structuring content](https://service-manual.ons.gov.uk/content/writing-for-users/structuring-content) — front-load important information and use concise descriptive headings.
|
|
125
|
+
|
|
126
|
+
Consult current primary guidance when researching a new content/design question. Attribute outside findings precisely, then distinguish the recommendation made for this application from what the research actually tested.
|