@wildo-ai/framework-knowledge 1.1.10 → 1.1.12
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/claude-marketplace/.claude-plugin/marketplace.json +1 -1
- package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +1 -1
- package/dist/claude-marketplace/plugins/wildo/references/acceptance.md +4 -0
- package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +25 -3
- package/dist/claude-marketplace/plugins/wildo/references/creation-state.md +40 -12
- package/dist/claude-marketplace/plugins/wildo/references/derived-artifacts.md +7 -5
- package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +12 -0
- package/dist/claude-marketplace/plugins/wildo/skills/answer/SKILL.md +19 -2
- package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +33 -9
- package/dist/esm/framework-knowledge.definitions.d.ts +2 -3
- package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.definitions.js +628 -107
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/framework-knowledge.loader.js.map +1 -1
- package/dist/esm/framework-knowledge.research-provenance.d.ts +90 -0
- package/dist/esm/framework-knowledge.research-provenance.d.ts.map +1 -0
- package/dist/esm/framework-knowledge.research-provenance.js +140 -0
- package/dist/esm/framework-knowledge.research-provenance.js.map +1 -0
- 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 +2 -0
- package/dist/esm/index.d.ts.map +1 -1
- package/dist/esm/index.js +2 -0
- package/dist/esm/index.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -3
- 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 +4 -12
- 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.map +1 -1
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +12 -1
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +10 -4
- 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 +82 -15
- 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 +1 -5
- 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 +4 -16
- 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 +1 -1
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js +1 -1
- package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +9 -5
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +11 -7
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js +1 -1
- package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js.map +1 -1
- 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 +38 -14
- 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 +16 -8
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +20 -8
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +29 -3
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +80 -16
- 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 +2 -2
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +7 -2
- package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts +2 -2
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js +2 -2
- package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +6 -2
- 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 +4 -3
- 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 +26 -7
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +23 -6
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts +45 -10
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js +61 -21
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts +4 -3
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +8 -5
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts +2 -2
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js +7 -3
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +3 -3
- 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.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +9 -7
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts +5 -0
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js +9 -2
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +5 -2
- 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 +15 -5
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js +6 -4
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts +3 -1
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js +4 -1
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +10 -1
- 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 +36 -13
- 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 +8 -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 +7 -1
- 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 +4 -1
- 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 +34 -6
- 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 +7 -3
- 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 +6 -4
- 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.js +2 -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 +22 -10
- 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 +39 -29
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
- 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 +8 -3
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js +24 -9
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +8 -2
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +8 -2
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js +1 -1
- package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js.map +1 -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.js +2 -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.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +1 -1
- 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.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +13 -5
- 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 +3 -7
- 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 +12 -14
- 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 +3 -0
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +2 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +3 -1
- 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 +2 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts +98 -0
- package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.service-method/playbook.definition.js +124 -0
- package/dist/esm/playbooks/top_down.service-method/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +3 -1
- 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 +4 -2
- 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 +34 -1
- 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 +39 -20
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
- package/dist/esm/source-anchor-grammar.d.ts +70 -0
- package/dist/esm/source-anchor-grammar.d.ts.map +1 -0
- package/dist/esm/source-anchor-grammar.js +114 -0
- package/dist/esm/source-anchor-grammar.js.map +1 -0
- 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 -1
- package/dist/knowledge/manifest.json +8 -8
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +12 -0
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +4 -4
- package/dist/knowledge/playbooks/bottom_up.build/method.md +12 -2
- package/dist/knowledge/playbooks/bottom_up.build/playbook.json +5 -3
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +788 -49
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +18 -4
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +451 -16
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +3 -6
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +2 -2
- package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +3 -2
- package/dist/knowledge/playbooks/bottom_up.conception/method.md +12 -7
- package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +4 -3
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +2 -2
- package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +2 -1
- package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +115 -2
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +11 -4
- package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +71 -7
- package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +19 -6
- package/dist/knowledge/playbooks/bottom_up.foundation/method.md +126 -24
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +51 -7
- package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +28 -9
- package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +5 -3
- package/dist/knowledge/playbooks/bottom_up.maturity-reading/method.md +10 -2
- package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +4 -3
- package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +67 -5
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +10 -3
- package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +176 -22
- package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +21 -3
- package/dist/knowledge/playbooks/cross_cutting.application-creation/method.md +27 -12
- package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +11 -5
- package/dist/knowledge/playbooks/cross_cutting.compliance/method.md +4 -4
- package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +7 -2
- package/dist/knowledge/playbooks/cross_cutting.feature-development/playbook.json +1 -0
- package/dist/knowledge/playbooks/cross_cutting.refinement/method.md +6 -5
- package/dist/knowledge/playbooks/cross_cutting.refinement/playbook.json +5 -2
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +153 -28
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +3 -2
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +36 -7
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +6 -2
- package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +9 -2
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/method.md +8 -6
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +2 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/method.md +9 -2
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +17 -5
- package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +11 -4
- package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +3 -2
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/method.md +16 -6
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +3 -2
- package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +5 -1
- package/dist/knowledge/playbooks/top_down.business-model/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.business-model/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.business-model/method.md +49 -11
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +24 -8
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +6 -2
- package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +1 -1
- package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +49 -14
- package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +15 -5
- package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +6 -2
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +20 -0
- package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +4 -3
- package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +69 -65
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +11 -7
- package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.definition/method.md +10 -3
- package/dist/knowledge/playbooks/top_down.definition/playbook.json +14 -5
- package/dist/knowledge/playbooks/top_down.expert-personas/method.md +10 -3
- package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +4 -3
- package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +2 -1
- package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +4 -2
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +4 -3
- package/dist/knowledge/playbooks/top_down.market-research/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +3 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +3 -2
- 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/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +10 -6
- package/dist/knowledge/playbooks/top_down.risk-register/method.md +8 -1
- package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +5 -1
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +6 -1
- package/dist/knowledge/playbooks/top_down.service-method/method.md +216 -0
- package/dist/knowledge/playbooks/top_down.service-method/playbook.json +108 -0
- package/dist/knowledge/playbooks/top_down.value-proposition/method.md +5 -2
- package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +9 -3
- package/dist/knowledge/playbooks/top_down.vision-elicitation/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.vision-elicitation/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +21 -2
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +63 -18
- package/dist/knowledge/references/acp.execution-profile.md +9 -1
- package/dist/knowledge/references/application-documentation-chapters.config.md +45 -10
- package/dist/knowledge/references/application-documentation-plan.config.md +2 -2
- package/dist/knowledge/references/application-maturity.config.md +28 -2
- package/dist/knowledge/references/backend.inbound-channels.attachment-adoption.md +57 -0
- package/dist/knowledge/references/backend.inbound-channels.handler-definition.md +65 -13
- package/dist/knowledge/references/backend.inbound-handlers.agents.md +10 -3
- package/dist/knowledge/references/backend.inbound-handlers.definition.md +463 -5
- package/dist/knowledge/references/backend.inbound-handlers.pipelines.md +62 -0
- package/dist/knowledge/references/blueprint.definition-contract.md +483 -0
- package/dist/knowledge/references/brand.name-screening.config.md +30 -3
- package/dist/knowledge/references/brand.visual-tone.config.md +26 -8
- package/dist/knowledge/references/build-plan.task-graph.config.md +438 -12
- package/dist/knowledge/references/business-model.pricing-plan.config.md +19 -9
- package/dist/knowledge/references/business-model.snapshot.config.md +29 -2
- package/dist/knowledge/references/business-model.snapshot.validation.md +29 -8
- package/dist/knowledge/references/capability-composition.config.md +4 -3
- package/dist/knowledge/references/cli.market.generate-command.md +2 -1
- package/dist/knowledge/references/companion.introspection.behaviors.market.md +3 -0
- package/dist/knowledge/references/companion.market.generation-service.md +46 -5
- package/dist/knowledge/references/companion.market.prompt-renderer.md +1 -1
- package/dist/knowledge/references/companion.technical-doc.service.md +342 -76
- package/dist/knowledge/references/domain-plan.record-partition.md +105 -0
- package/dist/knowledge/references/engine.client-bundle.allow-list.md +16 -0
- package/dist/knowledge/references/engine.saas-technical-doc.config.md +69 -15
- package/dist/knowledge/references/engine.saas-website.config.md +16 -44
- package/dist/knowledge/references/example.ai-use-declaration.agent.md +37 -0
- package/dist/knowledge/references/example.authorization.application-roles.office-and-field.md +10 -0
- package/dist/knowledge/references/{example.authorization.service-provider-organization-wide-access.md → example.authorization.relationship-organization-wide-access.md} +2 -2
- package/dist/knowledge/references/example.backend.addon-wiring.module.md +6 -0
- package/dist/knowledge/references/example.backend.custom-operation.child-line-total.md +4 -3
- package/dist/knowledge/references/example.backend.custom-operation.create-related-resource.md +22 -0
- package/dist/knowledge/references/example.backend.custom-operation.declared-refusal-code.md +41 -0
- package/dist/knowledge/references/example.backend.custom-operation.external-effect-reservation.md +107 -0
- package/dist/knowledge/references/example.blueprint.definition.internal-tool.md +47 -0
- package/dist/knowledge/references/example.config.app-shell.full.md +6 -3
- package/dist/knowledge/references/example.config.app-shell.hosted-components.md +4 -1
- package/dist/knowledge/references/example.config.backend.inbound-email.md +4 -2
- package/dist/knowledge/references/example.config.backend.required-floors.md +4 -2
- package/dist/knowledge/references/example.config.design-system.full.md +40 -116
- package/dist/knowledge/references/example.flows-actors.autonomous-agent.reviewed-write.md +10 -0
- package/dist/knowledge/references/example.flows-actors.chat-assistant.md +78 -19
- package/dist/knowledge/references/example.flows-actors.declared-flow.md +115 -0
- package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +12 -0
- package/dist/knowledge/references/example.inbound.email-channel-handler.md +10 -1
- package/dist/knowledge/references/example.infra.environment-config.local.md +34 -63
- package/dist/knowledge/references/example.layout-2d.registration.md +11 -0
- package/dist/knowledge/references/example.minion.contained-tick.md +1 -1
- package/dist/knowledge/references/example.module.companion-exports.full.md +1 -0
- package/dist/knowledge/references/example.module.relationships.actor-edge-back-to-scope-owner.md +35 -35
- package/dist/knowledge/references/example.module.relationships.scope-membership-junction.md +8 -10
- package/dist/knowledge/references/example.navigation.one-entry-per-concept.md +47 -0
- package/dist/knowledge/references/example.organization-identity.system-of-record-partitions.md +18 -0
- package/dist/knowledge/references/example.organizations.relationship-kinds.md +26 -0
- package/dist/knowledge/references/example.professional-qualifications.declaration.md +10 -0
- package/dist/knowledge/references/example.professional-qualifications.gate.md +25 -0
- package/dist/knowledge/references/example.provider.backend-module-shape.md +38 -4
- package/dist/knowledge/references/example.provider.frontend-facet.on-demand-sdk.md +41 -0
- package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +4 -5
- package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +7 -5
- package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +0 -5
- package/dist/knowledge/references/example.resource.custom-view.backend-refusal.md +75 -0
- package/dist/knowledge/references/example.resource.status-lifecycle.quote.md +8 -7
- package/dist/knowledge/references/example.resource.ui-behavior.enum-badge.md +23 -7
- package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +87 -22
- package/dist/knowledge/references/example.resource.ui-behavior.record-template.md +80 -0
- package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +20 -21
- package/dist/knowledge/references/example.resource.ui-behavior.workflow-record-page.md +212 -0
- package/dist/knowledge/references/example.spec.composite-view.workspace.md +10 -2
- package/dist/knowledge/references/example.subject-export.portability-archive.md +42 -0
- package/dist/knowledge/references/example.views.app-level.workflow-home.md +238 -0
- package/dist/knowledge/references/example.views.composite-view.workspace.md +10 -3
- package/dist/knowledge/references/example.website.blocks.section.md +20 -0
- package/dist/knowledge/references/example.website.blocks.site-choices.md +78 -0
- package/dist/knowledge/references/example.website.blocks.site-configs.md +155 -0
- package/dist/knowledge/references/example.website.demo.append.md +57 -0
- package/dist/knowledge/references/example.website.demo.approval.md +47 -0
- package/dist/knowledge/references/example.website.demo.celebrate.md +39 -0
- package/dist/knowledge/references/example.website.demo.complete-items.md +103 -0
- package/dist/knowledge/references/example.website.demo.connect.md +45 -0
- package/dist/knowledge/references/example.website.demo.dashboard.md +74 -0
- package/dist/knowledge/references/example.website.demo.query-answer.md +77 -0
- package/dist/knowledge/references/example.website.demo.status-lifecycle.md +71 -0
- package/dist/knowledge/references/example.website.demo.transform.md +43 -0
- package/dist/knowledge/references/example.website.page.manifest.md +2 -6
- package/dist/knowledge/references/example.website.pricing.audit-payloads.md +38 -0
- package/dist/knowledge/references/example.website.pricing.catalog-load.md +77 -0
- package/dist/knowledge/references/example.website.pricing.offers.md +43 -0
- package/dist/knowledge/references/example.website.pricing.plans-section.md +20 -0
- package/dist/knowledge/references/example.website.pricing.plans.md +88 -0
- package/dist/knowledge/references/example.website.section.bento.md +27 -0
- package/dist/knowledge/references/example.website.section.contact-form.md +15 -0
- package/dist/knowledge/references/example.website.section.factories.md +82 -0
- package/dist/knowledge/references/example.website.section.faq.md +17 -0
- package/dist/knowledge/references/example.website.section.footer-cta.md +13 -0
- package/dist/knowledge/references/example.website.section.hero.md +16 -0
- package/dist/knowledge/references/example.website.section.latest-posts.md +15 -0
- package/dist/knowledge/references/example.website.section.marquee.md +26 -0
- package/dist/knowledge/references/example.website.section.roadmap.md +25 -0
- package/dist/knowledge/references/example.website.section.site-block.md +43 -0
- package/dist/knowledge/references/example.website.section.solution-paths.md +17 -0
- package/dist/knowledge/references/example.website.section.stats.md +23 -0
- package/dist/knowledge/references/example.website.section.steps.md +15 -0
- package/dist/knowledge/references/example.website.showcase.tour.md +49 -0
- package/dist/knowledge/references/example.website.theme.composed.md +69 -0
- package/dist/knowledge/references/experience-plan.config.md +127 -1
- package/dist/knowledge/references/external-connectors.frontend-provider-consent-classification.md +8 -0
- package/dist/knowledge/references/external-connectors.frontend-provider-sdk-activation-mode.md +27 -0
- package/dist/knowledge/references/external-connectors.models.connection-target.md +99 -0
- package/dist/knowledge/references/external-connectors.models.file-storage-adapter.md +13 -0
- package/dist/knowledge/references/external-connectors.models.hook-inbound-endpoint.md +352 -0
- package/dist/knowledge/references/external-connectors.models.hook-signature-algorithms.md +168 -0
- package/dist/knowledge/references/external-connectors.models.hook-trigger-strategy.md +97 -0
- package/dist/knowledge/references/external-connectors.models.oauth2-audiences.md +72 -8
- package/dist/knowledge/references/external-connectors.models.oauth2-incremental-consent.md +235 -0
- package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +1272 -3
- package/dist/knowledge/references/external-connectors.models.subject-erasure-effect.md +105 -0
- package/dist/knowledge/references/external-connectors.private.provider-compliance-state-collector.md +36 -0
- package/dist/knowledge/references/external-connectors.private.provider-configuration-check.md +69 -0
- package/dist/knowledge/references/integration-plan.config.md +28 -8
- package/dist/knowledge/references/market.references.weighted-edges.md +14 -1
- package/dist/knowledge/references/minions.tick-contract.md +2 -2
- package/dist/knowledge/references/placement-plan.config.md +94 -13
- package/dist/knowledge/references/platform.config.backing-services.md +9 -11
- package/dist/knowledge/references/platform.config.environment.deployment.md +140 -7
- package/dist/knowledge/references/platform.config.infra-provider-resolution.md +3 -3
- package/dist/knowledge/references/platform.config.infrastructure-host.md +2 -1
- package/dist/knowledge/references/platform.config.platform-key-management.md +282 -0
- package/dist/knowledge/references/platform.config.saas.md +126 -32
- package/dist/knowledge/references/platform.key-management.vault-custody.md +78 -0
- package/dist/knowledge/references/presets.3d.frame-style-resolution.md +65 -0
- package/dist/knowledge/references/presets.3d.layout-contract.md +4 -30
- package/dist/knowledge/references/presets.3d.register-layout.md +14 -36
- package/dist/knowledge/references/presets.layouts-2d.authoring.md +157 -0
- package/dist/knowledge/references/presets.layouts-2d.register-layout.md +53 -0
- package/dist/knowledge/references/presets.layouts-2d.settings.md +53 -0
- package/dist/knowledge/references/presets.layouts-2d.vocabulary.md +41 -0
- package/dist/knowledge/references/presets.models.field-form-control-variant.md +32 -0
- package/dist/knowledge/references/presets.models.labelling.sections.md +39 -0
- package/dist/knowledge/references/presets.models.palette-contrast.md +183 -0
- package/dist/knowledge/references/presets.models.palette-derivation.md +93 -0
- package/dist/knowledge/references/presets.models.surface-policy.defaults.md +27 -0
- package/dist/knowledge/references/presets.models.surface-variant.md +11 -0
- package/dist/knowledge/references/presets.models.theme-contract.md +136 -0
- package/dist/knowledge/references/presets.models.theme-personality-lexicon.md +81 -0
- package/dist/knowledge/references/presets.models.theme-personality.md +159 -0
- package/dist/knowledge/references/presets.themes.compose-theme.md +47 -0
- package/dist/knowledge/references/requirements.non-functional-requirement.config.md +4 -4
- package/dist/knowledge/references/requirements.snapshot.config.md +2 -3
- package/dist/knowledge/references/roadmap.phase.config.md +2 -16
- package/dist/knowledge/references/saas.approval-seals.admin-endpoints.md +158 -0
- package/dist/knowledge/references/saas.backend.a2a.token-budget.md +85 -12
- package/dist/knowledge/references/saas.backend.actor-execution-continuation.md +179 -0
- package/dist/knowledge/references/saas.backend.app-config.backend-authored.md +5 -1
- package/dist/knowledge/references/saas.backend.application-initialization.assembly.md +3 -1
- package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +13 -1
- package/dist/knowledge/references/saas.backend.crypto-keys.application-keys.md +100 -0
- package/dist/knowledge/references/saas.backend.custom-operation.authoritative-fields.md +4 -1
- package/dist/knowledge/references/saas.backend.custom-operation.commit-outcome-read-back.md +208 -0
- package/dist/knowledge/references/saas.backend.custom-operation.core-write-precondition.md +38 -0
- package/dist/knowledge/references/saas.backend.custom-operation.external-effect-reservation.md +109 -0
- package/dist/knowledge/references/saas.backend.custom-operation.hook-transaction-posture.md +43 -0
- package/dist/knowledge/references/saas.backend.custom-operation.target-authority.md +33 -0
- package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +131 -1
- package/dist/knowledge/references/saas.backend.document-sequence.issue-in-operation.md +1 -1
- package/dist/knowledge/references/saas.backend.document-sequence.raise-floor.md +62 -13
- package/dist/knowledge/references/saas.backend.domain-module.md +105 -1
- package/dist/knowledge/references/saas.backend.email-template.definition.md +34 -0
- package/dist/knowledge/references/saas.backend.email-template.words.md +98 -0
- package/dist/knowledge/references/saas.backend.email.send.md +7 -0
- package/dist/knowledge/references/saas.backend.flows-actors.a2a-task-surface.md +35 -4
- package/dist/knowledge/references/saas.backend.flows-actors.ask-person-tool.md +79 -0
- package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-case-selector.md +71 -0
- package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-declaration.md +21 -10
- package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-schedule.md +11 -5
- package/dist/knowledge/references/saas.backend.flows-actors.chat-agent-declaration.md +51 -0
- package/dist/knowledge/references/saas.backend.flows-actors.chat-reply-handler.md +219 -0
- package/dist/knowledge/references/saas.backend.flows-actors.decision-notice-handler.md +239 -0
- package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +661 -3
- package/dist/knowledge/references/saas.backend.flows-actors.invoke-agent.md +15 -2
- package/dist/knowledge/references/saas.backend.flows-actors.operation-approval-resolvers.md +50 -0
- package/dist/knowledge/references/saas.backend.flows-actors.present-records-tool.md +106 -0
- package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +14 -1
- package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +9 -4
- package/dist/knowledge/references/saas.backend.flows-actors.retrieval-tool.md +205 -0
- package/dist/knowledge/references/saas.backend.flows-actors.tool-dispatch-obligations.md +21 -5
- package/dist/knowledge/references/saas.backend.flows.start-flow-method.md +28 -0
- package/dist/knowledge/references/saas.backend.flows.start-flow.md +47 -0
- package/dist/knowledge/references/saas.backend.pdf-template.collection-definition.md +5 -3
- package/dist/knowledge/references/saas.backend.privacy.subject-export-archive.md +26 -0
- package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +21 -19
- package/dist/knowledge/references/saas.backend.providers.optional-runtime-peers.md +15 -25
- package/dist/knowledge/references/saas.backend.rate-limit-service.check-policy.md +3 -2
- package/dist/knowledge/references/saas.backend.submission-challenge.md +4 -0
- package/dist/knowledge/references/saas.backend.system-access-service.md +394 -104
- package/dist/knowledge/references/saas.config.content-security-policy.md +26 -10
- package/dist/knowledge/references/saas.data-seeding.definition-input.md +1 -1
- package/dist/knowledge/references/saas.data-seeding.modes.md +4 -1
- package/dist/knowledge/references/saas.data-seeding.row-reference.md +2 -4
- package/dist/knowledge/references/saas.data-seeding.run-ledger.md +3 -0
- package/dist/knowledge/references/saas.external-data.admin-endpoints.md +70 -3
- package/dist/knowledge/references/saas.external-providers.backend-provider-loader.md +6 -0
- package/dist/knowledge/references/saas.external-providers.backend-provider-registry.runtime-filter.md +2 -0
- package/dist/knowledge/references/saas.external-providers.llm.model-configuration.md +3 -0
- package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +10 -2
- package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +10 -16
- package/dist/knowledge/references/saas.frontend.app-shell.building-blocks.md +7 -3
- package/dist/knowledge/references/saas.frontend.app-shell.register-shell-layout.md +97 -0
- package/dist/knowledge/references/saas.frontend.app-shell.shell-layout-contract.md +60 -0
- package/dist/knowledge/references/saas.frontend.app-shell.shell-motion-contract.md +274 -0
- package/dist/knowledge/references/saas.frontend.app-shell.use-shell-motion.md +73 -0
- package/dist/knowledge/references/saas.frontend.brand-identity.md +6 -0
- package/dist/knowledge/references/saas.frontend.chart-dashboard-view.md +43 -0
- package/dist/knowledge/references/saas.frontend.chart-dashboard.md +130 -0
- package/dist/knowledge/references/saas.frontend.chart-view.inserted-declaration.md +13 -0
- package/dist/knowledge/references/saas.frontend.chart-view.resource-chart-data.md +8 -4
- package/dist/knowledge/references/saas.frontend.chat-sign-in-completion.md +99 -0
- package/dist/knowledge/references/saas.frontend.collection-filter-presets.md +92 -23
- package/dist/knowledge/references/saas.frontend.command-menu.search-resource.md +3 -3
- package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +9 -3
- package/dist/knowledge/references/saas.frontend.domain-module.md +5 -0
- package/dist/knowledge/references/saas.frontend.embedded-resource-descent.md +2 -1
- package/dist/knowledge/references/saas.frontend.errors.backend-refusal.md +96 -0
- package/dist/knowledge/references/saas.frontend.execution-view.definition.md +57 -3
- package/dist/knowledge/references/saas.frontend.field-tiles.md +76 -0
- package/dist/knowledge/references/saas.frontend.flows-actors-view.md +10 -2
- package/dist/knowledge/references/saas.frontend.focus-indicator.md +119 -0
- package/dist/knowledge/references/saas.frontend.launcher.item-refs.md +14 -2
- package/dist/knowledge/references/saas.frontend.launcher.merge-rules.md +7 -4
- package/dist/knowledge/references/saas.frontend.launcher.runtime-availability.md +17 -16
- package/dist/knowledge/references/saas.frontend.linked-conversations-embed.md +3 -5
- package/dist/knowledge/references/saas.frontend.operation-key-and-resource-config-like.md +68 -1
- package/dist/knowledge/references/saas.frontend.providers.execute-operation.md +14 -24
- package/dist/knowledge/references/saas.frontend.record-page-parts.md +117 -0
- package/dist/knowledge/references/saas.frontend.related-resource-embeds.md +184 -5
- package/dist/knowledge/references/saas.frontend.related-resource-sections.md +6 -0
- package/dist/knowledge/references/saas.frontend.resource-header-title.md +98 -34
- package/dist/knowledge/references/saas.frontend.resource-label-params.md +3 -1
- package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +59 -19
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +344 -62
- package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +13 -8
- package/dist/knowledge/references/saas.frontend.section-stages.md +63 -0
- package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +183 -32
- package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +72 -13
- package/dist/knowledge/references/saas.frontend.viewer-may-perform-operation.md +52 -0
- package/dist/knowledge/references/saas.models.agent-suspension.md +75 -0
- package/dist/knowledge/references/saas.models.agent-work-capture-settings.md +2 -2
- package/dist/knowledge/references/saas.models.agent-work-decision-contents-read.md +69 -0
- package/dist/knowledge/references/saas.models.agent-work-decision-surface.md +11 -2
- package/dist/knowledge/references/saas.models.agent-work-decision-vocabulary.md +20 -3
- package/dist/knowledge/references/saas.models.agent-work-output-review.md +3 -3
- package/dist/knowledge/references/saas.models.agent-work-override-rate.md +6 -5
- package/dist/knowledge/references/saas.models.agent-work-review-config.md +22 -4
- package/dist/knowledge/references/saas.models.analytics.value-moments.md +22 -0
- package/dist/knowledge/references/saas.models.application-agent-policy.md +28 -0
- package/dist/knowledge/references/saas.models.application-entry-points.md +45 -0
- package/dist/knowledge/references/saas.models.audit-trails.actor-attribution.md +21 -0
- package/dist/knowledge/references/saas.models.audit.trail-config.md +18 -5
- package/dist/knowledge/references/saas.models.auth.relationship-grantor-authentication.md +175 -0
- package/dist/knowledge/references/saas.models.authorization.administrative-continuity-codes.md +4 -4
- package/dist/knowledge/references/saas.models.chat-identity-link-host.md +38 -0
- package/dist/knowledge/references/saas.models.compliance.ai-use-classification.md +179 -0
- package/dist/knowledge/references/saas.models.compliance.ai-use-posture.md +121 -0
- package/dist/knowledge/references/saas.models.config.declared-type-renames.md +246 -0
- package/dist/knowledge/references/saas.models.config.organization-types.md +54 -74
- package/dist/knowledge/references/saas.models.conversation-threads.md +43 -6
- package/dist/knowledge/references/saas.models.crypto-keys.floors.md +32 -0
- package/dist/knowledge/references/saas.models.crypto-keys.key-management-config.md +130 -0
- package/dist/knowledge/references/saas.models.crypto-keys.local-provider.md +29 -0
- package/dist/knowledge/references/saas.models.crypto-keys.purpose-descriptor.md +442 -0
- package/dist/knowledge/references/saas.models.crypto-keys.purposes.md +91 -0
- package/dist/knowledge/references/saas.models.data-mode-read-list.md +24 -79
- package/dist/knowledge/references/saas.models.engine-capabilities.md +39 -2
- package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +3 -0
- package/dist/knowledge/references/saas.models.evaluation-dataset-export.md +16 -9
- package/dist/knowledge/references/saas.models.evaluation-export-authorization.md +23 -6
- package/dist/knowledge/references/saas.models.external-data-conflict-vocabulary.md +53 -0
- package/dist/knowledge/references/saas.models.external-data-pipeline.md +96 -26
- package/dist/knowledge/references/saas.models.flows-actors.agent-behavior-report-config.md +28 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-behavior-report.md +321 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-configuration.md +29 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-content-guardrails.md +150 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-definition.md +45 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-operation-record.md +154 -0
- package/dist/knowledge/references/saas.models.flows-actors.autonomous-agents-vocabulary.md +49 -7
- package/dist/knowledge/references/saas.models.flows-actors.chat-agents-vocabulary.md +26 -0
- package/dist/knowledge/references/saas.models.flows-actors.decision-card-wording.md +284 -0
- package/dist/knowledge/references/saas.models.flows-actors.decision-notice-recorded-cards.md +93 -0
- package/dist/knowledge/references/saas.models.flows-actors.human-decision-decider.md +70 -0
- package/dist/knowledge/references/saas.models.flows-actors.human-input-form.md +349 -0
- package/dist/knowledge/references/saas.models.flows-actors.operation-approval-pending.md +55 -0
- package/dist/knowledge/references/saas.models.flows-actors.operation-approval-requirement.md +93 -0
- package/dist/knowledge/references/saas.models.flows-actors.review-deadline-vocabulary.md +6 -0
- package/dist/knowledge/references/saas.models.flows-actors.review-deadlines-declaration.md +4 -3
- package/dist/knowledge/references/saas.models.flows.run-state.md +49 -0
- package/dist/knowledge/references/saas.models.flows.runnable-model.md +274 -0
- package/dist/knowledge/references/saas.models.frontend-on-demand-capability-contract.md +54 -0
- package/dist/knowledge/references/saas.models.guidance-flow.md +1 -1
- package/dist/knowledge/references/saas.models.http-api-binding.md +176 -50
- package/dist/knowledge/references/saas.models.http-api-binding.rest-write-operations.md +3 -3
- package/dist/knowledge/references/saas.models.http-api-population-filter.md +51 -0
- package/dist/knowledge/references/saas.models.human-decision-review-marker.md +1 -1
- package/dist/knowledge/references/saas.models.inbound-channels.md +75 -3
- package/dist/knowledge/references/saas.models.inbound-email-domains.md +5 -5
- package/dist/knowledge/references/saas.models.inbound-email.md +2 -2
- package/dist/knowledge/references/saas.models.m2m-webhook-events.md +73 -0
- package/dist/knowledge/references/saas.models.model-cost-accounting-config.md +1 -1
- package/dist/knowledge/references/saas.models.model-cost-summary.md +56 -20
- package/dist/knowledge/references/saas.models.notifications.targets.md +28 -3
- package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +259 -21
- package/dist/knowledge/references/saas.models.on-demand-provider-capabilities.md +28 -0
- package/dist/knowledge/references/saas.models.organization-agent-policy.md +43 -0
- package/dist/knowledge/references/saas.models.organization-assigned-rows-declaration.md +74 -0
- package/dist/knowledge/references/saas.models.organization-own-rows-declaration.md +51 -0
- package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +6 -6
- package/dist/knowledge/references/saas.models.organizations.application-owner-codes.md +9 -10
- package/dist/knowledge/references/saas.models.organizations.identity-declaration.md +201 -0
- package/dist/knowledge/references/saas.models.organizations.organization-relationships.md +933 -0
- package/dist/knowledge/references/saas.models.organizations.professional-qualification-kinds.md +46 -0
- package/dist/knowledge/references/saas.models.organizations.professional-qualifications.md +168 -0
- package/dist/knowledge/references/{saas.models.organizations.service-provider-capability-grants.md → saas.models.organizations.relationship-capability-grants.md} +56 -35
- package/dist/knowledge/references/saas.models.organizations.relationship-grantor-controls.md +62 -0
- package/dist/knowledge/references/saas.models.organizations.relationship-invitations.md +228 -0
- package/dist/knowledge/references/saas.models.organizations.relationship-kinds.md +291 -0
- package/dist/knowledge/references/saas.models.organizations.relationship-record-separation.md +114 -0
- package/dist/knowledge/references/saas.models.privacy.data-residency.md +676 -0
- package/dist/knowledge/references/saas.models.privacy.legal-holds.md +114 -7
- package/dist/knowledge/references/saas.models.privacy.provider-capability-disclosure.md +73 -2
- package/dist/knowledge/references/saas.models.privacy.redaction-treatments.md +13 -14
- package/dist/knowledge/references/saas.models.privacy.retention-binding.md +84 -1
- package/dist/knowledge/references/saas.models.privacy.retention-enforcement-record.md +10 -0
- package/dist/knowledge/references/saas.models.privacy.retention-schedule.md +5 -3
- package/dist/knowledge/references/saas.models.privacy.subject-data-recipients.md +280 -40
- package/dist/knowledge/references/saas.models.privacy.subject-export.md +134 -0
- package/dist/knowledge/references/saas.models.provider-capabilities.md +38 -0
- package/dist/knowledge/references/saas.models.provider-usage-pricing-authority.md +50 -1
- package/dist/knowledge/references/saas.models.providers.capability-activation-policy.md +28 -0
- package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +20 -6
- package/dist/knowledge/references/saas.models.providers.compliance-choice.md +52 -0
- package/dist/knowledge/references/saas.models.providers.execute-operation-request.md +25 -0
- package/dist/knowledge/references/saas.models.providers.processing-region-reach.md +132 -0
- package/dist/knowledge/references/saas.models.providers.processing-region-selection.md +139 -0
- package/dist/knowledge/references/saas.models.providers.scope-reauthorization.md +1 -1
- package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +13 -1
- package/dist/knowledge/references/saas.models.rate-limit-configuration.md +4 -4
- package/dist/knowledge/references/saas.models.representative-activity.md +69 -0
- package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +165 -44
- package/dist/knowledge/references/saas.models.resource-config.metered-usage-recording.md +24 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +92 -11
- package/dist/knowledge/references/saas.models.resource-config.operation-auditable-event.md +4 -2
- package/dist/knowledge/references/saas.models.resource-config.operation-base.md +20 -3
- package/dist/knowledge/references/saas.models.resource-config.operation-bulk.md +37 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-chat-command.md +39 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-condition-parameters.md +56 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-idempotency-key.md +16 -6
- package/dist/knowledge/references/saas.models.resource-config.operation-mcp-exposure.md +1 -1
- package/dist/knowledge/references/saas.models.resource-config.operation-required-qualifications.md +30 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +137 -2
- package/dist/knowledge/references/saas.models.resource-config.operation-submission-challenge.md +1 -1
- package/dist/knowledge/references/saas.models.resource-config.operation-union.md +0 -1
- package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +1 -1
- package/dist/knowledge/references/saas.models.resource-config.record-label-fields.md +23 -0
- package/dist/knowledge/references/saas.models.resource-config.request-field-offers.md +104 -0
- package/dist/knowledge/references/saas.models.resource-config.required-features.md +20 -0
- package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +23 -16
- package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +25 -3
- package/dist/knowledge/references/saas.models.resource-config.retention-policy.md +46 -0
- package/dist/knowledge/references/saas.models.resource-config.system-access-policy.md +32 -15
- package/dist/knowledge/references/saas.models.resource-config.system-managed-fields.md +2 -1
- package/dist/knowledge/references/saas.models.resource-config.token-generation.md +1 -1
- package/dist/knowledge/references/saas.models.resource-operation-display-risk.md +5 -4
- package/dist/knowledge/references/saas.models.resource-operation-variant-runtime.md +3 -2
- package/dist/knowledge/references/saas.models.resource-relationship-builder-parameters.md +6 -2
- package/dist/knowledge/references/saas.models.roadmap.phase-horizon.md +31 -0
- package/dist/knowledge/references/saas.models.roles.definition.md +12 -1
- package/dist/knowledge/references/saas.models.roles.organization-defaults.md +12 -6
- package/dist/knowledge/references/saas.models.schema-family-builder.md +32 -4
- package/dist/knowledge/references/saas.models.scope-membership.md +2 -2
- package/dist/knowledge/references/saas.models.system-of-record-actions.md +65 -1
- package/dist/knowledge/references/saas.models.system-of-record-capabilities.md +123 -0
- package/dist/knowledge/references/saas.models.system-of-record-error-codes.md +19 -2
- package/dist/knowledge/references/saas.models.systems-of-record.md +110 -14
- package/dist/knowledge/references/saas.models.work-attribution-vocabulary.md +7 -3
- package/dist/knowledge/references/saas.models.work-unit-ref.md +17 -2
- package/dist/knowledge/references/saas.public-runtime.contract.md +75 -25
- package/dist/knowledge/references/saas.rag.retrieval-refusals.md +3 -2
- package/dist/knowledge/references/saas.specifications.assurance-control-markers.md +3 -2
- package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +13 -0
- package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +287 -17
- package/dist/knowledge/references/saas.specifications.catalogs.schema-org.catalog-spec-shared.md +5 -4
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +30 -2
- package/dist/knowledge/references/saas.specifications.engine-resource-sub-domain.md +105 -0
- package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +22 -4
- package/dist/knowledge/references/saas.specifications.processor-register.md +10 -1
- package/dist/knowledge/references/saas.specifications.recipient-disclosures.md +111 -2
- package/dist/knowledge/references/saas.specifications.recipient-population.md +46 -0
- package/dist/knowledge/references/saas.specifications.resource-frontend-configuration-aspect.md +7 -0
- package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +44 -5
- package/dist/knowledge/references/saas.specifications.resource-spec-config.md +21 -7
- package/dist/knowledge/references/saas.specifications.resource-spec-factory.md +113 -70
- package/dist/knowledge/references/saas.specifications.subject-data-recipients.md +136 -6
- package/dist/knowledge/references/saas.specifications.translation-glossary.md +80 -0
- package/dist/knowledge/references/saas.website.astro.bridge.md +51 -14
- package/dist/knowledge/references/saas.website.astro.head-renderer.md +63 -27
- package/dist/knowledge/references/saas.website.astro.i18n-helper.md +39 -10
- package/dist/knowledge/references/saas.website.astro.label-key-collector.md +12 -11
- package/dist/knowledge/references/saas.website.astro.label-loader.md +77 -14
- package/dist/knowledge/references/saas.website.astro.pick-labels-for-page.md +1 -2
- package/dist/knowledge/references/saas.website.astro.runtime-helper.md +49 -17
- package/dist/knowledge/references/saas.website.astro.site-context.md +17 -8
- package/dist/knowledge/references/saas.website.astro.structured-data-renderer.md +29 -8
- package/dist/knowledge/references/saas.website.blocks.actions.md +91 -0
- package/dist/knowledge/references/saas.website.blocks.band.md +41 -0
- package/dist/knowledge/references/saas.website.blocks.bento.md +70 -0
- package/dist/knowledge/references/saas.website.blocks.card-grid.md +115 -0
- package/dist/knowledge/references/saas.website.blocks.card.md +77 -0
- package/dist/knowledge/references/saas.website.blocks.cta-band.md +94 -0
- package/dist/knowledge/references/saas.website.blocks.define-block.md +123 -0
- package/dist/knowledge/references/saas.website.blocks.definitions.md +132 -0
- package/dist/knowledge/references/saas.website.blocks.faq.md +89 -0
- package/dist/knowledge/references/saas.website.blocks.feature-row.md +109 -0
- package/dist/knowledge/references/saas.website.blocks.hero.md +140 -0
- package/dist/knowledge/references/saas.website.blocks.intro.md +68 -0
- package/dist/knowledge/references/saas.website.blocks.latest-posts.md +104 -0
- package/dist/knowledge/references/saas.website.blocks.marquee.md +76 -0
- package/dist/knowledge/references/saas.website.blocks.pricing.md +395 -0
- package/dist/knowledge/references/saas.website.blocks.product-tour.md +158 -0
- package/dist/knowledge/references/saas.website.blocks.quote-cards.md +64 -0
- package/dist/knowledge/references/saas.website.blocks.roadmap.md +108 -0
- package/dist/knowledge/references/saas.website.blocks.section-slots.md +64 -0
- package/dist/knowledge/references/saas.website.blocks.solution-paths.md +71 -0
- package/dist/knowledge/references/saas.website.blocks.stats.md +183 -0
- package/dist/knowledge/references/saas.website.blocks.steps.md +69 -0
- package/dist/knowledge/references/saas.website.blocks.stylesheet.md +68 -0
- package/dist/knowledge/references/saas.website.blocks.tables.md +153 -0
- package/dist/knowledge/references/saas.website.blocks.vocabulary.md +227 -0
- package/dist/knowledge/references/saas.website.blog.bridge.md +98 -53
- package/dist/knowledge/references/saas.website.blog.collection-config.md +105 -49
- package/dist/knowledge/references/saas.website.blog.cover-resolver.md +93 -0
- package/dist/knowledge/references/saas.website.blog.frontmatter.md +106 -9
- package/dist/knowledge/references/saas.website.blog.head-renderer.md +37 -19
- package/dist/knowledge/references/saas.website.blog.index-builder.md +63 -0
- package/dist/knowledge/references/saas.website.blog.index.md +43 -0
- package/dist/knowledge/references/saas.website.blog.post-cover.md +38 -0
- package/dist/knowledge/references/saas.website.blog.post-renderer.md +115 -87
- package/dist/knowledge/references/saas.website.blog.react-mdx-integration.md +188 -0
- package/dist/knowledge/references/saas.website.blog.react-mdx-query.md +26 -0
- package/dist/knowledge/references/saas.website.blog.vocabulary-labels.md +113 -0
- package/dist/knowledge/references/saas.website.config.pricing-catalog-loader.md +5 -2
- package/dist/knowledge/references/saas.website.config.site-context-loader.md +26 -3
- package/dist/knowledge/references/saas.website.consent.banner.md +1 -1
- package/dist/knowledge/references/saas.website.consent.context.md +1 -1
- package/dist/knowledge/references/saas.website.design-tokens.bundle.md +28 -6
- package/dist/knowledge/references/saas.website.design-tokens.colors.md +7 -6
- package/dist/knowledge/references/saas.website.design-tokens.compose-function.md +35 -0
- package/dist/knowledge/references/saas.website.design-tokens.compose.md +76 -0
- package/dist/knowledge/references/saas.website.design-tokens.personality-derivation.md +22 -0
- package/dist/knowledge/references/saas.website.design-tokens.personality-lexicon.md +31 -0
- package/dist/knowledge/references/saas.website.design-tokens.personality.md +82 -0
- package/dist/knowledge/references/saas.website.design-tokens.product.md +122 -0
- package/dist/knowledge/references/saas.website.design-tokens.radius.md +12 -1
- package/dist/knowledge/references/saas.website.design-tokens.readers.md +58 -0
- package/dist/knowledge/references/saas.website.design-tokens.spacing.md +61 -0
- package/dist/knowledge/references/saas.website.design-tokens.surface-depth.md +60 -0
- package/dist/knowledge/references/saas.website.design-tokens.tones.md +75 -0
- package/dist/knowledge/references/saas.website.design-tokens.typography.md +115 -0
- package/dist/knowledge/references/saas.website.factories.define-page-manifest.md +23 -21
- package/dist/knowledge/references/saas.website.factories.define-section.md +36 -38
- package/dist/knowledge/references/saas.website.format.publication-date.md +26 -0
- package/dist/knowledge/references/saas.website.label-keys.compose-helper.md +1 -1
- package/dist/knowledge/references/saas.website.label-keys.format.md +4 -3
- package/dist/knowledge/references/saas.website.label-pack.validator.md +9 -8
- package/dist/knowledge/references/saas.website.labels.section-labels.md +34 -0
- package/dist/knowledge/references/saas.website.legal.public-document-links.md +19 -4
- package/dist/knowledge/references/saas.website.locale-switcher.label-keys.md +35 -0
- package/dist/knowledge/references/saas.website.menu.icons.md +123 -0
- package/dist/knowledge/references/saas.website.menu.label-keys.md +112 -0
- package/dist/knowledge/references/saas.website.menu.schema.md +92 -0
- package/dist/knowledge/references/saas.website.menu.vocabulary.md +79 -0
- package/dist/knowledge/references/saas.website.motion.demo-player.md +105 -0
- package/dist/knowledge/references/saas.website.motion.demo-scenario.md +460 -0
- package/dist/knowledge/references/saas.website.motion.demo.md +324 -0
- package/dist/knowledge/references/saas.website.motion.element-attributes.md +115 -0
- package/dist/knowledge/references/saas.website.motion.reveal-renditions.md +67 -0
- package/dist/knowledge/references/saas.website.motion.stylesheet.md +82 -0
- package/dist/knowledge/references/saas.website.motion.tempo-table.md +99 -0
- package/dist/knowledge/references/saas.website.motion.tokens.md +46 -0
- package/dist/knowledge/references/saas.website.motion.vocabulary.md +85 -0
- package/dist/knowledge/references/saas.website.page-layout.component.md +34 -8
- package/dist/knowledge/references/saas.website.page-manifest.meta-label-keys.md +4 -4
- package/dist/knowledge/references/saas.website.page-manifest.route-path.md +1 -1
- package/dist/knowledge/references/saas.website.page-manifest.schema.md +25 -29
- package/dist/knowledge/references/saas.website.page-manifest.seo.md +1 -1
- package/dist/knowledge/references/saas.website.page-navigation.md +44 -0
- package/dist/knowledge/references/saas.website.page.context.md +9 -2
- package/dist/knowledge/references/saas.website.primitives.button.md +6 -6
- package/dist/knowledge/references/saas.website.primitives.heading.md +17 -18
- package/dist/knowledge/references/saas.website.primitives.image.md +18 -15
- package/dist/knowledge/references/saas.website.primitives.internal-button.md +11 -12
- package/dist/knowledge/references/saas.website.primitives.internal-link.md +11 -35
- package/dist/knowledge/references/saas.website.primitives.link.md +22 -11
- package/dist/knowledge/references/saas.website.primitives.text.md +10 -8
- package/dist/knowledge/references/saas.website.product.atoms.md +366 -0
- package/dist/knowledge/references/saas.website.product.figures.md +320 -0
- package/dist/knowledge/references/saas.website.product.hooks.md +278 -0
- package/dist/knowledge/references/saas.website.product.panels.md +324 -0
- package/dist/knowledge/references/saas.website.product.stylesheet.md +1086 -0
- package/dist/knowledge/references/saas.website.refs.section.md +2 -2
- package/dist/knowledge/references/saas.website.root-config.schema.md +34 -17
- package/dist/knowledge/references/saas.website.routing.link-target.md +70 -0
- package/dist/knowledge/references/saas.website.routing.localized-path.md +15 -8
- package/dist/knowledge/references/saas.website.runtime.context.md +44 -17
- package/dist/knowledge/references/saas.website.section.component.md +21 -19
- package/dist/knowledge/references/saas.website.sections.category-enum.md +21 -2
- package/dist/knowledge/references/saas.website.sections.definition-schema.md +47 -39
- package/dist/knowledge/references/saas.website.site-footer.menu.md +47 -0
- package/dist/knowledge/references/saas.website.site-header.component.md +100 -0
- package/dist/knowledge/references/saas.website.site-header.scroll-behavior.md +26 -0
- package/dist/knowledge/references/saas.website.stacking.md +86 -0
- package/dist/knowledge/references/saas.website.structured-data.payload-shape.md +162 -0
- package/dist/knowledge/references/saas.website.use-blog-index.hook.md +27 -0
- package/dist/knowledge/references/saas.website.use-label.hook.md +6 -4
- package/dist/knowledge/references/service-method.config.md +303 -0
- package/dist/knowledge/references/vision.constraint.config.md +4 -2
- package/dist/knowledge/references/website-plan.config.md +544 -32
- package/dist/knowledge/references/website-plan.menu-placement.md +118 -0
- package/dist/knowledge/references/website-plan.page-kind-essentials.md +42 -0
- package/dist/knowledge/references/website-plan.page-routes.md +39 -0
- package/dist/knowledge/references/workers.node.worker-init-contract.md +4 -2
- package/dist/knowledge/references/zod.decorators.chainable-runtime.md +133 -9
- package/dist/knowledge/references/zod.decorators.chrome-modes.md +92 -0
- package/dist/knowledge/references/zod.decorators.data-categories.md +124 -34
- package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +99 -6
- package/dist/knowledge/references/zod.decorators.display-edit-modes.md +34 -1
- package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +41 -7
- package/dist/knowledge/references/zod.decorators.file-schema.md +10 -8
- package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +25 -9
- package/dist/knowledge/references/zod.decorators.primitive-ui.md +15 -3
- package/dist/knowledge/references/zod.decorators.rag-source.md +20 -20
- package/dist/knowledge/references/zod.decorators.schema-metadata.md +6 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +52 -18
- package/dist/knowledge/references/zod.decorators.shared-structural-params.md +107 -5
- package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +193 -9
- package/dist/knowledge/references/zod.factories.bigdecimal.md +17 -8
- package/dist/knowledge/references/zod.factories.code.md +18 -9
- package/dist/knowledge/references/zod.factories.duration.md +23 -14
- package/dist/knowledge/references/zod.factories.money.md +24 -15
- package/dist/knowledge/references/zod.factories.phone.md +23 -14
- package/dist/knowledge/references/zod.factories.range.md +5 -1
- package/dist/knowledge/references/zod.factories.year-month.md +79 -0
- package/dist/knowledge/registries/assurance-authority-bases.json +3 -3
- package/dist/knowledge/registries/framework-topics.json +5250 -2565
- package/dist/knowledge/registries/playbooks.json +88 -55
- package/dist/knowledge/registries/source-tags.json +9347 -4807
- package/dist/knowledge/rules/database-migration-obligation.md +10 -5
- package/dist/knowledge/rules/live-context-door.md +1 -1
- package/dist/knowledge/skills/INDEX.md +62 -33
- package/dist/knowledge/skills/agent-work-review/SKILL.md +86 -23
- package/dist/knowledge/skills/agent-work-review/references/framework-actor-execution-continuation-api.md +227 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-capture-settings-api.md +2 -2
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-decision-contents-api.md +79 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-output-review-api.md +4 -4
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-override-rate-api.md +6 -5
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-config-api.md +22 -4
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-marker-api.md +16 -4
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-vocabulary-api.md +20 -3
- package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-dataset-export-api.md +16 -9
- package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-export-authorization-api.md +24 -7
- package/dist/knowledge/skills/agent-work-review/references/framework-human-input-form-api.md +376 -0
- package/dist/knowledge/skills/ai-use-declaration/SKILL.md +192 -0
- package/dist/knowledge/skills/ai-use-declaration/references/choosing-the-domain-and-class.md +73 -0
- package/dist/knowledge/skills/ai-use-declaration/references/framework-ai-use-classification-api.md +194 -0
- package/dist/knowledge/skills/ai-use-declaration/references/framework-ai-use-posture-api.md +136 -0
- package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +30 -19
- package/dist/knowledge/skills/application-consumer-documentation-authoring/references/framework-documentation-chapters-api.md +48 -13
- package/dist/knowledge/skills/application-consumer-documentation-authoring/references/source-and-ownership-routing.md +2 -2
- package/dist/knowledge/skills/application-database-migrations/SKILL.md +26 -9
- package/dist/knowledge/skills/application-database-migrations/references/postgresql-supported-surfaces.md +64 -0
- package/dist/knowledge/skills/application-database-migrations/references/postgresql-vs-mongodb-obligations.md +37 -1
- package/dist/knowledge/skills/application-roles-authoring/SKILL.md +28 -3
- package/dist/knowledge/skills/application-roles-authoring/references/framework-application-roles-api.md +24 -7
- package/dist/knowledge/skills/application-roles-authoring/references/office-and-field-worked-example.md +22 -1
- package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +168 -3
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-assigned-rows-declaration-api.md +92 -0
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-organization-identity-declaration-api.md +247 -0
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-own-rows-declaration-api.md +66 -0
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +6 -6
- package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +6 -0
- package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +108 -2
- package/dist/knowledge/skills/backend-custom-operation/SKILL.md +81 -10
- package/dist/knowledge/skills/backend-custom-operation/references/after-the-operation.md +4 -1
- package/dist/knowledge/skills/backend-custom-operation/references/declared-refusal-codes.md +95 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-assurance-control-markers.md +3 -2
- package/dist/knowledge/skills/backend-custom-operation/references/framework-audit-log-event-api.md +5 -2
- package/dist/knowledge/skills/backend-custom-operation/references/framework-core-write-precondition-api.md +73 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-error-handling-api.md +5 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-external-effect-reservation-api.md +276 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-hook-transaction-posture-api.md +79 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-operation-base-and-path-api.md +20 -3
- package/dist/knowledge/skills/backend-custom-operation/references/framework-target-authority-api.md +61 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +368 -1
- package/dist/knowledge/skills/blueprint-authoring/SKILL.md +191 -0
- package/dist/knowledge/skills/blueprint-authoring/references/blueprint-content-kinds.md +29 -0
- package/dist/knowledge/skills/blueprint-authoring/references/framework-blueprint-definition-api.md +490 -0
- package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +127 -2
- package/dist/knowledge/skills/brand-logo-authoring/references/brand-authoring-decisions.md +15 -3
- package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-snapshot-api.md +26 -8
- package/dist/knowledge/skills/brand-logo-authoring/references/framework-style-word-lexicon-api.md +126 -0
- package/dist/knowledge/skills/brand-name-screening/SKILL.md +13 -2
- package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +30 -3
- package/dist/knowledge/skills/chat-agent-conversations/SKILL.md +166 -0
- package/dist/knowledge/skills/chat-agent-conversations/references/framework-chat-conversations-api.md +307 -0
- package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +2 -1
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +8 -6
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +179 -37
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +4 -3
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +13 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +48 -11
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +10 -1
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +896 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-disclosures.md +184 -4
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-population.md +46 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-subject-data-recipients.md +487 -61
- package/dist/knowledge/skills/config-app-shell/SKILL.md +62 -29
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +20 -18
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-building-blocks-api.md +7 -3
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-hosted-components-api.md +13 -0
- package/dist/knowledge/skills/config-app-shell/references/framework-brand-identity-api.md +20 -0
- package/dist/knowledge/skills/config-app-shell/references/framework-command-menu-omnibox-api.md +3 -3
- package/dist/knowledge/skills/config-app-shell/references/framework-launcher-items-api.md +21 -6
- package/dist/knowledge/skills/config-app-shell/references/framework-launcher-visibility-api.md +24 -22
- package/dist/knowledge/skills/config-app-shell/references/framework-shell-layout-api.md +528 -0
- package/dist/knowledge/skills/config-design-system/SKILL.md +245 -162
- package/dist/knowledge/skills/config-design-system/references/design-system-file.md +5 -1
- package/dist/knowledge/skills/config-design-system/references/framework-focus-indicator-api.md +182 -0
- package/dist/knowledge/skills/config-design-system/references/framework-palette-contrast-api.md +195 -0
- package/dist/knowledge/skills/config-design-system/references/framework-palette-derivation-api.md +108 -0
- package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +38 -0
- package/dist/knowledge/skills/config-design-system/references/framework-theme-composition-api.md +278 -0
- package/dist/knowledge/skills/config-design-system/references/theme-design-principles.md +202 -0
- package/dist/knowledge/skills/config-navigation/SKILL.md +2 -0
- package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +16 -5
- package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +1 -1
- package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +12 -1
- package/dist/knowledge/skills/config-navigation/references/one-entry-per-concept.md +101 -0
- package/dist/knowledge/skills/config-saas/SKILL.md +4 -2
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +51 -6
- package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +18 -5
- package/dist/knowledge/skills/config-saas/references/framework-auditable-event-catalog.md +333 -0
- package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +29 -1
- package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +83 -11
- package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +21 -19
- package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +26 -10
- package/dist/knowledge/skills/config-saas/references/framework-key-management-api.md +1370 -0
- package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +77 -2
- package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +171 -26
- package/dist/knowledge/skills/config-saas/references/framework-value-moments-api.md +22 -0
- package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +126 -32
- package/dist/knowledge/skills/config-saas/references/saas-config-scope.md +1 -1
- package/dist/knowledge/skills/config-saas-backend/SKILL.md +16 -4
- package/dist/knowledge/skills/config-saas-backend/references/framework-application-owner-organization-codes-api.md +9 -10
- package/dist/knowledge/skills/config-saas-backend/references/framework-backend-authored-config-api.md +5 -1
- package/dist/knowledge/skills/config-saas-backend/references/framework-declared-type-renames-api.md +261 -0
- package/dist/knowledge/skills/config-saas-backend/references/framework-federated-identity-provider-private-networks-api.md +6 -4
- package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +167 -84
- package/dist/knowledge/skills/config-saas-backend/references/renaming-organization-and-user-types.md +69 -0
- package/dist/knowledge/skills/configure-billing/SKILL.md +20 -0
- package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +38 -4
- package/dist/knowledge/skills/configure-billing/references/framework-backend-provider-reachability-api.md +2 -0
- package/dist/knowledge/skills/configure-billing/references/framework-metered-usage-recording-api.md +109 -0
- package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +4 -1
- package/dist/knowledge/skills/configure-coding-agent/references/framework-acp-execution-profile-api.md +18 -2
- package/dist/knowledge/skills/electronic-signature-deliverables/SKILL.md +131 -0
- package/dist/knowledge/skills/electronic-signature-deliverables/references/what-makes-a-request-signed.md +61 -0
- package/dist/knowledge/skills/email-add-template/SKILL.md +47 -6
- package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +11 -8
- package/dist/knowledge/skills/email-add-template/references/framework-email-send-api.md +10 -2
- package/dist/knowledge/skills/email-add-template/references/framework-email-template-api.md +134 -0
- package/dist/knowledge/skills/engine-product-definitions/references/framework-metered-usage-recording-api.md +28 -0
- package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +102 -23
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +103 -14
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +35 -4
- package/dist/knowledge/skills/flows-actors-autonomous-agents/SKILL.md +98 -9
- package/dist/knowledge/skills/flows-actors-autonomous-agents/references/binding-and-review.md +71 -16
- package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-autonomous-agent-api.md +160 -23
- package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-inbound-agents-api.md +10 -3
- package/dist/knowledge/skills/flows-actors-autonomous-agents/references/tool-posture.md +14 -2
- package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +298 -26
- package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +78 -19
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-behavior-reports-api.md +455 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-content-guardrails-api.md +446 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-operation-record-api.md +208 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-suspension-api.md +174 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-ask-person-tool-api.md +121 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-audit-agent-attribution-api.md +21 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-decision-deadlines-api.md +10 -3
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-realtime-catalog.md +69 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +695 -11
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +124 -6
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-model-spend-limits-api.md +276 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-present-records-tool-api.md +150 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-retrieval-tool-api.md +251 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +120 -16
- package/dist/knowledge/skills/flows-actors-declared-flow/SKILL.md +339 -0
- package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-flow-model-api.md +283 -0
- package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-start-flow-api.md +134 -0
- package/dist/knowledge/skills/flows-actors-declared-flow/references/step-kinds.md +16 -0
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +91 -5
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +78 -1
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-invocation-api.md +16 -3
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-operation-and-model-api.md +13 -6
- package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +5 -4
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +29 -19
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +166 -21
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-guidance-flow-api.md +1 -1
- package/dist/knowledge/skills/human-decision-notices/SKILL.md +150 -0
- package/dist/knowledge/skills/human-decision-notices/references/framework-decision-card-wording-api.md +292 -0
- package/dist/knowledge/skills/human-decision-notices/references/framework-decision-notice-handler-api.md +340 -0
- package/dist/knowledge/skills/i18n-label-generation/SKILL.md +17 -1
- package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +39 -0
- package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +1 -1
- package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +39 -0
- package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +35 -3
- package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +39 -0
- package/dist/knowledge/skills/i18n-translation-rerun/references/framework-translation-glossary-api.md +87 -0
- package/dist/knowledge/skills/inbound-channels/SKILL.md +93 -13
- package/dist/knowledge/skills/inbound-channels/references/email-channel.md +49 -4
- package/dist/knowledge/skills/inbound-channels/references/framework-inbound-channel-api.md +245 -27
- package/dist/knowledge/skills/inbound-channels/references/framework-inbound-email-api.md +8 -8
- package/dist/knowledge/skills/inbound-channels/references/framework-inbound-handler-api.md +471 -6
- package/dist/knowledge/skills/inbound-channels/references/framework-inbound-pipelines-api.md +73 -0
- package/dist/knowledge/skills/inbound-channels/references/inbound-delivery-lifecycle.md +44 -5
- package/dist/knowledge/skills/inbound-channels/references/receiving-email.md +39 -16
- package/dist/knowledge/skills/inbound-channels/references/sms-channel.md +93 -0
- package/dist/knowledge/skills/infra-environment-config/SKILL.md +226 -73
- package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +12 -14
- package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +140 -7
- package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +2 -1
- package/dist/knowledge/skills/infra-environment-config/references/framework-platform-key-management-api.md +370 -0
- package/dist/knowledge/skills/layout-2d-adoption/SKILL.md +158 -0
- package/dist/knowledge/skills/layout-2d-adoption/references/choosing-a-layout.md +43 -0
- package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-authoring-api.md +167 -0
- package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-registration-api.md +101 -0
- package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-settings-api.md +59 -0
- package/dist/knowledge/skills/layout-2d-adoption/references/framework-shell-motion-api.md +415 -0
- package/dist/knowledge/skills/layout-3d-adoption/SKILL.md +1 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-focal-plane-settings-api.md +16 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-frame-style-overrides-api.md +72 -0
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-contract-api.md +65 -32
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-registration-api.md +14 -36
- package/dist/knowledge/skills/layout-3d-adoption/references/framework-shell-building-blocks-api.md +7 -3
- package/dist/knowledge/skills/layout-3d-adoption/references/manual-adoption-and-removal.md +2 -2
- package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +12 -9
- package/dist/knowledge/skills/local-environment-bootstrap/references/derived-artifact-currency.md +7 -5
- package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +2 -2
- package/dist/knowledge/skills/local-environment-bootstrap/references/local-environment-troubleshooting.md +18 -10
- package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +7 -7
- package/dist/knowledge/skills/market-authoring-overview/references/framework-market-references-api.md +14 -1
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +33 -2
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +42 -2
- package/dist/knowledge/skills/market-generation-cli/SKILL.md +49 -7
- package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +63 -9
- package/dist/knowledge/skills/minion-authoring/examples/contained-tick.example.md +1 -1
- package/dist/knowledge/skills/minion-authoring/references/framework-minion-tick-contract.md +2 -2
- package/dist/knowledge/skills/model-cost-attribution/SKILL.md +43 -11
- package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-pricing-api.md +58 -3
- package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-summary-api.md +57 -21
- package/dist/knowledge/skills/model-cost-attribution/references/framework-work-attribution-api.md +7 -3
- package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +257 -46
- package/dist/knowledge/skills/module-companion-exports/SKILL.md +1 -0
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +30 -2
- package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +110 -1
- package/dist/knowledge/skills/module-relationships/SKILL.md +143 -119
- package/dist/knowledge/skills/module-relationships/references/framework-resource-relationship-authoring-api.md +8 -4
- package/dist/knowledge/skills/organization-relationships/SKILL.md +668 -0
- package/dist/knowledge/skills/organization-relationships/references/framework-organization-relationships-api.md +1259 -0
- package/dist/knowledge/skills/organization-relationships/references/framework-relationship-capability-grants-api.md +243 -0
- package/dist/knowledge/skills/organization-relationships/references/framework-relationship-grantor-authentication-api.md +284 -0
- package/dist/knowledge/skills/organization-relationships/references/framework-relationship-kinds-api.md +555 -0
- package/dist/knowledge/skills/organization-relationships/references/framework-relationship-record-separation-api.md +163 -0
- package/dist/knowledge/skills/organization-relationships/references/framework-representative-activity-api.md +149 -0
- package/dist/knowledge/skills/pdf-template-authoring/references/framework-pdf-collection-template-api.md +5 -3
- package/dist/knowledge/skills/professional-qualifications/SKILL.md +173 -0
- package/dist/knowledge/skills/professional-qualifications/references/choosing-who-may-decide.md +53 -0
- package/dist/knowledge/skills/professional-qualifications/references/framework-operation-approval-requirement-api.md +98 -0
- package/dist/knowledge/skills/professional-qualifications/references/framework-operation-required-qualifications-api.md +39 -0
- package/dist/knowledge/skills/professional-qualifications/references/framework-professional-qualifications-api.md +223 -0
- package/dist/knowledge/skills/provider-address-lookup/SKILL.md +1 -1
- package/dist/knowledge/skills/provider-address-lookup/references/framework-browser-operation-policy-api.md +3 -3
- package/dist/knowledge/skills/provider-backend-package/SKILL.md +388 -11
- package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +31 -28
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-augmentation-api.md +16 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-compliance-state-collector-api.md +96 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-configuration-check-api.md +130 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-file-storage-adapter-api.md +13 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-inbound-endpoint-api.md +755 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-incremental-consent-api.md +235 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-loader-api.md +6 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-processing-region-api.md +340 -0
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-shared-connection-api.md +72 -8
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-subject-erasure-effect-api.md +222 -0
- package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +9 -5
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-consent-api.md +11 -2
- package/dist/knowledge/skills/provider-frontend-module/SKILL.md +50 -5
- package/dist/knowledge/skills/provider-frontend-module/references/framework-on-demand-capabilities-api.md +306 -0
- package/dist/knowledge/skills/provider-frontend-module/references/package-frontend-facets.md +11 -3
- package/dist/knowledge/skills/provider-operation-calls/SKILL.md +41 -15
- package/dist/knowledge/skills/provider-operation-calls/references/browser-door-answers.md +56 -18
- package/dist/knowledge/skills/provider-operation-calls/references/framework-browser-operation-policy-api.md +1 -1
- package/dist/knowledge/skills/provider-operation-calls/references/framework-frontend-execute-operation-api.md +143 -25
- package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-operation-executor-api.md +6 -0
- package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-scope-reauthorization-api.md +9 -6
- package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +1275 -4
- package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +71 -35
- package/dist/knowledge/skills/rate-limit-authoring/references/framework-rate-limit-policy-api.md +27 -13
- package/dist/knowledge/skills/resource-add-field/SKILL.md +7 -0
- package/dist/knowledge/skills/resource-add-field/examples/add-priority-field-to-todos.example.md +32 -12
- package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +451 -67
- package/dist/knowledge/skills/resource-add-resource/SKILL.md +57 -8
- package/dist/knowledge/skills/resource-add-resource/references/framework-engine-api-reference-categories-api.md +119 -0
- package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +165 -44
- package/dist/knowledge/skills/resource-chat-commands/SKILL.md +138 -0
- package/dist/knowledge/skills/resource-chat-commands/references/framework-resource-chat-command-contract.md +72 -0
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +171 -7
- package/dist/knowledge/skills/resource-config-wiring/references/framework-administrative-continuity-codes-api.md +4 -4
- package/dist/knowledge/skills/resource-config-wiring/references/framework-authority-audit-interpretation.md +17 -8
- package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +8 -2
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-approval-api.md +371 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +51 -7
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-bulk-api.md +163 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-idempotency-key-api.md +66 -27
- package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +200 -61
- package/dist/knowledge/skills/resource-config-wiring/references/framework-request-field-offers-api.md +168 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-required-features-api.md +20 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-retention-policy-operations.md +8 -3
- package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +34 -10
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +8 -6
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +351 -159
- package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +160 -2
- package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +440 -119
- package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +426 -32
- package/dist/knowledge/skills/resource-config-wiring/references/framework-webhook-events-api.md +116 -0
- package/dist/knowledge/skills/resource-custom-view/SKILL.md +126 -1
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +344 -62
- package/dist/knowledge/skills/resource-custom-view/references/framework-backend-refusal-api.md +110 -0
- package/dist/knowledge/skills/resource-external-data/SKILL.md +326 -76
- package/dist/knowledge/skills/resource-external-data/references/bidirectional-pipelines.md +335 -0
- package/dist/knowledge/skills/resource-external-data/references/declared-expressions.md +18 -6
- package/dist/knowledge/skills/resource-external-data/references/erasure-suppression.md +71 -12
- package/dist/knowledge/skills/resource-external-data/references/facet-augmentations.md +6 -0
- package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +96 -26
- package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +257 -57
- package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +111 -11
- package/dist/knowledge/skills/resource-external-data/references/framework-system-of-record-capabilities-api.md +147 -0
- package/dist/knowledge/skills/resource-external-data/references/incremental-extraction.md +30 -4
- package/dist/knowledge/skills/resource-external-data/references/local-test-doubles.md +121 -0
- package/dist/knowledge/skills/resource-external-data/references/odata-v2-sources.md +21 -9
- package/dist/knowledge/skills/resource-external-data/references/outbound-pipelines.md +62 -15
- package/dist/knowledge/skills/resource-external-data/references/partition-from-the-domain-plan.md +230 -0
- package/dist/knowledge/skills/resource-external-data/references/presenting-a-copy-and-a-read-through.md +73 -0
- package/dist/knowledge/skills/resource-external-data/references/provenance-cue.md +18 -2
- package/dist/knowledge/skills/resource-external-data/references/rate-budgets-and-pacing.md +3 -1
- package/dist/knowledge/skills/resource-external-data/references/read-through-writes.md +65 -18
- package/dist/knowledge/skills/resource-external-data/references/remote-references.md +17 -7
- package/dist/knowledge/skills/resource-external-data/references/requested-keys.md +104 -0
- package/dist/knowledge/skills/resource-external-data/references/system-of-record-actions.md +77 -7
- package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +25 -4
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-resource-mcp-exposure-contract.md +2 -2
- package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-catalogue-withdrawal-and-verification.md +1 -1
- package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +18 -9
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +42 -3
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +29 -2
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-source-decorator-api.md +20 -20
- package/dist/knowledge/skills/resource-retention-binding/SKILL.md +21 -3
- package/dist/knowledge/skills/resource-retention-binding/references/framework-legal-holds-api.md +114 -7
- package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-binding-api.md +84 -1
- package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-enforcement-records-api.md +10 -0
- package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-schedule-api.md +5 -3
- package/dist/knowledge/skills/resource-retention-binding/references/framework-statutory-retention-api.md +46 -0
- package/dist/knowledge/skills/resource-retention-binding/references/start-point-decisions.md +14 -2
- package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +27 -11
- package/dist/knowledge/skills/resource-schema-authoring/examples/add-enum-field-with-ui.example.md +23 -7
- package/dist/knowledge/skills/resource-schema-authoring/references/computed-totals.md +13 -8
- package/dist/knowledge/skills/resource-schema-authoring/references/document-numbers.md +78 -17
- package/dist/knowledge/skills/resource-schema-authoring/references/field-type-selection.md +4 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +105 -6
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-erasure-scrub-treatments-api.md +19 -22
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +150 -35
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-schema-family-api.md +32 -4
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +58 -18
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +107 -5
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +200 -69
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-system-managed-fields-api.md +2 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +326 -18
- package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +7 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/special-factories.md +72 -0
- package/dist/knowledge/skills/resource-status-lifecycle/SKILL.md +42 -2
- package/dist/knowledge/skills/resource-status-lifecycle/references/framework-operation-condition-parameters-api.md +67 -0
- package/dist/knowledge/skills/resource-status-lifecycle/references/quote-lifecycle-worked-example.md +16 -12
- package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +219 -77
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-collection-filter-presets-api.md +105 -24
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +131 -1
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +41 -7
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-field-tiles-api.md +114 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +428 -72
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +25 -9
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +15 -3
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-record-page-parts-api.md +155 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-related-resource-embeds-api.md +223 -6
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +186 -65
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-section-stages-api.md +102 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/record-page-anatomy.md +138 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +89 -32
- package/dist/knowledge/skills/resource-ui-behavior/references/visual-quality-rubric.md +73 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/workflow-record-page.md +264 -0
- package/dist/knowledge/skills/seeding-authoring/SKILL.md +24 -4
- package/dist/knowledge/skills/seeding-authoring/references/cross-seed-row-references.md +12 -0
- package/dist/knowledge/skills/seeding-authoring/references/data-seeding-mode-picker.md +16 -1
- package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +7 -6
- package/dist/knowledge/skills/seeding-operations/references/data-seeding-admin-runbook.md +15 -8
- package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +3 -0
- package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +48 -11
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +183 -32
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +72 -13
- package/dist/knowledge/skills/spec-catalog-authoring/SKILL.md +5 -4
- package/dist/knowledge/skills/spec-catalog-authoring/references/catalog-spec-pattern-overview.md +5 -4
- package/dist/knowledge/skills/spec-companion-exports/SKILL.md +1 -0
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +30 -2
- package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +15 -7
- package/dist/knowledge/skills/spec-resource-update/SKILL.md +26 -0
- package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +186 -83
- package/dist/knowledge/skills/spec-resource-update/references/workflow-record-page-specification.md +237 -0
- package/dist/knowledge/skills/spec-update-after-change/references/framework-spec-factory-api.md +113 -70
- package/dist/knowledge/skills/subject-data-export/SKILL.md +176 -0
- package/dist/knowledge/skills/subject-data-export/references/file-content-exclusions.md +15 -0
- package/dist/knowledge/skills/subject-data-export/references/framework-subject-export-api.md +142 -0
- package/dist/knowledge/skills/subject-data-export/references/framework-subject-export-archive-api.md +33 -0
- package/dist/knowledge/skills/views-add-composite-view/SKILL.md +14 -5
- package/dist/knowledge/skills/views-add-custom-view/SKILL.md +10 -1
- package/dist/knowledge/skills/views-add-custom-view/references/framework-focus-indicator-api.md +145 -0
- package/dist/knowledge/skills/views-app-level/SKILL.md +3 -1
- package/dist/knowledge/skills/views-app-level/references/workflow-home.md +373 -0
- package/dist/knowledge/skills/views-chart-authoring/SKILL.md +41 -5
- package/dist/knowledge/skills/views-chart-authoring/references/framework-chart-view-contracts-api.md +13 -0
- package/dist/knowledge/skills/views-chart-authoring/references/framework-resource-chart-data-api.md +9 -5
- package/dist/knowledge/skills/views-composite-authoring/SKILL.md +15 -4
- package/dist/knowledge/skills/views-composite-authoring/references/framework-chart-dashboard-api.md +244 -0
- package/dist/knowledge/skills/views-execution-authoring/SKILL.md +11 -2
- package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +57 -3
- package/dist/knowledge/skills/website-anonymous-session/SKILL.md +61 -25
- package/dist/knowledge/skills/website-blog-authoring/SKILL.md +253 -78
- package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +1105 -222
- package/dist/knowledge/skills/website-building-blocks/SKILL.md +337 -0
- package/dist/knowledge/skills/website-building-blocks/references/framework-website-blocks-api.md +3050 -0
- package/dist/knowledge/skills/website-building-blocks/references/framework-website-demo-examples.md +627 -0
- package/dist/knowledge/skills/website-building-blocks/references/framework-website-product-kit-api.md +3309 -0
- package/dist/knowledge/skills/website-building-blocks/references/website-visual-quality-rubric.md +75 -0
- package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +42 -19
- package/dist/knowledge/skills/website-bundle-discipline/references/example-website-button-override.md +8 -12
- package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +20 -5
- package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +84 -28
- package/dist/knowledge/skills/website-factory-advanced/SKILL.md +67 -64
- package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +58 -23
- package/dist/knowledge/skills/website-inbound-contact-forms/references/framework-submission-challenge-api.md +5 -1
- package/dist/knowledge/skills/website-label-pack/SKILL.md +43 -21
- package/dist/knowledge/skills/website-layout-overrides/SKILL.md +112 -77
- package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +24 -13
- package/dist/knowledge/skills/website-motion-design/SKILL.md +277 -0
- package/dist/knowledge/skills/website-motion-design/references/framework-motion-api.md +1562 -0
- package/dist/knowledge/skills/website-motion-design/references/industry-practice.md +28 -0
- package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +255 -397
- package/dist/knowledge/skills/website-navigation-authoring/references/framework-menu-api.md +712 -0
- package/dist/knowledge/skills/website-navigation-authoring/references/framework-public-document-links-api.md +28 -6
- package/dist/knowledge/skills/website-navigation-authoring/references/menu-keys-and-styling.md +151 -0
- package/dist/knowledge/skills/website-navigation-authoring/references/worked-examples-header-footer.md +131 -326
- package/dist/knowledge/skills/website-page-authoring/SKILL.md +160 -67
- package/dist/knowledge/skills/website-page-authoring/references/framework-page-kinds-api.md +982 -0
- package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +29 -5
- package/dist/knowledge/skills/website-page-authoring/references/homepage-content-and-art-direction.md +19 -0
- package/dist/knowledge/skills/website-page-authoring/references/page-kinds.md +118 -0
- package/dist/knowledge/skills/website-page-variants/SKILL.md +70 -69
- package/dist/knowledge/skills/website-primitive-overrides/SKILL.md +48 -28
- package/dist/knowledge/skills/website-section-comparison/SKILL.md +1171 -0
- package/dist/knowledge/skills/website-section-comparison/references/define-website-section-api.md +679 -0
- package/dist/knowledge/skills/website-section-comparison/references/framework-website-tables-api.md +487 -0
- package/dist/knowledge/skills/website-section-contact/SKILL.md +409 -186
- package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +197 -119
- package/dist/knowledge/skills/website-section-cta/SKILL.md +399 -235
- package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +197 -119
- package/dist/knowledge/skills/website-section-faq/SKILL.md +562 -303
- package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +197 -119
- package/dist/knowledge/skills/website-section-faq/references/framework-website-faq-api.md +489 -0
- package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +648 -275
- package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +197 -119
- package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +573 -265
- package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +197 -119
- package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +533 -234
- package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +197 -119
- package/dist/knowledge/skills/website-section-hero/SKILL.md +604 -333
- package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +198 -120
- package/dist/knowledge/skills/website-section-how-it-works/SKILL.md +1150 -0
- package/dist/knowledge/skills/website-section-how-it-works/references/define-website-section-api.md +679 -0
- package/dist/knowledge/skills/website-section-how-it-works/references/framework-website-steps-api.md +337 -0
- package/dist/knowledge/skills/website-section-integrations/SKILL.md +974 -0
- package/dist/knowledge/skills/website-section-integrations/references/define-website-section-api.md +679 -0
- package/dist/knowledge/skills/website-section-integrations/references/framework-website-marquee-api.md +825 -0
- package/dist/knowledge/skills/website-section-latest-posts/SKILL.md +928 -0
- package/dist/knowledge/skills/website-section-latest-posts/references/define-website-section-api.md +679 -0
- package/dist/knowledge/skills/website-section-latest-posts/references/framework-website-latest-posts-api.md +465 -0
- package/dist/knowledge/skills/website-section-pricing/SKILL.md +594 -379
- package/dist/knowledge/skills/website-section-pricing/examples/pricing-offers.example.md +189 -0
- package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +197 -119
- package/dist/knowledge/skills/website-section-pricing/references/framework-pricing-catalog-api.md +5 -2
- package/dist/knowledge/skills/website-section-pricing/references/framework-website-pricing-api.md +670 -0
- package/dist/knowledge/skills/website-section-problem/SKILL.md +1150 -0
- package/dist/knowledge/skills/website-section-problem/references/define-website-section-api.md +679 -0
- package/dist/knowledge/skills/website-section-problem/references/framework-website-card-grid-api.md +664 -0
- package/dist/knowledge/skills/website-section-product-showcase/SKILL.md +1322 -0
- package/dist/knowledge/skills/website-section-product-showcase/references/define-website-section-api.md +679 -0
- package/dist/knowledge/skills/website-section-product-showcase/references/framework-website-card-grid-api.md +533 -0
- package/dist/knowledge/skills/website-section-product-showcase/references/framework-website-product-tour-api.md +917 -0
- package/dist/knowledge/skills/website-section-roadmap/SKILL.md +1133 -0
- package/dist/knowledge/skills/website-section-roadmap/references/define-website-section-api.md +679 -0
- package/dist/knowledge/skills/website-section-roadmap/references/framework-website-roadmap-api.md +475 -0
- package/dist/knowledge/skills/website-section-social-proof/SKILL.md +740 -316
- package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +197 -119
- package/dist/knowledge/skills/website-section-social-proof/references/framework-website-quote-cards-api.md +623 -0
- package/dist/knowledge/skills/website-section-solution-paths/SKILL.md +1057 -0
- package/dist/knowledge/skills/website-section-solution-paths/references/define-website-section-api.md +679 -0
- package/dist/knowledge/skills/website-section-solution-paths/references/framework-website-solution-paths-api.md +477 -0
- package/dist/knowledge/skills/website-section-stats/SKILL.md +1086 -0
- package/dist/knowledge/skills/website-section-stats/references/define-website-section-api.md +679 -0
- package/dist/knowledge/skills/website-section-stats/references/framework-website-stats-api.md +517 -0
- package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +183 -67
- package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +576 -57
- package/dist/knowledge/skills/website-seo-aeo-geo/references/geo-api.md +1 -1
- package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +6 -94
- package/dist/knowledge/skills/website-theme-authoring/SKILL.md +226 -0
- package/dist/knowledge/skills/website-theme-authoring/references/framework-website-theme-api.md +893 -0
- package/dist/knowledge/skills/worker-authoring/SKILL.md +4 -2
- package/dist/knowledge/skills/worker-authoring/references/framework-worker-init-contract.md +4 -2
- package/dist/knowledge/topic-index.json +17998 -8568
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/package.json +6 -6
- package/dist/knowledge/references/example.organizations.serves-as-provider.md +0 -12
- package/dist/knowledge/references/saas.models.auth.service-provider-client-authentication.md +0 -169
- package/dist/knowledge/references/saas.models.organizations.service-provider-activity-feed.md +0 -121
- package/dist/knowledge/references/saas.models.organizations.service-provider-client-controls.md +0 -49
- package/dist/knowledge/references/saas.models.organizations.service-provider-relationships.md +0 -567
- package/dist/knowledge/references/saas.website.root-config.navigation.md +0 -37
- package/dist/knowledge/skills/service-provider-relationships/SKILL.md +0 -455
- package/dist/knowledge/skills/service-provider-relationships/references/framework-organization-types-api.md +0 -270
- package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-activity-feed-api.md +0 -129
- package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-capability-grants-api.md +0 -161
- package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-client-authentication-api.md +0 -224
- package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-relationships-api.md +0 -576
- package/dist/tsconfig.tsbuildinfo +0 -1
|
@@ -0,0 +1,216 @@
|
|
|
1
|
+
# Service Method — How the Firm Works
|
|
2
|
+
|
|
3
|
+
### Target Application Framing
|
|
4
|
+
|
|
5
|
+
This knowledge is for configuring behavior in the target application.
|
|
6
|
+
Wildo is the framework surface being used, not the product being built.
|
|
7
|
+
|
|
8
|
+
Read and apply these patterns from the application-developer point of view:
|
|
9
|
+
|
|
10
|
+
- how the application should configure the relevant app-level file
|
|
11
|
+
- how the application should use framework-provided factories, enums, and helpers
|
|
12
|
+
- how the application should avoid mixing frontend, backend, and infrastructure concerns
|
|
13
|
+
|
|
14
|
+
|
|
15
|
+
## What this playbook does
|
|
16
|
+
|
|
17
|
+
You are writing down the firm's **method**: the services it sells to its clients and, for each, how a
|
|
18
|
+
case is worked. The output is one `ServiceMethod`. It is the one place the method is written down; the
|
|
19
|
+
domain plan, the roles and the build plan derive from it, so a method that is vague here is an
|
|
20
|
+
application that is vague everywhere.
|
|
21
|
+
|
|
22
|
+
A firm is not a product its users drive alone. A case is opened for a client, agents and the firm's
|
|
23
|
+
people work it, a qualified person takes the decisions that carry the firm's responsibility, and the
|
|
24
|
+
client receives something at the end. Write that down, case by case.
|
|
25
|
+
|
|
26
|
+
## What the creator decides, and what you draft
|
|
27
|
+
|
|
28
|
+
The interview has four questions:
|
|
29
|
+
|
|
30
|
+
- **`services`** — what the firm sells, what starts a case and what ends it.
|
|
31
|
+
- **`signatories`** — which decisions only a qualified person may take, and what that person must be.
|
|
32
|
+
- **`agent-work`** — which work in a case the creator wants agents to do.
|
|
33
|
+
- **`working-hours`** — where and when the firm's reviewers work.
|
|
34
|
+
|
|
35
|
+
An answer the creator gave is theirs: build on it, do not second-guess it. An answer recorded as an
|
|
36
|
+
ASSUMPTION (proposed, because the creator did not know or chose a quick interview) is a proposal: use it,
|
|
37
|
+
and keep anything resting on it easy to revise. `agent-work` and `working-hours` are usually assumptions.
|
|
38
|
+
|
|
39
|
+
Everything else you DRAFT from those answers, the vision and the market: the stages, the steps, the
|
|
40
|
+
deliverables, the evidence retention, the correction reasons. Draft them so the creator can accept them
|
|
41
|
+
as they are; they will review them.
|
|
42
|
+
|
|
43
|
+
If an answer says "propose it", the creator delegated that part: propose it from the services. If the
|
|
44
|
+
interview says "none", write none — an empty list is an answer.
|
|
45
|
+
|
|
46
|
+
An answer left **NOT DECIDED YET** is not "none", and the method must not read as if it were. Say it is
|
|
47
|
+
owed in `owed`:
|
|
48
|
+
|
|
49
|
+
- `signatories` not decided yet → `owed` includes `QUALIFIED_DECISIONS`. Write only the decisions and
|
|
50
|
+
qualifications the creator's other answers name; never invent a qualified decision to fill the gap.
|
|
51
|
+
- `agent-work` not decided yet → `owed` includes `AGENT_WORK`. A step the client does still names
|
|
52
|
+
`CLIENT`; a step of the firm's work whose performer waits on that answer names **no** `performedBy` and
|
|
53
|
+
no `agentShape`. Never decide for the creator which work an agent does.
|
|
54
|
+
|
|
55
|
+
`owed` is empty when every answer was given.
|
|
56
|
+
|
|
57
|
+
## Step 1 — One service per thing the firm sells
|
|
58
|
+
|
|
59
|
+
Each service is one entry in `services`:
|
|
60
|
+
|
|
61
|
+
- `serviceRef` — a kebab-case key (`month-end-close`, `annual-audit`). Later families name it.
|
|
62
|
+
- `label` — what the firm calls it.
|
|
63
|
+
- `purpose` — what the CLIENT gets, in one sentence. Not what the firm does: "the client's books closed
|
|
64
|
+
every month, reconciled and signed off", not "we reconcile bank lines".
|
|
65
|
+
|
|
66
|
+
Two services the creator described as one are one service. Do not split a service to look thorough.
|
|
67
|
+
|
|
68
|
+
## Step 2 — The case, and its stages
|
|
69
|
+
|
|
70
|
+
`case` is the unit of work a service is delivered in: one close, one audit engagement, one filing.
|
|
71
|
+
|
|
72
|
+
- `caseRef` — the PLANNED RESOURCE whose rows are the cases, in the domain plan's naming (plural,
|
|
73
|
+
kebab-case: `closes`, `audit-engagements`). The domain plan inventories it and the build plan makes it
|
|
74
|
+
the work unit, the record every model call on the case is costed to.
|
|
75
|
+
- `opensWhen` / `closesWhen` — the events, in the creator's words.
|
|
76
|
+
|
|
77
|
+
`stages` are the states a case moves through, in order, first stage first. Each has a `meaning`: what is
|
|
78
|
+
true of a case in that stage. Include the stage a case returns to when something surfaces after it was
|
|
79
|
+
finished ("reopened") when the creator's work has one. Stage refs are kebab-case and unique within the
|
|
80
|
+
service.
|
|
81
|
+
|
|
82
|
+
## Step 3 — The steps, and who carries each one
|
|
83
|
+
|
|
84
|
+
Each step happens in one stage and is performed by exactly one of (or, while `AGENT_WORK` is owed, by
|
|
85
|
+
none yet):
|
|
86
|
+
|
|
87
|
+
| `performedBy` | means |
|
|
88
|
+
|---|---|
|
|
89
|
+
| `AGENT` | an agent of the application does it. Say how it runs in `agentShape` |
|
|
90
|
+
| `PERSON` | one of the firm's people does it |
|
|
91
|
+
| `CLIENT` | the client does it (sends documents, answers a question) |
|
|
92
|
+
|
|
93
|
+
An agent step names its `agentShape`, and no other step does:
|
|
94
|
+
|
|
95
|
+
- `AUTONOMOUS` — it runs on its own, on a schedule or an event (reconciling every night, reading every
|
|
96
|
+
document that arrives);
|
|
97
|
+
- `CHAT_ASSISTANT` — a person talks to it and it proposes;
|
|
98
|
+
- `INVOKED` — another part of the application calls it;
|
|
99
|
+
- `FLOW_STEP` — it is one step of a declared flow the application runs.
|
|
100
|
+
|
|
101
|
+
Give work to an agent where it relieves the firm's people of reading, matching and drafting. **Never
|
|
102
|
+
give an agent a decision a qualified person must take**: an agent proposes, and the decision point in
|
|
103
|
+
Step 4 is where the person decides.
|
|
104
|
+
|
|
105
|
+
`readsRefs` and `producesRefs` name the planned resources a step reads and writes, in the domain plan's
|
|
106
|
+
naming. They are what lets the domain plan know a step needs a resource. Leave them empty rather than
|
|
107
|
+
inventing a resource no requirement implies.
|
|
108
|
+
|
|
109
|
+
## Step 4 — The decision points: who decides, on what ground, by when
|
|
110
|
+
|
|
111
|
+
A decision point is where the case waits for a person. Each sits at one step (`stepRef`) and says in
|
|
112
|
+
`decides` what is decided. Then three choices, and they are the heart of this artifact.
|
|
113
|
+
|
|
114
|
+
**Who decides (`route`):**
|
|
115
|
+
|
|
116
|
+
| `route` | when |
|
|
117
|
+
|---|---|
|
|
118
|
+
| `owner` | the person whose own work raised it confirms it (accepting what an assistant proposed to them). Nobody vets the owner, so it takes no qualification |
|
|
119
|
+
| `role` | anyone holding a role may decide (any qualified accountant serving the client) |
|
|
120
|
+
| `assignee` | one named person decides (the client's engagement partner). Say who in `assignee`, in the firm's words |
|
|
121
|
+
|
|
122
|
+
**On what ground (`qualificationRef`):** every `role` and `assignee` decision names a qualification from
|
|
123
|
+
`qualifications`, and an `owner` decision names none. A qualification says:
|
|
124
|
+
|
|
125
|
+
- `role` — the role the person holds for the client, as the role table keys it
|
|
126
|
+
(`ORG_QUALIFIED_ACCOUNTANT`). It says what the client ENTRUSTED the firm with.
|
|
127
|
+
- `heldBy` — whose people hold that role: `FIRM` when the firm's people take the decision for the client
|
|
128
|
+
(almost always: the qualified accountant, the engagement partner), `CLIENT` when the client's own staff
|
|
129
|
+
take it in their organization (the client's finance director approving a deliverable). A firm-held role
|
|
130
|
+
reaches the firm's people through the relationship the firm serves its clients through, so the build
|
|
131
|
+
confers it there; `ORG_REPRESENTATIVE` is conferred by that relationship already. A role is always one
|
|
132
|
+
a member of an organization holds: never an application role (`APP_…`), and a firm-held role is never
|
|
133
|
+
the client's administration (`ORG_OWNER`, `ORG_ADMIN`), which no relationship may confer.
|
|
134
|
+
- `professionalQualificationKind` — set ONLY when the PERSON must also hold a verified professional
|
|
135
|
+
qualification (a chartered accountant, a licensed engineer). It follows the person, and lapses with
|
|
136
|
+
their licence. The value is a kebab-case kind (`chartered-accountant`) the application declares in its
|
|
137
|
+
`professionalQualificationKinds`; name the kind you need, and the build declares it.
|
|
138
|
+
|
|
139
|
+
Use the creator's `signatories` answer to choose. A decision the creator tied to a profession ("a
|
|
140
|
+
chartered accountant") needs both the role and the professional qualification. A decision tied to a
|
|
141
|
+
position ("the engagement partner") is an `assignee` decision with the role. A review any expert serving
|
|
142
|
+
the client may do is a `role` decision whose qualification names the role alone. Most decisions need
|
|
143
|
+
only a role; the professional-qualifications skill shown to you explains the mechanisms and how they
|
|
144
|
+
combine.
|
|
145
|
+
|
|
146
|
+
**By when (`decisionDeadline`):** a review that keeps a client waiting says when it is due, as an
|
|
147
|
+
ISO-8601 duration (`PT9H`, `P2D`) counted on `basis`: `calendar` (the firm's working hours) or `elapsed`
|
|
148
|
+
(around the clock). A business-time deadline needs `reviewCalendar`, built from the `working-hours`
|
|
149
|
+
answer: the `timeZone` (an IANA name), the `workingDays`, the `workingHours` (`HH:MM` from and to) and
|
|
150
|
+
the `holidays` as dates (`YYYY-MM-DD`). When the creator names a calendar ("French public holidays"),
|
|
151
|
+
write out its dates for the current and next year. A decision with no deadline is allowed, and it is marked:
|
|
152
|
+
the engine's default lapse and reminders apply.
|
|
153
|
+
|
|
154
|
+
When `working-hours` is NOT DECIDED YET, write no `reviewCalendar` and never invent one: give each deadline on
|
|
155
|
+
`elapsed` time, or leave it out. A business-time deadline needs the calendar the creator has not given, and the
|
|
156
|
+
method is refused with one.
|
|
157
|
+
|
|
158
|
+
## Step 5 — What the client receives, what is kept, and what it costs
|
|
159
|
+
|
|
160
|
+
- `deliverables` — what a case produces for the client, at which stage, from which planned resource
|
|
161
|
+
(`fromResourceRef`). A close report, an audit opinion, a filed return.
|
|
162
|
+
- `evidenceRetention` — how long the case's evidence is kept: a `retentionClass` and its `ground`.
|
|
163
|
+
Records the law requires the firm to keep (accounting documents, working papers) are
|
|
164
|
+
`BUSINESS_RECORDS`; say the ground in plain words and name the jurisdiction the vision gives. You
|
|
165
|
+
state the firm's obligation as you understand it; the compliance lane governs the retention period.
|
|
166
|
+
- `pricing` — `PER_CASE` when each case is billed, `INCLUDED_IN_PLAN` when a subscription covers it,
|
|
167
|
+
`BILLED_OUTSIDE` when the firm bills from its own tools. Read it off the business model when one is on
|
|
168
|
+
record: a plan priced `per_usage` whose `usageUnit` is this service's case ("close") makes the service
|
|
169
|
+
`PER_CASE`; a subscription plan that covers the service makes it `INCLUDED_IN_PLAN`. With no business
|
|
170
|
+
model, `BILLED_OUTSIDE`, which commits the application to nothing. A service `PER_CASE` is billed one
|
|
171
|
+
metered unit when its case closes, once per case however often it is reopened; the build records it.
|
|
172
|
+
An internal tool has no billing at all, whatever a business model or a feature line brings: price
|
|
173
|
+
every service `BILLED_OUTSIDE` there. The coherence report names a price per case on such an
|
|
174
|
+
application as the method's gap, and no build can record it.
|
|
175
|
+
|
|
176
|
+
## Step 6 — How the client takes part, and why a person corrects an agent
|
|
177
|
+
|
|
178
|
+
- `clientParticipation` — one paragraph: what the client provides, what they answer, what they read.
|
|
179
|
+
- `correctionReasons` — when agents do work a person reviews, the short list of reasons a person gives
|
|
180
|
+
for correcting it (`wrong_account`, `missing_evidence`). Each `reasonCode` is lowercase snake_case.
|
|
181
|
+
They let the firm see why agent work is corrected. Five to eight reasons, specific to the work.
|
|
182
|
+
|
|
183
|
+
## Refine, don't re-author
|
|
184
|
+
|
|
185
|
+
When a method is already on record, refine it. Keep every ref that still names the same thing, because
|
|
186
|
+
later families name them; change the content, not the identity.
|
|
187
|
+
|
|
188
|
+
## What you emit
|
|
189
|
+
|
|
190
|
+
One `ServiceMethod`. The schema refuses:
|
|
191
|
+
|
|
192
|
+
- a step in a stage the service does not declare, and a deliverable at one;
|
|
193
|
+
- an agent step without an `agentShape`, and any other step with one;
|
|
194
|
+
- a step with no `performedBy` when `owed` does not include `AGENT_WORK`;
|
|
195
|
+
- a decision at a step the service does not declare;
|
|
196
|
+
- an `owner` decision naming a qualification, a `role` or `assignee` decision naming none, and a
|
|
197
|
+
qualification the method does not declare;
|
|
198
|
+
- one resource kept in two retention classes, because two services name it as their evidence;
|
|
199
|
+
- an `assignee` decision with no `assignee`, and an `assignee` on any other decision;
|
|
200
|
+
- a business-time deadline with no `reviewCalendar`, and a deadline that is not a positive duration
|
|
201
|
+
in weeks, days, hours, minutes or seconds (`PT8H`, `P2D`; no years or months);
|
|
202
|
+
- a qualification on a role no member of an organization holds (an application role, an inbound
|
|
203
|
+
handler's, a capability lent through a relationship), and a firm-held one on `ORG_OWNER` or `ORG_ADMIN`;
|
|
204
|
+
- any ref declared twice.
|
|
205
|
+
|
|
206
|
+
Fix the cause it names and answer again.
|
|
207
|
+
|
|
208
|
+
## Verification
|
|
209
|
+
|
|
210
|
+
- Every service's `purpose` says what the client gets.
|
|
211
|
+
- Every decision the `signatories` answer named is a decision point, with the role, and the professional
|
|
212
|
+
qualification when the answer named a profession.
|
|
213
|
+
- Every answer left not decided yet is in `owed`, and nothing it would have decided was invented.
|
|
214
|
+
- No agent step decides anything a decision point decides.
|
|
215
|
+
- Every `role` and `assignee` decision names a declared qualification; every qualification is used.
|
|
216
|
+
- Every reviewer decision that keeps a client waiting has a deadline, or the creator said it has none.
|
|
@@ -0,0 +1,108 @@
|
|
|
1
|
+
{
|
|
2
|
+
"ref": "top_down.service-method",
|
|
3
|
+
"version": "0.1.3",
|
|
4
|
+
"phase": "top_down",
|
|
5
|
+
"intent": "Write down how the firm works: the services it sells to its clients and, for each, the case it is worked in — the stages a case moves through, the steps an agent, a person of the firm or the client takes, the decisions only a qualified person may take (who decides, which qualification they need, how long the client waits), what the client receives, how long the evidence is kept and how the service is priced. The creator names the services and the decisions a licensed professional must take; everything else is DRAFTED from those answers, the vision and the market, with the agent work proposed where it relieves the firm's people and never where a decision belongs to them. Produces one ServiceMethod. It is the one place the method is written down: the domain plan, the roles and the build plan derive from it.",
|
|
6
|
+
"preconditions": [
|
|
7
|
+
{
|
|
8
|
+
"kind": "artifact_valid",
|
|
9
|
+
"selector": {
|
|
10
|
+
"family": "vision-brief"
|
|
11
|
+
}
|
|
12
|
+
}
|
|
13
|
+
],
|
|
14
|
+
"inputs": [
|
|
15
|
+
{
|
|
16
|
+
"family": "vision-brief"
|
|
17
|
+
},
|
|
18
|
+
{
|
|
19
|
+
"family": "market-snapshot",
|
|
20
|
+
"intent": "audience"
|
|
21
|
+
},
|
|
22
|
+
{
|
|
23
|
+
"family": "requirements",
|
|
24
|
+
"render": "map"
|
|
25
|
+
},
|
|
26
|
+
{
|
|
27
|
+
"family": "business-model"
|
|
28
|
+
},
|
|
29
|
+
{
|
|
30
|
+
"family": "service-method"
|
|
31
|
+
}
|
|
32
|
+
],
|
|
33
|
+
"outputs": [
|
|
34
|
+
{
|
|
35
|
+
"family": "service-method",
|
|
36
|
+
"schemaRef": "saas-specifications:ServiceMethod",
|
|
37
|
+
"description": "The firm's services and, for each, its case, stages, steps (agent, person or client), decision points (route, qualification, deadline), deliverables, evidence retention and pricing; with the qualifications the decisions need, how the client takes part, the review calendar deadlines are counted on, and the reasons a person gives when correcting an agent."
|
|
38
|
+
}
|
|
39
|
+
],
|
|
40
|
+
"stepOutputs": [],
|
|
41
|
+
"method": {
|
|
42
|
+
"guidance": "# Service Method — How the Firm Works\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## What this playbook does\n\nYou are writing down the firm's **method**: the services it sells to its clients and, for each, how a\ncase is worked. The output is one `ServiceMethod`. It is the one place the method is written down; the\ndomain plan, the roles and the build plan derive from it, so a method that is vague here is an\napplication that is vague everywhere.\n\nA firm is not a product its users drive alone. A case is opened for a client, agents and the firm's\npeople work it, a qualified person takes the decisions that carry the firm's responsibility, and the\nclient receives something at the end. Write that down, case by case.\n\n## What the creator decides, and what you draft\n\nThe interview has four questions:\n\n- **`services`** — what the firm sells, what starts a case and what ends it.\n- **`signatories`** — which decisions only a qualified person may take, and what that person must be.\n- **`agent-work`** — which work in a case the creator wants agents to do.\n- **`working-hours`** — where and when the firm's reviewers work.\n\nAn answer the creator gave is theirs: build on it, do not second-guess it. An answer recorded as an\nASSUMPTION (proposed, because the creator did not know or chose a quick interview) is a proposal: use it,\nand keep anything resting on it easy to revise. `agent-work` and `working-hours` are usually assumptions.\n\nEverything else you DRAFT from those answers, the vision and the market: the stages, the steps, the\ndeliverables, the evidence retention, the correction reasons. Draft them so the creator can accept them\nas they are; they will review them.\n\nIf an answer says \"propose it\", the creator delegated that part: propose it from the services. If the\ninterview says \"none\", write none — an empty list is an answer.\n\nAn answer left **NOT DECIDED YET** is not \"none\", and the method must not read as if it were. Say it is\nowed in `owed`:\n\n- `signatories` not decided yet → `owed` includes `QUALIFIED_DECISIONS`. Write only the decisions and\n qualifications the creator's other answers name; never invent a qualified decision to fill the gap.\n- `agent-work` not decided yet → `owed` includes `AGENT_WORK`. A step the client does still names\n `CLIENT`; a step of the firm's work whose performer waits on that answer names **no** `performedBy` and\n no `agentShape`. Never decide for the creator which work an agent does.\n\n`owed` is empty when every answer was given.\n\n## Step 1 — One service per thing the firm sells\n\nEach service is one entry in `services`:\n\n- `serviceRef` — a kebab-case key (`month-end-close`, `annual-audit`). Later families name it.\n- `label` — what the firm calls it.\n- `purpose` — what the CLIENT gets, in one sentence. Not what the firm does: \"the client's books closed\n every month, reconciled and signed off\", not \"we reconcile bank lines\".\n\nTwo services the creator described as one are one service. Do not split a service to look thorough.\n\n## Step 2 — The case, and its stages\n\n`case` is the unit of work a service is delivered in: one close, one audit engagement, one filing.\n\n- `caseRef` — the PLANNED RESOURCE whose rows are the cases, in the domain plan's naming (plural,\n kebab-case: `closes`, `audit-engagements`). The domain plan inventories it and the build plan makes it\n the work unit, the record every model call on the case is costed to.\n- `opensWhen` / `closesWhen` — the events, in the creator's words.\n\n`stages` are the states a case moves through, in order, first stage first. Each has a `meaning`: what is\ntrue of a case in that stage. Include the stage a case returns to when something surfaces after it was\nfinished (\"reopened\") when the creator's work has one. Stage refs are kebab-case and unique within the\nservice.\n\n## Step 3 — The steps, and who carries each one\n\nEach step happens in one stage and is performed by exactly one of (or, while `AGENT_WORK` is owed, by\nnone yet):\n\n| `performedBy` | means |\n|---|---|\n| `AGENT` | an agent of the application does it. Say how it runs in `agentShape` |\n| `PERSON` | one of the firm's people does it |\n| `CLIENT` | the client does it (sends documents, answers a question) |\n\nAn agent step names its `agentShape`, and no other step does:\n\n- `AUTONOMOUS` — it runs on its own, on a schedule or an event (reconciling every night, reading every\n document that arrives);\n- `CHAT_ASSISTANT` — a person talks to it and it proposes;\n- `INVOKED` — another part of the application calls it;\n- `FLOW_STEP` — it is one step of a declared flow the application runs.\n\nGive work to an agent where it relieves the firm's people of reading, matching and drafting. **Never\ngive an agent a decision a qualified person must take**: an agent proposes, and the decision point in\nStep 4 is where the person decides.\n\n`readsRefs` and `producesRefs` name the planned resources a step reads and writes, in the domain plan's\nnaming. They are what lets the domain plan know a step needs a resource. Leave them empty rather than\ninventing a resource no requirement implies.\n\n## Step 4 — The decision points: who decides, on what ground, by when\n\nA decision point is where the case waits for a person. Each sits at one step (`stepRef`) and says in\n`decides` what is decided. Then three choices, and they are the heart of this artifact.\n\n**Who decides (`route`):**\n\n| `route` | when |\n|---|---|\n| `owner` | the person whose own work raised it confirms it (accepting what an assistant proposed to them). Nobody vets the owner, so it takes no qualification |\n| `role` | anyone holding a role may decide (any qualified accountant serving the client) |\n| `assignee` | one named person decides (the client's engagement partner). Say who in `assignee`, in the firm's words |\n\n**On what ground (`qualificationRef`):** every `role` and `assignee` decision names a qualification from\n`qualifications`, and an `owner` decision names none. A qualification says:\n\n- `role` — the role the person holds for the client, as the role table keys it\n (`ORG_QUALIFIED_ACCOUNTANT`). It says what the client ENTRUSTED the firm with.\n- `heldBy` — whose people hold that role: `FIRM` when the firm's people take the decision for the client\n (almost always: the qualified accountant, the engagement partner), `CLIENT` when the client's own staff\n take it in their organization (the client's finance director approving a deliverable). A firm-held role\n reaches the firm's people through the relationship the firm serves its clients through, so the build\n confers it there; `ORG_REPRESENTATIVE` is conferred by that relationship already. A role is always one\n a member of an organization holds: never an application role (`APP_…`), and a firm-held role is never\n the client's administration (`ORG_OWNER`, `ORG_ADMIN`), which no relationship may confer.\n- `professionalQualificationKind` — set ONLY when the PERSON must also hold a verified professional\n qualification (a chartered accountant, a licensed engineer). It follows the person, and lapses with\n their licence. The value is a kebab-case kind (`chartered-accountant`) the application declares in its\n `professionalQualificationKinds`; name the kind you need, and the build declares it.\n\nUse the creator's `signatories` answer to choose. A decision the creator tied to a profession (\"a\nchartered accountant\") needs both the role and the professional qualification. A decision tied to a\nposition (\"the engagement partner\") is an `assignee` decision with the role. A review any expert serving\nthe client may do is a `role` decision whose qualification names the role alone. Most decisions need\nonly a role; the professional-qualifications skill shown to you explains the mechanisms and how they\ncombine.\n\n**By when (`decisionDeadline`):** a review that keeps a client waiting says when it is due, as an\nISO-8601 duration (`PT9H`, `P2D`) counted on `basis`: `calendar` (the firm's working hours) or `elapsed`\n(around the clock). A business-time deadline needs `reviewCalendar`, built from the `working-hours`\nanswer: the `timeZone` (an IANA name), the `workingDays`, the `workingHours` (`HH:MM` from and to) and\nthe `holidays` as dates (`YYYY-MM-DD`). When the creator names a calendar (\"French public holidays\"),\nwrite out its dates for the current and next year. A decision with no deadline is allowed, and it is marked:\nthe engine's default lapse and reminders apply.\n\nWhen `working-hours` is NOT DECIDED YET, write no `reviewCalendar` and never invent one: give each deadline on\n`elapsed` time, or leave it out. A business-time deadline needs the calendar the creator has not given, and the\nmethod is refused with one.\n\n## Step 5 — What the client receives, what is kept, and what it costs\n\n- `deliverables` — what a case produces for the client, at which stage, from which planned resource\n (`fromResourceRef`). A close report, an audit opinion, a filed return.\n- `evidenceRetention` — how long the case's evidence is kept: a `retentionClass` and its `ground`.\n Records the law requires the firm to keep (accounting documents, working papers) are\n `BUSINESS_RECORDS`; say the ground in plain words and name the jurisdiction the vision gives. You\n state the firm's obligation as you understand it; the compliance lane governs the retention period.\n- `pricing` — `PER_CASE` when each case is billed, `INCLUDED_IN_PLAN` when a subscription covers it,\n `BILLED_OUTSIDE` when the firm bills from its own tools. Read it off the business model when one is on\n record: a plan priced `per_usage` whose `usageUnit` is this service's case (\"close\") makes the service\n `PER_CASE`; a subscription plan that covers the service makes it `INCLUDED_IN_PLAN`. With no business\n model, `BILLED_OUTSIDE`, which commits the application to nothing. A service `PER_CASE` is billed one\n metered unit when its case closes, once per case however often it is reopened; the build records it.\n An internal tool has no billing at all, whatever a business model or a feature line brings: price\n every service `BILLED_OUTSIDE` there. The coherence report names a price per case on such an\n application as the method's gap, and no build can record it.\n\n## Step 6 — How the client takes part, and why a person corrects an agent\n\n- `clientParticipation` — one paragraph: what the client provides, what they answer, what they read.\n- `correctionReasons` — when agents do work a person reviews, the short list of reasons a person gives\n for correcting it (`wrong_account`, `missing_evidence`). Each `reasonCode` is lowercase snake_case.\n They let the firm see why agent work is corrected. Five to eight reasons, specific to the work.\n\n## Refine, don't re-author\n\nWhen a method is already on record, refine it. Keep every ref that still names the same thing, because\nlater families name them; change the content, not the identity.\n\n## What you emit\n\nOne `ServiceMethod`. The schema refuses:\n\n- a step in a stage the service does not declare, and a deliverable at one;\n- an agent step without an `agentShape`, and any other step with one;\n- a step with no `performedBy` when `owed` does not include `AGENT_WORK`;\n- a decision at a step the service does not declare;\n- an `owner` decision naming a qualification, a `role` or `assignee` decision naming none, and a\n qualification the method does not declare;\n- one resource kept in two retention classes, because two services name it as their evidence;\n- an `assignee` decision with no `assignee`, and an `assignee` on any other decision;\n- a business-time deadline with no `reviewCalendar`, and a deadline that is not a positive duration\n in weeks, days, hours, minutes or seconds (`PT8H`, `P2D`; no years or months);\n- a qualification on a role no member of an organization holds (an application role, an inbound\n handler's, a capability lent through a relationship), and a firm-held one on `ORG_OWNER` or `ORG_ADMIN`;\n- any ref declared twice.\n\nFix the cause it names and answer again.\n\n## Verification\n\n- Every service's `purpose` says what the client gets.\n- Every decision the `signatories` answer named is a decision point, with the role, and the professional\n qualification when the answer named a profession.\n- Every answer left not decided yet is in `owed`, and nothing it would have decided was invented.\n- No agent step decides anything a decision point decides.\n- Every `role` and `assignee` decision names a declared qualification; every qualification is used.\n- Every reviewer decision that keeps a client waiting has a deadline, or the creator said it has none.\n",
|
|
43
|
+
"skillRefs": [
|
|
44
|
+
"professional-qualifications",
|
|
45
|
+
"flows-actors-autonomous-agents",
|
|
46
|
+
"flows-actors-chat-assistant",
|
|
47
|
+
"agent-work-review",
|
|
48
|
+
"organization-relationships",
|
|
49
|
+
"application-roles-authoring",
|
|
50
|
+
"resource-retention-binding"
|
|
51
|
+
],
|
|
52
|
+
"skillBodyRefs": [
|
|
53
|
+
"professional-qualifications"
|
|
54
|
+
],
|
|
55
|
+
"elicitation": {
|
|
56
|
+
"questions": [
|
|
57
|
+
{
|
|
58
|
+
"ref": "services",
|
|
59
|
+
"question": "What services does the firm deliver to its clients? For each, say what the client gets, what starts a case and what ends it — \"a monthly close: it starts on the first business day, it ends when the partner signs the period off\".",
|
|
60
|
+
"kind": "free_text",
|
|
61
|
+
"depth": "essential"
|
|
62
|
+
},
|
|
63
|
+
{
|
|
64
|
+
"ref": "signatories",
|
|
65
|
+
"question": "Which decisions in a case must a qualified person of the firm take, and what must they be? Name the decision and the role or professional qualification (\"posting to the client's books: a chartered accountant\"; \"signing the period off: the client's engagement partner\"). Answer \"none\" if no decision needs a qualified person.",
|
|
66
|
+
"kind": "free_text",
|
|
67
|
+
"depth": "essential",
|
|
68
|
+
"regulatedDomain": true,
|
|
69
|
+
"nonAnswers": [
|
|
70
|
+
"not_applicable",
|
|
71
|
+
"deferred"
|
|
72
|
+
]
|
|
73
|
+
},
|
|
74
|
+
{
|
|
75
|
+
"ref": "agent-work",
|
|
76
|
+
"question": "Which work in a case would you like agents to do for the firm's people — reading documents, reconciling, drafting, answering the client? Answer \"propose it\" to have it proposed from the services, or \"none\".",
|
|
77
|
+
"kind": "free_text",
|
|
78
|
+
"depth": "detail",
|
|
79
|
+
"nonAnswers": [
|
|
80
|
+
"not_applicable",
|
|
81
|
+
"deferred"
|
|
82
|
+
]
|
|
83
|
+
},
|
|
84
|
+
{
|
|
85
|
+
"ref": "working-hours",
|
|
86
|
+
"question": "Where do the firm's reviewers work, and when? Give the time zone and the working hours (\"Europe/Paris, 9:00 to 18:00, French public holidays\"). Deadlines on a decision are counted in these hours.",
|
|
87
|
+
"kind": "free_text",
|
|
88
|
+
"depth": "detail",
|
|
89
|
+
"nonAnswers": [
|
|
90
|
+
"deferred"
|
|
91
|
+
]
|
|
92
|
+
}
|
|
93
|
+
]
|
|
94
|
+
},
|
|
95
|
+
"derivedFromAnswers": [],
|
|
96
|
+
"contextSources": [],
|
|
97
|
+
"draftableDocumentDefinitionRefs": [],
|
|
98
|
+
"suspendsForClarification": false,
|
|
99
|
+
"briefAdequacyGate": false,
|
|
100
|
+
"briefAdequacyExcludedSources": []
|
|
101
|
+
},
|
|
102
|
+
"executor": "companion_agent",
|
|
103
|
+
"approval": "approve_result",
|
|
104
|
+
"budget": {
|
|
105
|
+
"maxRuns": 5
|
|
106
|
+
},
|
|
107
|
+
"onFailure": "keep_and_flag"
|
|
108
|
+
}
|
|
@@ -122,8 +122,11 @@ Then sharpen:
|
|
|
122
122
|
Dropping an ICP, pain, gain, job, or benefit that a positioning, pillar, or
|
|
123
123
|
benefit still points at orphans the downstream ref (the validator catches
|
|
124
124
|
this as `ORPHAN_REF`, but honest refinement should not create the orphan).
|
|
125
|
-
|
|
126
|
-
|
|
125
|
+
Only your slices land (the benefits, the tones of voice and the positionings,
|
|
126
|
+
#3403): an edit to any other part of the snapshot is replaced by its current
|
|
127
|
+
value. If a slice from the market pass is genuinely wrong, say so in your
|
|
128
|
+
rationale for the snapshot's producer to correct; do not paper over it in the
|
|
129
|
+
value-prop layer.
|
|
127
130
|
|
|
128
131
|
## Quality gate
|
|
129
132
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"ref": "top_down.value-proposition",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.2.0",
|
|
4
4
|
"phase": "top_down",
|
|
5
5
|
"intent": "Top-down value-proposition / positioning: sharpen the product's value proposition on an EXISTING MarketSnapshot — the weighted benefits (relieves/creates/advances edges, Kano category per ICP), the tones of voice, and the per-ICP positioning pillars — framed by the product VisionSnapshot's differentiation. Runs after market-analysis (which produced the broad snapshot) and refines the same market-snapshot artifact; it does NOT create a new family (benefits, tone-of-voice, and positioning all live inside MarketSnapshot). Emits the refined MarketSnapshot validated by validateMarketSnapshot, consumed downstream by capability-map (benefits -> deliveredByFeatureRefs) and the refinement/coverage playbooks. v1 scaffold methodology — the FIT/Kano scoring precision and positioning rigor are iterated in a later depth phase, not here.",
|
|
6
6
|
"preconditions": [
|
|
@@ -23,12 +23,17 @@
|
|
|
23
23
|
{
|
|
24
24
|
"family": "market-snapshot",
|
|
25
25
|
"schemaRef": "saas-specifications:MarketSnapshot",
|
|
26
|
-
"description": "The SAME MarketSnapshot, refined so its value-proposition slices are sharp: benefits with weighted relieves/creates/advances edges and per-ICP Kano categories, the tones of voice, and one positioning pillar per targeted ICP. Validated by validateMarketSnapshot; feeds capability-map and refinement."
|
|
26
|
+
"description": "The SAME MarketSnapshot, refined so its value-proposition slices are sharp: benefits with weighted relieves/creates/advances edges and per-ICP Kano categories, the tones of voice, and one positioning pillar per targeted ICP. Validated by validateMarketSnapshot; feeds capability-map and refinement.",
|
|
27
|
+
"aspects": [
|
|
28
|
+
"market.benefit",
|
|
29
|
+
"market.tone-of-voice",
|
|
30
|
+
"market.positioning"
|
|
31
|
+
]
|
|
27
32
|
}
|
|
28
33
|
],
|
|
29
34
|
"stepOutputs": [],
|
|
30
35
|
"method": {
|
|
31
|
-
"guidance": "# Value Proposition & Positioning — Sharpen Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The refinement order, the benefit-weighting posture, and the\n> \"sharpen vs. leave\" rules below are deliberately explicit so they can be\n> tuned against real runs — treat them as a starting rubric, not a frozen\n> contract. The *analytical depth* of the value-proposition work (quantified\n> FIT / Kano scoring precision, positioning rigor) is intentionally shallow\n> here and is deepened in a later phase; do not perfect it in this playbook.\n\n## What this playbook does\n\nYou are the **positioning strategist**. Market-analysis already produced the\n**MarketSnapshot** — the category, ICPs, personas, and jobs/pains/gains. Your\none job is to **sharpen the value-proposition slices of that same snapshot**:\nthe benefits, the tones of voice, and the per-ICP positioning pillars, framed\nby the product's **VisionSnapshot** differentiation. You do not create a new\nartifact family — benefits, tone-of-voice, and positioning all live *inside*\n`MarketSnapshot`. You read the existing snapshot, tighten these three slices,\nand re-emit the same snapshot.\n\nThis is a **focused refinement pass**, distinct from market-analysis (which\ndoes the broad initial market sweep). Where market-analysis lays down the\nwhole snapshot at a first-pass depth, you come back over the value-proposition\nslices specifically and make them sharp, consistent with each other, and true\nto the vision.\n\nThe three slices you own, in dependency order (later slices reference earlier\nrefs, and all reference the jobs/pains/gains the market pass already authored):\n\n1. **Benefits** — the outcome claims the product delivers (`FeatureBenefit`),\n each a *weighted* set of edges: the pains it **relieves**, the gains it\n **creates**, and the jobs it **advances**, every edge carrying a `degree`\n (1..10) the FIT scorer multiplies by the ICP's own edge weight. Layer on\n `importanceByICP`: a per-ICP `weight` plus a **Kano category** from the\n `BenefitKanoCategory` enum — `THRESHOLD` (a must-have; its absence breaks\n the deal), `PERFORMANCE` (more is better), `DELIGHTER` (unexpected upside),\n plus `INDIFFERENT` / `REVERSE` for completeness — so the same benefit can\n matter differently to different segments. Benefits reference the\n pains/gains/jobs the market pass authored — never weight against a\n pain/gain/job that does not exist. (`market-add-feature-benefit`)\n - **Structural constraint (the U8 seam):** every benefit carries a\n non-empty `deliveredByFeatureRefs[]` — a benefit must be *deliverable*.\n At this top-down phase there is no feature registry yet, so these are\n **forward-reference** feature refs; the `ORPHAN_REF` resolution check is\n skipped until a feature set exists. **Wiring benefits to real spec-first\n feature drafts is the capability-map playbook's job (U8), not yours** —\n do not invent the feature registry here. Keep the refs you inherit;\n leave a placeholder ref only where the market pass already did.\n2. **Tones of voice** — the named brand voices the product speaks in\n (`ToneOfVoice`, addressed by `ToneOfVoiceRef`). Keep them few and distinct;\n each positioning and message template later speaks in one of them.\n (`market-tone-of-voice`)\n3. **Positioning** — the per-ICP marketing-truth promise (`MarketPositioning`):\n author **one positioning entry per ICP the product actually targets**\n (priority `CORE` or `EXPANSION`), each carrying **2–4 value pillars**\n (`valuePillars`) — the sharp claims that separate the product from the\n alternatives. Each pillar hangs off the weighted benefits above (it traces\n back to `FeatureBenefitRef[]`) and is framed by the vision's\n differentiation. (`market-positioning-authoring`)\n\nSharpen only the slices the product's stage warrants. A snapshot whose\nbenefits carry honest relieves/creates/advances weighting with per-ICP Kano\ncategories, at least one tone of voice, and one positioning entry (with its\nvalue pillars) per `CORE`/`EXPANSION` ICP is a legitimate v1; the depth of the\nweighting and the pillar prose is additive.\n\n## Frame everything by the vision\n\nThe **VisionSnapshot** (`vision-brief` family) is your differentiation anchor.\nRead its mission, its problem framing, and its success criteria before you\nweight a single benefit. A benefit's weight, a Kano category, and a positioning\npillar are only *right* if they express the product's actual differentiation —\nwhat the vision says makes this product worth building over the alternatives.\nWhen a benefit or pillar cannot be traced back to the vision's differentiation,\nthat is a signal to either sharpen the vision link or drop the claim, not to\ninvent a promise the product does not stand behind.\n\n## Where the snapshot lives\n\nThe MarketSnapshot for this journey is at\n`specifications/src/market/index.ts`. That is the artifact this\nplaybook refines in place — you read it, sharpen the value-proposition slices,\nand write the same artifact back. When the product's definition later\nstabilises, the snapshot is what seeds the durable market specification under\n`./specifications/` — but at this phase it is a journey artifact, not yet app\nsource.\n\n## Refine, don't re-author — read state first\n\nThis playbook is **idempotent** and, by construction, a *refinement*: a\nMarketSnapshot must already exist (the `artifact_exists` precondition enforces\nit). Before sharpening anything:\n\n1. Read the current journey state and scope from what this run is given — the loaded\n specifications and the workspace sections of your brief; do not re-derive it. That state tells you which scope\n the value proposition must hold *for*.\n2. Read the existing MarketSnapshot at this playbook's placement path and the\n VisionSnapshot at the `vision-brief` placement, so you sharpen against the\n real market intent and the real differentiation, not from scratch.\n\n\nThen sharpen:\n\n- **Keep what still holds.** Do not rewrite benefits, tones, or pillars that\n are already sharp and vision-true. Only add/correct where the current\n steering notes, the vision, or benefit-weight inconsistencies call for it.\n- **Never orphan a ref.** A positioning names an ICP and its pillars name\n benefits; a benefit names the pains/gains/jobs it relieves/creates/advances.\n Dropping an ICP, pain, gain, job, or benefit that a positioning, pillar, or\n benefit still points at orphans the downstream ref (the validator catches\n this as `ORPHAN_REF`, but honest refinement should not create the orphan).\n If a slice from the market pass is genuinely wrong, fix it at its source\n slice, do not paper over it in the value-prop layer.\n\n## Quality gate\n\nYour re-emitted snapshot is checked by the deterministic `market-snapshot-valid`\ngate (`validateMarketSnapshot`) before anything downstream consumes it. The\nvalue-proposition invariants it enforces are mostly **`ERROR`-severity hard\nfailures** — the snapshot does not advance until they clear:\n\n- **`MISSING_POSITIONING_FOR_ICP` (ERROR)** — a `CORE` or `EXPANSION` ICP has\n no `MarketPositioning`. This is the headline gap this playbook closes: a\n targeted ICP without a positioning is a *hard failure*, not a warning.\n (`EXPLORATORY` / `DEFERRED` / `ANTI_TARGET` ICPs are exempt.)\n- **`THRESHOLD_BENEFIT_WITHOUT_JOB` (ERROR)** — a benefit carries a\n `kanoCategory: THRESHOLD` entry but its `advances[]` is empty; a must-have\n claim needs a job to anchor against.\n- **`MULTIPLE_THRESHOLDS_PER_ICP_JOB` (ERROR)** — two distinct benefits both\n claim `THRESHOLD` for the same (icp, job); only one must-have per job.\n- **`EMPTY_BENEFIT_DELIVERED_BY` (ERROR)** — a benefit's `deliveredByFeatureRefs[]`\n is empty; every benefit must stay deliverable (see the U8 seam above).\n- **`ORPHAN_REF` (ERROR)** — a positioning naming a missing ICP, a pillar or\n benefit naming a missing pain/gain/job. (Feature-ref orphans are only\n checked once a feature registry is passed — not at this phase.)\n\n`WARN`-severity issues do not block but should be resolved: `DUPLICATE_EDGE_PER_ENTITY`\n(a duplicate `(benefit, icp)` importance edge) and `STALE_AUTHORED` (a slice\npast its review cadence). Read `market-snapshot-validation` for the full issue\ncatalogue and emit a clean snapshot the first time.\n\nBeyond the deterministic gate, the advisory judge reads the landed snapshot against\nthree criteria — vision-framed benefits, positioning coverage, and refinement rather\nthan re-authoring — and its verdicts reach the creator's review as notes. A verdict\nnever refuses a landing.\n\n## Scaffold-depth boundary (deferred to a later depth phase)\n\nKeep this playbook at scaffold depth. The following are explicitly **out of\nscope here** and are deepened in the methodology-depth phase, not now:\n\n- **Quantified FIT / Kano scoring precision** — the deterministic FIT scorer has\n already been run for you and its per-ICP scores arrive in\n the declared `market_fit_scores` context section of your brief; `market-scoring-interpretation` is how to\n READ them. At scaffold depth you consume them to sanity-check benefit weighting\n and Kano assignment, never to drive a precise prioritization model, and you never\n restate or estimate a score. The prioritization seam stays pluggable (the\n capability-map playbook owns wiring FIT scores into feature drafts). Do not\n build a scoring model here.\n- **Positioning rigor** — a pillar captures *the* sharp per-ICP promise; a\n full competitive positioning matrix, message-market-fit testing, or\n A/B-tested copy is later-phase work.\n- **Message-template rendering** — this playbook stops at the value-proposition\n slices (benefits / tone / pillars). Turning them into reusable message\n templates stays with the market-analysis playbook's `market_message_templates`\n slice.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at\nscaffold depth — depth is a dedicated later pass done once, holistically.\n\n## What you emit\n\nThe SAME MarketSnapshot at `specifications/src/market/index.ts`,\nwith its value-proposition slices sharpened: weighted benefits with per-ICP\nKano categories, the tones of voice, and one positioning entry (with its 2–4\nvalue pillars) per `CORE`/`EXPANSION` ICP — all framed by the vision's\ndifferentiation — passing the\n`market-snapshot-valid` gate. The creator reviews the result (approval posture\n`approve_result`) before it is accepted as the journey's refined market intent.\n\n## References\n\nThese are skill FOLDERS installed in the application, named so each piece of work has an\nauthoring contract a later coding agent can open. This step has no tools and does not open them;\nwhat reaches you is this method, your declared inputs, and the brief's own sections.\n\n- `market-add-feature-benefit` — author the benefit\n claims and their relieves/creates/advances weighting and per-ICP Kano\n categories.\n- `market-tone-of-voice` — author the named brand\n voices.\n- `market-positioning-authoring` — author the per-ICP\n positioning entries and their 2–4 value pillars.\n- `market-scoring-interpretation` — interpret the\n deterministic FIT scorer to sanity-check benefit weighting and Kano\n assignment (scaffold depth — sanity-check, not a scoring model).\n- `market-snapshot-validation` — the full validation\n issue catalogue the quality gate enforces.\n",
|
|
36
|
+
"guidance": "# Value Proposition & Positioning — Sharpen Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The refinement order, the benefit-weighting posture, and the\n> \"sharpen vs. leave\" rules below are deliberately explicit so they can be\n> tuned against real runs — treat them as a starting rubric, not a frozen\n> contract. The *analytical depth* of the value-proposition work (quantified\n> FIT / Kano scoring precision, positioning rigor) is intentionally shallow\n> here and is deepened in a later phase; do not perfect it in this playbook.\n\n## What this playbook does\n\nYou are the **positioning strategist**. Market-analysis already produced the\n**MarketSnapshot** — the category, ICPs, personas, and jobs/pains/gains. Your\none job is to **sharpen the value-proposition slices of that same snapshot**:\nthe benefits, the tones of voice, and the per-ICP positioning pillars, framed\nby the product's **VisionSnapshot** differentiation. You do not create a new\nartifact family — benefits, tone-of-voice, and positioning all live *inside*\n`MarketSnapshot`. You read the existing snapshot, tighten these three slices,\nand re-emit the same snapshot.\n\nThis is a **focused refinement pass**, distinct from market-analysis (which\ndoes the broad initial market sweep). Where market-analysis lays down the\nwhole snapshot at a first-pass depth, you come back over the value-proposition\nslices specifically and make them sharp, consistent with each other, and true\nto the vision.\n\nThe three slices you own, in dependency order (later slices reference earlier\nrefs, and all reference the jobs/pains/gains the market pass already authored):\n\n1. **Benefits** — the outcome claims the product delivers (`FeatureBenefit`),\n each a *weighted* set of edges: the pains it **relieves**, the gains it\n **creates**, and the jobs it **advances**, every edge carrying a `degree`\n (1..10) the FIT scorer multiplies by the ICP's own edge weight. Layer on\n `importanceByICP`: a per-ICP `weight` plus a **Kano category** from the\n `BenefitKanoCategory` enum — `THRESHOLD` (a must-have; its absence breaks\n the deal), `PERFORMANCE` (more is better), `DELIGHTER` (unexpected upside),\n plus `INDIFFERENT` / `REVERSE` for completeness — so the same benefit can\n matter differently to different segments. Benefits reference the\n pains/gains/jobs the market pass authored — never weight against a\n pain/gain/job that does not exist. (`market-add-feature-benefit`)\n - **Structural constraint (the U8 seam):** every benefit carries a\n non-empty `deliveredByFeatureRefs[]` — a benefit must be *deliverable*.\n At this top-down phase there is no feature registry yet, so these are\n **forward-reference** feature refs; the `ORPHAN_REF` resolution check is\n skipped until a feature set exists. **Wiring benefits to real spec-first\n feature drafts is the capability-map playbook's job (U8), not yours** —\n do not invent the feature registry here. Keep the refs you inherit;\n leave a placeholder ref only where the market pass already did.\n2. **Tones of voice** — the named brand voices the product speaks in\n (`ToneOfVoice`, addressed by `ToneOfVoiceRef`). Keep them few and distinct;\n each positioning and message template later speaks in one of them.\n (`market-tone-of-voice`)\n3. **Positioning** — the per-ICP marketing-truth promise (`MarketPositioning`):\n author **one positioning entry per ICP the product actually targets**\n (priority `CORE` or `EXPANSION`), each carrying **2–4 value pillars**\n (`valuePillars`) — the sharp claims that separate the product from the\n alternatives. Each pillar hangs off the weighted benefits above (it traces\n back to `FeatureBenefitRef[]`) and is framed by the vision's\n differentiation. (`market-positioning-authoring`)\n\nSharpen only the slices the product's stage warrants. A snapshot whose\nbenefits carry honest relieves/creates/advances weighting with per-ICP Kano\ncategories, at least one tone of voice, and one positioning entry (with its\nvalue pillars) per `CORE`/`EXPANSION` ICP is a legitimate v1; the depth of the\nweighting and the pillar prose is additive.\n\n## Frame everything by the vision\n\nThe **VisionSnapshot** (`vision-brief` family) is your differentiation anchor.\nRead its mission, its problem framing, and its success criteria before you\nweight a single benefit. A benefit's weight, a Kano category, and a positioning\npillar are only *right* if they express the product's actual differentiation —\nwhat the vision says makes this product worth building over the alternatives.\nWhen a benefit or pillar cannot be traced back to the vision's differentiation,\nthat is a signal to either sharpen the vision link or drop the claim, not to\ninvent a promise the product does not stand behind.\n\n## Where the snapshot lives\n\nThe MarketSnapshot for this journey is at\n`specifications/src/market/index.ts`. That is the artifact this\nplaybook refines in place — you read it, sharpen the value-proposition slices,\nand write the same artifact back. When the product's definition later\nstabilises, the snapshot is what seeds the durable market specification under\n`./specifications/` — but at this phase it is a journey artifact, not yet app\nsource.\n\n## Refine, don't re-author — read state first\n\nThis playbook is **idempotent** and, by construction, a *refinement*: a\nMarketSnapshot must already exist (the `artifact_exists` precondition enforces\nit). Before sharpening anything:\n\n1. Read the current journey state and scope from what this run is given — the loaded\n specifications and the workspace sections of your brief; do not re-derive it. That state tells you which scope\n the value proposition must hold *for*.\n2. Read the existing MarketSnapshot at this playbook's placement path and the\n VisionSnapshot at the `vision-brief` placement, so you sharpen against the\n real market intent and the real differentiation, not from scratch.\n\n\nThen sharpen:\n\n- **Keep what still holds.** Do not rewrite benefits, tones, or pillars that\n are already sharp and vision-true. Only add/correct where the current\n steering notes, the vision, or benefit-weight inconsistencies call for it.\n- **Never orphan a ref.** A positioning names an ICP and its pillars name\n benefits; a benefit names the pains/gains/jobs it relieves/creates/advances.\n Dropping an ICP, pain, gain, job, or benefit that a positioning, pillar, or\n benefit still points at orphans the downstream ref (the validator catches\n this as `ORPHAN_REF`, but honest refinement should not create the orphan).\n Only your slices land (the benefits, the tones of voice and the positionings,\n #3403): an edit to any other part of the snapshot is replaced by its current\n value. If a slice from the market pass is genuinely wrong, say so in your\n rationale for the snapshot's producer to correct; do not paper over it in the\n value-prop layer.\n\n## Quality gate\n\nYour re-emitted snapshot is checked by the deterministic `market-snapshot-valid`\ngate (`validateMarketSnapshot`) before anything downstream consumes it. The\nvalue-proposition invariants it enforces are mostly **`ERROR`-severity hard\nfailures** — the snapshot does not advance until they clear:\n\n- **`MISSING_POSITIONING_FOR_ICP` (ERROR)** — a `CORE` or `EXPANSION` ICP has\n no `MarketPositioning`. This is the headline gap this playbook closes: a\n targeted ICP without a positioning is a *hard failure*, not a warning.\n (`EXPLORATORY` / `DEFERRED` / `ANTI_TARGET` ICPs are exempt.)\n- **`THRESHOLD_BENEFIT_WITHOUT_JOB` (ERROR)** — a benefit carries a\n `kanoCategory: THRESHOLD` entry but its `advances[]` is empty; a must-have\n claim needs a job to anchor against.\n- **`MULTIPLE_THRESHOLDS_PER_ICP_JOB` (ERROR)** — two distinct benefits both\n claim `THRESHOLD` for the same (icp, job); only one must-have per job.\n- **`EMPTY_BENEFIT_DELIVERED_BY` (ERROR)** — a benefit's `deliveredByFeatureRefs[]`\n is empty; every benefit must stay deliverable (see the U8 seam above).\n- **`ORPHAN_REF` (ERROR)** — a positioning naming a missing ICP, a pillar or\n benefit naming a missing pain/gain/job. (Feature-ref orphans are only\n checked once a feature registry is passed — not at this phase.)\n\n`WARN`-severity issues do not block but should be resolved: `DUPLICATE_EDGE_PER_ENTITY`\n(a duplicate `(benefit, icp)` importance edge) and `STALE_AUTHORED` (a slice\npast its review cadence). Read `market-snapshot-validation` for the full issue\ncatalogue and emit a clean snapshot the first time.\n\nBeyond the deterministic gate, the advisory judge reads the landed snapshot against\nthree criteria — vision-framed benefits, positioning coverage, and refinement rather\nthan re-authoring — and its verdicts reach the creator's review as notes. A verdict\nnever refuses a landing.\n\n## Scaffold-depth boundary (deferred to a later depth phase)\n\nKeep this playbook at scaffold depth. The following are explicitly **out of\nscope here** and are deepened in the methodology-depth phase, not now:\n\n- **Quantified FIT / Kano scoring precision** — the deterministic FIT scorer has\n already been run for you and its per-ICP scores arrive in\n the declared `market_fit_scores` context section of your brief; `market-scoring-interpretation` is how to\n READ them. At scaffold depth you consume them to sanity-check benefit weighting\n and Kano assignment, never to drive a precise prioritization model, and you never\n restate or estimate a score. The prioritization seam stays pluggable (the\n capability-map playbook owns wiring FIT scores into feature drafts). Do not\n build a scoring model here.\n- **Positioning rigor** — a pillar captures *the* sharp per-ICP promise; a\n full competitive positioning matrix, message-market-fit testing, or\n A/B-tested copy is later-phase work.\n- **Message-template rendering** — this playbook stops at the value-proposition\n slices (benefits / tone / pillars). Turning them into reusable message\n templates stays with the market-analysis playbook's `market_message_templates`\n slice.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at\nscaffold depth — depth is a dedicated later pass done once, holistically.\n\n## What you emit\n\nThe SAME MarketSnapshot at `specifications/src/market/index.ts`,\nwith its value-proposition slices sharpened: weighted benefits with per-ICP\nKano categories, the tones of voice, and one positioning entry (with its 2–4\nvalue pillars) per `CORE`/`EXPANSION` ICP — all framed by the vision's\ndifferentiation — passing the\n`market-snapshot-valid` gate. The creator reviews the result (approval posture\n`approve_result`) before it is accepted as the journey's refined market intent.\n\n## References\n\nThese are skill FOLDERS installed in the application, named so each piece of work has an\nauthoring contract a later coding agent can open. This step has no tools and does not open them;\nwhat reaches you is this method, your declared inputs, and the brief's own sections.\n\n- `market-add-feature-benefit` — author the benefit\n claims and their relieves/creates/advances weighting and per-ICP Kano\n categories.\n- `market-tone-of-voice` — author the named brand\n voices.\n- `market-positioning-authoring` — author the per-ICP\n positioning entries and their 2–4 value pillars.\n- `market-scoring-interpretation` — interpret the\n deterministic FIT scorer to sanity-check benefit weighting and Kano\n assignment (scaffold depth — sanity-check, not a scoring model).\n- `market-snapshot-validation` — the full validation\n issue catalogue the quality gate enforces.\n",
|
|
32
37
|
"skillRefs": [
|
|
33
38
|
"market-add-feature-benefit",
|
|
34
39
|
"market-positioning-authoring",
|
|
@@ -37,6 +42,7 @@
|
|
|
37
42
|
"market-snapshot-validation"
|
|
38
43
|
],
|
|
39
44
|
"skillBodyRefs": [],
|
|
45
|
+
"derivedFromAnswers": [],
|
|
40
46
|
"contextSources": [
|
|
41
47
|
"market_fit_scores"
|
|
42
48
|
],
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"aggregationPolicyRef":"application-creation:aggregation/worst-vision-elicitation-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/vision-coherence-and-readiness","criterionVersion":
|
|
1
|
+
{"aggregationPolicyRef":"application-creation:aggregation/worst-vision-elicitation-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/vision-coherence-and-readiness","criterionVersion":4,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/vision-coherence-and-readiness","requirementVersion":1}],"instruction":"Assess whether the validated vision is internally coherent, grounded in the creator input carried in this brief, non-vacuous for the current horizon, and explicit about important uncertainty. Do not reward polished prose that lacks a real problem, mission, observable success basis or binding constraints. Read each creator answer WITH its standing: an answer marked ASSUMED was proposed for the creator and never stated by them, so the vision must present it as an assumption or working hypothesis. Labelling it so is correct and never drift; presenting an ASSUMED answer as the creator's own statement is drift, and so is labelling a DECIDED answer as an assumption. A problem, mission or set of success criteria the creator left NOT DECIDED YET is correctly absent: its absence is never drift, and filling it in from other answers is. A regulated-domain question the creator left NOT DECIDED YET must appear as a compliance constraint stating that open question; leaving it out, which reads as 'no', or stating it as settled either way is drift. Separate severities by CONSEQUENCE: limited repairable drift from the creator input is a CONCERN; a substituted product, audience or constraint set — or an internal contradiction — is a GAP.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Usable WITH REVISION: grounded in the creator input overall, but carrying limited repairable drift (an embellished emphasis, a missing secondary element, weak evidence, or explicit material uncertainty) that revision can fix without re-eliciting the creator.","GAP":"NOT usable as direction: a foundational vision element is missing, the candidate contradicts itself, or it substitutes a DIFFERENT product, audience or binding-constraint set than the creator input states.","INDETERMINATE":"The creator input or candidate evidence needed to decide this criterion is absent or insufficient.","PASS":"The candidate is valid, internally coherent, grounded in the creator input, and sufficient to guide the current horizon."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/vision-elicitation","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.vision-elicitation"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-vision-snapshot","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/vision-coherence-and-readiness"],"requirementRef":"application-creation:authority-requirement/vision-elicitation-result","requirementVersion":1,"riskClassRef":"application-creation:risk/foundational-vision-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/vision-elicitation","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/vision-elicitation-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/vision-elicitation","policyVersion":1},"decisionPointRef":"application-creation:decision-point/vision-elicitation-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/vision-elicitation-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/vision-elicitation","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/vision-coherence-and-readiness","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/vision-snapshot-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/foundational-vision-change","triggerRefs":["application-creation:trigger/vision-snapshot-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-vision-elicitation-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/vision-coherence-and-readiness"],"hardFloorRef":"application-creation:hard-floor/vision-snapshot-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/vision-elicitation-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/vision-elicitation","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-vision-elicitation-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/vision-coherence-and-readiness","criterionVersion":
|
|
1
|
+
{"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-vision-snapshot","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/vision-coherence-and-readiness"],"requirementRef":"application-creation:authority-requirement/vision-elicitation-result","requirementVersion":1,"riskClassRef":"application-creation:risk/foundational-vision-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/vision-elicitation","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/vision-elicitation-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/vision-elicitation","policyVersion":1},"decisionPointRef":"application-creation:decision-point/vision-elicitation-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/vision-elicitation-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/vision-elicitation","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/vision-coherence-and-readiness","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/vision-snapshot-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/foundational-vision-change","triggerRefs":["application-creation:trigger/vision-snapshot-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-vision-elicitation-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/vision-coherence-and-readiness"],"hardFloorRef":"application-creation:hard-floor/vision-snapshot-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/vision-elicitation-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/vision-elicitation","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-vision-elicitation-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/vision-coherence-and-readiness","criterionVersion":4,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/vision-coherence-and-readiness","requirementVersion":1}],"instruction":"Assess whether the validated vision is internally coherent, grounded in the creator input carried in this brief, non-vacuous for the current horizon, and explicit about important uncertainty. Do not reward polished prose that lacks a real problem, mission, observable success basis or binding constraints. Read each creator answer WITH its standing: an answer marked ASSUMED was proposed for the creator and never stated by them, so the vision must present it as an assumption or working hypothesis. Labelling it so is correct and never drift; presenting an ASSUMED answer as the creator's own statement is drift, and so is labelling a DECIDED answer as an assumption. A problem, mission or set of success criteria the creator left NOT DECIDED YET is correctly absent: its absence is never drift, and filling it in from other answers is. A regulated-domain question the creator left NOT DECIDED YET must appear as a compliance constraint stating that open question; leaving it out, which reads as 'no', or stating it as settled either way is drift. Separate severities by CONSEQUENCE: limited repairable drift from the creator input is a CONCERN; a substituted product, audience or constraint set — or an internal contradiction — is a GAP.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Usable WITH REVISION: grounded in the creator input overall, but carrying limited repairable drift (an embellished emphasis, a missing secondary element, weak evidence, or explicit material uncertainty) that revision can fix without re-eliciting the creator.","GAP":"NOT usable as direction: a foundational vision element is missing, the candidate contradicts itself, or it substitutes a DIFFERENT product, audience or binding-constraint set than the creator input states.","INDETERMINATE":"The creator input or candidate evidence needed to decide this criterion is absent or insufficient.","PASS":"The candidate is valid, internally coherent, grounded in the creator input, and sufficient to guide the current horizon."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/vision-elicitation","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.vision-elicitation"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/vision-elicitation","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-vision-input-and-candidate","criterionRef":"application-creation:criterion/vision-coherence-and-readiness","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":2,"requirementRef":"application-creation:evidence-requirement/vision-coherence-and-readiness","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-bootstrap-and-candidate"}],"schemaVersion":1}
|
|
@@ -40,6 +40,10 @@ The creator's answer is recorded exactly as given and decides which playbooks th
|
|
|
40
40
|
from here on. It is **not** part of the `VisionSnapshot`: do not restate it in the vision, and never
|
|
41
41
|
answer it on the creator's behalf. If the creator is unsure, describe each option and let them choose.
|
|
42
42
|
|
|
43
|
+
An application created from a blueprint that carries a line already has this question answered: `wildo init`
|
|
44
|
+
recorded the blueprint's line, answered by `blueprint:<id>@<version>`. Choosing the blueprint was the creator's
|
|
45
|
+
choice of line, so it is not asked again. The creator may still change it by answering again.
|
|
46
|
+
|
|
43
47
|
## The elicitation posture
|
|
44
48
|
|
|
45
49
|
- **Interview, do not fill a form.** The typed questions on this playbook
|
|
@@ -110,6 +114,16 @@ questions:
|
|
|
110
114
|
per-regime obligation model (control catalogs, data-flow / residency
|
|
111
115
|
matrices) is the compliance-posture step's job, not yours. Getting the
|
|
112
116
|
compliance *seam* named here is what lets that later step engage.
|
|
117
|
+
- **A regulated-domain question left NOT DECIDED YET is an open compliance
|
|
118
|
+
constraint.** When the creator left one of the five regulated-domain
|
|
119
|
+
questions (children's or specially protected data, financial services,
|
|
120
|
+
healthcare, legal or compliance decisions, public sector or critical
|
|
121
|
+
infrastructure) not decided yet, record a `kind: compliance` constraint
|
|
122
|
+
whose statement names the OPEN QUESTION and what it decides ("Whether the
|
|
123
|
+
application will process health or clinical data is not decided yet; it
|
|
124
|
+
decides whether health-data rules apply."), with the creator's reason as
|
|
125
|
+
its rationale when they gave one. Never leave it out, which a later step
|
|
126
|
+
reads as "no", and never answer it either way from the other answers.
|
|
113
127
|
|
|
114
128
|
### The product's shape: workflow, users, boundary
|
|
115
129
|
|
|
@@ -123,7 +137,8 @@ Carry them into the snapshot in the creator's own terms:
|
|
|
123
137
|
|
|
124
138
|
- the workflow's stages, in order, in the idea's `description`;
|
|
125
139
|
- the user groups, what each does, and their devices, in the problem's "who is affected" (and in the
|
|
126
|
-
idea when the product's shape depends on them, such as work done in the field on a phone
|
|
140
|
+
idea when the product's shape depends on them, such as work done in the field on a phone; in the
|
|
141
|
+
idea's `description` when the creator left the problem not decided yet, so they are never lost);
|
|
127
142
|
- each scope boundary as a `constraint` of kind `business`, stated as an exclusion ("Invoicing is out
|
|
128
143
|
of scope: customers keep their accounting tool"), with the creator's reason as its rationale.
|
|
129
144
|
|
|
@@ -138,8 +153,12 @@ A single `VisionSnapshot`:
|
|
|
138
153
|
otherwise).
|
|
139
154
|
- `idea` — the required anchor (`oneLiner`, `description`, optional `notes`).
|
|
140
155
|
- `problem` / `mission` — the optional singletons, present only if elicited.
|
|
156
|
+
When the creator left the problem statement or the mission NOT DECIDED YET,
|
|
157
|
+
emit that singleton as `null`; never fill it from the other answers.
|
|
141
158
|
- `successCriteria[]` — each with a stable kebab-case `ref` prefixed
|
|
142
|
-
`success-criterion-`, unique across the set.
|
|
159
|
+
`success-criterion-`, unique across the set. Empty when the creator left the
|
|
160
|
+
success criteria not decided yet: an empty set is honest, and the validator
|
|
161
|
+
WARNs on it so it stays visible.
|
|
143
162
|
- `constraints[]` — each with a stable kebab-case `ref` prefixed `constraint-`,
|
|
144
163
|
unique across the set, and a `kind`.
|
|
145
164
|
|