@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
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
{
|
|
2
2
|
"ref": "top_down.compliance-analysis",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.2.0",
|
|
4
4
|
"phase": "top_down",
|
|
5
|
-
"intent": "Establish the compliance posture by gathering regime EVIDENCE from authoritative sources, judging whether it is enough, and recording the applicable regimes
|
|
5
|
+
"intent": "Establish the compliance posture by gathering regime EVIDENCE from authoritative sources, judging whether it is enough, and recording the applicable regimes in the compliance posture only once it is. An umbrella: it authors nothing itself — its deliverable is what its children land, and the order between them is decided by their own preconditions rather than declared here.",
|
|
6
6
|
"preconditions": [
|
|
7
7
|
{
|
|
8
8
|
"kind": "artifact_valid",
|
|
@@ -19,7 +19,7 @@
|
|
|
19
19
|
"outputs": [],
|
|
20
20
|
"stepOutputs": [],
|
|
21
21
|
"method": {
|
|
22
|
-
"guidance": "# Compliance Analysis — the evidence-grounded posture composite\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 **conductor's scheduler**, not an author. This composite exists so the\napplication's compliance posture rests on regime texts and regulator pages someone\nactually read — not on what a model remembers about the law, which is confident,\nfluent, and stale in exactly the cases that carry liability.\n\n## The shape\n\nThree children, self-ordered by their own preconditions:\n\n1. **compliance-research** — a read-only web lane gathering regime evidence for the\n jurisdictions, data classes and sector the vision (and the creator's answers)\n put in scope. Returns a condensed, source-attributed brief.\n2. **compliance-evidence-adequacy** — judges whether the evidence is ENOUGH to\n state a posture from, and when it is not, names precisely what is missing so the\n next research round is aimed rather than repeated.\n3. **compliance-posture** — the artifact-producing child: records each applicable\n regime as a
|
|
22
|
+
"guidance": "# Compliance Analysis — the evidence-grounded posture composite\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 **conductor's scheduler**, not an author. This composite exists so the\napplication's compliance posture rests on regime texts and regulator pages someone\nactually read — not on what a model remembers about the law, which is confident,\nfluent, and stale in exactly the cases that carry liability.\n\n## The shape\n\nThree children, self-ordered by their own preconditions:\n\n1. **compliance-research** — a read-only web lane gathering regime evidence for the\n jurisdictions, data classes and sector the vision (and the creator's answers)\n put in scope. Returns a condensed, source-attributed brief.\n2. **compliance-evidence-adequacy** — judges whether the evidence is ENOUGH to\n state a posture from, and when it is not, names precisely what is missing so the\n next research round is aimed rather than repeated.\n3. **compliance-posture** — the artifact-producing child: records each applicable\n regime as a constraint in the `compliance-posture` family, deriving from the\n creator's elicitation answers AND the gathered evidence, only once the adequacy\n gate has returned ADEQUATE.\n\n## What a round's research objective should name\n\nCompose each research objective for THIS round: on the first pass, the candidate\nregimes the vision's jurisdictions/data/sector suggest (verify applicability\ntriggers against authoritative sources — regulator pages, official texts, not\nblogs); on later passes, exactly the gaps the adequacy verdict named. Never re-ask\nwhat a prior round established — its evidence is in the step results.\n",
|
|
23
23
|
"skillRefs": [],
|
|
24
24
|
"skillBodyRefs": [],
|
|
25
25
|
"elicitation": {
|
|
@@ -29,73 +29,108 @@
|
|
|
29
29
|
"question": "Does the product store, process, or transmit personal data or otherwise regulated data (health, financial, biometric, children's, government) — either from end users or on behalf of customers?",
|
|
30
30
|
"kind": "confirm",
|
|
31
31
|
"depth": "detail",
|
|
32
|
-
"regulatedDomain": true
|
|
32
|
+
"regulatedDomain": true,
|
|
33
|
+
"nonAnswers": [
|
|
34
|
+
"deferred"
|
|
35
|
+
]
|
|
33
36
|
},
|
|
34
37
|
{
|
|
35
38
|
"ref": "data-classes",
|
|
36
39
|
"question": "Which classes of sensitive data does the product touch? List them (e.g. names/emails, health records, payment card data, government IDs, precise location, employee data). Answer \"none\" if it handles no personal or sensitive data.",
|
|
37
40
|
"kind": "free_text",
|
|
38
41
|
"depth": "detail",
|
|
39
|
-
"regulatedDomain": true
|
|
42
|
+
"regulatedDomain": true,
|
|
43
|
+
"nonAnswers": [
|
|
44
|
+
"not_applicable",
|
|
45
|
+
"deferred"
|
|
46
|
+
]
|
|
40
47
|
},
|
|
41
48
|
{
|
|
42
49
|
"ref": "vendor-establishment",
|
|
43
50
|
"question": "Where is the VENDOR established — the legal entity (or intended entity) operating the product, its country/region, and where is the product hosted or planned to be hosted? Territorial-scope tests (GDPR Art. 3, UK GDPR, CCPA \"doing business\") turn on the vendor's establishment and conduct, not only on where users live. Answer \"not yet decided\" for whatever is genuinely open.",
|
|
44
51
|
"kind": "free_text",
|
|
45
52
|
"depth": "essential",
|
|
46
|
-
"regulatedDomain": true
|
|
53
|
+
"regulatedDomain": true,
|
|
54
|
+
"nonAnswers": [
|
|
55
|
+
"deferred"
|
|
56
|
+
]
|
|
47
57
|
},
|
|
48
58
|
{
|
|
49
59
|
"ref": "jurisdictions",
|
|
50
60
|
"question": "In which jurisdictions do your users live and your data reside or transit (e.g. EU/EEA, UK, US, California, Canada, specific countries)? This is what drives which privacy regimes apply.",
|
|
51
61
|
"kind": "free_text",
|
|
52
62
|
"depth": "essential",
|
|
53
|
-
"regulatedDomain": true
|
|
63
|
+
"regulatedDomain": true,
|
|
64
|
+
"nonAnswers": [
|
|
65
|
+
"deferred"
|
|
66
|
+
]
|
|
54
67
|
},
|
|
55
68
|
{
|
|
56
69
|
"ref": "sector",
|
|
57
70
|
"question": "Does the product operate in a regulated sector with its own rules (healthcare, finance/banking, insurance, education, government, telecoms)? Name the sector, or answer \"none\".",
|
|
58
71
|
"kind": "free_text",
|
|
59
72
|
"depth": "detail",
|
|
60
|
-
"regulatedDomain": true
|
|
73
|
+
"regulatedDomain": true,
|
|
74
|
+
"nonAnswers": [
|
|
75
|
+
"not_applicable",
|
|
76
|
+
"deferred"
|
|
77
|
+
]
|
|
61
78
|
},
|
|
62
79
|
{
|
|
63
80
|
"ref": "gdpr-applies",
|
|
64
81
|
"question": "Do you serve EU/EEA (or UK) individuals or process their personal data? (This is the primary trigger for GDPR / UK GDPR.)",
|
|
65
82
|
"kind": "confirm",
|
|
66
83
|
"depth": "detail",
|
|
67
|
-
"regulatedDomain": true
|
|
84
|
+
"regulatedDomain": true,
|
|
85
|
+
"nonAnswers": [
|
|
86
|
+
"deferred"
|
|
87
|
+
]
|
|
68
88
|
},
|
|
69
89
|
{
|
|
70
90
|
"ref": "hipaa-applies",
|
|
71
91
|
"question": "Do you handle US protected health information as, or on behalf of, a covered entity or business associate? (This is the primary trigger for HIPAA.)",
|
|
72
92
|
"kind": "confirm",
|
|
73
93
|
"depth": "detail",
|
|
74
|
-
"regulatedDomain": true
|
|
94
|
+
"regulatedDomain": true,
|
|
95
|
+
"nonAnswers": [
|
|
96
|
+
"deferred"
|
|
97
|
+
]
|
|
75
98
|
},
|
|
76
99
|
{
|
|
77
100
|
"ref": "external-assurance-applies",
|
|
78
101
|
"question": "Do enterprise customers (or your own security posture) require an independent attestation or certification covering security / availability / confidentiality of the service? Name the requested target only as an external source requirement.",
|
|
79
102
|
"kind": "confirm",
|
|
80
103
|
"depth": "detail",
|
|
81
|
-
"regulatedDomain": true
|
|
104
|
+
"regulatedDomain": true,
|
|
105
|
+
"nonAnswers": [
|
|
106
|
+
"deferred"
|
|
107
|
+
]
|
|
82
108
|
},
|
|
83
109
|
{
|
|
84
110
|
"ref": "data-residency",
|
|
85
111
|
"question": "Are there data-residency or sovereignty requirements — must certain data stay within a region or country (e.g. EU-only hosting, in-country storage)? Describe them, or answer \"none\".",
|
|
86
112
|
"kind": "free_text",
|
|
87
113
|
"depth": "detail",
|
|
88
|
-
"regulatedDomain": true
|
|
114
|
+
"regulatedDomain": true,
|
|
115
|
+
"nonAnswers": [
|
|
116
|
+
"not_applicable",
|
|
117
|
+
"deferred"
|
|
118
|
+
]
|
|
89
119
|
},
|
|
90
120
|
{
|
|
91
121
|
"ref": "additional-regimes",
|
|
92
122
|
"question": "Any other legal regimes, sector frameworks, government programs, or contractual security commitments that apply? List the externally named sources, or answer \"none\".",
|
|
93
123
|
"kind": "free_text",
|
|
94
124
|
"depth": "detail",
|
|
95
|
-
"regulatedDomain": true
|
|
125
|
+
"regulatedDomain": true,
|
|
126
|
+
"nonAnswers": [
|
|
127
|
+
"not_applicable",
|
|
128
|
+
"deferred"
|
|
129
|
+
]
|
|
96
130
|
}
|
|
97
131
|
]
|
|
98
132
|
},
|
|
133
|
+
"derivedFromAnswers": [],
|
|
99
134
|
"contextSources": [],
|
|
100
135
|
"draftableDocumentDefinitionRefs": [],
|
|
101
136
|
"choreography": {
|
|
@@ -104,7 +139,7 @@
|
|
|
104
139
|
"top_down.compliance-research",
|
|
105
140
|
"top_down.compliance-evidence-adequacy"
|
|
106
141
|
],
|
|
107
|
-
"maximumIterations":
|
|
142
|
+
"maximumIterations": 8,
|
|
108
143
|
"maximumLanesPerIteration": 3,
|
|
109
144
|
"maximumDepth": 1,
|
|
110
145
|
"maximumDurationMs": 4800000
|
|
@@ -19,8 +19,8 @@ Read and apply these patterns from the application-developer point of view:
|
|
|
19
19
|
|
|
20
20
|
## What this playbook does
|
|
21
21
|
|
|
22
|
-
The compliance-posture step decided **which regimes apply**, in prose, as
|
|
23
|
-
|
|
22
|
+
The compliance-posture step decided **which regimes apply**, in prose, as the constraints of the
|
|
23
|
+
`compliance-posture` family; the vision may also carry `kind: compliance` constraints the creator stated. You turn that into the application's **assurance programme**: which Wildo
|
|
24
24
|
control objectives this product binds, which external requirement each one answers, who is
|
|
25
25
|
accountable, and what is explicitly undetermined.
|
|
26
26
|
|
|
@@ -29,7 +29,7 @@ artifact — the `compliance-program` family — and nothing else.
|
|
|
29
29
|
|
|
30
30
|
## The one rule that governs everything below
|
|
31
31
|
|
|
32
|
-
**A
|
|
32
|
+
**A posture sentence is not a control mapping.** The posture step recorded "must be GDPR-compliant for
|
|
33
33
|
EU customer personal data". That is product intent. It is *not* a decision that this application binds
|
|
34
34
|
`WILDO.PRIVACY.SUBJECT_DATA_EXPORT`, and converting one into the other by reading is exactly what the
|
|
35
35
|
posture step's own method forbids: the transition "must not reinterpret a vision sentence as a control
|
|
@@ -60,6 +60,13 @@ The runtime normalizes your answer and **rejects** it — spending one of three
|
|
|
60
60
|
were shown exactly which. There is no partial credit for a plausible objective.
|
|
61
61
|
- cite a source the registry does not carry. `sourceSlug` is the registry ref minus its `source:`
|
|
62
62
|
prefix, spelled exactly.
|
|
63
|
+
- answer an obligation under a source its objective was not reviewed under. The authority section
|
|
64
|
+
names, per objective, the sources the basis reviewed it under. You choose one of those; the
|
|
65
|
+
requirements the obligation cites are stamped from the basis, so you do not write them.
|
|
66
|
+
- give a `sourceSlug` for an objective the authority section marks as reviewed under no source by
|
|
67
|
+
design, or omit it for one that was reviewed under a source. Whether an objective answers any
|
|
68
|
+
external source is the basis's decision: such an obligation omits `sourceSlug` and is stamped as
|
|
69
|
+
answering no source.
|
|
63
70
|
- bind the same objective twice.
|
|
64
71
|
- bind an objective the authority section marks `NOT_APPLICABLE` for this application. Every capability
|
|
65
72
|
it requires is absent, so nothing could ever evidence it.
|
|
@@ -79,8 +86,11 @@ For each objective you were shown, ask three questions **in order**, and stop at
|
|
|
79
86
|
whose intent describes something the declarations do not show is not bound. Read the computed
|
|
80
87
|
applicability first: a `NOT_APPLICABLE` objective is refused, and an `UNDETERMINED` one is bound only
|
|
81
88
|
as `UNDETERMINED`.
|
|
82
|
-
2. **Which
|
|
83
|
-
|
|
89
|
+
2. **Which source does it answer, and does that source reach this application?** Only a source the
|
|
90
|
+
objective was reviewed under can be answered; which of its requirements apply is the basis's
|
|
91
|
+
review, not yours. If the product serves no EU data subjects, GDPR does not reach it and no
|
|
92
|
+
obligation should cite it. An objective the basis reviews under no source by design answers
|
|
93
|
+
none: skip this question for it, and decide its applicability on the objective alone.
|
|
84
94
|
3. **Can you justify binding it from the evidence you were shown?** Write the disposition you can
|
|
85
95
|
defend, with the reason. `APPROVED` is not you asserting that a review happened — the review is
|
|
86
96
|
the human's COMMIT, and until then this is a proposal on disk. What is forbidden is a
|
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
"ref": "top_down.compliance-conception",
|
|
3
3
|
"version": "0.6.0",
|
|
4
4
|
"phase": "top_down",
|
|
5
|
-
"intent": "Compliance-conception pass: turn the applicable regimes the posture step recorded as prose constraints into the application's accepted `compliance-program` — the structured, reviewable record of which Wildo control objectives this product binds, which external requirement each answers, who is accountable, and what is explicitly undetermined. It does NOT re-elicit the vision and it does not draft any document. It is the first step in the lane that produces a POSITIVE compliance claim, so every claim it makes is derived — from an engine authority, the application's declarations, or the one thing no declaration records (what the creator says is genuinely undetermined) — drafted as a proposal a human accepts by committing it, and read back by an advisory judge. Nothing is inferred from a vision sentence.",
|
|
5
|
+
"intent": "Compliance-conception pass: turn the applicable regimes the posture step recorded as prose constraints into the application's accepted `compliance-program` — the structured, reviewable record of which Wildo control objectives this product binds, which external requirement each answers, who is accountable, and what is explicitly undetermined. It does NOT re-elicit the vision and it does not draft any document. It is the first step in the lane that produces a POSITIVE compliance claim, so every claim it makes is derived — from an engine authority, the application's declarations, or the one thing no declaration records (what the creator says is genuinely undetermined) — drafted as a proposal a human accepts by committing it, and read back by an advisory judge. Nothing is inferred from a posture or vision sentence.",
|
|
6
6
|
"preconditions": [
|
|
7
7
|
{
|
|
8
8
|
"kind": "artifact_exists",
|
|
@@ -14,6 +14,9 @@
|
|
|
14
14
|
"inputs": [
|
|
15
15
|
{
|
|
16
16
|
"family": "vision-brief"
|
|
17
|
+
},
|
|
18
|
+
{
|
|
19
|
+
"family": "compliance-posture"
|
|
17
20
|
}
|
|
18
21
|
],
|
|
19
22
|
"outputs": [
|
|
@@ -35,7 +38,7 @@
|
|
|
35
38
|
],
|
|
36
39
|
"stepOutputs": [],
|
|
37
40
|
"method": {
|
|
38
|
-
"guidance": "# Compliance Conception — Derivation Method (v1)\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 the first step in the journey that makes a POSITIVE compliance claim.** Everything before\n> it describes the product. This one says what the product commits to, and a governed document will\n> later quote it. Treat every sentence you write as something an auditor may read back to the\n> operator.\n\n## What this playbook does\n\nThe compliance-posture step decided **which regimes apply**, in prose, as `compliance`-kind\nconstraints on the vision. You turn that into the application's **assurance programme**: which Wildo\ncontrol objectives this product binds, which external requirement each one answers, who is\naccountable, and what is explicitly undetermined.\n\nYou do **not** re-elicit the vision, design the domain, or draft any document. You produce one\nartifact — the `compliance-program` family — and nothing else.\n\n## The one rule that governs everything below\n\n**A vision sentence is not a control mapping.** The posture step recorded \"must be GDPR-compliant for\nEU customer personal data\". That is product intent. It is *not* a decision that this application binds\n`WILDO.PRIVACY.SUBJECT_DATA_EXPORT`, and converting one into the other by reading is exactly what the\nposture step's own method forbids: the transition \"must not reinterpret a vision sentence as a control\nmapping or positive compliance claim.\"\n\nSo every element of the programme comes from one of exactly three places:\n\n| element | comes from |\n|---|---|\n| which objectives exist, what they demand, what proves them | the **engine authority** you were shown — never invented |\n| which sources exist, their edition, authority and rights | the **source registry** — you supply only a slug |\n| what the programme COVERS — the product, its type, its services and modules | the declared `compliance_primary_facts` context section of your brief — DECLARED, never described |\n| which roles this application declares, and which holds the administrative ceiling | the declared `application_role_graph` context section of your brief — a CLOSED SET you select from |\n| WHEN this draft was produced | the HOST's observed instant — stamped, never answered |\n| WHEN it is next reviewed | the application's declared review cadence, applied by the host — a dated commitment, or a stamped limitation saying none is committed |\n| whether an objective CAN apply here | the application's enabled capabilities, computed per objective in the declared `assurance_program_authority` context section of your brief — a lookup, never your finding |\n| whether an objective's intent is TRUE of this product | your reading of the declarations against that intent — a proposal, read back by an advisory judge and accepted by a commit |\n| what is genuinely undetermined | the **creator's answer in this run** — the one thing no declaration records |\n\nIf something comes from none of those, it does not go in the programme. Say it is `UNDETERMINED`, or\nstate it as a limitation.\n\n## What you will be refused for\n\nThe runtime normalizes your answer and **rejects** it — spending one of three runs — if you:\n\n- bind an objective the authority basis states no expectation for. The basis covers a small set; you\n were shown exactly which. There is no partial credit for a plausible objective.\n- cite a source the registry does not carry. `sourceSlug` is the registry ref minus its `source:`\n prefix, spelled exactly.\n- bind the same objective twice.\n- bind an objective the authority section marks `NOT_APPLICABLE` for this application. Every capability\n it requires is absent, so nothing could ever evidence it.\n- state `APPLICABLE` for an objective the authority section marks `UNDETERMINED`. A capability that would\n attest it is absent here, so the evidence `APPLICABLE` promises cannot be produced; state it\n `UNDETERMINED` and say what is open.\n\nThese are not style checks. Each one is a claim the framework cannot stand behind, and the rejection\nmessage names what you got wrong — read it and fix that, rather than restructuring the answer.\n\n## Deciding an obligation\n\nFor each objective you were shown, ask three questions **in order**, and stop at the first \"no\".\n\n1. **Does this application actually do what the intent describes?** You have its resource declarations\n — erasure treatment, data-subject kinds, whether subject export is declared. Use them. An objective\n whose intent describes something the declarations do not show is not bound. Read the computed\n applicability first: a `NOT_APPLICABLE` objective is refused, and an `UNDETERMINED` one is bound only\n as `UNDETERMINED`.\n2. **Which external requirement does it answer, and does that source reach this application?** If the\n product serves no EU data subjects, GDPR does not reach it and no obligation should cite it.\n3. **Can you justify binding it from the evidence you were shown?** Write the disposition you can\n defend, with the reason. `APPROVED` is not you asserting that a review happened — the review is\n the human's COMMIT, and until then this is a proposal on disk. What is forbidden is a\n disposition you cannot point at evidence for; \"the objective sounded right\" is the failure this\n whole step exists to prevent.\n\nAn objective that fails (1) or (2) is simply absent from the programme. **Absence is a legitimate,\nreadable answer** — a programme binding one objective honestly is worth more than one binding four\nhopefully.\n\n### Applicability: `APPLICABLE` or `UNDETERMINED`, never a guess\n\n`UNDETERMINED` with a reason is the right answer whenever the run cannot settle it, and the posture\nstep asks for exactly that. It is visible, it is actionable, and a later pass can close it. A confident\n`APPLICABLE` that nobody could justify is invisible and reads as a decision somebody made.\n\n`NOT_APPLICABLE` is not offered to you. That branch requires evidence that the obligation does not\napply, and evidence is not something a derivation can produce.\n\n## Limitations are required, and they are the honest part\n\nYou must state at least one. The programme you produce binds a handful of objectives out of everything\na regime demands, and a reader who is not told that will read it as a complete posture. Say plainly\nwhat it does not cover: which objectives are unbound, that no operating effectiveness is claimed, and\nthat the programme is not a conformity assertion for any named regime.\n\nThis is not a disclaimer bolted on. It is what makes the rest of the document quotable.\n\n## What reads your programme back\n\nAn advisory judge reads the landed programme against the same declarations and the same computed\napplicability you were given. For each obligation it asks whether the objective's intent is true of this\nproduct, whether an `UNDETERMINED` says what is open, and whether anything claims operating effectiveness, regime conformity or a wider scope. It refuses\nnothing — its verdict travels with the result — but it is why \"the objective sounded right\" does not\nsurvive to the commit.\n\nIt replaced a question that asked the creator, per objective, whether the application met it. That answer\nis either in the declarations, where you can read it, or it is a judgement — which is a judge's job, not a\nform's.\n\n## What you never do\n\n- **Never author a rights record, an edition, or an authority name.** Those come from the registry\n because they govern what may be reproduced from a source. Inventing one is a licensing claim nobody\n reviewed.\n- **Never invent a reviewer, and never author a review instant.** You are not asked for one: the host\n stamps the instant it observed this draft. What makes the dispositions a REVIEW is the human's\n COMMIT — a landed programme is a working edit until then — so write the disposition you can\n justify from the evidence and let acceptance happen where acceptance happens.\n- **Never author a next-review date, and never write a review-schedule limitation.** You are not asked\n for either. The host applies the application's declared review cadence; where none is declared the\n programme is still produced and carries a stamped limitation saying no schedule is committed. A\n limitation of your own on the same point would say it twice, in words nothing checks.\n- **Never invent a ROLE KEY, and do not ask for one either.** The accountable and operating roles are\n SELECTED from the declared `application_role_graph` context section of your brief, which lists every role this application\n declares and marks the administrative ceiling at each scope. A role key that resolves to nothing is\n worse than an absent one — it reads as a named accountable party. If no declared role genuinely holds\n a responsibility, record an explicit gap.\n\n **A programme role is THREE fields, and the key goes in only one of them.** `applicationRoleRef` is the\n application's role key, spelled exactly as that section shows it (`APP_ADMIN_SUPER_ADMIN`). `slug` is\n the programme's OWN lowercase, hyphenated identifier for the responsibility (`application-owner`,\n `control-operator`), and it is the slug — never the key — that `responsibility`'s role lists and\n `reviewerRoleSlug` refer to. `title` is the role's name as a person reads it (`Application owner`,\n `Control operator`) — what the creator sees wherever the role is named. Two programme roles may map to\n the same key; a slug never carries one.\n- **Never name an organization-scope role as accountable for the PROGRAMME.** An organization role\n answers for one tenant; the programme is about the product. The two scopes are rendered separately\n and labelled for exactly this reason.\n- **Never state operating effectiveness.** That a control is configured is not that it has worked. The\n programme has no way to say the latter, and a document downstream is refused for claiming it.\n- **Never widen the scope you were given, and do not ask for it.** What the programme covers is\n DECLARED: the product, its type and its services are in\n the declared `compliance_primary_facts` context section of your brief, which also separates the contracted service from\n build-time tooling that is deliberately outside it. State the boundary from that, naming the\n services individually — an application, its environments and its services, never the operator's\n whole organisation. A service not listed there is not part of this application.\n\n## The two routing decisions you emit beside the programme\n\nNaming which documents are required and stopping there leaves the next step with nothing to route by.\nSo this playbook also answers where those documents are published, and what must happen before one\nfaces a real reader.\n\n### `document-publication` — which variants exist at all\n\nOne entry per exact **locale x jurisdiction** combination the application publishes in. The two are an\nINSEPARABLE pair: `en-GB` for `jurisdiction:eu` and `en-GB` for `jurisdiction:gb` are two variants\ncarrying different clauses, and neither implies a third assembled from one of each. Nothing\ndownstream may recombine the axes.\n\nTake the jurisdictions from what the application has DECLARED — its operating regions, its posture —\nnever from where you imagine it might expand. A variant nobody publishes in is a routing claim no\ndocument can honour, and every later release must name a variant declared here.\n\n### `document-release-policy` — which approval lane each requirement takes\n\nOne selection per documentation requirement the authority section lists under **Documentation\nrequirements this application owes**, keyed by that `requirementRef` and `requirementVersion` exactly.\nThose are DERIVED from what the application declares — the programme declares exactly them, and you do\nnot write them — so a selection naming any other requirement is refused:\n\n| lane | means |\n|---|---|\n| `DRAFT_ONLY` | the document may be drafted and retained; nothing may serve it as published |\n| `OPERATOR_ATTESTED` | an accountable operator may release an exact draft with explicit limitations, which the selection must list |\n| `QUALIFIED_REVIEW` | the reviewer-authority route is required before it is served |\n\n**Choose the lane the application can honestly satisfy today, and prefer the strictest only where it\nis true.** `DRAFT_ONLY` is the right answer for a document nobody has reviewed, and it is not a\nfailure state: a drafted document and an unapproved release are both legitimate artifacts an\napplication holds for most of its life.\n\n**None of these lanes blocks drafting or composing a release.** They decide what must be true before\na document faces a REAL READER, which is a later question than the one this journey is answering. A\nlane that stopped the build would be a compliance workflow standing in front of the\napplication-creation mechanism.\n\n## Where this leaves the journey\n\nThe programme you land is the accepted answer for which controls this product commits to. It is what\nan obligation register reads, what a governed document cites when it says the operator has a\nprogramme, and what a later mapping pass binds to external framework identifiers.\n\nIt is accepted the way everything is accepted here: by a commit, which this run does not make. Who\nmakes it is the host's autonomy posture, and the programme's dispositions become a REVIEW only when a\nPERSON commits them. A commit the development companion makes under the YOLO posture is authored as\nthe companion: it accepts the working edit and reviews nothing.\n",
|
|
41
|
+
"guidance": "# Compliance Conception — Derivation Method (v1)\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 the first step in the journey that makes a POSITIVE compliance claim.** Everything before\n> it describes the product. This one says what the product commits to, and a governed document will\n> later quote it. Treat every sentence you write as something an auditor may read back to the\n> operator.\n\n## What this playbook does\n\nThe compliance-posture step decided **which regimes apply**, in prose, as the constraints of the\n`compliance-posture` family; the vision may also carry `kind: compliance` constraints the creator stated. You turn that into the application's **assurance programme**: which Wildo\ncontrol objectives this product binds, which external requirement each one answers, who is\naccountable, and what is explicitly undetermined.\n\nYou do **not** re-elicit the vision, design the domain, or draft any document. You produce one\nartifact — the `compliance-program` family — and nothing else.\n\n## The one rule that governs everything below\n\n**A posture sentence is not a control mapping.** The posture step recorded \"must be GDPR-compliant for\nEU customer personal data\". That is product intent. It is *not* a decision that this application binds\n`WILDO.PRIVACY.SUBJECT_DATA_EXPORT`, and converting one into the other by reading is exactly what the\nposture step's own method forbids: the transition \"must not reinterpret a vision sentence as a control\nmapping or positive compliance claim.\"\n\nSo every element of the programme comes from one of exactly three places:\n\n| element | comes from |\n|---|---|\n| which objectives exist, what they demand, what proves them | the **engine authority** you were shown — never invented |\n| which sources exist, their edition, authority and rights | the **source registry** — you supply only a slug |\n| what the programme COVERS — the product, its type, its services and modules | the declared `compliance_primary_facts` context section of your brief — DECLARED, never described |\n| which roles this application declares, and which holds the administrative ceiling | the declared `application_role_graph` context section of your brief — a CLOSED SET you select from |\n| WHEN this draft was produced | the HOST's observed instant — stamped, never answered |\n| WHEN it is next reviewed | the application's declared review cadence, applied by the host — a dated commitment, or a stamped limitation saying none is committed |\n| whether an objective CAN apply here | the application's enabled capabilities, computed per objective in the declared `assurance_program_authority` context section of your brief — a lookup, never your finding |\n| whether an objective's intent is TRUE of this product | your reading of the declarations against that intent — a proposal, read back by an advisory judge and accepted by a commit |\n| what is genuinely undetermined | the **creator's answer in this run** — the one thing no declaration records |\n\nIf something comes from none of those, it does not go in the programme. Say it is `UNDETERMINED`, or\nstate it as a limitation.\n\n## What you will be refused for\n\nThe runtime normalizes your answer and **rejects** it — spending one of three runs — if you:\n\n- bind an objective the authority basis states no expectation for. The basis covers a small set; you\n were shown exactly which. There is no partial credit for a plausible objective.\n- cite a source the registry does not carry. `sourceSlug` is the registry ref minus its `source:`\n prefix, spelled exactly.\n- answer an obligation under a source its objective was not reviewed under. The authority section\n names, per objective, the sources the basis reviewed it under. You choose one of those; the\n requirements the obligation cites are stamped from the basis, so you do not write them.\n- give a `sourceSlug` for an objective the authority section marks as reviewed under no source by\n design, or omit it for one that was reviewed under a source. Whether an objective answers any\n external source is the basis's decision: such an obligation omits `sourceSlug` and is stamped as\n answering no source.\n- bind the same objective twice.\n- bind an objective the authority section marks `NOT_APPLICABLE` for this application. Every capability\n it requires is absent, so nothing could ever evidence it.\n- state `APPLICABLE` for an objective the authority section marks `UNDETERMINED`. A capability that would\n attest it is absent here, so the evidence `APPLICABLE` promises cannot be produced; state it\n `UNDETERMINED` and say what is open.\n\nThese are not style checks. Each one is a claim the framework cannot stand behind, and the rejection\nmessage names what you got wrong — read it and fix that, rather than restructuring the answer.\n\n## Deciding an obligation\n\nFor each objective you were shown, ask three questions **in order**, and stop at the first \"no\".\n\n1. **Does this application actually do what the intent describes?** You have its resource declarations\n — erasure treatment, data-subject kinds, whether subject export is declared. Use them. An objective\n whose intent describes something the declarations do not show is not bound. Read the computed\n applicability first: a `NOT_APPLICABLE` objective is refused, and an `UNDETERMINED` one is bound only\n as `UNDETERMINED`.\n2. **Which source does it answer, and does that source reach this application?** Only a source the\n objective was reviewed under can be answered; which of its requirements apply is the basis's\n review, not yours. If the product serves no EU data subjects, GDPR does not reach it and no\n obligation should cite it. An objective the basis reviews under no source by design answers\n none: skip this question for it, and decide its applicability on the objective alone.\n3. **Can you justify binding it from the evidence you were shown?** Write the disposition you can\n defend, with the reason. `APPROVED` is not you asserting that a review happened — the review is\n the human's COMMIT, and until then this is a proposal on disk. What is forbidden is a\n disposition you cannot point at evidence for; \"the objective sounded right\" is the failure this\n whole step exists to prevent.\n\nAn objective that fails (1) or (2) is simply absent from the programme. **Absence is a legitimate,\nreadable answer** — a programme binding one objective honestly is worth more than one binding four\nhopefully.\n\n### Applicability: `APPLICABLE` or `UNDETERMINED`, never a guess\n\n`UNDETERMINED` with a reason is the right answer whenever the run cannot settle it, and the posture\nstep asks for exactly that. It is visible, it is actionable, and a later pass can close it. A confident\n`APPLICABLE` that nobody could justify is invisible and reads as a decision somebody made.\n\n`NOT_APPLICABLE` is not offered to you. That branch requires evidence that the obligation does not\napply, and evidence is not something a derivation can produce.\n\n## Limitations are required, and they are the honest part\n\nYou must state at least one. The programme you produce binds a handful of objectives out of everything\na regime demands, and a reader who is not told that will read it as a complete posture. Say plainly\nwhat it does not cover: which objectives are unbound, that no operating effectiveness is claimed, and\nthat the programme is not a conformity assertion for any named regime.\n\nThis is not a disclaimer bolted on. It is what makes the rest of the document quotable.\n\n## What reads your programme back\n\nAn advisory judge reads the landed programme against the same declarations and the same computed\napplicability you were given. For each obligation it asks whether the objective's intent is true of this\nproduct, whether an `UNDETERMINED` says what is open, and whether anything claims operating effectiveness, regime conformity or a wider scope. It refuses\nnothing — its verdict travels with the result — but it is why \"the objective sounded right\" does not\nsurvive to the commit.\n\nIt replaced a question that asked the creator, per objective, whether the application met it. That answer\nis either in the declarations, where you can read it, or it is a judgement — which is a judge's job, not a\nform's.\n\n## What you never do\n\n- **Never author a rights record, an edition, or an authority name.** Those come from the registry\n because they govern what may be reproduced from a source. Inventing one is a licensing claim nobody\n reviewed.\n- **Never invent a reviewer, and never author a review instant.** You are not asked for one: the host\n stamps the instant it observed this draft. What makes the dispositions a REVIEW is the human's\n COMMIT — a landed programme is a working edit until then — so write the disposition you can\n justify from the evidence and let acceptance happen where acceptance happens.\n- **Never author a next-review date, and never write a review-schedule limitation.** You are not asked\n for either. The host applies the application's declared review cadence; where none is declared the\n programme is still produced and carries a stamped limitation saying no schedule is committed. A\n limitation of your own on the same point would say it twice, in words nothing checks.\n- **Never invent a ROLE KEY, and do not ask for one either.** The accountable and operating roles are\n SELECTED from the declared `application_role_graph` context section of your brief, which lists every role this application\n declares and marks the administrative ceiling at each scope. A role key that resolves to nothing is\n worse than an absent one — it reads as a named accountable party. If no declared role genuinely holds\n a responsibility, record an explicit gap.\n\n **A programme role is THREE fields, and the key goes in only one of them.** `applicationRoleRef` is the\n application's role key, spelled exactly as that section shows it (`APP_ADMIN_SUPER_ADMIN`). `slug` is\n the programme's OWN lowercase, hyphenated identifier for the responsibility (`application-owner`,\n `control-operator`), and it is the slug — never the key — that `responsibility`'s role lists and\n `reviewerRoleSlug` refer to. `title` is the role's name as a person reads it (`Application owner`,\n `Control operator`) — what the creator sees wherever the role is named. Two programme roles may map to\n the same key; a slug never carries one.\n- **Never name an organization-scope role as accountable for the PROGRAMME.** An organization role\n answers for one tenant; the programme is about the product. The two scopes are rendered separately\n and labelled for exactly this reason.\n- **Never state operating effectiveness.** That a control is configured is not that it has worked. The\n programme has no way to say the latter, and a document downstream is refused for claiming it.\n- **Never widen the scope you were given, and do not ask for it.** What the programme covers is\n DECLARED: the product, its type and its services are in\n the declared `compliance_primary_facts` context section of your brief, which also separates the contracted service from\n build-time tooling that is deliberately outside it. State the boundary from that, naming the\n services individually — an application, its environments and its services, never the operator's\n whole organisation. A service not listed there is not part of this application.\n\n## The two routing decisions you emit beside the programme\n\nNaming which documents are required and stopping there leaves the next step with nothing to route by.\nSo this playbook also answers where those documents are published, and what must happen before one\nfaces a real reader.\n\n### `document-publication` — which variants exist at all\n\nOne entry per exact **locale x jurisdiction** combination the application publishes in. The two are an\nINSEPARABLE pair: `en-GB` for `jurisdiction:eu` and `en-GB` for `jurisdiction:gb` are two variants\ncarrying different clauses, and neither implies a third assembled from one of each. Nothing\ndownstream may recombine the axes.\n\nTake the jurisdictions from what the application has DECLARED — its operating regions, its posture —\nnever from where you imagine it might expand. A variant nobody publishes in is a routing claim no\ndocument can honour, and every later release must name a variant declared here.\n\n### `document-release-policy` — which approval lane each requirement takes\n\nOne selection per documentation requirement the authority section lists under **Documentation\nrequirements this application owes**, keyed by that `requirementRef` and `requirementVersion` exactly.\nThose are DERIVED from what the application declares — the programme declares exactly them, and you do\nnot write them — so a selection naming any other requirement is refused:\n\n| lane | means |\n|---|---|\n| `DRAFT_ONLY` | the document may be drafted and retained; nothing may serve it as published |\n| `OPERATOR_ATTESTED` | an accountable operator may release an exact draft with explicit limitations, which the selection must list |\n| `QUALIFIED_REVIEW` | the reviewer-authority route is required before it is served |\n\n**Choose the lane the application can honestly satisfy today, and prefer the strictest only where it\nis true.** `DRAFT_ONLY` is the right answer for a document nobody has reviewed, and it is not a\nfailure state: a drafted document and an unapproved release are both legitimate artifacts an\napplication holds for most of its life.\n\n**None of these lanes blocks drafting or composing a release.** They decide what must be true before\na document faces a REAL READER, which is a later question than the one this journey is answering. A\nlane that stopped the build would be a compliance workflow standing in front of the\napplication-creation mechanism.\n\n## Where this leaves the journey\n\nThe programme you land is the accepted answer for which controls this product commits to. It is what\nan obligation register reads, what a governed document cites when it says the operator has a\nprogramme, and what a later mapping pass binds to external framework identifiers.\n\nIt is accepted the way everything is accepted here: by a commit, which this run does not make. Who\nmakes it is the host's autonomy posture, and the programme's dispositions become a REVIEW only when a\nPERSON commits them. A commit the development companion makes under the YOLO posture is authored as\nthe companion: it accepts the working edit and reviews nothing.\n",
|
|
39
42
|
"skillRefs": [],
|
|
40
43
|
"skillBodyRefs": [],
|
|
41
44
|
"elicitation": {
|
|
@@ -49,6 +52,7 @@
|
|
|
49
52
|
}
|
|
50
53
|
]
|
|
51
54
|
},
|
|
55
|
+
"derivedFromAnswers": [],
|
|
52
56
|
"contextSources": [
|
|
53
57
|
"assurance_program_authority",
|
|
54
58
|
"compliance_primary_facts",
|
|
@@ -48,6 +48,26 @@ DECIDED scope needed. Reserve the authoritative-source bar for the regimes the
|
|
|
48
48
|
declared facts actually reach; for the conditional tier, the deliverable is the
|
|
49
49
|
precise list of deciding facts, and the posture records exactly that.
|
|
50
50
|
|
|
51
|
+
## Only what RESEARCH can close is a gap
|
|
52
|
+
|
|
53
|
+
Every item you would name is one of three kinds, and only the first is a gap:
|
|
54
|
+
|
|
55
|
+
| kind | example | where it goes |
|
|
56
|
+
|---|---|---|
|
|
57
|
+
| **Research can close it** — a source not yet read, a trigger not yet looked up, a claim cited only through an unofficial copy | "GDPR Art. 3 is cited only through a commentary site; read the Official Journal text" | `gaps` |
|
|
58
|
+
| **A fact about the product or its operator** — something the creator or the application's declarations own, which no page answers | "whether the vendor is processor or controller for each processing activity"; "whether the CRM submits material to procurement portals or only organises tender information" | `openFacts` |
|
|
59
|
+
| **A regime conditional on a fact declared open** — see the section above | "tenderer-facing duties in DE, FR, IT and ES, should the product serve public procurement" | `openFacts` |
|
|
60
|
+
|
|
61
|
+
Write each open fact as the fact and what it decides: *"Whether the vendor is processor for customer CRM
|
|
62
|
+
data decides which GDPR duties attach to it (Art. 28 terms or controller duties)."* The posture records it
|
|
63
|
+
as an open or conditional constraint, which is a correct posture, not an unfinished one.
|
|
64
|
+
|
|
65
|
+
**The verdict is ADEQUATE when no research gap is left**, however many open facts there are. An
|
|
66
|
+
INSUFFICIENT verdict with no research gap is refused: the next round would have nothing to look for, and
|
|
67
|
+
that shape is what kept a run researching for seven rounds without a verdict (reference run 42120979649,
|
|
68
|
+
#3385). The first verdict of the next run named four gaps, three of them product facts or a conditional
|
|
69
|
+
regime.
|
|
70
|
+
|
|
51
71
|
## What INSUFFICIENT must do
|
|
52
72
|
|
|
53
73
|
Name the gaps so the next round is AIMED: which regime, which trigger question,
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"ref": "top_down.compliance-evidence-adequacy",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.2.0",
|
|
4
4
|
"phase": "top_down",
|
|
5
5
|
"intent": "Judge whether the regime evidence gathered so far is ENOUGH to state a compliance posture 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,14 +19,15 @@
|
|
|
19
19
|
{
|
|
20
20
|
"ref": "compliance-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 posture step is conditioned on."
|
|
24
24
|
}
|
|
25
25
|
],
|
|
26
26
|
"method": {
|
|
27
|
-
"guidance": "# Compliance Evidence Adequacy — is this enough to state a posture 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**, not the author. You read what the research rounds gathered\nand answer one question: is this enough to record the product's compliance posture\n— or what, precisely, is still missing?\n\n## What ADEQUATE means here\n\nEvidence is adequate when, for the jurisdictions, data classes and sector the\nvision (and the creator's answers) put in scope:\n\n1. **Every plausible candidate regime has a settled applicability answer** —\n applies, does not apply, or genuinely cannot be established — grounded in an\n authoritative source, never in recollection.\n2. **No scope dimension is unexamined.** A jurisdiction the vision names with no\n regime evidence at all is a gap, whatever was gathered elsewhere.\n3. **The claims carry sources.** An unsourced applicability claim counts as\n missing, not as weak — the posture that cites it would be recollection wearing\n evidence's clothes.\n\n## A regime whose triggering facts are DECLARED OPEN is settled as CONDITIONAL\n\n\"Settled\" has three answers, and the third is not a failure: **applies**, **does\nnot apply**, and **conditional on named open facts**. When the creator's own\nanswers declare a triggering fact undecided — a hosting region not chosen, a\nmarket not yet targeted, a threshold nobody can know before launch — the settled\nanswer for every regime that turns on that fact is *conditional on it*, stated\nwith the exact facts that would decide it. That answer is ADEQUATE as it stands.\n\nDo not send research after statute-level verification of conditional regimes.\nThe measured failure this paragraph exists for: a run whose creator had declared\nUS targeting undecided spent its final rounds demanding primary-source triggers\nand thresholds for twelve individual US state statutes — evidence that decides\nnothing until the open fact is decided, purchased at the cost of the rounds the\nDECIDED scope needed. Reserve the authoritative-source bar for the regimes the\ndeclared facts actually reach; for the conditional tier, the deliverable is the\nprecise list of deciding facts, and the posture records exactly that.\n\n## What INSUFFICIENT must do\n\nName the gaps so the next round is AIMED: which regime, which trigger question,\nwhich jurisdiction. \"More research needed\" is not a gap — it is the shape that\nmade the market loop's early rounds spend tokens converging on nothing.\n\n## What you never do\n\nYou never lower the bar because rounds are running out — the composite's breaker\nowns that trade, not you. And you never fill a gap yourself: a gate that authors\nevidence has measured nothing.\n",
|
|
27
|
+
"guidance": "# Compliance Evidence Adequacy — is this enough to state a posture 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**, not the author. You read what the research rounds gathered\nand answer one question: is this enough to record the product's compliance posture\n— or what, precisely, is still missing?\n\n## What ADEQUATE means here\n\nEvidence is adequate when, for the jurisdictions, data classes and sector the\nvision (and the creator's answers) put in scope:\n\n1. **Every plausible candidate regime has a settled applicability answer** —\n applies, does not apply, or genuinely cannot be established — grounded in an\n authoritative source, never in recollection.\n2. **No scope dimension is unexamined.** A jurisdiction the vision names with no\n regime evidence at all is a gap, whatever was gathered elsewhere.\n3. **The claims carry sources.** An unsourced applicability claim counts as\n missing, not as weak — the posture that cites it would be recollection wearing\n evidence's clothes.\n\n## A regime whose triggering facts are DECLARED OPEN is settled as CONDITIONAL\n\n\"Settled\" has three answers, and the third is not a failure: **applies**, **does\nnot apply**, and **conditional on named open facts**. When the creator's own\nanswers declare a triggering fact undecided — a hosting region not chosen, a\nmarket not yet targeted, a threshold nobody can know before launch — the settled\nanswer for every regime that turns on that fact is *conditional on it*, stated\nwith the exact facts that would decide it. That answer is ADEQUATE as it stands.\n\nDo not send research after statute-level verification of conditional regimes.\nThe measured failure this paragraph exists for: a run whose creator had declared\nUS targeting undecided spent its final rounds demanding primary-source triggers\nand thresholds for twelve individual US state statutes — evidence that decides\nnothing until the open fact is decided, purchased at the cost of the rounds the\nDECIDED scope needed. Reserve the authoritative-source bar for the regimes the\ndeclared facts actually reach; for the conditional tier, the deliverable is the\nprecise list of deciding facts, and the posture records exactly that.\n\n## Only what RESEARCH can close is a gap\n\nEvery item you would name is one of three kinds, and only the first is a gap:\n\n| kind | example | where it goes |\n|---|---|---|\n| **Research can close it** — a source not yet read, a trigger not yet looked up, a claim cited only through an unofficial copy | \"GDPR Art. 3 is cited only through a commentary site; read the Official Journal text\" | `gaps` |\n| **A fact about the product or its operator** — something the creator or the application's declarations own, which no page answers | \"whether the vendor is processor or controller for each processing activity\"; \"whether the CRM submits material to procurement portals or only organises tender information\" | `openFacts` |\n| **A regime conditional on a fact declared open** — see the section above | \"tenderer-facing duties in DE, FR, IT and ES, should the product serve public procurement\" | `openFacts` |\n\nWrite each open fact as the fact and what it decides: *\"Whether the vendor is processor for customer CRM\ndata decides which GDPR duties attach to it (Art. 28 terms or controller duties).\"* The posture records it\nas an open or conditional constraint, which is a correct posture, not an unfinished one.\n\n**The verdict is ADEQUATE when no research gap is left**, however many open facts there are. An\nINSUFFICIENT verdict with no research gap is refused: the next round would have nothing to look for, and\nthat shape is what kept a run researching for seven rounds without a verdict (reference run 42120979649,\n#3385). The first verdict of the next run named four gaps, three of them product facts or a conditional\nregime.\n\n## What INSUFFICIENT must do\n\nName the gaps so the next round is AIMED: which regime, which trigger question,\nwhich jurisdiction. \"More research needed\" is not a gap — it is the shape that\nmade the market loop's early rounds spend tokens converging on nothing.\n\n## What you never do\n\nYou never lower the bar because rounds are running out — the composite's breaker\nowns that trade, not you. And you never fill a gap yourself: a gate that authors\nevidence has measured nothing.\n",
|
|
28
28
|
"skillRefs": [],
|
|
29
29
|
"skillBodyRefs": [],
|
|
30
|
+
"derivedFromAnswers": [],
|
|
30
31
|
"contextSources": [],
|
|
31
32
|
"draftableDocumentDefinitionRefs": [],
|
|
32
33
|
"suspendsForClarification": false,
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"aggregationPolicyRef":"application-creation:aggregation/worst-compliance-posture-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["
|
|
1
|
+
{"aggregationPolicyRef":"application-creation:aggregation/worst-compliance-posture-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["compliance-posture.constraint"],"criterionRef":"application-creation:criterion/compliance-posture-one-regime-one-constraint-and-convergence","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-posture-one-regime-one-constraint-and-convergence","requirementVersion":1}],"instruction":"Determine whether the posture is written as one constraint per regime with a stable, unique semantic slug; whether a regime already present in the previous posture (when one was given) was matched by the regime its statement names and kept under its existing ref; and whether re-running would converge to one entry per regime rather than accumulating near-duplicates.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Regimes are separate but a ref is minted for a regime that already existed under another slug, or two statements overlap in scope.","GAP":"An omnibus constraint merging several regimes, a duplicate entry for one regime, or a malformed ref.","INDETERMINATE":"A previous posture exists but is not in evidence, so convergence cannot be compared.","PASS":"One entry per regime, stable unique refs, and every pre-existing regime refined under its own ref."}},{"criterionRef":"application-creation:criterion/compliance-posture-regime-derivation-grounding","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-posture-regime-derivation-grounding","requirementVersion":1}],"instruction":"Determine whether each compliance constraint is derived rather than recalled: its statement names the regime, the trigger (jurisdiction, data class, sector or commitment) and what it governs, in the terms of the regime evidence and the creator's facts this run carried; a regime the evidence EXCLUDES is not written as a constraint and, where the creator's answers suggested it, the exclusion is made legible on a neighbouring constraint; a trigger the evidence could NOT establish becomes a constraint stating the open question, never a guessed answer; and a product with no triggers honestly carries no compliance constraints.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Grounded overall, but a statement is thinner than the evidence allows, or an exclusion is dropped silently where the creator had suggested the regime.","GAP":"A regime stated as settled that the evidence did not establish, a regime invented to look thorough, or a regime the evidence establishes that is absent.","INDETERMINATE":"The regime evidence or the creator's facts are not in evidence, so derivation cannot be checked.","PASS":"Every constraint is grounded in the evidence, exclusions are legible, and open triggers are stated as open."}},{"assessesAspects":["compliance-posture.constraint","vision.constraint"],"criterionRef":"application-creation:criterion/compliance-posture-slice-discipline","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-posture-slice-discipline","requirementVersion":1}],"instruction":"Determine whether every constraint stays a prose regime statement at scaffold depth, and whether the posture is consistent with the creator's own compliance constraints on the vision: a regime the creator stated is recorded with the evidence's sharper statement or, when the evidence excludes it, the exclusion is legible on a neighbouring constraint. No constraint models controls, obligation graphs, residency matrices, retention schedules or audit configuration, which belong to the later compliance-conception step.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A constraint drifts toward listing controls, or a regime the creator stated is dropped without its exclusion being legible.","GAP":"A constraint that models controls or obligations, or a posture that contradicts the creator's stated compliance constraint without evidence.","INDETERMINATE":"The creator's compliance constraints on the vision are not in evidence, so consistency cannot be checked.","PASS":"Each constraint is a prose regime statement at scaffold depth, and every compliance constraint the creator stated is either sharpened or its exclusion made legible."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/compliance-posture","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.compliance-posture"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-vision-brief","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/compliance-posture-one-regime-one-constraint-and-convergence"],"requirementRef":"application-creation:authority-requirement/compliance-posture-result","requirementVersion":1,"riskClassRef":"application-creation:risk/vision-brief-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/compliance-posture","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/compliance-posture-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/compliance-posture","policyVersion":1},"decisionPointRef":"application-creation:decision-point/compliance-posture-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/compliance-posture-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/compliance-posture","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-posture-one-regime-one-constraint-and-convergence","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/compliance-posture-regime-derivation-grounding","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/compliance-posture-slice-discipline","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/vision-brief-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/current-horizon-vision-brief-change","triggerRefs":["application-creation:trigger/vision-brief-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-compliance-posture-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/compliance-posture-regime-derivation-grounding"],"hardFloorRef":"application-creation:hard-floor/vision-brief-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/compliance-posture-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/compliance-posture","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-compliance-posture-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["vision.constraint"],"criterionRef":"application-creation:criterion/compliance-posture-one-regime-one-constraint-and-convergence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-posture-one-regime-one-constraint-and-convergence","requirementVersion":1}],"instruction":"Determine whether the posture is written as one constraint per regime with a stable kebab-case ref prefixed `constraint-`, unique across the set; whether a regime already present in the vision (under any slug the vision-elicitation step chose) was matched by the regime its statement names and updated IN PLACE under its existing ref; and whether re-running would converge to one entry per regime rather than accumulating near-duplicates.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Regimes are separate but a ref is minted for a regime that already existed under another slug, or two statements overlap in scope.","GAP":"An omnibus constraint merging several regimes, a duplicate entry for one regime, or a malformed ref.","INDETERMINATE":"The vision's prior constraints are not in evidence, so convergence cannot be compared.","PASS":"One entry per regime, stable unique refs, and every pre-existing regime refined under its own ref."}},{"criterionRef":"application-creation:criterion/compliance-posture-regime-derivation-grounding","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-posture-regime-derivation-grounding","requirementVersion":1}],"instruction":"Determine whether each compliance constraint is derived rather than recalled: its statement names the regime, the trigger (jurisdiction, data class, sector or commitment) and what it governs, in the terms of the regime evidence and the creator's facts this run carried; a regime the evidence EXCLUDES is not written as a constraint and, where the creator's answers suggested it, the exclusion is made legible on a neighbouring constraint; a trigger the evidence could NOT establish becomes a constraint stating the open question, never a guessed answer; and a product with no triggers honestly carries no compliance constraints.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Grounded overall, but a statement is thinner than the evidence allows, or an exclusion is dropped silently where the creator had suggested the regime.","GAP":"A regime stated as settled that the evidence did not establish, a regime invented to look thorough, or a regime the evidence establishes that is absent.","INDETERMINATE":"The regime evidence or the creator's facts are not in evidence, so derivation cannot be checked.","PASS":"Every constraint is grounded in the evidence, exclusions are legible, and open triggers are stated as open."}},{"assessesAspects":["vision.constraint","vision.idea","vision.problem","vision.mission","vision.success-criterion"],"criterionRef":"application-creation:criterion/compliance-posture-slice-discipline","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-posture-slice-discipline","requirementVersion":1}],"instruction":"Determine whether the run touched exactly the `kind: compliance` entries of the vision's constraints and nothing else: the idea, problem, mission, success criteria and every non-compliance constraint are unchanged, and no constraint models controls, obligation graphs, residency matrices, retention schedules or audit configuration, which belong to the later compliance-conception step.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A non-compliance entity was reworded incidentally, or a constraint drifts toward listing controls.","GAP":"A vision entity outside the compliance constraints altered, or a constraint that models controls or obligations.","INDETERMINATE":"The vision as it was BEFORE this run is not in evidence.","PASS":"Only compliance constraints changed, and each stays a prose regime statement at scaffold depth."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/compliance-posture","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.compliance-posture"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/compliance-posture","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-compliance-posture-inputs-and-candidate","criterionRef":"application-creation:criterion/compliance-posture-one-regime-one-constraint-and-convergence","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":3,"minCount":1,"requirementRef":"application-creation:evidence-requirement/compliance-posture-one-regime-one-constraint-and-convergence","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-and-regime-evidence-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-compliance-posture-inputs-and-candidate","criterionRef":"application-creation:criterion/compliance-posture-regime-derivation-grounding","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":3,"minCount":1,"requirementRef":"application-creation:evidence-requirement/compliance-posture-regime-derivation-grounding","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-and-regime-evidence-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-compliance-posture-inputs-and-candidate","criterionRef":"application-creation:criterion/compliance-posture-slice-discipline","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":3,"minCount":1,"requirementRef":"application-creation:evidence-requirement/compliance-posture-slice-discipline","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-and-regime-evidence-candidate"}],"schemaVersion":1}
|
|
1
|
+
{"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-compliance-posture","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/compliance-posture-one-regime-one-constraint-and-convergence"],"requirementRef":"application-creation:authority-requirement/compliance-posture-result","requirementVersion":1,"riskClassRef":"application-creation:risk/compliance-posture-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/compliance-posture","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/compliance-posture-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/compliance-posture","policyVersion":1},"decisionPointRef":"application-creation:decision-point/compliance-posture-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/compliance-posture-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/compliance-posture","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-posture-one-regime-one-constraint-and-convergence","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/compliance-posture-regime-derivation-grounding","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/compliance-posture-slice-discipline","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/compliance-posture-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/current-horizon-compliance-posture-change","triggerRefs":["application-creation:trigger/compliance-posture-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-compliance-posture-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/compliance-posture-regime-derivation-grounding"],"hardFloorRef":"application-creation:hard-floor/compliance-posture-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/compliance-posture-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/compliance-posture","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-compliance-posture-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["compliance-posture.constraint"],"criterionRef":"application-creation:criterion/compliance-posture-one-regime-one-constraint-and-convergence","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-posture-one-regime-one-constraint-and-convergence","requirementVersion":1}],"instruction":"Determine whether the posture is written as one constraint per regime with a stable, unique semantic slug; whether a regime already present in the previous posture (when one was given) was matched by the regime its statement names and kept under its existing ref; and whether re-running would converge to one entry per regime rather than accumulating near-duplicates.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Regimes are separate but a ref is minted for a regime that already existed under another slug, or two statements overlap in scope.","GAP":"An omnibus constraint merging several regimes, a duplicate entry for one regime, or a malformed ref.","INDETERMINATE":"A previous posture exists but is not in evidence, so convergence cannot be compared.","PASS":"One entry per regime, stable unique refs, and every pre-existing regime refined under its own ref."}},{"criterionRef":"application-creation:criterion/compliance-posture-regime-derivation-grounding","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-posture-regime-derivation-grounding","requirementVersion":1}],"instruction":"Determine whether each compliance constraint is derived rather than recalled: its statement names the regime, the trigger (jurisdiction, data class, sector or commitment) and what it governs, in the terms of the regime evidence and the creator's facts this run carried; a regime the evidence EXCLUDES is not written as a constraint and, where the creator's answers suggested it, the exclusion is made legible on a neighbouring constraint; a trigger the evidence could NOT establish becomes a constraint stating the open question, never a guessed answer; and a product with no triggers honestly carries no compliance constraints.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Grounded overall, but a statement is thinner than the evidence allows, or an exclusion is dropped silently where the creator had suggested the regime.","GAP":"A regime stated as settled that the evidence did not establish, a regime invented to look thorough, or a regime the evidence establishes that is absent.","INDETERMINATE":"The regime evidence or the creator's facts are not in evidence, so derivation cannot be checked.","PASS":"Every constraint is grounded in the evidence, exclusions are legible, and open triggers are stated as open."}},{"assessesAspects":["compliance-posture.constraint","vision.constraint"],"criterionRef":"application-creation:criterion/compliance-posture-slice-discipline","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-posture-slice-discipline","requirementVersion":1}],"instruction":"Determine whether every constraint stays a prose regime statement at scaffold depth, and whether the posture is consistent with the creator's own compliance constraints on the vision: a regime the creator stated is recorded with the evidence's sharper statement or, when the evidence excludes it, the exclusion is legible on a neighbouring constraint. No constraint models controls, obligation graphs, residency matrices, retention schedules or audit configuration, which belong to the later compliance-conception step.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A constraint drifts toward listing controls, or a regime the creator stated is dropped without its exclusion being legible.","GAP":"A constraint that models controls or obligations, or a posture that contradicts the creator's stated compliance constraint without evidence.","INDETERMINATE":"The creator's compliance constraints on the vision are not in evidence, so consistency cannot be checked.","PASS":"Each constraint is a prose regime statement at scaffold depth, and every compliance constraint the creator stated is either sharpened or its exclusion made legible."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/compliance-posture","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.compliance-posture"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/compliance-posture","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-compliance-posture-inputs-and-candidate","criterionRef":"application-creation:criterion/compliance-posture-one-regime-one-constraint-and-convergence","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":3,"minCount":1,"requirementRef":"application-creation:evidence-requirement/compliance-posture-one-regime-one-constraint-and-convergence","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-and-regime-evidence-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-compliance-posture-inputs-and-candidate","criterionRef":"application-creation:criterion/compliance-posture-regime-derivation-grounding","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":3,"minCount":1,"requirementRef":"application-creation:evidence-requirement/compliance-posture-regime-derivation-grounding","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-and-regime-evidence-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-compliance-posture-inputs-and-candidate","criterionRef":"application-creation:criterion/compliance-posture-slice-discipline","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":3,"minCount":1,"requirementRef":"application-creation:evidence-requirement/compliance-posture-slice-discipline","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-and-regime-evidence-candidate"}],"schemaVersion":1}
|