@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
|
@@ -22,19 +22,20 @@ Read and apply these patterns from the application-developer point of view:
|
|
|
22
22
|
## What this playbook does
|
|
23
23
|
|
|
24
24
|
You determine the product's **compliance posture** — which regulatory regimes
|
|
25
|
-
it must be built to satisfy — and record each as a
|
|
26
|
-
|
|
27
|
-
compliance _seam_ in passing (a single "we handle EU personal data" line
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
prose statement.
|
|
32
|
-
|
|
33
|
-
You do **not**
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
25
|
+
it must be built to satisfy — and record each as a constraint in the
|
|
26
|
+
`compliance-posture` family. The vision-elicitation step may already have named
|
|
27
|
+
the compliance _seam_ in passing (a single "we handle EU personal data" line, a
|
|
28
|
+
`kind: compliance` constraint on the vision). Your job is the focused,
|
|
29
|
+
deliberate pass over that seam: reason from the product's jurisdictions, the
|
|
30
|
+
classes of data it handles, and its sector to the concrete set of regimes, and
|
|
31
|
+
write each one down as its own constraint with a clear prose statement.
|
|
32
|
+
|
|
33
|
+
You do **not** edit the vision, design the domain, or draft requirements. The
|
|
34
|
+
vision is your INPUT: read its facts and the creator's own compliance
|
|
35
|
+
constraints, and leave it exactly as you found it. Your output is the posture,
|
|
36
|
+
a family of its own, so that recording a regime re-opens only the steps that
|
|
37
|
+
read the posture (the compliance conception, the document facts, the build
|
|
38
|
+
decomposer) and not every step that read the vision.
|
|
38
39
|
|
|
39
40
|
## The scaffold-depth boundary (read this before you start)
|
|
40
41
|
|
|
@@ -59,7 +60,7 @@ right, in prose, is the win.
|
|
|
59
60
|
### Transition to structured compliance conception
|
|
60
61
|
|
|
61
62
|
This playbook does not write the dedicated `compliance-program` family. Its
|
|
62
|
-
accepted
|
|
63
|
+
accepted posture constraints are precursor facts for a later, separately
|
|
63
64
|
approved compliance-conception step. That step may initialize or revise the
|
|
64
65
|
optional structured family only after it resolves exact source versions and
|
|
65
66
|
rights records, declarative application scope, applicability authority, Wildo
|
|
@@ -67,8 +68,8 @@ objective bindings, implementation choices, responsibilities, documentation
|
|
|
67
68
|
requirements and explicit gaps.
|
|
68
69
|
|
|
69
70
|
The transition is not an automatic conversion and must not reinterpret a
|
|
70
|
-
|
|
71
|
-
the
|
|
71
|
+
posture sentence as a control mapping or positive compliance claim. Preserve
|
|
72
|
+
the posture constraint as product intent, record any missing detail as
|
|
72
73
|
`UNDETERMINED` or an explicit gap, and land the structured family as files in the
|
|
73
74
|
specifications package. Landing is not accepting: the run leaves working edits,
|
|
74
75
|
and acceptance is a later commit. Who makes it is the host's autonomy posture, and only a
|
|
@@ -111,57 +112,50 @@ control occurrences and assessments remain outside both artifacts.
|
|
|
111
112
|
|
|
112
113
|
## What you emit
|
|
113
114
|
|
|
114
|
-
You
|
|
115
|
-
|
|
116
|
-
|
|
117
|
-
|
|
118
|
-
-
|
|
119
|
-
|
|
120
|
-
|
|
121
|
-
|
|
122
|
-
|
|
123
|
-
|
|
124
|
-
|
|
125
|
-
|
|
126
|
-
|
|
127
|
-
|
|
128
|
-
|
|
129
|
-
|
|
130
|
-
|
|
131
|
-
|
|
132
|
-
|
|
133
|
-
|
|
134
|
-
|
|
135
|
-
|
|
136
|
-
|
|
137
|
-
|
|
138
|
-
|
|
139
|
-
**reuse that entry's existing `ref`** so it updates in place rather than
|
|
140
|
-
forking; only mint a fresh `constraint-<regime>-<scope>` slug for a regime that
|
|
141
|
-
is genuinely new. Re-running this playbook on an already-posture'd vision must
|
|
142
|
-
converge to one entry per regime, never accumulate near-duplicate
|
|
143
|
-
`constraint-gdpr-*` entries.
|
|
115
|
+
You emit the whole posture: a `constraints[]` list, one entry per regime.
|
|
116
|
+
|
|
117
|
+
- Each entry has a stable kebab-case semantic `slug` naming the regime and its
|
|
118
|
+
scope (e.g. `gdpr-eu-personal-data`, `hipaa-us-phi`,
|
|
119
|
+
`external-assurance-security`, `data-residency-eu`), unique across the list.
|
|
120
|
+
The runtime stamps the `posture-` prefix to make its ref, so do not write it.
|
|
121
|
+
- Each entry's `statement` is a prose sentence naming the regime, its trigger
|
|
122
|
+
and the data / jurisdiction it governs. Its `rationale` names the evidence or
|
|
123
|
+
the creator's fact it rests on (a customer contract, a specific law), or is
|
|
124
|
+
`null`.
|
|
125
|
+
|
|
126
|
+
**Idempotent — refine, do not duplicate.** When a previous posture is in your
|
|
127
|
+
brief (the `compliance-posture` input), reconcile against it: update a
|
|
128
|
+
statement that is now sharper, add a regime that was missed, and remove one
|
|
129
|
+
only when the evidence now excludes it. When you keep a regime that is already
|
|
130
|
+
present, **reuse its slug** (its ref without the `posture-` prefix) so it
|
|
131
|
+
updates in place rather than forking. Re-running this playbook must converge
|
|
132
|
+
to one entry per regime, never accumulate near-duplicate `gdpr-*` entries.
|
|
133
|
+
|
|
134
|
+
**The creator's own compliance constraints stay on the vision.** When the
|
|
135
|
+
vision carries a `kind: compliance` constraint the creator stated, match it by
|
|
136
|
+
the REGIME its statement names (its slug follows no convention), and record
|
|
137
|
+
that regime here with the evidence's sharper statement, or, when the evidence
|
|
138
|
+
excludes it, make the exclusion legible on a neighbouring constraint. Never
|
|
139
|
+
silently contradict what the creator said.
|
|
144
140
|
|
|
145
141
|
## Quality gate
|
|
146
142
|
|
|
147
|
-
Your
|
|
148
|
-
gate
|
|
149
|
-
|
|
150
|
-
|
|
151
|
-
|
|
152
|
-
unique refs the first time. Note that a vision with no compliance constraints
|
|
153
|
-
is perfectly valid — an honestly unregulated product should pass the gate with
|
|
154
|
-
none.
|
|
143
|
+
Your posture is checked by the deterministic `validateCompliancePosture`
|
|
144
|
+
gate before it lands. Two slugs that stamp to the same ref are refused at
|
|
145
|
+
generation, with the entry named, so emit unique slugs the first time. A
|
|
146
|
+
posture with no constraints is perfectly valid — an honestly unregulated
|
|
147
|
+
product should pass the gate with none.
|
|
155
148
|
|
|
156
|
-
Beyond the deterministic gate, the advisory judge reads the
|
|
149
|
+
Beyond the deterministic gate, the advisory judge reads the posture against
|
|
157
150
|
three criteria — regime derivation grounded in the evidence, one regime per constraint
|
|
158
|
-
converging on re-run, and
|
|
159
|
-
review as notes. A verdict
|
|
151
|
+
converging on re-run, and scaffold depth consistent with the creator's own
|
|
152
|
+
constraints — and its verdicts reach the creator's review as notes. A verdict
|
|
153
|
+
never refuses a landing.
|
|
160
154
|
|
|
161
155
|
## Approval
|
|
162
156
|
|
|
163
|
-
The
|
|
164
|
-
|
|
157
|
+
The posture is presented to the creator for approval before it becomes the
|
|
158
|
+
committed `compliance-posture`. Show the derived compliance posture back
|
|
165
159
|
in plain prose — the list of regimes, each with the data / jurisdiction it
|
|
166
160
|
governs and why it applies — and let the creator confirm or correct it.
|
|
167
161
|
Compliance drives real downstream engine capability, audit, and retention
|
|
@@ -170,12 +164,12 @@ right.
|
|
|
170
164
|
|
|
171
165
|
## Runtime context
|
|
172
166
|
|
|
173
|
-
Before you start, read the current journey state and scope,
|
|
174
|
-
|
|
175
|
-
fresh, disconnected set.
|
|
167
|
+
Before you start, read the current journey state and scope, the vision (its
|
|
168
|
+
facts and the creator's compliance constraints), and the previous posture when
|
|
169
|
+
there is one, so you refine it rather than writing a fresh, disconnected set.
|
|
176
170
|
|
|
177
|
-
(The
|
|
178
|
-
|
|
171
|
+
(The vision is in your brief as the `vision-brief` input section, and a previous
|
|
172
|
+
posture, when one has landed, as the `compliance-posture` section.)
|
|
179
173
|
|
|
180
174
|
## The evidence, and how to use it
|
|
181
175
|
|
|
@@ -183,7 +177,7 @@ Your run carries what sibling steps gathered — source-attributed regime eviden
|
|
|
183
177
|
verdict that admitted this step. Derive each constraint from the creator's answers AND that
|
|
184
178
|
evidence, never from recollection:
|
|
185
179
|
|
|
186
|
-
- A regime the evidence establishes as APPLICABLE becomes a
|
|
180
|
+
- A regime the evidence establishes as APPLICABLE becomes a posture constraint whose statement
|
|
187
181
|
names the regime, the trigger (jurisdiction / data class / sector / commitment), and what it
|
|
188
182
|
governs — in the evidence's terms.
|
|
189
183
|
- A regime the evidence EXCLUDES is not written as a constraint, and is not silently dropped either:
|
|
@@ -192,6 +186,16 @@ evidence, never from recollection:
|
|
|
192
186
|
- A trigger the evidence could NOT establish becomes a constraint stating the OPEN QUESTION, never a
|
|
193
187
|
guessed answer — an unestablished regime stated as settled is the defect this composite exists to
|
|
194
188
|
end.
|
|
189
|
+
- Every `openFacts` entry of the adequacy verdict is such an open question: a fact about the product or
|
|
190
|
+
its operator that no research could settle, or a regime conditional on a fact declared open. Record
|
|
191
|
+
each as its own constraint naming the fact and what it decides (*"Whether the vendor is processor for
|
|
192
|
+
customer CRM data is open; it decides whether Art. 28 processor terms or controller duties attach."*).
|
|
193
|
+
The gate admitted you WITH them open on purpose (#3385); do not drop one because it is unresolved.
|
|
194
|
+
- A vision compliance constraint that states an OPEN regulated-domain question (the creator left it not
|
|
195
|
+
decided yet, #3484) is such an open question too. Carry it as its own constraint naming the question and
|
|
196
|
+
the regimes it decides; never settle it from the other answers, in either direction.
|
|
197
|
+
- The same holds for the `jurisdictions` answer left not decided yet (#3484): record where the users are as an open
|
|
198
|
+
question naming the regimes it decides (territorial scope turns on it), and never assume a place.
|
|
195
199
|
|
|
196
200
|
## References
|
|
197
201
|
|
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
{
|
|
2
2
|
"ref": "top_down.compliance-posture",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.3.1",
|
|
4
4
|
"phase": "top_down",
|
|
5
|
-
"intent": "Derive
|
|
5
|
+
"intent": "Derive the product's compliance posture from its vision's jurisdictions, data classes, sector, customer commitments and gathered regime evidence. This is the artifact-producing child of top_down.compliance-analysis: it runs when the current compliance-adequacy assessment is adequate, and records the posture in its own compliance-posture family; it never rewrites the vision. Record source-backed applicability and unresolved product facts as posture constraints; runtime controls, evidence assignments and organization assessments belong to their own mechanisms.",
|
|
6
6
|
"preconditions": [
|
|
7
7
|
{
|
|
8
8
|
"kind": "artifact_exists",
|
|
@@ -22,23 +22,27 @@
|
|
|
22
22
|
"inputs": [
|
|
23
23
|
{
|
|
24
24
|
"family": "vision-brief"
|
|
25
|
+
},
|
|
26
|
+
{
|
|
27
|
+
"family": "compliance-posture"
|
|
25
28
|
}
|
|
26
29
|
],
|
|
27
30
|
"outputs": [
|
|
28
31
|
{
|
|
29
|
-
"family": "
|
|
30
|
-
"schemaRef": "saas-specifications:
|
|
31
|
-
"description": "The
|
|
32
|
+
"family": "compliance-posture",
|
|
33
|
+
"schemaRef": "saas-specifications:CompliancePosture",
|
|
34
|
+
"description": "The compliance posture: one `constraints[]` entry per applicable regime (or per regime whose applicability turns on an open product fact), each a prose `statement` naming the regime, its trigger and what it governs, with the evidence it rests on as its `rationale`. An empty list is the honest posture of an unregulated product. Validated by validateCompliancePosture.",
|
|
32
35
|
"aspects": [
|
|
33
|
-
"
|
|
36
|
+
"compliance-posture.constraint"
|
|
34
37
|
]
|
|
35
38
|
}
|
|
36
39
|
],
|
|
37
40
|
"stepOutputs": [],
|
|
38
41
|
"method": {
|
|
39
|
-
"guidance": "# Compliance Posture — Derivation 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.** The regime-derivation rubric below\n> (which triggers imply which regime, how much to capture) is a deliberately\n> explicit first cut meant to be tuned against real runs. Treat it as a\n> starting rubric, not a frozen contract. Crucially, it derives compliance\n> **posture at scaffold depth** — prose constraints, not a per-regime\n> obligation model.\n\n## What this playbook does\n\nYou determine the product's **compliance posture** — which regulatory regimes\nit must be built to satisfy — and record each as a `compliance`-kind constraint\non the existing vision. The vision-elicitation step already named the\ncompliance _seam_ in passing (a single \"we handle EU personal data\" line). Your\njob is the focused, deliberate pass over that seam: reason from the product's\njurisdictions, the classes of data it handles, and its sector to the concrete\nset of regimes, and write each one down as its own constraint with a clear\nprose statement.\n\nYou do **not** re-elicit the whole vision, design the domain, or draft\nrequirements. You touch exactly one slice of the `VisionSnapshot`: its\n`constraints[]` entries of `kind: compliance`. Everything else on the snapshot\n— the idea, the problem, the mission, the success criteria, the\nnon-compliance constraints — you leave exactly as you found it.\n\n## The scaffold-depth boundary (read this before you start)\n\nAt this stage compliance is captured as **prose constraints only**. Each\napplicable regime becomes one constraint entry whose `statement` names the\nregime and the data / jurisdiction it governs — e.g. _\"Must be GDPR-compliant\nfor EU/EEA customer personal data.\"_ That is the whole deliverable.\n\nDo **not** build, and do not try to author into the snapshot:\n\n- per-regime control catalogs or obligation graphs (legal-article mappings,\n sector safeguards, external-assurance criteria),\n- data-flow / residency matrices,\n- retention schedules, DPA registries, or audit-config derivations.\n\nThat deep per-regime obligation model is a deliberately deferred later concern.\nIf you catch yourself modelling controls or obligations, **stop** — you have\nleft scaffold depth. Naming the regime seam accurately here is exactly what\nlets that later, deeper step engage. Getting the _set of applicable regimes_\nright, in prose, is the win.\n\n### Transition to structured compliance conception\n\nThis playbook does not write the dedicated `compliance-program` family. Its\naccepted vision constraints are precursor facts for a later, separately\napproved compliance-conception step. That step may initialize or revise the\noptional structured family only after it resolves exact source versions and\nrights records, declarative application scope, applicability authority, Wildo\nobjective bindings, implementation choices, responsibilities, documentation\nrequirements and explicit gaps.\n\nThe transition is not an automatic conversion and must not reinterpret a\nvision sentence as a control mapping or positive compliance claim. Preserve\nthe vision constraint as product intent, record any missing detail as\n`UNDETERMINED` or an explicit gap, and land the structured family as files in the\nspecifications package. Landing is not accepting: the run leaves working edits,\nand acceptance is a later commit. Who makes it is the host's autonomy posture, and only a\nperson's commit reviews what it accepts. Runtime organizations, assignees, evidence,\ncontrol occurrences and assessments remain outside both artifacts.\n\n## The derivation posture\n\n- **Derive from the product and gathered evidence.** Read the existing vision,\n product facts and cumulative regime evidence supplied by the parent choreography.\n The current `compliance-adequacy` verdict establishes readiness. This playbook\n declares no interview: do not fabricate answers or submit arbitrary\n `elicitationAnswers`. Preserve source-backed applicability reasoning and explicit\n uncertainty. Creator-owned facts that remain unresolved need a supported input or\n clarification path; do not ask the creator to reconstruct externally researchable obligations.\n- **Regime derivation rubric (v1).** Use these as the starting triggers, and\n follow up where an answer is thin:\n - **GDPR / UK GDPR** — serving EU/EEA (or UK) individuals, or processing\n their personal data. Triggered by jurisdiction (EU/EEA/UK) + any personal\n data.\n - **HIPAA** — handling US protected health information as, or on behalf of, a\n covered entity or business associate. Triggered by health data + US\n healthcare context.\n - **External assurance commitments** — enterprise customers or the product's own security posture\n require an independent attestation or certification over security / availability /\n confidentiality. Often contractual rather than statutory — capture the requested target as\n externally supplied source metadata when the go-to-market depends on it.\n - **Data residency / sovereignty** — a requirement that certain data stay\n within a region or country. Triggered by residency answers or sector rules;\n record as its own compliance constraint even when it rides alongside GDPR.\n - **Sector & additional regimes** — payment-card, consumer-privacy, children's-data,\n government-security, contractual-assurance and sector-code obligations. Add each that\n the triggers imply; preserve the exact named source only in the later source registry.\n - When the triggers are genuinely absent (no personal data, no regulated\n sector), the honest posture is _no compliance constraints_ — say so and add\n none. Do not invent a regime to look thorough.\n- **One regime, one constraint.** Keep regimes as separate constraint entries\n rather than one omnibus \"must be compliant\" line — the set is read\n downstream, and a merged statement loses which regimes are actually in play.\n\n## What you emit\n\nYou refine the **existing** `VisionSnapshot` in place. Concretely, you\nadd or update entries in `constraints[]`:\n\n- Each applicable regime is one entry with `kind: compliance`.\n- Each entry has a stable kebab-case `ref` prefixed `constraint-`\n (e.g. `constraint-gdpr-eu-personal-data`,\n `constraint-hipaa-us-phi`, `constraint-external-assurance-security`,\n `constraint-data-residency-eu`), unique across the whole `constraints[]` set.\n- Each entry's `statement` is a prose sentence naming the regime and the data /\n jurisdiction it governs. Where the creator gave the source of the limit\n (a customer contract, a specific law), capture it as the constraint's\n rationale.\n\nLeave every non-`compliance` constraint, and every other vision entity,\nuntouched.\n\n**Idempotent — refine, do not duplicate.** Read the vision first. If compliance\nconstraints already exist (the vision-elicitation step, or a prior run of this\nplaybook, may have written some), reconcile against them: update a statement\nthat is now sharper, add a regime that was missed, and remove one only if the\ncreator confirms it never applied. **Match existing constraints by the REGIME\ntheir `statement` names, not by their `ref` slug** — the vision-elicitation step\nwrites compliance prose without following this playbook's ref convention, so a\nGDPR line it left may sit under any slug (`constraint-gdpr`,\n`constraint-eu-data`, …). When you refine a regime that is already present,\n**reuse that entry's existing `ref`** so it updates in place rather than\nforking; only mint a fresh `constraint-<regime>-<scope>` slug for a regime that\nis genuinely new. Re-running this playbook on an already-posture'd vision must\nconverge to one entry per regime, never accumulate near-duplicate\n`constraint-gdpr-*` entries.\n\n## Quality gate\n\nYour refined snapshot is checked by the deterministic `vision-snapshot-valid`\ngate (`validateVisionSnapshot`) before it commits — the same gate the\nvision-elicitation step uses, because you write to the same family. Duplicate\nrefs and malformed refs (a constraint ref that is not kebab-case with the\n`constraint-` prefix) are hard **errors**; the gate rejects them. Emit clean,\nunique refs the first time. Note that a vision with no compliance constraints\nis perfectly valid — an honestly unregulated product should pass the gate with\nnone.\n\nBeyond the deterministic gate, the advisory judge reads the refined vision against\nthree criteria — regime derivation grounded in the evidence, one regime per constraint\nconverging on re-run, and slice discipline — and its verdicts reach the creator's\nreview as notes. A verdict never refuses a landing.\n\n## Approval\n\nThe refined `VisionSnapshot` is presented to the creator for approval before it\nbecomes the committed `vision-brief`. Show the derived compliance posture back\nin plain prose — the list of regimes, each with the data / jurisdiction it\ngoverns and why it applies — and let the creator confirm or correct it.\nCompliance drives real downstream engine capability, audit, and retention\nchoices, so it is worth one explicit human sign-off that the regime set is\nright.\n\n## Runtime context\n\nBefore you start, read the current journey state and scope, and read the\nexisting vision so you refine its compliance constraints rather than writing a\nfresh, disconnected set.\n\n(The existing vision and its current constraints are already in your brief as the `vision-brief`\ninput section.)\n\n## The evidence, and how to use it\n\nYour run carries what sibling steps gathered — source-attributed regime evidence and the adequacy\nverdict that admitted this step. Derive each constraint from the creator's answers AND that\nevidence, never from recollection:\n\n- A regime the evidence establishes as APPLICABLE becomes a `compliance` constraint whose statement\n names the regime, the trigger (jurisdiction / data class / sector / commitment), and what it\n governs — in the evidence's terms.\n- A regime the evidence EXCLUDES is not written as a constraint, and is not silently dropped either:\n where the creator's answers suggested it, the statement of a neighbouring constraint may note the\n exclusion so the decision is legible.\n- A trigger the evidence could NOT establish becomes a constraint stating the OPEN QUESTION, never a\n guessed answer — an unestablished regime stated as settled is the defect this composite exists to\n end.\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",
|
|
42
|
+
"guidance": "# Compliance Posture — Derivation 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.** The regime-derivation rubric below\n> (which triggers imply which regime, how much to capture) is a deliberately\n> explicit first cut meant to be tuned against real runs. Treat it as a\n> starting rubric, not a frozen contract. Crucially, it derives compliance\n> **posture at scaffold depth** — prose constraints, not a per-regime\n> obligation model.\n\n## What this playbook does\n\nYou determine the product's **compliance posture** — which regulatory regimes\nit must be built to satisfy — and record each as a constraint in the\n`compliance-posture` family. The vision-elicitation step may already have named\nthe compliance _seam_ in passing (a single \"we handle EU personal data\" line, a\n`kind: compliance` constraint on the vision). Your job is the focused,\ndeliberate pass over that seam: reason from the product's jurisdictions, the\nclasses of data it handles, and its sector to the concrete set of regimes, and\nwrite each one down as its own constraint with a clear prose statement.\n\nYou do **not** edit the vision, design the domain, or draft requirements. The\nvision is your INPUT: read its facts and the creator's own compliance\nconstraints, and leave it exactly as you found it. Your output is the posture,\na family of its own, so that recording a regime re-opens only the steps that\nread the posture (the compliance conception, the document facts, the build\ndecomposer) and not every step that read the vision.\n\n## The scaffold-depth boundary (read this before you start)\n\nAt this stage compliance is captured as **prose constraints only**. Each\napplicable regime becomes one constraint entry whose `statement` names the\nregime and the data / jurisdiction it governs — e.g. _\"Must be GDPR-compliant\nfor EU/EEA customer personal data.\"_ That is the whole deliverable.\n\nDo **not** build, and do not try to author into the snapshot:\n\n- per-regime control catalogs or obligation graphs (legal-article mappings,\n sector safeguards, external-assurance criteria),\n- data-flow / residency matrices,\n- retention schedules, DPA registries, or audit-config derivations.\n\nThat deep per-regime obligation model is a deliberately deferred later concern.\nIf you catch yourself modelling controls or obligations, **stop** — you have\nleft scaffold depth. Naming the regime seam accurately here is exactly what\nlets that later, deeper step engage. Getting the _set of applicable regimes_\nright, in prose, is the win.\n\n### Transition to structured compliance conception\n\nThis playbook does not write the dedicated `compliance-program` family. Its\naccepted posture constraints are precursor facts for a later, separately\napproved compliance-conception step. That step may initialize or revise the\noptional structured family only after it resolves exact source versions and\nrights records, declarative application scope, applicability authority, Wildo\nobjective bindings, implementation choices, responsibilities, documentation\nrequirements and explicit gaps.\n\nThe transition is not an automatic conversion and must not reinterpret a\nposture sentence as a control mapping or positive compliance claim. Preserve\nthe posture constraint as product intent, record any missing detail as\n`UNDETERMINED` or an explicit gap, and land the structured family as files in the\nspecifications package. Landing is not accepting: the run leaves working edits,\nand acceptance is a later commit. Who makes it is the host's autonomy posture, and only a\nperson's commit reviews what it accepts. Runtime organizations, assignees, evidence,\ncontrol occurrences and assessments remain outside both artifacts.\n\n## The derivation posture\n\n- **Derive from the product and gathered evidence.** Read the existing vision,\n product facts and cumulative regime evidence supplied by the parent choreography.\n The current `compliance-adequacy` verdict establishes readiness. This playbook\n declares no interview: do not fabricate answers or submit arbitrary\n `elicitationAnswers`. Preserve source-backed applicability reasoning and explicit\n uncertainty. Creator-owned facts that remain unresolved need a supported input or\n clarification path; do not ask the creator to reconstruct externally researchable obligations.\n- **Regime derivation rubric (v1).** Use these as the starting triggers, and\n follow up where an answer is thin:\n - **GDPR / UK GDPR** — serving EU/EEA (or UK) individuals, or processing\n their personal data. Triggered by jurisdiction (EU/EEA/UK) + any personal\n data.\n - **HIPAA** — handling US protected health information as, or on behalf of, a\n covered entity or business associate. Triggered by health data + US\n healthcare context.\n - **External assurance commitments** — enterprise customers or the product's own security posture\n require an independent attestation or certification over security / availability /\n confidentiality. Often contractual rather than statutory — capture the requested target as\n externally supplied source metadata when the go-to-market depends on it.\n - **Data residency / sovereignty** — a requirement that certain data stay\n within a region or country. Triggered by residency answers or sector rules;\n record as its own compliance constraint even when it rides alongside GDPR.\n - **Sector & additional regimes** — payment-card, consumer-privacy, children's-data,\n government-security, contractual-assurance and sector-code obligations. Add each that\n the triggers imply; preserve the exact named source only in the later source registry.\n - When the triggers are genuinely absent (no personal data, no regulated\n sector), the honest posture is _no compliance constraints_ — say so and add\n none. Do not invent a regime to look thorough.\n- **One regime, one constraint.** Keep regimes as separate constraint entries\n rather than one omnibus \"must be compliant\" line — the set is read\n downstream, and a merged statement loses which regimes are actually in play.\n\n## What you emit\n\nYou emit the whole posture: a `constraints[]` list, one entry per regime.\n\n- Each entry has a stable kebab-case semantic `slug` naming the regime and its\n scope (e.g. `gdpr-eu-personal-data`, `hipaa-us-phi`,\n `external-assurance-security`, `data-residency-eu`), unique across the list.\n The runtime stamps the `posture-` prefix to make its ref, so do not write it.\n- Each entry's `statement` is a prose sentence naming the regime, its trigger\n and the data / jurisdiction it governs. Its `rationale` names the evidence or\n the creator's fact it rests on (a customer contract, a specific law), or is\n `null`.\n\n**Idempotent — refine, do not duplicate.** When a previous posture is in your\nbrief (the `compliance-posture` input), reconcile against it: update a\nstatement that is now sharper, add a regime that was missed, and remove one\nonly when the evidence now excludes it. When you keep a regime that is already\npresent, **reuse its slug** (its ref without the `posture-` prefix) so it\nupdates in place rather than forking. Re-running this playbook must converge\nto one entry per regime, never accumulate near-duplicate `gdpr-*` entries.\n\n**The creator's own compliance constraints stay on the vision.** When the\nvision carries a `kind: compliance` constraint the creator stated, match it by\nthe REGIME its statement names (its slug follows no convention), and record\nthat regime here with the evidence's sharper statement, or, when the evidence\nexcludes it, make the exclusion legible on a neighbouring constraint. Never\nsilently contradict what the creator said.\n\n## Quality gate\n\nYour posture is checked by the deterministic `validateCompliancePosture`\ngate before it lands. Two slugs that stamp to the same ref are refused at\ngeneration, with the entry named, so emit unique slugs the first time. A\nposture with no constraints is perfectly valid — an honestly unregulated\nproduct should pass the gate with none.\n\nBeyond the deterministic gate, the advisory judge reads the posture against\nthree criteria — regime derivation grounded in the evidence, one regime per constraint\nconverging on re-run, and scaffold depth consistent with the creator's own\nconstraints — and its verdicts reach the creator's review as notes. A verdict\nnever refuses a landing.\n\n## Approval\n\nThe posture is presented to the creator for approval before it becomes the\ncommitted `compliance-posture`. Show the derived compliance posture back\nin plain prose — the list of regimes, each with the data / jurisdiction it\ngoverns and why it applies — and let the creator confirm or correct it.\nCompliance drives real downstream engine capability, audit, and retention\nchoices, so it is worth one explicit human sign-off that the regime set is\nright.\n\n## Runtime context\n\nBefore you start, read the current journey state and scope, the vision (its\nfacts and the creator's compliance constraints), and the previous posture when\nthere is one, so you refine it rather than writing a fresh, disconnected set.\n\n(The vision is in your brief as the `vision-brief` input section, and a previous\nposture, when one has landed, as the `compliance-posture` section.)\n\n## The evidence, and how to use it\n\nYour run carries what sibling steps gathered — source-attributed regime evidence and the adequacy\nverdict that admitted this step. Derive each constraint from the creator's answers AND that\nevidence, never from recollection:\n\n- A regime the evidence establishes as APPLICABLE becomes a posture constraint whose statement\n names the regime, the trigger (jurisdiction / data class / sector / commitment), and what it\n governs — in the evidence's terms.\n- A regime the evidence EXCLUDES is not written as a constraint, and is not silently dropped either:\n where the creator's answers suggested it, the statement of a neighbouring constraint may note the\n exclusion so the decision is legible.\n- A trigger the evidence could NOT establish becomes a constraint stating the OPEN QUESTION, never a\n guessed answer — an unestablished regime stated as settled is the defect this composite exists to\n end.\n- Every `openFacts` entry of the adequacy verdict is such an open question: a fact about the product or\n its operator that no research could settle, or a regime conditional on a fact declared open. Record\n each as its own constraint naming the fact and what it decides (*\"Whether the vendor is processor for\n customer CRM data is open; it decides whether Art. 28 processor terms or controller duties attach.\"*).\n The gate admitted you WITH them open on purpose (#3385); do not drop one because it is unresolved.\n- A vision compliance constraint that states an OPEN regulated-domain question (the creator left it not\n decided yet, #3484) is such an open question too. Carry it as its own constraint naming the question and\n the regimes it decides; never settle it from the other answers, in either direction.\n- The same holds for the `jurisdictions` answer left not decided yet (#3484): record where the users are as an open\n question naming the regimes it decides (territorial scope turns on it), and never assume a place.\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",
|
|
40
43
|
"skillRefs": [],
|
|
41
44
|
"skillBodyRefs": [],
|
|
45
|
+
"derivedFromAnswers": [],
|
|
42
46
|
"contextSources": [],
|
|
43
47
|
"draftableDocumentDefinitionRefs": [],
|
|
44
48
|
"suspendsForClarification": false,
|
|
@@ -28,6 +28,7 @@
|
|
|
28
28
|
"guidance": "# Compliance Research — gather the regime evidence\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\nYou are the **researcher**. Your one job is to find out which regimes plausibly\napply to this product and report it with sources. You do not decide the posture,\nauthor constraints, or touch any file — a sibling does that, from what you bring\nback.\n\n## Why this step exists\n\nThe playbook that records the compliance posture used to derive it from nine\ninterview answers plus what the model remembered about the law. Recollection is\nconfident, fluent, and wrong in exactly the cases that matter here: thresholds\nchange, regimes gain territorial reach, sector rules turn on definitions no one\nremembers precisely — and a wrongly excluded regime is a legal statement about the\nproduct, not a stale price.\n\nThis step exists so the posture rests on pages someone actually read.\n\n## What counts as a regime\n\nA regime is **public law or a regulator's instrument** — a statute, a regulation, a\ndirective as transposed, a supervisory authority's binding guidance. Those are what\nyou research, name and quote: they bind the product whether or not anyone agreed to\nthem, so applicability is a question of fact you can settle from a source.\n\nA **voluntary security certification or attestation framework is not a regime.** It\nbinds only where the creator has committed to it, which makes it an elicited fact\nrather than a researched one — so there is nothing for you to establish and no\nthreshold to test. Report the whole class as one line (\"voluntary\nsecurity-certification and attestation frameworks — commitments, not legal\nobligations; none committed\" or whatever the creator's answers say), and do not name\nan individual proprietary standard or reproduce any of its control identifiers: those\ncatalogues are licensed material, and this evidence store is committed into the\napplication's repository.\n\nThe distinction is not bookkeeping. A list that mixes the two invites a posture to\nread a certification as an obligation the product is failing, which is a false legal\nstatement about the product — the exact defect this lane exists to prevent, arriving\nfrom the other direction.\n\n## What to establish\n\nWork the objective you were given — it was composed for THIS round, and on a later\nround it names what the earlier rounds could not establish. Where it is broad,\nthese are the questions worth answering, per candidate regime:\n\n1. **The applicability trigger, exactly.** What makes it apply — territorial scope,\n data classes, sector, size thresholds — quoted or closely paraphrased from an\n authoritative source, with enough precision that a reader can test THIS product\n against it. Name a customer commitment only where the regime's OWN text makes one\n part of its trigger; a commitment is otherwise an elicited fact, and treating it as\n a research question is what pulled voluntary certification into this lane.\n2. **Whether THIS product trips it**, given the vision's jurisdictions, data\n classes and sector — stated as your reading, distinct from the trigger itself.\n3. **What the regime obliges at posture level.** One or two sentences — the deep\n obligation model is a later concern; the posture needs \"applies / does not\n apply / cannot be established, because …\".\n\n## How to report\n\n- **Authoritative sources first.** A regulator's page or the official text over any\n vendor summary; name the source beside every claim, with its URL.\n- **Say what you could NOT establish.** The gaps aim the next round; hiding them\n produces a posture that reads complete and is not — the exact defect this lane\n replaces.\n- **Never pad.** A regime you found no trigger for is one line, not a paragraph.\n",
|
|
29
29
|
"skillRefs": [],
|
|
30
30
|
"skillBodyRefs": [],
|
|
31
|
+
"derivedFromAnswers": [],
|
|
31
32
|
"contextSources": [],
|
|
32
33
|
"draftableDocumentDefinitionRefs": [],
|
|
33
34
|
"suspendsForClarification": false,
|
|
@@ -22,7 +22,9 @@ which is the lane's closing decision.
|
|
|
22
22
|
The chain, each leaf gated by the families the ones before it land:
|
|
23
23
|
|
|
24
24
|
- **`top_down.vision-elicitation`** — the vision brief, from the creator's own
|
|
25
|
-
answers.
|
|
25
|
+
answers. This lane opens only once a valid vision is on record: the creation runs the
|
|
26
|
+
interview in a round of its own, so the compliance lane can start beside this one. Here
|
|
27
|
+
it is offered only as a REFRESH, when the creator's vision answers changed.
|
|
26
28
|
- **`top_down.market-analysis`** — a NESTED LANE, not a leaf: it gathers web evidence,
|
|
27
29
|
judges whether it is enough, and lands the `market-snapshot` only once the verdict is
|
|
28
30
|
`adequate`, re-searching against the gaps the gate named for as long as it needs. Its
|
|
@@ -47,6 +49,11 @@ needed by nothing downstream of this lane:
|
|
|
47
49
|
- **`top_down.brand-identity`** — the visual identity, from the creator's answers. Its
|
|
48
50
|
`brand-name` is a CHOICE among the screened names, so it runs after the naming lane.
|
|
49
51
|
- **`top_down.risk-register`** — the register the assurance mechanisms read.
|
|
52
|
+
- **`top_down.service-method`** — a service firm's method: the services it sells, how each case
|
|
53
|
+
is worked, decided and delivered. Needs the vision alone, so it usually runs first beside the
|
|
54
|
+
chain; offer it again as a REFRESH as the market snapshot, the requirements and the business
|
|
55
|
+
model land, since each sharpens it (the business model is what settles per-case pricing). It
|
|
56
|
+
is not applicable on a B2B SaaS or an internal tool until a feature line needs it.
|
|
50
57
|
|
|
51
58
|
Nothing above is a sequence. Each child declares what it needs, and the runtime
|
|
52
59
|
re-computes what may run after every round. That is what makes the lane re-runnable
|
|
@@ -62,8 +69,8 @@ vision whole, the others as a map of what exists — and the children that may r
|
|
|
62
69
|
since it landed is not offered at all. Every option is marked FIRST RUN, or REFRESH
|
|
63
70
|
with the input that moved and the run that moved it. Prefer first runs; take a
|
|
64
71
|
refresh when the change it names matters to that child.
|
|
65
|
-
- **Independent children share a round.** The brand identity
|
|
66
|
-
ride beside the chain; several research lanes with genuinely different objectives
|
|
72
|
+
- **Independent children share a round.** The brand identity, the risk register and a
|
|
73
|
+
firm's method ride beside the chain; several research lanes with genuinely different objectives
|
|
67
74
|
return more than one asked everything.
|
|
68
75
|
- **A child whose interview is unanswered is not offered.** The dossier answers the
|
|
69
76
|
creator's questions per leaf; a leaf the dossier does not cover waits for the creator,
|
|
@@ -1,9 +1,16 @@
|
|
|
1
1
|
{
|
|
2
2
|
"ref": "top_down.definition",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.2.0",
|
|
4
4
|
"phase": "top_down",
|
|
5
|
-
"intent": "Drive the top-down DEFINITION of the application as one lane: from an answered vision through market evidence, the market snapshot, the value proposition, the requirements, the capability map, the business model and the roadmap, to the phase gate — with the brand naming (screened name proposals), the brand identity
|
|
6
|
-
"preconditions": [
|
|
5
|
+
"intent": "Drive the top-down DEFINITION of the application as one lane: from an answered vision through market evidence, the market snapshot, the value proposition, the requirements, the capability map, the business model and the roadmap, to the phase gate — with the brand naming (screened name proposals), the brand identity, the risk register and the firm's method (its services, decisions and signatories; on a service firm, or wherever a feature line needs it) beside the chain. An umbrella: it authors nothing itself; every child declares what it needs and the runtime recomputes what may run after each round, so the order is the leaves' preconditions and never a list. Select what is MISSING from the accepted truth shown to you. A child already on record whose inputs have not changed since it landed is not offered at all; every option is marked FIRST RUN, or REFRESH with the input that moved. Prefer first runs; take a refresh when its changed input matters to it. Run independent children in the same round (brand naming or the brand identity, and the risk register or the firm's method beside the chain; several research lanes with different objectives). Run the phase gate once the roadmap is on record, and STOP after it has run — its verdict is this lane's closing decision, and it is not re-run in the same run. A child whose interview the creator has not answered is not offered; run everything else and stop when nothing eligible advances the definition.",
|
|
6
|
+
"preconditions": [
|
|
7
|
+
{
|
|
8
|
+
"kind": "artifact_valid",
|
|
9
|
+
"selector": {
|
|
10
|
+
"family": "vision-brief"
|
|
11
|
+
}
|
|
12
|
+
}
|
|
13
|
+
],
|
|
7
14
|
"inputs": [
|
|
8
15
|
{
|
|
9
16
|
"family": "vision-brief"
|
|
@@ -44,9 +51,10 @@
|
|
|
44
51
|
}
|
|
45
52
|
],
|
|
46
53
|
"method": {
|
|
47
|
-
"guidance": "# The Definition Lane — the umbrella\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\nThis playbook produces nothing itself. It drives the leaves that DEFINE the\napplication — what it is, for whom, against which market, delivering which\nrequirements, in which order, sold how — and it ends on the phase gate's verdict,\nwhich is the lane's closing decision.\n\n## The children, and why the order is not written here\n\nThe chain, each leaf gated by the families the ones before it land:\n\n- **`top_down.vision-elicitation`** — the vision brief, from the creator's own\n answers.
|
|
54
|
+
"guidance": "# The Definition Lane — the umbrella\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\nThis playbook produces nothing itself. It drives the leaves that DEFINE the\napplication — what it is, for whom, against which market, delivering which\nrequirements, in which order, sold how — and it ends on the phase gate's verdict,\nwhich is the lane's closing decision.\n\n## The children, and why the order is not written here\n\nThe chain, each leaf gated by the families the ones before it land:\n\n- **`top_down.vision-elicitation`** — the vision brief, from the creator's own\n answers. This lane opens only once a valid vision is on record: the creation runs the\n interview in a round of its own, so the compliance lane can start beside this one. Here\n it is offered only as a REFRESH, when the creator's vision answers changed.\n- **`top_down.market-analysis`** — a NESTED LANE, not a leaf: it gathers web evidence,\n judges whether it is enough, and lands the `market-snapshot` only once the verdict is\n `adequate`, re-searching against the gaps the gate named for as long as it needs. Its\n evidence loop is its own business; this lane sees only that a market snapshot landed.\n- **`top_down.value-proposition`** — refines the same snapshot: benefits, tones of\n voice, one positioning pillar per targeted ICP.\n- **`top_down.requirements-definition`** — the requirements, from vision and market.\n- **`top_down.capability-map`** — benefit → feature edges on the snapshot, and the\n feature drafts.\n- **`top_down.business-model`** — revenue model and pricing plans, from the creator's\n pricing intent.\n- **`top_down.scope-roadmap`** — the phases that deliver or defer the requirements and\n the success criteria.\n- **`top_down.phase-gate`** — five criteria over the coherence report. Lands nothing;\n its verdict is what this lane ends on.\n\nBeside the chain, needing the vision (and the business model, for the register) and\nneeded by nothing downstream of this lane:\n\n- **`top_down.brand-naming`** — a nested lane: proposes names and runs a minimal trademark\n screening of each, landing the `brand-name-screening`. Needs the market snapshot.\n- **`top_down.brand-identity`** — the visual identity, from the creator's answers. Its\n `brand-name` is a CHOICE among the screened names, so it runs after the naming lane.\n- **`top_down.risk-register`** — the register the assurance mechanisms read.\n- **`top_down.service-method`** — a service firm's method: the services it sells, how each case\n is worked, decided and delivered. Needs the vision alone, so it usually runs first beside the\n chain; offer it again as a REFRESH as the market snapshot, the requirements and the business\n model land, since each sharpens it (the business model is what settles per-case pricing). It\n is not applicable on a B2B SaaS or an internal tool until a feature line needs it.\n\nNothing above is a sequence. Each child declares what it needs, and the runtime\nre-computes what may run after every round. That is what makes the lane re-runnable\non an application where most of it exists: whatever is on record satisfies the gates of\nwhatever is not.\n\n## Selecting the next children\n\nThe selector is shown the accepted truth for the families this lane declares — the\nvision whole, the others as a map of what exists — and the children that may run.\n\n- **Missing beats present.** A child already on record whose inputs have not changed\n since it landed is not offered at all. Every option is marked FIRST RUN, or REFRESH\n with the input that moved and the run that moved it. Prefer first runs; take a\n refresh when the change it names matters to that child.\n- **Independent children share a round.** The brand identity, the risk register and a\n firm's method ride beside the chain; several research lanes with genuinely different objectives\n return more than one asked everything.\n- **A child whose interview is unanswered is not offered.** The dossier answers the\n creator's questions per leaf; a leaf the dossier does not cover waits for the creator,\n and the lane runs everything else it can.\n- **The phase gate runs once, last, then the lane stops.** It lands nothing and returns\n nothing the runtime can mark delivered, so the round history is the record that it\n ran.\n\n## Composing an objective for a child\n\nEach dispatch carries an objective composed for that round. For a research child the\nmarket umbrella's rule holds: the first round broad, a later round naming the gap the\ngate named. For a chain leaf the objective names what changed upstream since its output\nlast landed — a re-derived market snapshot, a revised vision — so the leaf refines\nrather than restarts.\n\n## When to stop\n\nStop when the phase gate has run: its verdict is the decision. Stop also when nothing\neligible advances the definition — every remaining child is waiting for the creator, or\nthe evidence gate has named the same gap twice and a further round could not close it.\nSay which, in the rationale.\n\n## What the phase gate's verdict re-opens\n\nThe lane declares this table, and the runtime applies it: a GAP on one of the first four\ncriteria offers the mapped leaf again, even though it already landed in this run. When a\nleaf you have already seen land is eligible again after the gate, that is this loop-back,\nnot churn. Re-run that leaf against the gate's rationale for the faulted criterion, then run\nthe gate again. A PASS re-opens nothing, and CONCERN or INDETERMINATE re-open nothing\neither: re-deriving a leaf does not answer advice, and it does not produce evidence.\n\n| criterion | re-opens |\n|---|---|\n| requirement coverage | `top_down.scope-roadmap` |\n| success-criterion coverage | `top_down.scope-roadmap` |\n| capability completeness | `top_down.capability-map` |\n| positioning / ICP coherence | `top_down.value-proposition` |\n| compliance presence | the compliance lane, which this lane does not admit — the root re-opens it, from this lane's exported verdict |\n\n## What the creator reviews\n\nThe definition set, family by family, exactly as each leaf's own review guide says —\nand the phase gate's verdict, which is the one decision this lane ends on: accept the\ndefinition, or send it back to the leaf the verdict names.\n",
|
|
48
55
|
"skillRefs": [],
|
|
49
56
|
"skillBodyRefs": [],
|
|
57
|
+
"derivedFromAnswers": [],
|
|
50
58
|
"contextSources": [],
|
|
51
59
|
"draftableDocumentDefinitionRefs": [],
|
|
52
60
|
"choreography": {
|
|
@@ -62,7 +70,8 @@
|
|
|
62
70
|
"top_down.vision-elicitation",
|
|
63
71
|
"top_down.brand-naming",
|
|
64
72
|
"top_down.brand-identity",
|
|
65
|
-
"top_down.risk-register"
|
|
73
|
+
"top_down.risk-register",
|
|
74
|
+
"top_down.service-method"
|
|
66
75
|
],
|
|
67
76
|
"maximumIterations": 20,
|
|
68
77
|
"maximumLanesPerIteration": 3,
|
|
@@ -32,9 +32,14 @@ critic, and a FINALIZE pass when the critique asks for one — then promotes the
|
|
|
32
32
|
|
|
33
33
|
- **Overwrite a human-edited charter.** A committed charter carrying an `authored` block is never
|
|
34
34
|
replaced; the accept step refuses and the run reports it.
|
|
35
|
-
- **Re-derive a
|
|
36
|
-
|
|
37
|
-
|
|
35
|
+
- **Re-derive a current charter.** A committed charter is derived again only when one of its shaping inputs
|
|
36
|
+
changed AFTER it (written by a later run, edited, or committed later): the brand's visual tone, the market, the vision, the requirements, the business
|
|
37
|
+
model, the brand's promoted assets or the design-system configuration, whichever that role reads. The
|
|
38
|
+
board then offers this step as a refresh naming the inputs that moved, and the run reports those roles
|
|
39
|
+
as derived again. Each input is dated from the file the persona reads, so promoting a logo moves only
|
|
40
|
+
the roles that read the promoted assets.
|
|
41
|
+
- **Re-derive a drifted charter a person edited.** It is named in the run's report with the inputs that
|
|
42
|
+
moved, for the person to update by hand.
|
|
38
43
|
- **Fail on a role whose inputs are not landed.** A role needing the brand brief on an application with
|
|
39
44
|
no brand yet is REPORTED as waiting, with the families it waits on. The step re-runs when they land.
|
|
40
45
|
|
|
@@ -54,3 +59,5 @@ therefore which roles are derivable now.
|
|
|
54
59
|
and `index.ts` lists every one of them.
|
|
55
60
|
- `companion-exports.ts` wires `expertPersonaCharters` onto the aggregator.
|
|
56
61
|
- The eligibility board no longer reports `PANEL_UNSTAFFED` for `bottom_up.placement-plan`.
|
|
62
|
+
- After the run, the board offers this step as current: no charter is older than an input it reads, apart
|
|
63
|
+
from those a person edited, which the run named, and those still waiting on a family.
|
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
{
|
|
2
2
|
"ref": "top_down.expert-personas",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.3.0",
|
|
4
4
|
"phase": "top_down",
|
|
5
|
-
"intent": "Staff every expert panel the catalog convenes: derive and accept an application-specific charter for each framework expert role that a deliberated playbook (`method.deliberation`) or a companion generation step (the logo panel) seats, grounded in the application's own vision, market, requirements, business model and brand. Idempotent: a role whose charter is committed is left alone (a human-edited
|
|
5
|
+
"intent": "Staff every expert panel the catalog convenes: derive and accept an application-specific charter for each framework expert role that a deliberated playbook (`method.deliberation`) or a companion generation step (the logo panel) seats, grounded in the application's own vision, market, requirements, business model and brand. Idempotent: a role whose charter is committed and current is left alone, a committed charter older than one of its shaping inputs is derived again (a human-edited one is never overwritten and is named for the person to update, #2819), and a role whose shaping inputs have not landed yet is REPORTED as waiting rather than failing the run. Before this step existed the panel's staffing was not a journey step at all — every deliberated playbook failed closed at bind time on an application whose charters nobody had curled in by hand (#572).",
|
|
6
6
|
"preconditions": [
|
|
7
7
|
{
|
|
8
8
|
"kind": "artifact_exists",
|
|
@@ -42,9 +42,10 @@
|
|
|
42
42
|
],
|
|
43
43
|
"stepOutputs": [],
|
|
44
44
|
"method": {
|
|
45
|
-
"guidance": "# Expert personas — staff the panels the catalog convenes\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 step does\n\nSeveral steps of the creation journey are DECIDED BY A PANEL rather than by a single generation:\n`bottom_up.placement-plan` convenes an information architect and a design-system guardian, the logo\ngeneration step convenes an art director, a brand strategist and a design-system guardian. A panel is\nbuilt from **expert-persona charters** — one committed charter per framework expert role, derived from\nthis application's own vision, market, requirements, business model and brand, so a reviewer speaks\nfor THIS product rather than for a generic one.\n\nThis step derives and accepts those charters. It is runner-owned: no prompt is composed here. For every\nrole the catalog convenes (read off every playbook's `method.deliberation` and off the generation\nsteps' own panels), it runs the companion's derive → accept flow — a DRAFT, a CRITIQUE by a dedicated\ncritic, and a FINALIZE pass when the critique asks for one — then promotes the proposal into\n`specifications/src/personas/<role>.charter.generated.ts`, regenerates the aggregator and wires the\n`expertPersonaCharters` companion-exports slot.\n\n## What it will not do\n\n- **Overwrite a human-edited charter.** A committed charter carrying an `authored` block is never\n replaced; the accept step refuses and the run reports it.\n- **Re-derive a
|
|
45
|
+
"guidance": "# Expert personas — staff the panels the catalog convenes\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 step does\n\nSeveral steps of the creation journey are DECIDED BY A PANEL rather than by a single generation:\n`bottom_up.placement-plan` convenes an information architect and a design-system guardian, the logo\ngeneration step convenes an art director, a brand strategist and a design-system guardian. A panel is\nbuilt from **expert-persona charters** — one committed charter per framework expert role, derived from\nthis application's own vision, market, requirements, business model and brand, so a reviewer speaks\nfor THIS product rather than for a generic one.\n\nThis step derives and accepts those charters. It is runner-owned: no prompt is composed here. For every\nrole the catalog convenes (read off every playbook's `method.deliberation` and off the generation\nsteps' own panels), it runs the companion's derive → accept flow — a DRAFT, a CRITIQUE by a dedicated\ncritic, and a FINALIZE pass when the critique asks for one — then promotes the proposal into\n`specifications/src/personas/<role>.charter.generated.ts`, regenerates the aggregator and wires the\n`expertPersonaCharters` companion-exports slot.\n\n## What it will not do\n\n- **Overwrite a human-edited charter.** A committed charter carrying an `authored` block is never\n replaced; the accept step refuses and the run reports it.\n- **Re-derive a current charter.** A committed charter is derived again only when one of its shaping inputs\n changed AFTER it (written by a later run, edited, or committed later): the brand's visual tone, the market, the vision, the requirements, the business\n model, the brand's promoted assets or the design-system configuration, whichever that role reads. The\n board then offers this step as a refresh naming the inputs that moved, and the run reports those roles\n as derived again. Each input is dated from the file the persona reads, so promoting a logo moves only\n the roles that read the promoted assets.\n- **Re-derive a drifted charter a person edited.** It is named in the run's report with the inputs that\n moved, for the person to update by hand.\n- **Fail on a role whose inputs are not landed.** A role needing the brand brief on an application with\n no brand yet is REPORTED as waiting, with the families it waits on. The step re-runs when they land.\n\n## Cost, so it is scheduled knowingly\n\nA derivation is an agentic three-pass protocol over the application's own artifacts: measured at about\n200 seconds per role on a real application. Five roles is a quarter of an hour. Submit the run detached.\n\n## What you read\n\nThe current journey state this run is given, to see which families have landed and\ntherefore which roles are derivable now.\n\n## Verification\n\n- `specifications/src/personas/` holds one `*.charter.generated.ts` per role the run reports as derived,\n and `index.ts` lists every one of them.\n- `companion-exports.ts` wires `expertPersonaCharters` onto the aggregator.\n- The eligibility board no longer reports `PANEL_UNSTAFFED` for `bottom_up.placement-plan`.\n- After the run, the board offers this step as current: no charter is older than an input it reads, apart\n from those a person edited, which the run named, and those still waiting on a family.\n",
|
|
46
46
|
"skillRefs": [],
|
|
47
47
|
"skillBodyRefs": [],
|
|
48
|
+
"derivedFromAnswers": [],
|
|
48
49
|
"contextSources": [],
|
|
49
50
|
"draftableDocumentDefinitionRefs": [],
|
|
50
51
|
"suspendsForClarification": false,
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"ref": "top_down.feature-drafts",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.1",
|
|
4
4
|
"phase": "top_down",
|
|
5
5
|
"intent": "Draft the product capabilities an application needs from its accepted requirements and vision, for an application whose line has no market: one spec-first, ref-less feature specification draft per capability the requirements call for, each tracing to the requirements it serves.",
|
|
6
6
|
"preconditions": [
|
|
@@ -42,6 +42,7 @@
|
|
|
42
42
|
"spec-feature-update"
|
|
43
43
|
],
|
|
44
44
|
"skillBodyRefs": [],
|
|
45
|
+
"derivedFromAnswers": [],
|
|
45
46
|
"contextSources": [],
|
|
46
47
|
"draftableDocumentDefinitionRefs": [],
|
|
47
48
|
"suspendsForClarification": false,
|
|
@@ -40,8 +40,10 @@ Name the GAP, not the feeling. `"no pricing found for any competitor"` sends the
|
|
|
40
40
|
round somewhere; `"the evidence is thin"` sends it nowhere and it comes back the same.
|
|
41
41
|
|
|
42
42
|
Each gap should be answerable. If a gap is genuinely unanswerable from the public web
|
|
43
|
-
— private pricing, a market nobody writes about —
|
|
44
|
-
than emitting a gap that will fail again.
|
|
43
|
+
— private pricing, a market nobody writes about — put it in `openFacts` (the fact, and
|
|
44
|
+
what it would decide) rather than emitting a gap that will fail again. Only what research
|
|
45
|
+
can still find is a gap; an INSUFFICIENT verdict with no gap is refused, and with every
|
|
46
|
+
remaining item in `openFacts` the verdict is ADEQUATE. A loop that keeps asking for something that
|
|
45
47
|
does not exist is worse than a snapshot honestly marked incomplete.
|
|
46
48
|
|
|
47
49
|
## Be willing to say ADEQUATE
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"ref": "top_down.market-evidence-adequacy",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.2",
|
|
4
4
|
"phase": "top_down",
|
|
5
5
|
"intent": "Judge whether the evidence gathered so far is ENOUGH to derive a market snapshot from, and when it is not, name precisely what is missing so the next research round is aimed rather than repeated. Returns a verdict a sibling's precondition READS; it authors nothing and lands nothing.",
|
|
6
6
|
"preconditions": [
|
|
@@ -19,16 +19,17 @@
|
|
|
19
19
|
{
|
|
20
20
|
"ref": "evidence-adequacy",
|
|
21
21
|
"schemaRef": "saas-models:MetaWorkflow_EvidenceAdequacy",
|
|
22
|
-
"condensation": "A verdict
|
|
22
|
+
"condensation": "A verdict; the gaps a further research round can still close (none when ADEQUATE); the open facts no research can close, each with what it decides; and a rationale grounded in what was actually gathered.",
|
|
23
23
|
"description": "The adequacy gate the produce step is conditioned on."
|
|
24
24
|
}
|
|
25
25
|
],
|
|
26
26
|
"method": {
|
|
27
|
-
"guidance": "# Evidence Adequacy — is this enough to derive from?\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\nYou are the **gate**. You judge whether the evidence gathered so far is enough to\nderive a market snapshot from — and when it is not, you say precisely what is missing.\n\n## The question you answer\n\nNot \"is this good research?\" and not \"is this market attractive?\". Only:\n\n> **Could a competent analyst write a defensible market snapshot from what is here,\n> without inventing anything?**\n\nIf yes, the verdict is `adequate`. If no, it is `insufficient`, and your `gaps` are\nwhat the next research round will be aimed at.\n\n## What makes evidence adequate\n\n- **The category is named by a source**, not assumed.\n- **At least a few real competing alternatives**, each with something concrete about\n what it costs or how it is sold. \"There are competitors\" is not evidence.\n- **Buyer language observed rather than imagined** — at least some of how the people\n with this problem describe it.\n- **Claims carry sources**, and the unsourced ones are marked as such.\n\n## What makes it insufficient, and how to say so\n\nName the GAP, not the feeling. `\"no pricing found for any competitor\"` sends the next\nround somewhere; `\"the evidence is thin\"` sends it nowhere and it comes back the same.\n\nEach gap should be answerable. If a gap is genuinely unanswerable from the public web\n— private pricing, a market nobody writes about —
|
|
27
|
+
"guidance": "# Evidence Adequacy — is this enough to derive from?\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\nYou are the **gate**. You judge whether the evidence gathered so far is enough to\nderive a market snapshot from — and when it is not, you say precisely what is missing.\n\n## The question you answer\n\nNot \"is this good research?\" and not \"is this market attractive?\". Only:\n\n> **Could a competent analyst write a defensible market snapshot from what is here,\n> without inventing anything?**\n\nIf yes, the verdict is `adequate`. If no, it is `insufficient`, and your `gaps` are\nwhat the next research round will be aimed at.\n\n## What makes evidence adequate\n\n- **The category is named by a source**, not assumed.\n- **At least a few real competing alternatives**, each with something concrete about\n what it costs or how it is sold. \"There are competitors\" is not evidence.\n- **Buyer language observed rather than imagined** — at least some of how the people\n with this problem describe it.\n- **Claims carry sources**, and the unsourced ones are marked as such.\n\n## What makes it insufficient, and how to say so\n\nName the GAP, not the feeling. `\"no pricing found for any competitor\"` sends the next\nround somewhere; `\"the evidence is thin\"` sends it nowhere and it comes back the same.\n\nEach gap should be answerable. If a gap is genuinely unanswerable from the public web\n— private pricing, a market nobody writes about — put it in `openFacts` (the fact, and\nwhat it would decide) rather than emitting a gap that will fail again. Only what research\ncan still find is a gap; an INSUFFICIENT verdict with no gap is refused, and with every\nremaining item in `openFacts` the verdict is ADEQUATE. A loop that keeps asking for something that\ndoes not exist is worse than a snapshot honestly marked incomplete.\n\n## Be willing to say ADEQUATE\n\nThe failure mode of a gate is not being too lenient. It is holding out for completeness\nthat no public source can provide, so the loop spends its rounds and stops on a ceiling\nwith nothing produced. Enough is enough; perfect is not the bar.\n\n## What you do not do\n\nYou author nothing, you land nothing, and you do not write the snapshot. Your verdict\nis read by the step that does.\n",
|
|
28
28
|
"skillRefs": [
|
|
29
29
|
"market-snapshot-validation"
|
|
30
30
|
],
|
|
31
31
|
"skillBodyRefs": [],
|
|
32
|
+
"derivedFromAnswers": [],
|
|
32
33
|
"contextSources": [],
|
|
33
34
|
"draftableDocumentDefinitionRefs": [],
|
|
34
35
|
"suspendsForClarification": false,
|
|
@@ -156,6 +156,9 @@ So:
|
|
|
156
156
|
- An entity you INFERRED carries that word, and `confidence` set honestly — `LOW` for
|
|
157
157
|
a hypothesis, not `HIGH` because it reads well.
|
|
158
158
|
- An entity the evidence did not cover is still authorable, and says so.
|
|
159
|
+
- Each `openFacts` entry of the adequacy verdict is something no research could settle (a
|
|
160
|
+
fact about the product or its creator's decision). Where it bears on an entity, say it is
|
|
161
|
+
open on that entity, never fill it in.
|
|
159
162
|
|
|
160
163
|
Omit `authoredMetadata` only where the content is so self-evident that provenance
|
|
161
164
|
would be noise. A competitor's price is never that.
|