@wildo-ai/framework-knowledge 1.1.11 → 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 +3 -3
- 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 +170 -32
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.loader.js.map +1 -1
- package/dist/esm/framework-knowledge.research-provenance.d.ts +6 -4
- package/dist/esm/framework-knowledge.research-provenance.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.research-provenance.js.map +1 -1
- package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.schemas.js.map +1 -1
- package/dist/esm/index.d.ts.map +1 -1
- package/dist/esm/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 +7 -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 +76 -14
- 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 +0 -4
- 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 +3 -15
- 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.map +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.map +1 -1
- 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 +35 -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 +19 -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.map +1 -1
- 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 +5 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +3 -2
- 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.map +1 -1
- 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.d.ts.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 +3 -5
- 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.d.ts.map +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 +8 -6
- 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 +8 -1
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.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 +4 -1
- 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 +11 -3
- 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.d.ts.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 +5 -2
- 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 +4 -3
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.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.d.ts.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 +16 -7
- 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.map +1 -1
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts.map +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.d.ts.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.d.ts.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.d.ts.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.d.ts.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 +4 -1
- package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.service-method/playbook.definition.js +14 -1
- package/dist/esm/playbooks/top_down.service-method/playbook.definition.js.map +1 -1
- 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 +35 -17
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
- package/dist/esm/source-anchor-grammar.d.ts.map +1 -1
- package/dist/esm/source-anchor-grammar.js.map +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
- package/dist/knowledge/manifest.json +7 -7
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +6 -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 +439 -27
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +15 -4
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +203 -7
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -5
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +1 -0
- package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +1 -0
- 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 +104 -2
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +8 -4
- package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +59 -4
- package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +18 -6
- package/dist/knowledge/playbooks/bottom_up.foundation/method.md +121 -24
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +51 -7
- package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +15 -8
- package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +2 -1
- 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 +34 -0
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +9 -2
- package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +1 -0
- 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 -6
- package/dist/knowledge/playbooks/cross_cutting.refinement/playbook.json +3 -4
- 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 +56 -5
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +3 -2
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +6 -4
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +5 -1
- package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +8 -1
- package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +1 -0
- 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/playbook.json +15 -3
- 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 +43 -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 +3 -3
- 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 +3 -1
- package/dist/knowledge/playbooks/top_down.definition/playbook.json +11 -3
- package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +1 -0
- package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +1 -0
- 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 +7 -0
- 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 +19 -1
- package/dist/knowledge/playbooks/top_down.service-method/playbook.json +16 -4
- 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 +17 -2
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +59 -15
- 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 +27 -1
- package/dist/knowledge/references/backend.inbound-channels.attachment-adoption.md +4 -2
- package/dist/knowledge/references/backend.inbound-channels.handler-definition.md +52 -11
- package/dist/knowledge/references/backend.inbound-handlers.definition.md +38 -1
- package/dist/knowledge/references/brand.name-screening.config.md +30 -3
- package/dist/knowledge/references/build-plan.task-graph.config.md +200 -4
- package/dist/knowledge/references/business-model.pricing-plan.config.md +12 -9
- package/dist/knowledge/references/business-model.snapshot.config.md +29 -2
- package/dist/knowledge/references/business-model.snapshot.validation.md +11 -8
- 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 +195 -63
- package/dist/knowledge/references/domain-plan.record-partition.md +105 -0
- package/dist/knowledge/references/engine.client-bundle.allow-list.md +3 -1
- package/dist/knowledge/references/engine.saas-technical-doc.config.md +69 -15
- package/dist/knowledge/references/example.authorization.application-roles.office-and-field.md +10 -0
- package/dist/knowledge/references/example.backend.addon-wiring.module.md +6 -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 +4 -2
- package/dist/knowledge/references/example.flows-actors.chat-assistant.md +8 -5
- package/dist/knowledge/references/example.infra.environment-config.local.md +13 -66
- 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.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.provider.backend-module-shape.md +28 -4
- package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +0 -4
- 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.operation-icon.md +37 -2
- package/dist/knowledge/references/example.resource.ui-behavior.record-template.md +0 -1
- package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +1 -1
- package/dist/knowledge/references/example.resource.ui-behavior.workflow-record-page.md +212 -0
- 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.website.demo.complete-items.md +3 -3
- 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.stats.md +1 -1
- package/dist/knowledge/references/experience-plan.config.md +111 -1
- package/dist/knowledge/references/external-connectors.frontend-provider-consent-classification.md +2 -0
- package/dist/knowledge/references/external-connectors.models.file-storage-adapter.md +8 -1
- package/dist/knowledge/references/external-connectors.models.hook-signature-algorithms.md +104 -0
- package/dist/knowledge/references/external-connectors.models.oauth2-audiences.md +11 -6
- package/dist/knowledge/references/external-connectors.models.oauth2-incremental-consent.md +165 -0
- package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +1035 -19
- 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 +7 -7
- package/dist/knowledge/references/placement-plan.config.md +19 -0
- package/dist/knowledge/references/platform.config.backing-services.md +9 -11
- package/dist/knowledge/references/platform.config.environment.deployment.md +133 -8
- package/dist/knowledge/references/platform.config.infra-provider-resolution.md +3 -3
- package/dist/knowledge/references/platform.config.infrastructure-host.md +0 -1
- package/dist/knowledge/references/platform.config.platform-key-management.md +84 -8
- package/dist/knowledge/references/platform.config.saas.md +20 -18
- package/dist/knowledge/references/presets.3d.frame-style-resolution.md +65 -0
- package/dist/knowledge/references/presets.layouts-2d.authoring.md +1 -1
- 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.surface-policy.defaults.md +3 -3
- package/dist/knowledge/references/presets.models.surface-variant.md +5 -4
- package/dist/knowledge/references/presets.themes.compose-theme.md +2 -1
- 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/saas.approval-seals.admin-endpoints.md +29 -2
- package/dist/knowledge/references/saas.backend.a2a.token-budget.md +11 -4
- package/dist/knowledge/references/saas.backend.actor-execution-continuation.md +21 -0
- package/dist/knowledge/references/saas.backend.app-config.backend-authored.md +5 -1
- package/dist/knowledge/references/saas.backend.application-initialization.assembly.md +1 -1
- package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +13 -1
- package/dist/knowledge/references/saas.backend.custom-operation.authoritative-fields.md +4 -1
- 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.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 +30 -1
- package/dist/knowledge/references/saas.backend.flows-actors.a2a-task-surface.md +26 -3
- package/dist/knowledge/references/saas.backend.flows-actors.chat-reply-handler.md +13 -1
- package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +363 -2
- package/dist/knowledge/references/saas.backend.flows-actors.invoke-agent.md +5 -3
- package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +1 -1
- package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +9 -4
- package/dist/knowledge/references/saas.backend.flows.start-flow-method.md +2 -1
- 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.system-access-service.md +159 -4
- package/dist/knowledge/references/saas.config.content-security-policy.md +26 -9
- 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.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.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.resource-chart-data.md +8 -4
- package/dist/knowledge/references/saas.frontend.collection-filter-presets.md +76 -9
- package/dist/knowledge/references/saas.frontend.command-menu.search-resource.md +3 -3
- package/dist/knowledge/references/saas.frontend.errors.backend-refusal.md +96 -0
- package/dist/knowledge/references/saas.frontend.execution-view.definition.md +40 -0
- package/dist/knowledge/references/saas.frontend.launcher.item-refs.md +4 -0
- package/dist/knowledge/references/saas.frontend.linked-conversations-embed.md +3 -5
- package/dist/knowledge/references/saas.frontend.record-page-parts.md +117 -0
- package/dist/knowledge/references/saas.frontend.related-resource-embeds.md +46 -16
- package/dist/knowledge/references/saas.frontend.related-resource-sections.md +6 -0
- package/dist/knowledge/references/saas.frontend.resource-header-title.md +1 -1
- package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +43 -9
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +259 -15
- package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +4 -2
- package/dist/knowledge/references/saas.frontend.section-stages.md +63 -0
- package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +42 -0
- package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +6 -9
- package/dist/knowledge/references/saas.frontend.viewer-may-perform-operation.md +52 -0
- package/dist/knowledge/references/saas.models.agent-suspension.md +8 -8
- package/dist/knowledge/references/saas.models.audit-trails.actor-attribution.md +21 -0
- package/dist/knowledge/references/saas.models.auth.relationship-grantor-authentication.md +2 -2
- package/dist/knowledge/references/saas.models.config.declared-type-renames.md +246 -0
- package/dist/knowledge/references/saas.models.config.organization-types.md +20 -0
- package/dist/knowledge/references/saas.models.conversation-threads.md +39 -3
- package/dist/knowledge/references/saas.models.crypto-keys.floors.md +10 -0
- package/dist/knowledge/references/saas.models.crypto-keys.local-provider.md +2 -0
- package/dist/knowledge/references/saas.models.crypto-keys.purpose-descriptor.md +39 -0
- package/dist/knowledge/references/saas.models.crypto-keys.purposes.md +7 -0
- package/dist/knowledge/references/saas.models.data-mode-read-list.md +0 -78
- package/dist/knowledge/references/saas.models.engine-capabilities.md +11 -2
- package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +3 -0
- package/dist/knowledge/references/saas.models.external-data-pipeline.md +15 -8
- package/dist/knowledge/references/saas.models.flows-actors.agent-behavior-report.md +13 -9
- package/dist/knowledge/references/saas.models.flows-actors.agent-configuration.md +29 -0
- package/dist/knowledge/references/saas.models.flows-actors.agent-operation-record.md +7 -0
- package/dist/knowledge/references/saas.models.flows-actors.human-decision-decider.md +8 -0
- package/dist/knowledge/references/saas.models.flows-actors.human-input-form.md +47 -12
- package/dist/knowledge/references/saas.models.flows-actors.operation-approval-requirement.md +31 -0
- package/dist/knowledge/references/saas.models.flows-actors.review-deadlines-declaration.md +3 -3
- package/dist/knowledge/references/saas.models.flows.runnable-model.md +21 -2
- package/dist/knowledge/references/saas.models.guidance-flow.md +1 -1
- package/dist/knowledge/references/saas.models.http-api-binding.md +19 -8
- package/dist/knowledge/references/saas.models.human-decision-review-marker.md +1 -1
- package/dist/knowledge/references/saas.models.inbound-channels.md +71 -2
- package/dist/knowledge/references/saas.models.model-cost-accounting-config.md +1 -1
- package/dist/knowledge/references/saas.models.notifications.targets.md +3 -1
- package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +201 -15
- package/dist/knowledge/references/saas.models.organization-assigned-rows-declaration.md +2 -1
- package/dist/knowledge/references/saas.models.organization-own-rows-declaration.md +5 -2
- package/dist/knowledge/references/saas.models.organizations.identity-declaration.md +201 -0
- package/dist/knowledge/references/saas.models.organizations.organization-relationships.md +25 -3
- package/dist/knowledge/references/saas.models.organizations.relationship-invitations.md +6 -2
- package/dist/knowledge/references/saas.models.organizations.relationship-kinds.md +14 -0
- package/dist/knowledge/references/saas.models.organizations.relationship-record-separation.md +1 -0
- package/dist/knowledge/references/saas.models.privacy.data-residency.md +676 -0
- package/dist/knowledge/references/saas.models.privacy.legal-holds.md +46 -2
- package/dist/knowledge/references/saas.models.privacy.provider-capability-disclosure.md +6 -0
- 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 +2 -0
- package/dist/knowledge/references/saas.models.privacy.subject-export.md +134 -0
- package/dist/knowledge/references/saas.models.provider-capabilities.md +5 -0
- package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +12 -6
- package/dist/knowledge/references/saas.models.providers.compliance-choice.md +15 -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.representative-activity.md +4 -0
- package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +107 -42
- package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +35 -0
- package/dist/knowledge/references/saas.models.resource-config.operation-auditable-event.md +4 -2
- 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-scope-admissions.md +38 -0
- package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +14 -16
- package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +2 -2
- package/dist/knowledge/references/saas.models.resource-config.retention-policy.md +21 -0
- package/dist/knowledge/references/saas.models.resource-config.system-access-policy.md +32 -15
- package/dist/knowledge/references/saas.models.resource-operation-display-risk.md +5 -4
- package/dist/knowledge/references/saas.models.roles.definition.md +12 -1
- package/dist/knowledge/references/saas.models.roles.organization-defaults.md +6 -0
- package/dist/knowledge/references/saas.models.schema-family-builder.md +17 -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 +3 -1
- package/dist/knowledge/references/saas.models.system-of-record-error-codes.md +16 -0
- package/dist/knowledge/references/saas.models.systems-of-record.md +75 -14
- package/dist/knowledge/references/saas.public-runtime.contract.md +41 -23
- package/dist/knowledge/references/saas.rag.retrieval-refusals.md +3 -2
- package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +12 -4
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +21 -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 +6 -2
- package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +20 -3
- package/dist/knowledge/references/saas.specifications.resource-spec-factory.md +100 -71
- package/dist/knowledge/references/saas.specifications.translation-glossary.md +80 -0
- package/dist/knowledge/references/saas.website.astro.label-loader.md +44 -10
- package/dist/knowledge/references/saas.website.astro.runtime-helper.md +3 -2
- package/dist/knowledge/references/saas.website.blog.collection-config.md +36 -32
- package/dist/knowledge/references/saas.website.blog.cover-resolver.md +1 -1
- package/dist/knowledge/references/saas.website.blog.frontmatter.md +2 -2
- package/dist/knowledge/references/saas.website.blog.post-renderer.md +2 -2
- package/dist/knowledge/references/saas.website.blog.react-mdx-integration.md +26 -19
- package/dist/knowledge/references/saas.website.blog.react-mdx-query.md +1 -1
- package/dist/knowledge/references/saas.website.config.pricing-catalog-loader.md +3 -1
- package/dist/knowledge/references/saas.website.config.site-context-loader.md +6 -3
- package/dist/knowledge/references/saas.website.label-keys.format.md +3 -2
- package/dist/knowledge/references/saas.website.label-pack.validator.md +3 -1
- package/dist/knowledge/references/service-method.config.md +35 -2
- package/dist/knowledge/references/vision.constraint.config.md +4 -2
- package/dist/knowledge/references/zod.decorators.chainable-runtime.md +60 -0
- package/dist/knowledge/references/zod.decorators.data-categories.md +46 -46
- package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +24 -0
- package/dist/knowledge/references/zod.decorators.display-edit-modes.md +11 -0
- package/dist/knowledge/references/zod.decorators.file-schema.md +4 -3
- package/dist/knowledge/references/zod.decorators.rag-source.md +20 -20
- package/dist/knowledge/references/zod.decorators.schema-metadata.md +2 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +30 -24
- package/dist/knowledge/references/zod.decorators.shared-structural-params.md +63 -0
- package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +63 -0
- package/dist/knowledge/references/zod.factories.bigdecimal.md +4 -4
- package/dist/knowledge/references/zod.factories.code.md +4 -4
- package/dist/knowledge/references/zod.factories.duration.md +4 -4
- package/dist/knowledge/references/zod.factories.money.md +4 -4
- package/dist/knowledge/references/zod.factories.phone.md +4 -4
- package/dist/knowledge/references/zod.factories.year-month.md +79 -0
- package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
- package/dist/knowledge/registries/framework-topics.json +415 -2
- package/dist/knowledge/registries/playbooks.json +51 -39
- package/dist/knowledge/registries/source-tags.json +2412 -1604
- package/dist/knowledge/rules/database-migration-obligation.md +6 -7
- package/dist/knowledge/rules/live-context-door.md +1 -1
- package/dist/knowledge/skills/INDEX.md +3 -1
- package/dist/knowledge/skills/agent-work-review/references/framework-actor-execution-continuation-api.md +24 -0
- package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-marker-api.md +1 -1
- package/dist/knowledge/skills/agent-work-review/references/framework-human-input-form-api.md +47 -12
- 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 +10 -11
- 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 +13 -11
- package/dist/knowledge/skills/application-roles-authoring/SKILL.md +28 -3
- package/dist/knowledge/skills/application-roles-authoring/references/framework-application-roles-api.md +18 -1
- 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 +46 -2
- package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-assigned-rows-declaration-api.md +5 -3
- 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 +12 -5
- package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +6 -0
- package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +31 -2
- package/dist/knowledge/skills/backend-custom-operation/SKILL.md +51 -14
- 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-audit-log-event-api.md +2 -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/blueprint-authoring/SKILL.md +4 -2
- 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 +3 -0
- package/dist/knowledge/skills/chat-agent-conversations/references/framework-chat-conversations-api.md +13 -1
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +45 -4
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +17 -7
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +859 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-disclosures.md +6 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-subject-data-recipients.md +2 -0
- package/dist/knowledge/skills/config-app-shell/SKILL.md +5 -1
- 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 +4 -0
- package/dist/knowledge/skills/config-design-system/SKILL.md +1 -1
- package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +8 -7
- package/dist/knowledge/skills/config-design-system/references/framework-theme-composition-api.md +44 -1
- package/dist/knowledge/skills/config-navigation/SKILL.md +2 -0
- package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +5 -0
- package/dist/knowledge/skills/config-navigation/references/one-entry-per-concept.md +101 -0
- package/dist/knowledge/skills/config-saas/SKILL.md +2 -2
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +40 -3
- package/dist/knowledge/skills/config-saas/references/framework-auditable-event-catalog.md +20 -1
- package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +75 -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 -9
- package/dist/knowledge/skills/config-saas/references/framework-key-management-api.md +197 -9
- package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +16 -2
- package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +116 -16
- package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +20 -18
- package/dist/knowledge/skills/config-saas/references/saas-config-scope.md +1 -1
- package/dist/knowledge/skills/config-saas-backend/SKILL.md +11 -1
- 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-organization-types-api.md +20 -0
- package/dist/knowledge/skills/config-saas-backend/references/renaming-organization-and-user-types.md +69 -0
- package/dist/knowledge/skills/configure-billing/SKILL.md +6 -0
- package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +28 -4
- package/dist/knowledge/skills/configure-billing/references/framework-backend-provider-reachability-api.md +2 -0
- package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +4 -1
- 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 +1 -1
- 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 +3 -2
- package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +31 -9
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +11 -4
- package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +26 -3
- package/dist/knowledge/skills/flows-actors-autonomous-agents/SKILL.md +1 -1
- package/dist/knowledge/skills/flows-actors-autonomous-agents/references/binding-and-review.md +27 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +18 -7
- package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +8 -5
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-behavior-reports-api.md +13 -9
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-content-guardrails-api.md +44 -4
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-operation-record-api.md +7 -0
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-suspension-api.md +11 -9
- 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 +3 -3
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-realtime-catalog.md +7 -1
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +375 -8
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +30 -1
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-model-spend-limits-api.md +36 -15
- package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +8 -0
- package/dist/knowledge/skills/flows-actors-declared-flow/SKILL.md +1 -1
- package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-flow-model-api.md +21 -2
- package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-start-flow-api.md +2 -1
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +1 -1
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +33 -1
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-invocation-api.md +5 -3
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +3 -3
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +37 -14
- package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-guidance-flow-api.md +1 -1
- package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +39 -0
- package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +39 -0
- package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +31 -2
- 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 +31 -9
- package/dist/knowledge/skills/inbound-channels/references/email-channel.md +16 -4
- package/dist/knowledge/skills/inbound-channels/references/framework-inbound-channel-api.md +169 -23
- package/dist/knowledge/skills/inbound-channels/references/framework-inbound-handler-api.md +38 -1
- package/dist/knowledge/skills/inbound-channels/references/inbound-delivery-lifecycle.md +43 -4
- package/dist/knowledge/skills/inbound-channels/references/receiving-email.md +15 -3
- package/dist/knowledge/skills/inbound-channels/references/sms-channel.md +93 -0
- package/dist/knowledge/skills/infra-environment-config/SKILL.md +125 -77
- 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 +133 -8
- package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +0 -1
- package/dist/knowledge/skills/infra-environment-config/references/framework-platform-key-management-api.md +84 -8
- package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-authoring-api.md +1 -1
- 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/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 +3 -3
- 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-companion-prompt-enrichment/SKILL.md +24 -2
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +33 -2
- package/dist/knowledge/skills/market-generation-cli/SKILL.md +47 -6
- package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +61 -8
- package/dist/knowledge/skills/model-cost-attribution/SKILL.md +3 -1
- package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-pricing-api.md +1 -1
- package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +107 -42
- package/dist/knowledge/skills/module-companion-exports/SKILL.md +1 -0
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +21 -2
- package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +30 -1
- package/dist/knowledge/skills/module-relationships/SKILL.md +92 -91
- package/dist/knowledge/skills/organization-relationships/references/framework-organization-relationships-api.md +31 -5
- package/dist/knowledge/skills/organization-relationships/references/framework-relationship-grantor-authentication-api.md +2 -2
- package/dist/knowledge/skills/organization-relationships/references/framework-relationship-kinds-api.md +34 -0
- package/dist/knowledge/skills/organization-relationships/references/framework-relationship-record-separation-api.md +1 -0
- package/dist/knowledge/skills/organization-relationships/references/framework-representative-activity-api.md +4 -0
- package/dist/knowledge/skills/professional-qualifications/references/framework-operation-approval-requirement-api.md +31 -0
- package/dist/knowledge/skills/provider-backend-package/SKILL.md +255 -12
- package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +4 -5
- 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 +8 -1
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-inbound-endpoint-api.md +124 -3
- package/dist/knowledge/skills/provider-backend-package/references/framework-provider-incremental-consent-api.md +165 -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 +11 -6
- package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-consent-api.md +2 -0
- package/dist/knowledge/skills/provider-frontend-module/SKILL.md +5 -2
- package/dist/knowledge/skills/provider-frontend-module/references/package-frontend-facets.md +1 -1
- package/dist/knowledge/skills/provider-operation-calls/SKILL.md +17 -3
- package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +1035 -19
- package/dist/knowledge/skills/resource-add-field/SKILL.md +7 -0
- package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +322 -15
- package/dist/knowledge/skills/resource-add-resource/SKILL.md +9 -5
- 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 +107 -42
- package/dist/knowledge/skills/resource-chat-commands/SKILL.md +2 -1
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +71 -5
- package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +2 -2
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-approval-api.md +48 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +33 -7
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-bulk-api.md +15 -11
- 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 +140 -58
- package/dist/knowledge/skills/resource-config-wiring/references/framework-retention-policy-operations.md +7 -2
- 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 +5 -4
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +158 -138
- package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +52 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +205 -19
- package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +253 -25
- package/dist/knowledge/skills/resource-custom-view/SKILL.md +126 -1
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +259 -15
- package/dist/knowledge/skills/resource-custom-view/references/framework-backend-refusal-api.md +110 -0
- package/dist/knowledge/skills/resource-external-data/SKILL.md +46 -12
- package/dist/knowledge/skills/resource-external-data/references/bidirectional-pipelines.md +1 -1
- package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +15 -8
- package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +19 -8
- package/dist/knowledge/skills/resource-external-data/references/framework-system-of-record-capabilities-api.md +3 -1
- package/dist/knowledge/skills/resource-external-data/references/local-test-doubles.md +121 -0
- package/dist/knowledge/skills/resource-external-data/references/outbound-pipelines.md +1 -1
- 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/read-through-writes.md +26 -5
- package/dist/knowledge/skills/resource-external-data/references/system-of-record-actions.md +76 -6
- package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +8 -0
- package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +12 -9
- package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +11 -2
- 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 +18 -2
- package/dist/knowledge/skills/resource-retention-binding/references/framework-legal-holds-api.md +46 -2
- 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 +21 -0
- package/dist/knowledge/skills/resource-retention-binding/references/start-point-decisions.md +14 -2
- package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +1 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/computed-totals.md +4 -1
- 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 +2 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +26 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +46 -46
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-schema-family-api.md +17 -2
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +36 -24
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +63 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +104 -23
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +123 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +1 -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 +66 -3
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-collection-filter-presets-api.md +89 -10
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +11 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +263 -17
- 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 +83 -16
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +44 -10
- 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 +9 -2
- package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +33 -2
- package/dist/knowledge/skills/resource-ui-behavior/references/visual-quality-rubric.md +19 -2
- 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/framework-data-seeding-api.md +7 -6
- package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +6 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +42 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +6 -9
- 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 +21 -2
- 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 +121 -75
- 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 +100 -71
- 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-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 +36 -5
- 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 +4 -0
- package/dist/knowledge/skills/views-composite-authoring/references/framework-chart-dashboard-api.md +244 -0
- package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +40 -0
- package/dist/knowledge/skills/website-blog-authoring/SKILL.md +8 -6
- package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +70 -59
- package/dist/knowledge/skills/website-building-blocks/SKILL.md +1 -1
- package/dist/knowledge/skills/website-building-blocks/references/framework-website-demo-examples.md +3 -3
- package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +4 -2
- package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +3 -1
- package/dist/knowledge/skills/website-label-pack/SKILL.md +20 -5
- package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +6 -3
- package/dist/knowledge/skills/website-section-comparison/SKILL.md +2 -2
- package/dist/knowledge/skills/website-section-contact/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-cta/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-faq/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-hero/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-how-it-works/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-integrations/SKILL.md +3 -3
- package/dist/knowledge/skills/website-section-latest-posts/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-pricing/SKILL.md +142 -98
- package/dist/knowledge/skills/website-section-pricing/examples/pricing-offers.example.md +178 -66
- package/dist/knowledge/skills/website-section-pricing/references/framework-pricing-catalog-api.md +3 -1
- package/dist/knowledge/skills/website-section-problem/SKILL.md +3 -3
- package/dist/knowledge/skills/website-section-product-showcase/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-roadmap/SKILL.md +4 -4
- package/dist/knowledge/skills/website-section-social-proof/SKILL.md +1 -1
- package/dist/knowledge/skills/website-section-solution-paths/SKILL.md +2 -2
- package/dist/knowledge/skills/website-section-stats/SKILL.md +3 -3
- package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +3 -2
- package/dist/knowledge/skills/worker-authoring/SKILL.md +4 -2
- package/dist/knowledge/topic-index.json +2275 -715
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/package.json +6 -6
- package/dist/tsconfig.tsbuildinfo +0 -1
|
@@ -1 +1 @@
|
|
|
1
|
-
{"attributionNotices":["Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","Contains public sector information licensed under the Open Government Licence v3.0. Link to the licence where possible, and do not imply official status or endorsement.","Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","Credit the OWASP AI Exchange and link to https://owaspai.org where practical; do not imply OWASP endorsement or use OWASP marks.","Identify HHS as the authority and link to the current official source; no HHS content bytes are bundled under this record.","Identify the PCI Security Standards Council as the owner of PCI DSS and link to its document library; never state or imply PCI certification, compliance or endorsement."],"evaluatedAt":"2026-10-21T19:32:46.710Z","mapped":[{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-govern-accountable-role-retention","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"Every scope keeps at least one usable administrator: a removal, demotion or deactivation that would strand an application or a tenant is refused, concurrent reductions are serialized so two of them cannot pass each other, a data-protection erasure proceeds only on an explicit acknowledgement that records the breach it causes, and any scope that has already been stranded is reported at startup.","objectiveRef":"WILDO.ACCESS.ADMINISTRATIVE_CONTINUITY","title":"Retain an administrator for every scope"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-audit-of-access-decisions","reviewedAt":"2026-09-01T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-audit-of-access-decisions-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"Access-control decisions, refusals included, are attributable and reviewable; repeated refusals stay detectable without the record itself becoming an availability risk; and a failure of the recording pipeline is detectable and attributable to the specific action it lost.","objectiveRef":"WILDO.ACCESS.AUTHORIZATION_DECISION_AUDIT","title":"Record access decisions, refusals included"},{"citations":[{"attributionNotice":"Identify HHS as the authority and link to the current official source; no HHS content bytes are bundled under this record.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html","contentUsePermission":"REQUIRES_ADDITIONAL_RIGHTS","metadataCitationAuthorized":true,"requirementRef":"source-requirement:hhs-security-access-authorization-recording","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:paul-cayon-assurance-owner","rightsRef":"rights:hhs-reference-only-v1","sourceRef":"source:hhs-hipaa-security-rule","sourceTitle":"HIPAA Security Rule"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_GUIDANCE","canonicalLocator":"https://doi.org/10.6028/NIST.SP.800-66r2","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-66-access-authorization-recording","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-66-rev-2","sourceTitle":"Implementing the HIPAA Security Rule: A Cybersecurity Resource Guide"}],"intent":"Platform-tier administration of a tenant is never ambient: a crossing is admitted only by an explicitly enumerated operation variant, requires an elevation that was requested rather than assumed and — where the tenant demands it — approved by that tenant, is recorded as a distinct event naming the tenant reached, and an undeclared crossing fails closed.","objectiveRef":"WILDO.ACCESS.CROSS_TENANT_ADMINISTRATION","title":"Declare every crossing of a tenant boundary"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-least-privilege-enforcement","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-least-privilege-authority-limit","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-least-privilege-authority-limit-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"A principal can never grant authority it does not itself hold — role assignment and machine-credential minting are bounded by the caller’s own ceiling — and a non-controller surface facing an external caller applies the same declared operation-role gate the controller tier applies, through the same predicate, before a self-service verb, a retrieval corpus or an agent-facing tool is reached.","objectiveRef":"WILDO.ACCESS.LEAST_PRIVILEGE","title":"Grant no more authority than the action needs"},{"citations":[{"attributionNotice":"Identify HHS as the authority and link to the current official source; no HHS content bytes are bundled under this record.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html","contentUsePermission":"REQUIRES_ADDITIONAL_RIGHTS","metadataCitationAuthorized":true,"requirementRef":"source-requirement:hhs-security-workforce-access-termination","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:paul-cayon-assurance-owner","rightsRef":"rights:hhs-reference-only-v1","sourceRef":"source:hhs-hipaa-security-rule","sourceTitle":"HIPAA Security Rule"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-account-disable-on-relationship-end","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-account-disable-on-relationship-end-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_GUIDANCE","canonicalLocator":"https://doi.org/10.6028/NIST.SP.800-66r2","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-66-workforce-access-termination","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-66-rev-2","sourceTitle":"Implementing the HIPAA Security Rule: A Cybersecurity Resource Guide"}],"intent":"Access rights, and the credentials that assert them, are withdrawn when the relationship conferring them ends, and restoring access is as attributable as removing it.","objectiveRef":"WILDO.ACCESS.LIFECYCLE","title":"Withdraw and restore access attributably"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-temporary-account-expiry","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-temporary-account-expiry-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"An access restriction declared as time-boxed is lifted when its window elapses, through the same guarded authority that imposed it, so a measure taken as temporary cannot silently become permanent.","objectiveRef":"WILDO.ACCESS.LIFECYCLE_TIME_BOUND","title":"Release a time-boxed restriction automatically"},{"citations":[{"attributionNotice":"Identify HHS as the authority and link to the current official source; no HHS content bytes are bundled under this record.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html","contentUsePermission":"REQUIRES_ADDITIONAL_RIGHTS","metadataCitationAuthorized":true,"requirementRef":"source-requirement:hipaa-security-privileged-access-review","reviewedAt":"2026-08-13T08:57:58.000Z","reviewedByRef":"reviewer:paul-cayon-assurance-owner","rightsRef":"rights:hhs-reference-only-v1","sourceRef":"source:hhs-hipaa-security-rule","sourceTitle":"HIPAA Security Rule"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-govern-access-review","reviewedAt":"2026-08-03T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_GUIDANCE","canonicalLocator":"https://doi.org/10.6028/NIST.SP.800-66r2","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-66-privileged-access-review","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-66-rev-2","sourceTitle":"Implementing the HIPAA Security Rule: A Cybersecurity Resource Guide"}],"intent":"Privileged access is explicitly scoped, periodically reviewed, decided by authorized people and retained as traceable evidence without implying remediation completion.","objectiveRef":"WILDO.ACCESS.PRIVILEGED_REVIEW","title":"Review privileged access"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-privileged-grant-evidence","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"Every grant, widening, narrowing and revocation of privilege — a role, a unit-scoped membership, a discretionary entitlement or a subscription-derived one — leaves durable evidence of the assignment’s full life, not merely of its current state.","objectiveRef":"WILDO.ACCESS.PRIVILEGE_EVIDENCE","title":"Keep evidence of a privileged assignment’s whole life"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-separation-of-duties","reviewedAt":"2026-10-05T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-separation-of-duties-assessment","reviewedAt":"2026-10-05T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"A decision the product holds for a person's review — an agent's gated tool call, an actor's reviewable output, a granting organization's admission of a representing organization's representative, a person's operation the application declares needs another person's approval — is answered, claimed, reassigned or escalated only by someone the one decision predicate admits at the moment they act: under any route other than the requester's own, the person whose work raised it can never act on it, a deadline rule can hand it only to someone that predicate would admit to answer it, the eligible role is re-checked when the person acts rather than when the decision was routed, and every refused act is recorded with its reason. An operation the application does not declare as needing approval is applied at once and is outside it.","objectiveRef":"WILDO.ACCESS.REQUESTER_REVIEWER_SEPARATION","title":"Never let the requester answer the decision their own work raised"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-processing-confidentiality","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-information-flow-confinement","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-information-flow-confinement-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"Reads and writes are narrowed to the tenant, unit subtree or parent row the caller’s own grant reaches; the conferring grant is recorded alongside the decision, a unit grant expands to exactly its declared subtree and no further, and a tenant cannot lift a narrowing the platform imposed on it.","objectiveRef":"WILDO.ACCESS.SCOPE_CONFINEMENT","title":"Confine a query to the scope the caller reached it by"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.AI.100-2e2025","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-ai-100-2-injection-assumed-system-design","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-ai-100-2-e2025","sourceTitle":"Adversarial Machine Learning: A Taxonomy and Terminology of Attacks and Mitigations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-least-privilege-processes-acting-for-users","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-least-privilege-processes-acting-for-users-assessment","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"},{"attributionNotice":"Credit the OWASP AI Exchange and link to https://owaspai.org where practical; do not imply OWASP endorsement or use OWASP marks.","authorityKind":"COMMUNITY_GUIDANCE","canonicalLocator":"https://owaspai.org/","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:owasp-ai-exchange-agent-acts-with-served-principal-authority","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:owasp-ai-exchange-cc0-v1","sourceRef":"source:owasp-ai-exchange","sourceTitle":"OWASP AI Exchange"},{"attributionNotice":"Contains public sector information licensed under the Open Government Licence v3.0. Link to the licence where possible, and do not imply official status or endorsement.","authorityKind":"GOVERNMENT_GUIDANCE","canonicalLocator":"https://www.gov.uk/government/publications/ai-cyber-security-code-of-practice/code-of-practice-for-the-cyber-security-of-ai","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:uk-ai-code-ai-system-permissions-limited-and-assessed","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:uk-open-government-licence-v3","sourceRef":"source:uk-ai-cyber-security-code-of-practice","sourceTitle":"Code of Practice for the Cyber Security of AI"}],"intent":"An agent's tool acts with no more authority than the person or declared machine principal whose turn calls it, and the model can never supply that authority: every tool runs on its caller's server-verified identity, the engine's tools dispatch each operation through that operation's own role gate, tenancy filter and rate limit for the caller, an autonomous turn runs as a declared machine principal rather than the application's system authority, a turn started by content from outside is offered no write a reviewer does not see first, and every hand-written tool declares how it reaches data, so a tool that reaches beyond its caller is named.","objectiveRef":"WILDO.AI.AGENT_AUTHORITY_CONFINEMENT","title":"Confine an AI agent's tools to the authority of the principal it acts for"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.AI.100-1","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-ai-rmf-ai-system-deactivation-mechanism","reviewedAt":"2026-10-20T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-ai-rmf-1.0","sourceTitle":"Artificial Intelligence Risk Management Framework (AI RMF 1.0)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.AI.100-1","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-ai-rmf-human-oversight-processes-documented","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-ai-rmf-1.0","sourceTitle":"Artificial Intelligence Risk Management Framework (AI RMF 1.0)"},{"attributionNotice":"Credit the OWASP AI Exchange and link to https://owaspai.org where practical; do not imply OWASP endorsement or use OWASP marks.","authorityKind":"COMMUNITY_GUIDANCE","canonicalLocator":"https://owaspai.org/","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:owasp-ai-exchange-human-approval-before-high-impact-agent-actions","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:owasp-ai-exchange-cc0-v1","sourceRef":"source:owasp-ai-exchange","sourceTitle":"OWASP AI Exchange"},{"attributionNotice":"Contains public sector information licensed under the Open Government Licence v3.0. Link to the licence where possible, and do not imply official status or endorsement.","authorityKind":"GOVERNMENT_GUIDANCE","canonicalLocator":"https://www.gov.uk/government/publications/ai-cyber-security-code-of-practice/code-of-practice-for-the-cyber-security-of-ai","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:uk-ai-code-technical-measures-for-human-oversight","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:uk-open-government-licence-v3","sourceRef":"source:uk-ai-cyber-security-code-of-practice","sourceTitle":"Code of Practice for the Cyber Security of AI"}],"intent":"An agent action of consequence waits for a person before it runs: a gated tool call or a held operation is decided by its owner or, where the gate routes it to a role or an assignee, by a reviewer who is not its requester, within a declared deadline, and every decision reaches the people who can answer it; a person can stop a running turn; an organization's administrator can suspend one of its agents for that organization, and the application's super-administrator for everybody with a justification, after which a call to the agent is refused before its model runs, at every door that reaches the engine's agent service, for each organization the call works for (the one it names, the tenant of the case it works on, and the organization of the conversation, flow run or work it is made in) and, after an application-wide suspension, for every call, a call that works for no organization answering to the application's suspensions only; a suspension or a case that cannot be read, or an application whose id cannot be resolved, refuses the call too; each suspension, resumption and refused call is recorded; a call already running when the agent is suspended is not stopped and ends after its bounded steps, a queued autonomous run is refused at its first model call rather than skipped, the dev companion and the platform's own services, which boot no application, answer to no suspension, and the person sees the suspension named on a live turn only, a reloaded conversation or a chat platform showing the turn as interrupted until the refusal's code is stored (#2827); and every AI use declared to affect a person reaches one of the approval gates or held operations above, so its human review is evidenced rather than only stated.","objectiveRef":"WILDO.AI.HUMAN_OVERSIGHT","title":"Put a person in front of what an AI agent does"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.AI.100-1","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-ai-rmf-end-user-problem-reporting-established","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-ai-rmf-1.0","sourceTitle":"Artificial Intelligence Risk Management Framework (AI RMF 1.0)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.AI.100-1","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-ai-rmf-incidents-tracked-and-responded-to","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-ai-rmf-1.0","sourceTitle":"Artificial Intelligence Risk Management Framework (AI RMF 1.0)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.AI.100-1","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-ai-rmf-user-input-capture-and-incident-response-implemented","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-ai-rmf-1.0","sourceTitle":"Artificial Intelligence Risk Management Framework (AI RMF 1.0)"},{"attributionNotice":"Credit the OWASP AI Exchange and link to https://owaspai.org where practical; do not imply OWASP endorsement or use OWASP marks.","authorityKind":"COMMUNITY_GUIDANCE","canonicalLocator":"https://owaspai.org/","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:owasp-ai-exchange-agentic-incident-detection-and-triage","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:owasp-ai-exchange-cc0-v1","sourceRef":"source:owasp-ai-exchange","sourceTitle":"OWASP AI Exchange"}],"intent":"A person reading an agent's stored reply in the in-app conversation, while working in an organization, can report it from that conversation, choosing a category from a closed vocabulary and optionally saying why; the report is recorded against the organization the conversation was held in (one held in another organization's context is refused) or, for a conversation held in the person's own context, the organization they are working in; it points at the reply and never copies it, and carries a severity derived from its category, a critical report's received audit row being a CRITICAL row that reaches what CRITICAL rows reach (the organization's SIEM route when one is configured, the audit-trail provider fan-out when it is enabled) while nobody is paged, since the engine has no alerting; only that organization's administrators triage it, read the reported reply and end it resolved or dismissed, with an outcome of that ending and a stated note, a guardrail remedy being a guardrail decision of that organization or of the reported conversation; each step is recorded on the audit trail after the report commits, best-effort (a failed write is logged, not retried), against triage and outcome targets the application declares or, absent a declaration, a day and a week, and a report open past a target is counted, not escalated; the operator reads reports across organizations only through the application audit door; a reporter's erasure removes their id and comment and keeps the report, and their access export carries the reports they filed and their comment but not the outcome note or who triaged and closed them; a person may file five reports a minute, thirty an hour and a hundred a day, counted per signed-in person and never per address, so colleagues behind one address each have their own bound, and refused past the bound with a client error naming when to retry, the first refusal of each window being recorded as an audit row; and a repeat report of the same reply by the same person while an earlier one is open answers with that open report at its current status, received or triaged, without who took it on, writing nothing and recording nothing again, even when the two arrive at once.","objectiveRef":"WILDO.AI.INCIDENT_HANDLING","title":"A person can report an agent's reply, and each report reaches an outcome against a declared target"},{"citations":[{"attributionNotice":"Credit the OWASP AI Exchange and link to https://owaspai.org where practical; do not imply OWASP endorsement or use OWASP marks.","authorityKind":"COMMUNITY_GUIDANCE","canonicalLocator":"https://owaspai.org/","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:owasp-ai-exchange-model-spend-bounded","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:owasp-ai-exchange-cc0-v1","sourceRef":"source:owasp-ai-exchange","sourceTitle":"OWASP AI Exchange"}],"intent":"An organization's model spend is bounded per period: every model call the engine's agent service makes in a conversational turn or a declared flow, a call nested in another included, is counted against the allowance of the organization that work is for, at every door that work runs through (an external agent, an autonomous agent, a chat-platform message, in-app chat and a declared flow), and in in-app chat one person cannot exhaust it. A turn whose allowance or person ceiling is spent, or whose allowance or consumption cannot be verified, is refused before it runs; a declared flow is asked before each of its model calls, and a call whose organization allowance is spent, or cannot be verified, is refused before the model runs; a flow is never counted against a person's ceiling; every refusal is recorded. The bound is what the application's plans, or its default features profile, grant. Consumption is counted after each call, at the usage the provider reported or, when it reported none, an estimate (four characters to a token, 6,240 tokens per image; the larger of the two when the report is marked incomplete; a coding agent reporting no token counter is charged the size of its context, which under-counts), so work already running, or a turn resumed from a decision, when a limit is reached may overrun it. A model call made outside any turn or flow, such as one in a job a flow enqueues, is counted only when it is attributed to an organization and is never refused (#2957). Embeddings, document extraction and content screening are not counted against that allowance: each is bounded per organization by a ceiling of its own, in the unit it is billed by (embedding tokens, extraction pages, screening text records), asked before every such call wherever it is made, a background job included; a call whose organization's ceiling for its unit is spent, or cannot be verified, is refused before the provider is called and the refusal is recorded; a refused embedding leaves its chunks unembedded until the period rolls, a refused extraction falls back without the document being judged unreadable, and a refused screening or moderation withholds the text as an unscreened one is; a ceiling that is not granted bounds nothing (#3030).","objectiveRef":"WILDO.AI.MODEL_SPEND_LIMIT","title":"Bound what an organization's agents spend on models, per period and per person"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.AI.100-1","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-ai-rmf-post-deployment-monitoring-implemented","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-ai-rmf-1.0","sourceTitle":"Artificial Intelligence Risk Management Framework (AI RMF 1.0)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.AI.100-1","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-ai-rmf-production-behaviour-monitored","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-ai-rmf-1.0","sourceTitle":"Artificial Intelligence Risk Management Framework (AI RMF 1.0)"},{"attributionNotice":"Credit the OWASP AI Exchange and link to https://owaspai.org where practical; do not imply OWASP endorsement or use OWASP marks.","authorityKind":"COMMUNITY_GUIDANCE","canonicalLocator":"https://owaspai.org/","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:owasp-ai-exchange-model-use-monitored","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:owasp-ai-exchange-cc0-v1","sourceRef":"source:owasp-ai-exchange","sourceTitle":"OWASP AI Exchange"},{"attributionNotice":"Contains public sector information licensed under the Open Government Licence v3.0. Link to the licence where possible, and do not imply official status or endorsement.","authorityKind":"GOVERNMENT_GUIDANCE","canonicalLocator":"https://www.gov.uk/government/publications/ai-cyber-security-code-of-practice/code-of-practice-for-the-cyber-security-of-ai","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:uk-ai-code-system-and-user-actions-logged","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:uk-open-government-licence-v3","sourceRef":"source:uk-ai-cyber-security-code-of-practice","sourceTitle":"Code of Practice for the Cyber Security of AI"}],"intent":"Every agent invocation the engine's agent runtime traces, including one that failed before a provider answered, leaves one record beside the invocation's provider-call record, naming the run when the call site or its work frame names one, that states the model ids the provider reported answering with, each tool the agent called and the phase it ended at, what the agent's content guardrails decided (how many personal fields its model was not sent and their categories, what screening concluded about each tool result, what output moderation judged and withheld) and how the invocation ended, with its failure code; the record holds no tool input or result, no prompt, reply or error message, no id of a row a tool read and no person id, and is kept for the application's declared operational-log period; recording is best-effort: an agent call whose provider-call record was written but whose operation record was not is counted rather than hidden, a call whose provider-call record itself failed to write leaves neither row and no count shows it, and a call made outside the engine's agent runtime leaves no record.","objectiveRef":"WILDO.AI.OPERATION_RECORD","title":"Record what every agent call did, without keeping what it read"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.AI.100-2e2025","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-ai-100-2-harmful-generation-detected-and-terminated","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-ai-100-2-e2025","sourceTitle":"Adversarial Machine Learning: A Taxonomy and Terminology of Attacks and Mitigations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.AI.600-1","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-ai-600-1-problematic-output-filtered","reviewedAt":"2026-10-18T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-ai-600-1","sourceTitle":"Artificial Intelligence Risk Management Framework: Generative Artificial Intelligence Profile"},{"attributionNotice":"Credit the OWASP AI Exchange and link to https://owaspai.org where practical; do not imply OWASP endorsement or use OWASP marks.","authorityKind":"COMMUNITY_GUIDANCE","canonicalLocator":"https://owaspai.org/","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:owasp-ai-exchange-harmful-output-detected-and-withheld","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:owasp-ai-exchange-cc0-v1","sourceRef":"source:owasp-ai-exchange","sourceTitle":"OWASP AI Exchange"}],"intent":"An agent that declares an output-moderation policy has everything its model writes — the reply, its shown reasoning, the input of a tool call and a structured answer — judged per harm category by a classifier before it is shown, stored, sent or acted on. Text at or above the severity the policy withholds, and text the classifier could not judge, is withheld and the turn ends there with the withholding recorded; an agent whose policy no selected classifier can serve, in every category it names, is refused before its model is called rather than run unjudged.","objectiveRef":"WILDO.AI.OUTPUT_MODERATION","title":"Judge what an AI model writes before anyone receives it"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.AI.100-1","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-ai-rmf-third-party-ai-components-identified","reviewedAt":"2026-09-25T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-ai-rmf-1.0","sourceTitle":"Artificial Intelligence Risk Management Framework (AI RMF 1.0)"},{"attributionNotice":"Credit the OWASP AI Exchange and link to https://owaspai.org where practical; do not imply OWASP endorsement or use OWASP marks.","authorityKind":"COMMUNITY_GUIDANCE","canonicalLocator":"https://owaspai.org/","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:owasp-ai-exchange-external-ai-services-recorded","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:owasp-ai-exchange-cc0-v1","sourceRef":"source:owasp-ai-exchange","sourceTitle":"OWASP AI Exchange"},{"attributionNotice":"Contains public sector information licensed under the Open Government Licence v3.0. Link to the licence where possible, and do not imply official status or endorsement.","authorityKind":"GOVERNMENT_GUIDANCE","canonicalLocator":"https://www.gov.uk/government/publications/ai-cyber-security-code-of-practice/code-of-practice-for-the-cyber-security-of-ai","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:uk-ai-code-ai-asset-inventory","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:uk-open-government-licence-v3","sourceRef":"source:uk-ai-cyber-security-code-of-practice","sourceTitle":"Code of Practice for the Cyber Security of AI"}],"intent":"Every AI capability the contracted service uses declares what it is for and whether it decides anything about a person, and every provider serving it is either run by the operator or named on the processor register with its legal entity, regions and sub-processors — so the AI a person's data reaches can be listed from what the application declares, and a new model vendor cannot be added unnoticed.","objectiveRef":"WILDO.AI.THIRD_PARTY_COMPONENTS","title":"Identify every third-party AI component the service runs on"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.AI.100-2e2025","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-ai-100-2-third-party-instruction-filtering","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-ai-100-2-e2025","sourceTitle":"Adversarial Machine Learning: A Taxonomy and Terminology of Attacks and Mitigations"},{"attributionNotice":"Credit the OWASP AI Exchange and link to https://owaspai.org where practical; do not imply OWASP endorsement or use OWASP marks.","authorityKind":"COMMUNITY_GUIDANCE","canonicalLocator":"https://owaspai.org/","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:owasp-ai-exchange-indirect-prompt-injection-screening","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:owasp-ai-exchange-cc0-v1","sourceRef":"source:owasp-ai-exchange","sourceTitle":"OWASP AI Exchange"},{"attributionNotice":"Contains public sector information licensed under the Open Government Licence v3.0. Link to the licence where possible, and do not imply official status or endorsement.","authorityKind":"GOVERNMENT_GUIDANCE","canonicalLocator":"https://www.gov.uk/government/publications/ai-cyber-security-code-of-practice/code-of-practice-for-the-cyber-security-of-ai","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:uk-ai-code-resilience-to-adversarial-input","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:uk-open-government-licence-v3","sourceRef":"source:uk-ai-cyber-security-code-of-practice","sourceTitle":"Code of Practice for the Cyber Security of AI"}],"intent":"An agent that declares prompt-injection screening has the content other people wrote — what its tools return, and the content of an inbound delivery that starts its turn — screened for an injected instruction by a classifier before its model reads it. Content judged an attack, and content that could not be screened, never reaches the model: a tool result arrives as a notice that it was withheld and an inbound delivery does not start the turn, each recorded with where the content came from; where no selected classifier can serve an agent's screening, a turn that would bring it third-party content — one that offers it tools, or one an inbound delivery would start — is refused rather than run unscreened.","objectiveRef":"WILDO.AI.UNTRUSTED_CONTENT_SCREENING","title":"Screen what an AI model reads from third parties before it reads it"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2024/1689/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:eu-ai-act-high-risk-candidate-use-identified","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-ai-act-2024-1689","sourceTitle":"Regulation (EU) 2024/1689 laying down harmonised rules on artificial intelligence (Artificial Intelligence Act)"},{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2024/1689/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:eu-ai-act-prohibited-practice-identified","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-ai-act-2024-1689","sourceTitle":"Regulation (EU) 2024/1689 laying down harmonised rules on artificial intelligence (Artificial Intelligence Act)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.AI.100-1","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-ai-rmf-intended-purpose-and-legal-context-documented","reviewedAt":"2026-10-18T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-ai-rmf-1.0","sourceTitle":"Artificial Intelligence Risk Management Framework (AI RMF 1.0)"},{"attributionNotice":"Credit the OWASP AI Exchange and link to https://owaspai.org where practical; do not imply OWASP endorsement or use OWASP marks.","authorityKind":"COMMUNITY_GUIDANCE","canonicalLocator":"https://owaspai.org/","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:owasp-ai-exchange-ai-use-legal-class-assessed","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:owasp-ai-exchange-cc0-v1","sourceRef":"source:owasp-ai-exchange","sourceTitle":"OWASP AI Exchange"},{"attributionNotice":"Contains public sector information licensed under the Open Government Licence v3.0. Link to the licence where possible, and do not imply official status or endorsement.","authorityKind":"GOVERNMENT_GUIDANCE","canonicalLocator":"https://www.gov.uk/government/publications/ai-cyber-security-code-of-practice/code-of-practice-for-the-cyber-security-of-ai","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:uk-ai-code-ai-purpose-documented","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:uk-open-government-licence-v3","sourceRef":"source:uk-ai-cyber-security-code-of-practice","sourceTitle":"Code of Practice for the Cyber Security of AI"}],"intent":"Every AI use the contracted service runs, whether declared on the capability or on the agent that runs it, declares its use domain from a closed vocabulary, and its regulatory class is derived from that domain rather than asserted: where the EU AI Act applies, a use in an Annex III area is reported as a high-risk candidate and a use in an Article 5(1) practice as a prohibited-practice candidate, each marked for a person to confirm and neither stopping the build.","objectiveRef":"WILDO.AI.USE_CLASSIFICATION","title":"Classify every AI use the service runs by its declared domain"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-accountability-demonstration","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-detect-attributable-event-record","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"A security-relevant action records who performed it, and never disguises an unattributable action as an ordinary automated one; read-through access to an external system carries the real initiating user through the shared service principal, and an outbound deletion there names the subject it served and the system it reached.","objectiveRef":"WILDO.AUDIT.ATTRIBUTION","title":"Name who performed a security-relevant action"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-audit-record-context-binding","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-audit-record-context-binding-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"The actor and tenant an audit row names survive the trusted-system write that persists it, and a log record names which application and which environment produced it — so a record cannot silently lose or change the principal, tenant or deployment it belongs to.","objectiveRef":"WILDO.AUDIT.CONTEXT_ATTRIBUTION","title":"Bind a record to the context it actually ran in"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-audit-record-content-and-protection","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-audit-record-content-and-protection-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"A privileged action on a resource is attributable, and the authorization effect it had is reconstructable from the record itself rather than re-derived from role tables afterwards; the configuration deciding what the trail captures is governed as part of the trail.","objectiveRef":"WILDO.AUDIT.EVIDENCE_INTEGRITY","title":"Govern the audit trail as evidence in its own right"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.CSWP.29","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-detect-security-event-logging","reviewedAt":"2026-09-01T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"Authentication, authorization, privilege, credential and security-configuration changes each emit a typed auditable event; non-human privileged access is audited or refused; and the absence of the audit delivery path is surfaced at boot rather than tolerated silently.","objectiveRef":"WILDO.AUDIT.SECURITY_EVENT","title":"Emit a typed event for every security-relevant change"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-transaction-authorization-separation","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-transaction-authorization-separation-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"An increase in a credit balance is reachable only through a system or payment-gated door, so no ordinary principal can grant itself economic value.","objectiveRef":"WILDO.BILLING.CREDIT_GRANT_INTEGRITY","title":"Gate a credit grant to system or payment authority"},{"citations":[{"attributionNotice":"Identify HHS as the authority and link to the current official source; no HHS content bytes are bundled under this record.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html","contentUsePermission":"REQUIRES_ADDITIONAL_RIGHTS","metadataCitationAuthorized":true,"requirementRef":"source-requirement:hhs-security-transmission-confidentiality","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:paul-cayon-assurance-owner","rightsRef":"rights:hhs-reference-only-v1","sourceRef":"source:hhs-hipaa-security-rule","sourceTitle":"HIPAA Security Rule"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_GUIDANCE","canonicalLocator":"https://doi.org/10.6028/NIST.SP.800-66r2","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-66-transmission-confidentiality","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-66-rev-2","sourceTitle":"Implementing the HIPAA Security Rule: A Cybersecurity Resource Guide"}],"intent":"Material a schema declares backend-only does not cross the client boundary, except at a single first exposure that is itself audited.","objectiveRef":"WILDO.DATA.CONFIDENTIALITY","title":"Keep backend-only material off the client boundary"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-information-integrity-verification","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-information-integrity-verification-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"A uniqueness or integrity control the schema declares is proven to exist in the datastore before the application serves traffic, rather than assumed to have been created.","objectiveRef":"WILDO.DATA.INTEGRITY_CONSTRAINTS","title":"Prove a declared constraint exists before serving traffic"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-erasure-with-retention-carve-out","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-media-sanitization-and-disposal","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-media-sanitization-and-disposal-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"Destruction of an identity, a tenant or its data is a deliberate, attributable, evidenced decision, reversible until its declared window elapses and then carried out on schedule; an erased-but-retained record is hidden from, and immutable to, every ORDINARY access path — the only door is an audited see-through read — and its derived copies are excluded by a live check against the parent row rather than by waiting for a sweep.","objectiveRef":"WILDO.DATA.SECURE_LIFECYCLE","title":"Destroy data deliberately, on a recorded schedule"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-shared-resource-isolation","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-shared-resource-isolation-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"A caller cannot widen its own query scope: tenancy narrowing is derived from the resolved execution context and never offered as a parameter — to a client, to an agent, or to a retrieval surface — and where the read is a similarity search the predicate is evaluated INSIDE the traversal rather than over its results, then re-checked by an authorized read of the owning row.","objectiveRef":"WILDO.DATA.TENANT_ISOLATION","title":"Derive tenancy from the caller, never from the request"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-transaction-recovery-integrity","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-transaction-recovery-integrity-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"A resource declares its persistence isolation before it may sit on a non-default adapter, and a configuration whose cross-resource writes could not be atomic is refused when the registry is built rather than discovered under load.","objectiveRef":"WILDO.DATA.TRANSACTIONAL_INTEGRITY","title":"Refuse a configuration that cannot write atomically"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-entitlement-change-authority","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"Feature and entitlement writes are reachable only through an operator-gated door, so a principal cannot widen what it is entitled to.","objectiveRef":"WILDO.ENTITLEMENT.NO_SELF_GRANT","title":"Keep an entitlement write operator-gated"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-identify-service-identity-verification","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"A client identity is bound to a domain the client demonstrably controls, and both a client identity created by a party that authenticated to nothing and every refused client assertion are recorded.","objectiveRef":"WILDO.IDENTITY.CLIENT_IDENTITY_ASSERTION","title":"Bind a client identity to a verifiable assertion"},{"citations":[{"attributionNotice":"Identify HHS as the authority and link to the current official source; no HHS content bytes are bundled under this record.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html","contentUsePermission":"REQUIRES_ADDITIONAL_RIGHTS","metadataCitationAuthorized":true,"requirementRef":"source-requirement:hhs-security-credential-management","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:paul-cayon-assurance-owner","rightsRef":"rights:hhs-reference-only-v1","sourceRef":"source:hhs-hipaa-security-rule","sourceTitle":"HIPAA Security Rule"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-credential-state-transitions","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_GUIDANCE","canonicalLocator":"https://doi.org/10.6028/NIST.SP.800-66r2","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-66-credential-management","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-66-rev-2","sourceTitle":"Implementing the HIPAA Security Rule: A Cybersecurity Resource Guide"}],"intent":"Issuance, refresh, rotation, revocation and expiry of a credential are explicit attributable transitions; credential theft is detected and answered by invalidation; and a revocation actually terminates the sessions and tokens it names rather than merely marking a record.","objectiveRef":"WILDO.IDENTITY.CREDENTIAL_LIFECYCLE","title":"Make every credential state transition explicit"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-delegated-access-authorization","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"A third party acts for a user only on that user’s recorded authorization: approval, refusal, persistence and failure of the delegated exchange are each audited, proof of possession is enforced on the exchange, and the issued token carries no more than the grant declared.","objectiveRef":"WILDO.IDENTITY.DELEGATED_AUTHORIZATION","title":"Let a user authorize third-party access deliberately"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-automated-account-management","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-automated-account-management-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"Where an application opts in, a directory becomes the authority for accounts and for unit membership — which is an authorization grant, not a label — and the switches conferring that authority are declared explicitly rather than implied by the presence of a connection.","objectiveRef":"WILDO.IDENTITY.DIRECTORY_PROVISIONING","title":"Honour the directory as the provisioning authority"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-account-enable-disable-authority","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-account-enable-disable-authority-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"A change to whether a principal may authenticate runs through one guarded, evidenced authority: the status carrying it is excluded from ordinary updates, so the change cannot arrive as a side effect of an unrelated write.","objectiveRef":"WILDO.IDENTITY.LIFECYCLE","title":"Record every change to whether a principal may authenticate"},{"citations":[{"attributionNotice":"Identify HHS as the authority and link to the current official source; no HHS content bytes are bundled under this record.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://www.hhs.gov/hipaa/for-professionals/security/index.html","contentUsePermission":"REQUIRES_ADDITIONAL_RIGHTS","metadataCitationAuthorized":true,"requirementRef":"source-requirement:hipaa-security-authentication-controls","reviewedAt":"2026-09-01T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:hhs-reference-only-v1","sourceRef":"source:hhs-hipaa-security-rule","sourceTitle":"HIPAA Security Rule"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/63/b/4/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-63b-authenticator-activation-verified","reviewedAt":"2026-09-17T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-63b-4","sourceTitle":"Digital Identity Guidelines: Authentication and Authenticator Management"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/63/b/4/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-63b-distinct-authentication-factors","reviewedAt":"2026-09-17T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-63b-4","sourceTitle":"Digital Identity Guidelines: Authentication and Authenticator Management"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/63/b/4/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-63b-out-of-band-channel-separation","reviewedAt":"2026-09-17T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-63b-4","sourceTitle":"Digital Identity Guidelines: Authentication and Authenticator Management"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_GUIDANCE","canonicalLocator":"https://doi.org/10.6028/NIST.SP.800-66r2","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-66-authentication-controls","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-66-rev-2","sourceTitle":"Implementing the HIPAA Security Rule: A Cybersecurity Resource Guide"}],"intent":"Enrolled second factors are verified through one authority that is replay-resistant and timing-safe, so no caller builds a second, weaker door onto the same credential; and a session counts a second factor only when it proves something the first factor did not, so two methods reaching one channel cannot together satisfy a multi-factor requirement.","objectiveRef":"WILDO.IDENTITY.MULTI_FACTOR","title":"Verify enrolled second factors through one authority, and count only independent proofs"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-redirect-target-constraint","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"A registered OAuth redirect target is constrained to a safe absolute URL, closing the open-redirect and stored-XSS delegation primitive a permissive target would otherwise create.","objectiveRef":"WILDO.IDENTITY.REDIRECT_TARGET_VALIDATION","title":"Constrain a registered redirect target"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-govern-authentication-posture-change","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/63/b/4/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-63b-phishing-resistant-authentication","reviewedAt":"2026-09-17T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-63b-4","sourceTitle":"Digital Identity Guidelines: Authentication and Authenticator Management"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/63/c/4/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-63c-assertion-states-its-authentication","reviewedAt":"2026-09-17T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-63c-4","sourceTitle":"Digital Identity Guidelines: Federation and Assertions"}],"intent":"How principals may authenticate — the MFA, password, lockout, methods, step-up and session posture, whether single sign-on is enforced, which identity provider is trusted, and whether its assertions are actually verified — is explicitly configured, and every genuine change to that posture is detected at startup and evidenced once, from the runtime that puts it into effect.","objectiveRef":"WILDO.IDENTITY.SESSION_ASSURANCE","title":"Decide, and record changes to, the assurance a session carries"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-concurrent-session-control","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-concurrent-session-control-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"A principal holds a bounded number of concurrent sessions, and the eviction enforcing that bound retires the OLDEST refresh chain — the property that pushes a stolen chain out instead of a legitimate one.","objectiveRef":"WILDO.IDENTITY.SESSION_CONCURRENCY_LIMIT","title":"Bound the concurrent sessions a principal holds"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-cryptographic-key-establishment-and-management","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-cryptographic-key-establishment-and-management-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"A rotated signing key can be given an explicit retirement instant, after which it stops being advertised and stops verifying tokens — so an aged or compromised prior key need not stay trusted until someone edits configuration.","objectiveRef":"WILDO.IDENTITY.SIGNING_KEY_LIFECYCLE","title":"Bound the lifetime of a retired signing key"},{"citations":[{"attributionNotice":"Identify HHS as the authority and link to the current official source; no HHS content bytes are bundled under this record.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html","contentUsePermission":"REQUIRES_ADDITIONAL_RIGHTS","metadataCitationAuthorized":true,"requirementRef":"source-requirement:hhs-security-person-or-entity-reverification","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:paul-cayon-assurance-owner","rightsRef":"rights:hhs-reference-only-v1","sourceRef":"source:hhs-hipaa-security-rule","sourceTitle":"HIPAA Security Rule"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-reauthentication-for-privileged-action","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-reauthentication-for-privileged-action-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/63/b/4/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-63b-reauthentication-at-assurance-level","reviewedAt":"2026-09-17T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-63b-4","sourceTitle":"Digital Identity Guidelines: Authentication and Authenticator Management"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_GUIDANCE","canonicalLocator":"https://doi.org/10.6028/NIST.SP.800-66r2","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-66-person-or-entity-reverification","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-66-rev-2","sourceTitle":"Implementing the HIPAA Security Rule: A Cybersecurity Resource Guide"}],"intent":"A high-impact action requires a fresh re-proof of identity, over any factor the principal actually holds, and that ceremony cannot be satisfied by a credential presented for a different purpose.","objectiveRef":"WILDO.IDENTITY.STEP_UP_AUTHENTICATION","title":"Re-prove identity before a high-impact action"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-assertion-integrity","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"An ID token’s protocol and security claims are authored by the server alone, from one named reserved-claim set, so a caller cannot smuggle a reserved claim in through supplied extras.","objectiveRef":"WILDO.IDENTITY.TOKEN_INTEGRITY","title":"Author a token’s protocol claims on the server only"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-detect-outbound-connection-monitoring","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"Outbound traffic leaves through a single named egress per capability, and every physical call is recorded — provider, model, usage and outcome for a provider call, the initiating actor for an administrative probe — so a reviewer can enumerate what was sent and when.","objectiveRef":"WILDO.INTEGRATION.OUTBOUND_ACTIVITY_AUDIT","title":"Attribute every outbound connection the application makes"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-authority-not-inferred-from-state","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"A self-reported lifecycle stage confers no capability and cannot cross a scope boundary; authority comes only from a decision an authorized party actually made.","objectiveRef":"WILDO.LIFECYCLE.STAGE_IS_NOT_AUTHORITY","title":"Confer no capability from a self-reported stage"},{"citations":[{"attributionNotice":"Credit the OWASP AI Exchange and link to https://owaspai.org where practical; do not imply OWASP endorsement or use OWASP marks.","authorityKind":"COMMUNITY_GUIDANCE","canonicalLocator":"https://owaspai.org/","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:owasp-ai-exchange-external-agent-access-rate-limited","reviewedAt":"2026-10-20T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:owasp-ai-exchange-cc0-v1","sourceRef":"source:owasp-ai-exchange","sourceTitle":"OWASP AI Exchange"}],"intent":"An authenticated caller reaching the application from outside its own screens drives a bounded amount of work per window and is refused before anything is dispatched once it passes the bound: an agent's A2A turns and an MCP client's tool calls are counted against the principal's owner, the delegating person or the organization or application whose machine credential it is, never against the credential, so every credential an organization issues shares one window; a linked member's chat-platform messages, commands and searches are counted against that member, within the organization the delivery arrived in. An A2A or MCP caller over the bound is answered as a client error naming when it may retry, and the first such refusal of each window, and only it, is recorded as an audit row naming the transport, the owner counted, the window and the limit both as declared and as enforced, so a caller saturated for a whole window leaves one row rather than one per request; the row is written without holding up the refusal, and a failed write is logged, not retried. A chat member over the bound is answered with a refusal reply, a refused command or search being recorded as that command's run and a refused message not recorded. In development and test every bound is relaxed by a fixed factor; staging and production enforce the declared number. When the A2A or MCP counter store is unavailable the bound is not enforced and the outage is a warning log line, never a refusal; when a chat message or command counter cannot be read nothing is refused and the delivery is tried again, and when the search counter cannot be read the search fails and the person is asked to try again. An operation's own declared rate limit is a separate guard on every plane that dispatches it (an MCP tool call, an agent's function tool, a chat command, and the operation's own HTTP route once a signed-in person or machine is authorized), counted per client (the machine credential, else the person: through a client they delegated to, in the application, as a linked chat member, or signed in) in a bucket of each plane's own, and failing closed when its counter cannot be read; on the HTTP route a caller who is not a signed-in person or machine (a visitor, a public request, a link token) is counted per source address instead, a count whose refusals are not recorded, each request is counted once, and a request whose credential does not verify is counted by neither; the first refusal of each of its declared windows is recorded as its own audit row naming the plane, the operation, the subject counted and the window as declared and as enforced. It bounds a burst of requests, not what they spend.","objectiveRef":"WILDO.OPERATIONS.AUTHENTICATED_BURST_LIMIT","title":"Bound how fast an authenticated caller from outside the application may drive work"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-error-handling-diagnostics","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-error-handling-diagnostics-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"A constraint conflict is reported with the identity that was violated rather than as an opaque datastore failure, so an operator can tell a benign duplicate from an unexpected collision.","objectiveRef":"WILDO.OPERATIONS.CONFLICT_DIAGNOSTICS","title":"Report a conflict by the identity it violated"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-declared-interface-integrity","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"A declared, API-reachable operation stays reachable and is actually implemented: an interface must not report success for an action it did not perform, and a named verb must not silently widen into an unconstrained write over fields its resource never exposed for update.","objectiveRef":"WILDO.OPERATIONS.EXECUTION_INTEGRITY","title":"Never report success for an action that was not performed"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-denial-of-service-resource-bounds","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-denial-of-service-resource-bounds-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"An unauthenticated request consumes a bounded amount of resource, and an over-limit request is answered as a client error rather than surfacing as a server failure.","objectiveRef":"WILDO.OPERATIONS.RESOURCE_LIMIT","title":"Bound what an unauthenticated request may consume"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-bulk-disclosure-record","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.CSWP.01162020","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-privacy-disclosure-records","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-privacy-framework-1.0","sourceTitle":"NIST Privacy Framework: A Tool for Improving Privacy through Enterprise Risk Management, Version 1.0"}],"intent":"A bulk export of a resource collection is a recorded event naming the resource exported, the operation it was taken from, and the format it was rendered in.","objectiveRef":"WILDO.PRIVACY.COLLECTION_DATA_EXPORT","title":"Record a bulk export of a resource collection"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-consent-withdrawal-effect","reviewedAt":"2026-10-05T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.CSWP.01162020","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-privacy-individual-preference-enablement","reviewedAt":"2026-10-05T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-privacy-framework-1.0","sourceTitle":"NIST Privacy Framework: A Tool for Improving Privacy through Enterprise Risk Management, Version 1.0"}],"intent":"Processing that rests on a person's consent runs only while that consent stands: a purpose the application requires of its whole service, or that an operation declares it cannot run without, is checked on every user-initiated surface — REST, MCP, A2A and conversational turns, started or resumed — and a person who has not granted it is refused, the refusal recorded, with a consent that cannot be read counted as none granted; and a browser-side provider that rests on a consent purpose is started only once that purpose is granted and only if a withdrawal can stop it, so one that would inject a script nothing could stop is never started at all.","objectiveRef":"WILDO.PRIVACY.CONSENT_ENFORCEMENT","title":"Run processing that rests on consent only while the consent stands"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-consent-demonstrability","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.CSWP.01162020","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-privacy-processing-authorization-maintenance","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-privacy-framework-1.0","sourceTitle":"NIST Privacy Framework: A Tool for Improving Privacy through Enterprise Risk Management, Version 1.0"}],"intent":"A consent decision — given, changed or withdrawn — is recorded exactly once and never lost to a race, naming the previous and the resulting value; every verb able to change consent routes through one emission point, and resetting a subject’s privacy preferences is itself such a decision.","objectiveRef":"WILDO.PRIVACY.CONSENT_RECORD","title":"Record a consent decision exactly once"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-data-minimisation","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.AI.100-1","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-ai-rmf-privacy-risk-examined","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-ai-rmf-1.0","sourceTitle":"Artificial Intelligence Risk Management Framework (AI RMF 1.0)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.CSWP.01162020","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-privacy-selective-collection-and-disclosure","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-privacy-framework-1.0","sourceTitle":"NIST Privacy Framework: A Tool for Improving Privacy through Enterprise Risk Management, Version 1.0"}],"intent":"Only the data a declared purpose requires leaves its boundary: an external processor receives the payload and nothing identifying the requester or its row, observability surfaces receive summaries rather than the raw content, and a device-stored pseudonymous identifier is collected only under an explicit application opt-in — absent that policy, not at all — and can be withdrawn or narrowed afterwards.","objectiveRef":"WILDO.PRIVACY.DATA_MINIMIZATION","title":"Send only what the declared purpose requires"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.CSWP.01162020","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-privacy-deletion-communicated-across-ecosystem","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-privacy-framework-1.0","sourceTitle":"NIST Privacy Framework: A Tool for Improving Privacy through Enterprise Risk Management, Version 1.0"}],"intent":"A subject erasure accounts per store rather than returning one verdict for the request: each of the subject's dependent relationships — its direct dependents and every relationship below a dependent the erasure deletes, at any depth — is reported with the disposition its configuration declared and whether its teardown actually ran, a relationship nobody classified at any depth refuses the erasure before anything is written, and each registered external erasure effect is reported with its own outcome, where any outcome that may leave data live at a third party — including one the controller deliberately acknowledged — never reads as complete; a store whose records a system of record holds is reported as handled at that source, which answers requests about its own records, and a copy the application keeps of them beyond the source is erased as the application's own; and where erasure deletes rows in an external system or destroys the subject's own third-party credentials, it leaves a durable record naming that store. The accounting does not extend below a relationship whose rows the erasure retains, or to derived copies.","objectiveRef":"WILDO.PRIVACY.ERASURE_PROPAGATION","title":"Account per store for what a subject erasure reached"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-lawful-basis-per-purpose","reviewedAt":"2026-08-03T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"}],"intent":"Every purpose for which this application processes personal data declares the lawful basis it rests on, and a basis whose lawfulness depends on a balancing test carries that assessment rather than asserting a conclusion nobody reached; an application that has declared no basis at all is reported as not having answered, never as having nothing to declare.","objectiveRef":"WILDO.PRIVACY.LAWFUL_BASIS","title":"State the ground each processing purpose stands on"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-records-of-processing-categories","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.CSWP.01162020","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-privacy-data-element-inventory","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-privacy-framework-1.0","sourceTitle":"NIST Privacy Framework: A Tool for Improving Privacy through Enterprise Risk Management, Version 1.0"}],"intent":"The application declares, on the field itself, which CATEGORIES of personal data it holds — never inferred from the field’s name, because an inventory assembled by pattern-matching identifiers is a guess whose misses go silently undisclosed.","objectiveRef":"WILDO.PRIVACY.PERSONAL_DATA_INVENTORY","title":"Declare in the schema which fields hold personal data"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-compatible-further-processing","reviewedAt":"2026-10-05T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.CSWP.01162020","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-privacy-further-use-authorization","reviewedAt":"2026-10-05T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-privacy-framework-1.0","sourceTitle":"NIST Privacy Framework: A Tool for Improving Privacy through Enterprise Risk Management, Version 1.0"}],"intent":"A further use of a tenant's records of how its deciders decided on agents' proposals — exporting them as evaluation data — runs only while the tenant holds an active authorization naming the documented basis it rests on, either its controller's documented instruction to a processor or a controller's assessment that the further use is compatible with the original purpose: an authorization is never left active without its basis, a granted one is withdrawn only by revoking it, and every change to it is recorded; a case subject the tenant excluded (a client, a patient, an account), and a privileged case, or one holding special-category or criminal-offence data, without its subject's recorded consent, leave in no export, and while any case subject is excluded a case whose subject cannot be read is left out rather than assumed to have none; every refused export is recorded; and withdrawing the basis, or erasing a case, marks every dataset already exported under it as no longer usable. It marks the export ledger and cannot recall a dataset already delivered.","objectiveRef":"WILDO.PRIVACY.SECONDARY_USE_AUTHORIZATION","title":"Rest every further use of client work on a recorded authorization"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-storage-limitation","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.CSWP.01162020","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-privacy-destruction-according-to-policy","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-privacy-framework-1.0","sourceTitle":"NIST Privacy Framework: A Tool for Improving Privacy through Enterprise Risk Management, Version 1.0"}],"intent":"Declared row-retention windows are enforced, and a configuration whose derived copies of subject text could outlive the row they came from — unreachable by the erasure seams — is refused at startup.","objectiveRef":"WILDO.PRIVACY.STORAGE_LIMITATION","title":"Keep data no longer than its declared window"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-subject-access-portability","reviewedAt":"2026-08-03T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.CSWP.01162020","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-privacy-data-access-for-review-and-transmission","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-privacy-framework-1.0","sourceTitle":"NIST Privacy Framework: A Tool for Improving Privacy through Enterprise Risk Management, Version 1.0"}],"intent":"Authorized subject access and portability exports are purpose-specific, resource-opted-in, subject-isolated and auditable: the export event names the purpose, the subject, the resource types included, the record count and the fields withheld as derived.","objectiveRef":"WILDO.PRIVACY.SUBJECT_DATA_EXPORT","title":"Export subject data safely"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-erasure-and-restriction","reviewedAt":"2026-09-01T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.CSWP.01162020","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-privacy-data-access-for-deletion","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-privacy-framework-1.0","sourceTitle":"NIST Privacy Framework: A Tool for Improving Privacy through Enterprise Risk Management, Version 1.0"}],"intent":"A subject’s erasure request is recorded on intake whether the subject or the controller raised it, may be withdrawn by the subject while it is pending, is executed on the declared schedule, and terminates the erased person’s sessions.","objectiveRef":"WILDO.PRIVACY.SUBJECT_ERASURE","title":"Execute a subject erasure request, and evidence it"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-processor-engagement","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.CSWP.01162020","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-privacy-third-party-role-inventory","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-privacy-framework-1.0","sourceTitle":"NIST Privacy Framework: A Tool for Improving Privacy through Enterprise Risk Management, Version 1.0"},{"attributionNotice":"Identify the PCI Security Standards Council as the owner of PCI DSS and link to its document library; never state or imply PCI certification, compliance or endorsement.","authorityKind":"PROPRIETARY_STANDARD","canonicalLocator":"https://www.pcisecuritystandards.org/document_library/","contentUsePermission":"REQUIRES_ADDITIONAL_RIGHTS","metadataCitationAuthorized":true,"requirementRef":"source-requirement:pci-dss-third-party-service-provider-list","reviewedAt":"2026-09-25T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:pci-ssc-reference-only-v1","sourceRef":"source:pci-dss-4.0.1","sourceTitle":"Payment Card Industry Data Security Standard: Requirements and Testing Procedures, Version 4.0.1"}],"intent":"Routing data to an external service makes that service a processor of it, so such routing is opt-in by construction: nothing leaves unless the application selects a provider for that capability, and with no selection the work is served locally with no egress at all.","objectiveRef":"WILDO.PRIVACY.THIRD_PARTY_PROCESSING","title":"Name the processors that data is routed to"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-risk-appetite-and-tolerance-statements","reviewedAt":"2026-08-03T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-risk-documentation-and-prioritization-method","reviewedAt":"2026-08-03T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-risk-response-options-direction","reviewedAt":"2026-08-03T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"The exposures an application carries are DERIVED from what it declares and implements rather than asserted by anyone — which capabilities are enabled, which providers are vendor-hosted, which resources have answered the personal-data question, what an external agent can reach — and each carries the treatment its operator chose with the reasoning for that choice. A treatment claiming an exposure is not taken at all is checked against the measurement and reported when the two disagree, so the register is a set of statements the product itself can contradict rather than a document about intentions.","objectiveRef":"WILDO.RISK.TREATMENT_DECLARED","title":"Say what the risks are, and what was decided about each"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-authenticator-storage-protection","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-authenticator-storage-protection-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"The shape of a provider’s secret contract is tracked so that drift in it is detectable, without ever persisting the secret values themselves.","objectiveRef":"WILDO.SECRETS.CONTRACT_INTEGRITY","title":"Detect drift in a values-free secret contract"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-authenticator-disclosure-record","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"The first disclosure of server-minted secret material is an attributable, audited event.","objectiveRef":"WILDO.SECRETS.DISCLOSURE_AUDIT","title":"Audit the first disclosure of minted secret material"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-fail-secure-behaviour","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"A control that cannot be evaluated refuses what it guards, and stays diagnosable while doing so: untrusted input is rejected whole rather than partly sanitized, and a validator whose dependency is unavailable fails closed without its degradation being mistaken for a rejected signature.","objectiveRef":"WILDO.SECURITY.FAIL_CLOSED","title":"Refuse rather than degrade when a control cannot run"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-malicious-code-protection","reviewedAt":"2026-08-03T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-malicious-code-protection-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"Content uploaded into the application is inspected for malicious code before it is servable, and the inspection reaches a member of the file's own status vocabulary — clean, infected, quarantined or failed — rather than an opaque success, so a file that was never inspected and a file that passed are distinguishable.","objectiveRef":"WILDO.SECURITY.INGESTED_CONTENT_INSPECTION","title":"Inspect ingested content before it can be served"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.SP.800-218","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-218-code-access-least-privilege","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-218","sourceTitle":"Secure Software Development Framework (SSDF) Version 1.1"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.SP.800-218","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-218-development-environment-separated","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-218","sourceTitle":"Secure Software Development Framework (SSDF) Version 1.1"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.SP.800-218","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-218-development-toolchain-specified","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-218","sourceTitle":"Secure Software Development Framework (SSDF) Version 1.1"},{"attributionNotice":"Credit the OWASP AI Exchange and link to https://owaspai.org where practical; do not imply OWASP endorsement or use OWASP marks.","authorityKind":"COMMUNITY_GUIDANCE","canonicalLocator":"https://owaspai.org/","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:owasp-ai-exchange-coding-brief-indirect-prompt-injection-screening","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:owasp-ai-exchange-cc0-v1","sourceRef":"source:owasp-ai-exchange","sourceTitle":"OWASP AI Exchange"}],"intent":"Code a coding agent writes into the application is produced inside the permission ceiling and write scope the application declares, by coding-agent vendors it declares with an established compliance profile, and only in the environments its execution profile admits, which never include production, and every change accepted through the creation lane's accept door is attributed to whoever accepted it: the host answers every permission request the agent raises and refuses a declared edit outside the task's scope even under an unrestricted ceiling; an agent that cannot be held to a narrower ceiling, because it never asks before writing or asks only when the host supplies its escalating configuration, runs only under a ceiling declared unrestricted; what a run changed outside its scope inside the application, a shell command's writes included, is recorded after the run, except a new file a shell command creates outside the application, which nothing lists; an acceptance the system makes under the autonomy posture is committed under the companion's own identity, never a person's, so the history says which accepted changes a person accepted; and a commit an agent makes itself through a shell command carries the local identity and is not attributed to the agent. What a coding agent's brief carries from outside the repository (what a research step brought in from the web, and the specification elements a step filled from it) travels only in sections marked third-party. The classifier the application binds in its build-time companion scope screens it, and a flagged element is withheld from that brief, though it stays in the specifications and the `wildo context elements` door returns it unscreened (#2938). With no classifier, or one that cannot answer, it travels marked as unscreened, never unmarked. Which text came from the web is recorded per family and aspect, never per statement. Text a step writes after reading research-informed input travels as trusted (#2937). When the catalog cannot say which elements came from the web, the served and website-plan elements are routed as third-party, marked and never blocked.","objectiveRef":"WILDO.SOFTWARE.AI_PRODUCED_CHANGE_CONTROL","title":"Produce AI-written code inside declared bounds and attribute every accepted change"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-configuration-settings-enforcement","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-configuration-settings-enforcement-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"A server-owned field has exactly one named authority that writes it, and that authority is proven at boot rather than assumed — so no second path can set the field and no reader has to work out which value is current.","objectiveRef":"WILDO.SOFTWARE.AUTHORITY_INTEGRITY","title":"Give every server-owned field exactly one named authority"}],"mappingRef":"assurance-external-mapping:wildo-safe-baseline-v1","mappingVersion":1,"normativeSourceContentIncluded":false,"tailoringCaveat":"A control catalog requires tailoring, implementation and assessment; catalog inclusion is not proof of operation. This mapping records which external source each Wildo objective was reviewed against. It is not a conformity assertion, it claims no operating effectiveness, and it reproduces no normative source text.","unmapped":[{"objectiveRef":"WILDO.ACCESS.SEGREGATION_OF_DUTIES","reason":"The assurance authority basis states no expectation for this objective, so no source requirement has been reviewed against it. An objective the framework has not bound cannot honestly cite an external source (#207).","title":"Require a second person for an act nobody else can check"},{"objectiveRef":"WILDO.AUDIT.TAMPER_RESISTANCE","reason":"The assurance authority basis states no expectation for this objective, so no source requirement has been reviewed against it. An objective the framework has not bound cannot honestly cite an external source (#207).","title":"Let a named runtime principal append to the audit trail and never alter it"},{"objectiveRef":"WILDO.BILLING.PROVIDER_RECONCILIATION","reason":"The assurance authority basis states no expectation for this objective, so no source requirement has been reviewed against it. An objective the framework has not bound cannot honestly cite an external source (#207).","title":"Reconcile local billing state against the provider"},{"objectiveRef":"WILDO.BILLING.USAGE_REPORTING","reason":"The assurance authority basis states no expectation for this objective, so no source requirement has been reviewed against it. An objective the framework has not bound cannot honestly cite an external source (#207).","title":"Report metered usage to the billing provider"},{"objectiveRef":"WILDO.DOCUMENTS.APPROVAL_BEFORE_PRESENTATION","reason":"The assurance authority basis states no expectation for this objective, so no source requirement has been reviewed against it. An objective the framework has not bound cannot honestly cite an external source (#207).","title":"Show or ask a person to accept a governed document only once it is approved"},{"objectiveRef":"WILDO.NETWORK.OUTBOUND_TARGET_CONTROL","reason":"The assurance authority basis states no expectation for this objective, so no source requirement has been reviewed against it. An objective the framework has not bound cannot honestly cite an external source (#207).","title":"Reach only an admitted address from a destination someone else chose"},{"objectiveRef":"WILDO.SECRETS.CREDENTIAL_SCOPING","reason":"The assurance authority basis states no expectation for this objective, so no source requirement has been reviewed against it. An objective the framework has not bound cannot honestly cite an external source (#207).","title":"A configuration cannot choose which secret a vendor or an agent receives"}]}
|
|
1
|
+
{"attributionNotices":["Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","Contains public sector information licensed under the Open Government Licence v3.0. Link to the licence where possible, and do not imply official status or endorsement.","Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","Credit the OWASP AI Exchange and link to https://owaspai.org where practical; do not imply OWASP endorsement or use OWASP marks.","Identify HHS as the authority and link to the current official source; no HHS content bytes are bundled under this record.","Identify the PCI Security Standards Council as the owner of PCI DSS and link to its document library; never state or imply PCI certification, compliance or endorsement."],"evaluatedAt":"2026-11-12T14:36:04.596Z","mapped":[{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-govern-accountable-role-retention","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"Every scope keeps at least one usable administrator: a removal, demotion or deactivation that would strand an application or a tenant is refused, concurrent reductions are serialized so two of them cannot pass each other, a data-protection erasure proceeds only on an explicit acknowledgement that records the breach it causes, and any scope that has already been stranded is reported at startup.","objectiveRef":"WILDO.ACCESS.ADMINISTRATIVE_CONTINUITY","title":"Retain an administrator for every scope"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-audit-of-access-decisions","reviewedAt":"2026-09-01T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-audit-of-access-decisions-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"Access-control decisions, refusals included, are attributable and reviewable; repeated refusals stay detectable without the record itself becoming an availability risk; and a failure of the recording pipeline is detectable and attributable to the specific action it lost.","objectiveRef":"WILDO.ACCESS.AUTHORIZATION_DECISION_AUDIT","title":"Record access decisions, refusals included"},{"citations":[{"attributionNotice":"Identify HHS as the authority and link to the current official source; no HHS content bytes are bundled under this record.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html","contentUsePermission":"REQUIRES_ADDITIONAL_RIGHTS","metadataCitationAuthorized":true,"requirementRef":"source-requirement:hhs-security-access-authorization-recording","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:paul-cayon-assurance-owner","rightsRef":"rights:hhs-reference-only-v1","sourceRef":"source:hhs-hipaa-security-rule","sourceTitle":"HIPAA Security Rule"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_GUIDANCE","canonicalLocator":"https://doi.org/10.6028/NIST.SP.800-66r2","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-66-access-authorization-recording","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-66-rev-2","sourceTitle":"Implementing the HIPAA Security Rule: A Cybersecurity Resource Guide"}],"intent":"Platform-tier administration of a tenant is never ambient: a crossing is admitted only by an explicitly enumerated operation variant, requires an elevation that was requested rather than assumed and — where the tenant demands it — approved by that tenant, is recorded as a distinct event naming the tenant reached, and an undeclared crossing fails closed.","objectiveRef":"WILDO.ACCESS.CROSS_TENANT_ADMINISTRATION","title":"Declare every crossing of a tenant boundary"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-least-privilege-enforcement","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-least-privilege-authority-limit","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-least-privilege-authority-limit-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"A principal can never grant authority it does not itself hold — role assignment and machine-credential minting are bounded by the caller’s own ceiling — and a non-controller surface facing an external caller applies the same declared operation-role gate the controller tier applies, through the same predicate, before a self-service verb, a retrieval corpus or an agent-facing tool is reached.","objectiveRef":"WILDO.ACCESS.LEAST_PRIVILEGE","title":"Grant no more authority than the action needs"},{"citations":[{"attributionNotice":"Identify HHS as the authority and link to the current official source; no HHS content bytes are bundled under this record.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html","contentUsePermission":"REQUIRES_ADDITIONAL_RIGHTS","metadataCitationAuthorized":true,"requirementRef":"source-requirement:hhs-security-workforce-access-termination","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:paul-cayon-assurance-owner","rightsRef":"rights:hhs-reference-only-v1","sourceRef":"source:hhs-hipaa-security-rule","sourceTitle":"HIPAA Security Rule"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-account-disable-on-relationship-end","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-account-disable-on-relationship-end-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_GUIDANCE","canonicalLocator":"https://doi.org/10.6028/NIST.SP.800-66r2","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-66-workforce-access-termination","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-66-rev-2","sourceTitle":"Implementing the HIPAA Security Rule: A Cybersecurity Resource Guide"}],"intent":"Access rights, and the credentials that assert them, are withdrawn when the relationship conferring them ends, and restoring access is as attributable as removing it.","objectiveRef":"WILDO.ACCESS.LIFECYCLE","title":"Withdraw and restore access attributably"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-temporary-account-expiry","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-temporary-account-expiry-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"An access restriction declared as time-boxed is lifted when its window elapses, through the same guarded authority that imposed it, so a measure taken as temporary cannot silently become permanent.","objectiveRef":"WILDO.ACCESS.LIFECYCLE_TIME_BOUND","title":"Release a time-boxed restriction automatically"},{"citations":[{"attributionNotice":"Identify HHS as the authority and link to the current official source; no HHS content bytes are bundled under this record.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html","contentUsePermission":"REQUIRES_ADDITIONAL_RIGHTS","metadataCitationAuthorized":true,"requirementRef":"source-requirement:hipaa-security-privileged-access-review","reviewedAt":"2026-08-13T08:57:58.000Z","reviewedByRef":"reviewer:paul-cayon-assurance-owner","rightsRef":"rights:hhs-reference-only-v1","sourceRef":"source:hhs-hipaa-security-rule","sourceTitle":"HIPAA Security Rule"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-govern-access-review","reviewedAt":"2026-08-03T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_GUIDANCE","canonicalLocator":"https://doi.org/10.6028/NIST.SP.800-66r2","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-66-privileged-access-review","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-66-rev-2","sourceTitle":"Implementing the HIPAA Security Rule: A Cybersecurity Resource Guide"}],"intent":"Privileged access is explicitly scoped, periodically reviewed, decided by authorized people and retained as traceable evidence without implying remediation completion.","objectiveRef":"WILDO.ACCESS.PRIVILEGED_REVIEW","title":"Review privileged access"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-privileged-grant-evidence","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"Every grant, widening, narrowing and revocation of privilege — a role, a unit-scoped membership, a discretionary entitlement or a subscription-derived one — leaves durable evidence of the assignment’s full life, not merely of its current state.","objectiveRef":"WILDO.ACCESS.PRIVILEGE_EVIDENCE","title":"Keep evidence of a privileged assignment’s whole life"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-separation-of-duties","reviewedAt":"2026-10-05T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-separation-of-duties-assessment","reviewedAt":"2026-10-05T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"A decision the product holds for a person's review — an agent's gated tool call, an actor's reviewable output, a granting organization's admission of a representing organization's representative, a person's operation the application declares needs another person's approval — is answered, claimed, reassigned or escalated only by someone the one decision predicate admits at the moment they act: under any route other than the requester's own, the person whose work raised it can never act on it, a deadline rule can hand it only to someone that predicate would admit to answer it, the eligible role is re-checked when the person acts rather than when the decision was routed, and every refused act is recorded with its reason. An operation the application does not declare as needing approval is applied at once and is outside it.","objectiveRef":"WILDO.ACCESS.REQUESTER_REVIEWER_SEPARATION","title":"Never let the requester answer the decision their own work raised"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-processing-confidentiality","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-information-flow-confinement","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-information-flow-confinement-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"Reads and writes are narrowed to the tenant, unit subtree or parent row the caller’s own grant reaches; the conferring grant is recorded alongside the decision, a unit grant expands to exactly its declared subtree and no further, and a tenant cannot lift a narrowing the platform imposed on it.","objectiveRef":"WILDO.ACCESS.SCOPE_CONFINEMENT","title":"Confine a query to the scope the caller reached it by"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.AI.100-2e2025","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-ai-100-2-injection-assumed-system-design","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-ai-100-2-e2025","sourceTitle":"Adversarial Machine Learning: A Taxonomy and Terminology of Attacks and Mitigations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-least-privilege-processes-acting-for-users","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-least-privilege-processes-acting-for-users-assessment","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"},{"attributionNotice":"Credit the OWASP AI Exchange and link to https://owaspai.org where practical; do not imply OWASP endorsement or use OWASP marks.","authorityKind":"COMMUNITY_GUIDANCE","canonicalLocator":"https://owaspai.org/","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:owasp-ai-exchange-agent-acts-with-served-principal-authority","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:owasp-ai-exchange-cc0-v1","sourceRef":"source:owasp-ai-exchange","sourceTitle":"OWASP AI Exchange"},{"attributionNotice":"Contains public sector information licensed under the Open Government Licence v3.0. Link to the licence where possible, and do not imply official status or endorsement.","authorityKind":"GOVERNMENT_GUIDANCE","canonicalLocator":"https://www.gov.uk/government/publications/ai-cyber-security-code-of-practice/code-of-practice-for-the-cyber-security-of-ai","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:uk-ai-code-ai-system-permissions-limited-and-assessed","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:uk-open-government-licence-v3","sourceRef":"source:uk-ai-cyber-security-code-of-practice","sourceTitle":"Code of Practice for the Cyber Security of AI"}],"intent":"An agent's tool acts with no more authority than the person or declared machine principal whose turn calls it, and the model can never supply that authority: every tool runs on its caller's server-verified identity, the engine's tools dispatch each operation through that operation's own role gate, tenancy filter and rate limit for the caller, an autonomous turn runs as a declared machine principal rather than the application's system authority, a turn started by content from outside is offered no write a reviewer does not see first, and every hand-written tool declares how it reaches data, so a tool that reaches beyond its caller is named.","objectiveRef":"WILDO.AI.AGENT_AUTHORITY_CONFINEMENT","title":"Confine an AI agent's tools to the authority of the principal it acts for"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.AI.100-1","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-ai-rmf-ai-system-deactivation-mechanism","reviewedAt":"2026-10-20T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-ai-rmf-1.0","sourceTitle":"Artificial Intelligence Risk Management Framework (AI RMF 1.0)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.AI.100-1","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-ai-rmf-human-oversight-processes-documented","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-ai-rmf-1.0","sourceTitle":"Artificial Intelligence Risk Management Framework (AI RMF 1.0)"},{"attributionNotice":"Credit the OWASP AI Exchange and link to https://owaspai.org where practical; do not imply OWASP endorsement or use OWASP marks.","authorityKind":"COMMUNITY_GUIDANCE","canonicalLocator":"https://owaspai.org/","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:owasp-ai-exchange-human-approval-before-high-impact-agent-actions","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:owasp-ai-exchange-cc0-v1","sourceRef":"source:owasp-ai-exchange","sourceTitle":"OWASP AI Exchange"},{"attributionNotice":"Contains public sector information licensed under the Open Government Licence v3.0. Link to the licence where possible, and do not imply official status or endorsement.","authorityKind":"GOVERNMENT_GUIDANCE","canonicalLocator":"https://www.gov.uk/government/publications/ai-cyber-security-code-of-practice/code-of-practice-for-the-cyber-security-of-ai","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:uk-ai-code-technical-measures-for-human-oversight","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:uk-open-government-licence-v3","sourceRef":"source:uk-ai-cyber-security-code-of-practice","sourceTitle":"Code of Practice for the Cyber Security of AI"}],"intent":"An agent action of consequence waits for a person before it runs: a gated tool call or a held operation is decided by its owner or, where the gate routes it to a role or an assignee, by a reviewer who is not its requester, within a declared deadline, and every decision reaches the people who can answer it; a person can stop a running turn; an organization's administrator can suspend one of its agents for that organization, and the application's super-administrator for everybody with a justification, after which a call to the agent is refused before its model runs, at every door that reaches the engine's agent service, for each organization the call works for (the one it names, the tenant of the case it works on, and the organization of the conversation, flow run or work it is made in) and, after an application-wide suspension, for every call, a call that works for no organization answering to the application's suspensions only; a suspension or a case that cannot be read, or an application whose id cannot be resolved, refuses the call too; each suspension, resumption and refused call is recorded; a call already running when the agent is suspended is not stopped and ends after its bounded steps, a queued autonomous run is refused at its first model call rather than skipped, the dev companion and the platform's own services, which boot no application, answer to no suspension, and the ended turn stores the refusal's code, so the person sees the suspension named live and after a reload, a chat platform's reply names it, and an A2A client polling the task reads it (#2827, #3020); and every AI use declared to affect a person reaches one of the approval gates or held operations above, so its human review is evidenced rather than only stated.","objectiveRef":"WILDO.AI.HUMAN_OVERSIGHT","title":"Put a person in front of what an AI agent does"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.AI.100-1","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-ai-rmf-end-user-problem-reporting-established","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-ai-rmf-1.0","sourceTitle":"Artificial Intelligence Risk Management Framework (AI RMF 1.0)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.AI.100-1","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-ai-rmf-incidents-tracked-and-responded-to","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-ai-rmf-1.0","sourceTitle":"Artificial Intelligence Risk Management Framework (AI RMF 1.0)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.AI.100-1","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-ai-rmf-user-input-capture-and-incident-response-implemented","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-ai-rmf-1.0","sourceTitle":"Artificial Intelligence Risk Management Framework (AI RMF 1.0)"},{"attributionNotice":"Credit the OWASP AI Exchange and link to https://owaspai.org where practical; do not imply OWASP endorsement or use OWASP marks.","authorityKind":"COMMUNITY_GUIDANCE","canonicalLocator":"https://owaspai.org/","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:owasp-ai-exchange-agentic-incident-detection-and-triage","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:owasp-ai-exchange-cc0-v1","sourceRef":"source:owasp-ai-exchange","sourceTitle":"OWASP AI Exchange"}],"intent":"A person reading an agent's stored reply in the in-app conversation, while working in an organization, can report it from that conversation, choosing a category from a closed vocabulary and optionally saying why; the report is recorded against the organization the conversation was held in (one held in another organization's context is refused) or, for a conversation held in the person's own context, the organization they are working in; it points at the reply and never copies it, and carries a severity derived from its category, a critical report's received audit row being a CRITICAL row that reaches what CRITICAL rows reach (the organization's SIEM route when one is configured, the audit-trail provider fan-out when it is enabled) while nobody is paged, since the engine has no alerting; only that organization's administrators triage it, read the reported reply and end it resolved or dismissed, with an outcome of that ending and a stated note, a guardrail remedy being a guardrail decision of that organization or of the reported conversation; each step is recorded on the audit trail after the report commits, best-effort (a failed write is logged, not retried), against triage and outcome targets the application declares or, absent a declaration, a day and a week, and a report open past a target is counted, not escalated; the operator reads reports across organizations only through the application audit door; a reporter's erasure removes their id and comment and keeps the report, and their access export carries the reports they filed and their comment but not the outcome note or who triaged and closed them; a person may file five reports a minute, thirty an hour and a hundred a day, counted per signed-in person and never per address, so colleagues behind one address each have their own bound, and refused past the bound with a client error naming when to retry, the first refusal of each window being recorded as an audit row; and a repeat report of the same reply by the same person while an earlier one is open answers with that open report at its current status, received or triaged, without who took it on, writing nothing and recording nothing again, even when the two arrive at once.","objectiveRef":"WILDO.AI.INCIDENT_HANDLING","title":"A person can report an agent's reply, and each report reaches an outcome against a declared target"},{"citations":[{"attributionNotice":"Credit the OWASP AI Exchange and link to https://owaspai.org where practical; do not imply OWASP endorsement or use OWASP marks.","authorityKind":"COMMUNITY_GUIDANCE","canonicalLocator":"https://owaspai.org/","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:owasp-ai-exchange-model-spend-bounded","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:owasp-ai-exchange-cc0-v1","sourceRef":"source:owasp-ai-exchange","sourceTitle":"OWASP AI Exchange"}],"intent":"An organization's model spend is bounded per period: every model call the engine's agent service makes in a conversational turn or a declared flow, a call nested in another included, is counted against the allowance of the organization that work is for, at every door that work runs through (an external agent, an autonomous agent, a chat-platform message, in-app chat and a declared flow), and in in-app chat one person cannot exhaust it. A turn whose allowance or person ceiling is spent, or whose allowance or consumption cannot be verified, is refused before it runs; a declared flow is asked before each of its model calls, and a call whose organization allowance is spent, or cannot be verified, is refused before the model runs; a flow is never counted against a person's ceiling; every refusal is recorded. The bound is what the application's plans, or its default features profile, grant. Consumption is counted after each call, at the usage the provider reported or, when it reported none, an estimate (four characters to a token, 6,240 tokens per image; the larger of the two when the report is marked incomplete; a coding agent reporting no token counter is charged the size of its context, which under-counts), so work already running, or a turn resumed from a decision, when a limit is reached may overrun it. A model call a resource operation makes is counted, and asked before it runs, as the operation's principal: against that principal's own allowance, else the organization the operation's work is for, else the application it names, and a call none of them can pay for is refused; its refusal names the operation's principal. A model call made outside any turn, flow or operation is counted, and asked before it runs, only when it is attributed to an organization; its refusal names that organization and no person (#2957). Embeddings, document extraction and content screening are not counted against that allowance: each is bounded per organization by a ceiling of its own, in the unit it is billed by (embedding tokens, extraction pages, screening text records), asked before every such call wherever it is made, a background job included; a call whose organization's ceiling for its unit is spent, or cannot be verified, is refused before the provider is called and the refusal is recorded (once per refusal in a turn or a flow, and at least once per organization, unit, reason and period for a call made in neither); a refused embedding leaves its chunks unembedded until the period rolls, a refused extraction falls back without the document being judged unreadable, and a refused screening or moderation withholds the text as an unscreened one is; a ceiling that is not granted bounds nothing (#3030).","objectiveRef":"WILDO.AI.MODEL_SPEND_LIMIT","title":"Bound what an organization's agents spend on models, per period and per person"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.AI.100-1","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-ai-rmf-post-deployment-monitoring-implemented","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-ai-rmf-1.0","sourceTitle":"Artificial Intelligence Risk Management Framework (AI RMF 1.0)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.AI.100-1","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-ai-rmf-production-behaviour-monitored","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-ai-rmf-1.0","sourceTitle":"Artificial Intelligence Risk Management Framework (AI RMF 1.0)"},{"attributionNotice":"Credit the OWASP AI Exchange and link to https://owaspai.org where practical; do not imply OWASP endorsement or use OWASP marks.","authorityKind":"COMMUNITY_GUIDANCE","canonicalLocator":"https://owaspai.org/","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:owasp-ai-exchange-model-use-monitored","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:owasp-ai-exchange-cc0-v1","sourceRef":"source:owasp-ai-exchange","sourceTitle":"OWASP AI Exchange"},{"attributionNotice":"Contains public sector information licensed under the Open Government Licence v3.0. Link to the licence where possible, and do not imply official status or endorsement.","authorityKind":"GOVERNMENT_GUIDANCE","canonicalLocator":"https://www.gov.uk/government/publications/ai-cyber-security-code-of-practice/code-of-practice-for-the-cyber-security-of-ai","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:uk-ai-code-system-and-user-actions-logged","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:uk-open-government-licence-v3","sourceRef":"source:uk-ai-cyber-security-code-of-practice","sourceTitle":"Code of Practice for the Cyber Security of AI"}],"intent":"Every agent invocation the engine's agent runtime traces, including one that failed before a provider answered, leaves one record beside the invocation's provider-call record, naming the run when the call site or its work frame names one, that states the model ids the provider reported answering with, each tool the agent called and the phase it ended at, what the agent's content guardrails decided (how many personal fields its model was not sent and their categories, what screening concluded about each tool result, what output moderation judged and withheld) and how the invocation ended, with its failure code; the record holds no tool input or result, no prompt, reply or error message, no id of a row a tool read and no person id, and is kept for the application's declared operational-log period; recording is best-effort: an agent call whose provider-call record was written but whose operation record was not is counted rather than hidden, a call whose provider-call record itself failed to write leaves neither row and no count shows it, and a call made outside the engine's agent runtime leaves no record.","objectiveRef":"WILDO.AI.OPERATION_RECORD","title":"Record what every agent call did, without keeping what it read"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.AI.100-2e2025","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-ai-100-2-harmful-generation-detected-and-terminated","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-ai-100-2-e2025","sourceTitle":"Adversarial Machine Learning: A Taxonomy and Terminology of Attacks and Mitigations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.AI.600-1","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-ai-600-1-problematic-output-filtered","reviewedAt":"2026-10-18T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-ai-600-1","sourceTitle":"Artificial Intelligence Risk Management Framework: Generative Artificial Intelligence Profile"},{"attributionNotice":"Credit the OWASP AI Exchange and link to https://owaspai.org where practical; do not imply OWASP endorsement or use OWASP marks.","authorityKind":"COMMUNITY_GUIDANCE","canonicalLocator":"https://owaspai.org/","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:owasp-ai-exchange-harmful-output-detected-and-withheld","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:owasp-ai-exchange-cc0-v1","sourceRef":"source:owasp-ai-exchange","sourceTitle":"OWASP AI Exchange"}],"intent":"An agent that declares an output-moderation policy has everything its model writes — the reply, its shown reasoning, the input of a tool call and a structured answer — judged per harm category by a classifier before it is shown, stored, sent or acted on. Text at or above the severity the policy withholds, and text the classifier could not judge, is withheld and the turn ends there with the withholding recorded; an agent whose policy no selected classifier can serve, in every category it names, is refused before its model is called rather than run unjudged.","objectiveRef":"WILDO.AI.OUTPUT_MODERATION","title":"Judge what an AI model writes before anyone receives it"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.AI.100-1","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-ai-rmf-third-party-ai-components-identified","reviewedAt":"2026-09-25T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-ai-rmf-1.0","sourceTitle":"Artificial Intelligence Risk Management Framework (AI RMF 1.0)"},{"attributionNotice":"Credit the OWASP AI Exchange and link to https://owaspai.org where practical; do not imply OWASP endorsement or use OWASP marks.","authorityKind":"COMMUNITY_GUIDANCE","canonicalLocator":"https://owaspai.org/","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:owasp-ai-exchange-external-ai-services-recorded","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:owasp-ai-exchange-cc0-v1","sourceRef":"source:owasp-ai-exchange","sourceTitle":"OWASP AI Exchange"},{"attributionNotice":"Contains public sector information licensed under the Open Government Licence v3.0. Link to the licence where possible, and do not imply official status or endorsement.","authorityKind":"GOVERNMENT_GUIDANCE","canonicalLocator":"https://www.gov.uk/government/publications/ai-cyber-security-code-of-practice/code-of-practice-for-the-cyber-security-of-ai","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:uk-ai-code-ai-asset-inventory","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:uk-open-government-licence-v3","sourceRef":"source:uk-ai-cyber-security-code-of-practice","sourceTitle":"Code of Practice for the Cyber Security of AI"}],"intent":"Every AI capability the contracted service uses declares what it is for and whether it decides anything about a person, and every provider serving it is either run by the operator or named on the processor register with its legal entity, regions and sub-processors — so the AI a person's data reaches can be listed from what the application declares, and a new model vendor cannot be added unnoticed.","objectiveRef":"WILDO.AI.THIRD_PARTY_COMPONENTS","title":"Identify every third-party AI component the service runs on"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.AI.100-2e2025","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-ai-100-2-third-party-instruction-filtering","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-ai-100-2-e2025","sourceTitle":"Adversarial Machine Learning: A Taxonomy and Terminology of Attacks and Mitigations"},{"attributionNotice":"Credit the OWASP AI Exchange and link to https://owaspai.org where practical; do not imply OWASP endorsement or use OWASP marks.","authorityKind":"COMMUNITY_GUIDANCE","canonicalLocator":"https://owaspai.org/","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:owasp-ai-exchange-indirect-prompt-injection-screening","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:owasp-ai-exchange-cc0-v1","sourceRef":"source:owasp-ai-exchange","sourceTitle":"OWASP AI Exchange"},{"attributionNotice":"Contains public sector information licensed under the Open Government Licence v3.0. Link to the licence where possible, and do not imply official status or endorsement.","authorityKind":"GOVERNMENT_GUIDANCE","canonicalLocator":"https://www.gov.uk/government/publications/ai-cyber-security-code-of-practice/code-of-practice-for-the-cyber-security-of-ai","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:uk-ai-code-resilience-to-adversarial-input","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:uk-open-government-licence-v3","sourceRef":"source:uk-ai-cyber-security-code-of-practice","sourceTitle":"Code of Practice for the Cyber Security of AI"}],"intent":"An agent that declares prompt-injection screening has the content other people wrote — what its tools return, and the content of an inbound delivery that starts its turn — screened for an injected instruction by a classifier before its model reads it. Content judged an attack, and content that could not be screened, never reaches the model: a tool result arrives as a notice that it was withheld and an inbound delivery does not start the turn, each recorded with where the content came from; where no selected classifier can serve an agent's screening, a turn that would bring it third-party content — one that offers it tools, or one an inbound delivery would start — is refused rather than run unscreened.","objectiveRef":"WILDO.AI.UNTRUSTED_CONTENT_SCREENING","title":"Screen what an AI model reads from third parties before it reads it"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2024/1689/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:eu-ai-act-high-risk-candidate-use-identified","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-ai-act-2024-1689","sourceTitle":"Regulation (EU) 2024/1689 laying down harmonised rules on artificial intelligence (Artificial Intelligence Act)"},{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2024/1689/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:eu-ai-act-prohibited-practice-identified","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-ai-act-2024-1689","sourceTitle":"Regulation (EU) 2024/1689 laying down harmonised rules on artificial intelligence (Artificial Intelligence Act)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.AI.100-1","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-ai-rmf-intended-purpose-and-legal-context-documented","reviewedAt":"2026-10-18T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-ai-rmf-1.0","sourceTitle":"Artificial Intelligence Risk Management Framework (AI RMF 1.0)"},{"attributionNotice":"Credit the OWASP AI Exchange and link to https://owaspai.org where practical; do not imply OWASP endorsement or use OWASP marks.","authorityKind":"COMMUNITY_GUIDANCE","canonicalLocator":"https://owaspai.org/","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:owasp-ai-exchange-ai-use-legal-class-assessed","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:owasp-ai-exchange-cc0-v1","sourceRef":"source:owasp-ai-exchange","sourceTitle":"OWASP AI Exchange"},{"attributionNotice":"Contains public sector information licensed under the Open Government Licence v3.0. Link to the licence where possible, and do not imply official status or endorsement.","authorityKind":"GOVERNMENT_GUIDANCE","canonicalLocator":"https://www.gov.uk/government/publications/ai-cyber-security-code-of-practice/code-of-practice-for-the-cyber-security-of-ai","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:uk-ai-code-ai-purpose-documented","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:uk-open-government-licence-v3","sourceRef":"source:uk-ai-cyber-security-code-of-practice","sourceTitle":"Code of Practice for the Cyber Security of AI"}],"intent":"Every AI use the contracted service runs, whether declared on the capability or on the agent that runs it, declares its use domain from a closed vocabulary, and its regulatory class is derived from that domain rather than asserted: where the EU AI Act applies, a use in an Annex III area is reported as a high-risk candidate and a use in an Article 5(1) practice as a prohibited-practice candidate, each marked for a person to confirm and neither stopping the build.","objectiveRef":"WILDO.AI.USE_CLASSIFICATION","title":"Classify every AI use the service runs by its declared domain"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-accountability-demonstration","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-detect-attributable-event-record","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"A security-relevant action records who performed it, and never disguises an unattributable action as an ordinary automated one; read-through access to an external system carries the real initiating user through the shared service principal, and an outbound deletion there names the subject it served and the system it reached.","objectiveRef":"WILDO.AUDIT.ATTRIBUTION","title":"Name who performed a security-relevant action"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-audit-record-context-binding","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-audit-record-context-binding-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"The actor and tenant an audit row names survive the trusted-system write that persists it, and a log record names which application and which environment produced it — so a record cannot silently lose or change the principal, tenant or deployment it belongs to.","objectiveRef":"WILDO.AUDIT.CONTEXT_ATTRIBUTION","title":"Bind a record to the context it actually ran in"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-audit-record-content-and-protection","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-audit-record-content-and-protection-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"A privileged action on a resource is attributable, and the authorization effect it had is reconstructable from the record itself rather than re-derived from role tables afterwards; the configuration deciding what the trail captures is governed as part of the trail.","objectiveRef":"WILDO.AUDIT.EVIDENCE_INTEGRITY","title":"Govern the audit trail as evidence in its own right"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.CSWP.29","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-detect-security-event-logging","reviewedAt":"2026-09-01T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"Authentication, authorization, privilege, credential and security-configuration changes each emit a typed auditable event; non-human privileged access is audited or refused; and the absence of the audit delivery path is surfaced at boot rather than tolerated silently.","objectiveRef":"WILDO.AUDIT.SECURITY_EVENT","title":"Emit a typed event for every security-relevant change"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-transaction-authorization-separation","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-transaction-authorization-separation-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"An increase in a credit balance is reachable only through a system or payment-gated door, so no ordinary principal can grant itself economic value.","objectiveRef":"WILDO.BILLING.CREDIT_GRANT_INTEGRITY","title":"Gate a credit grant to system or payment authority"},{"citations":[{"attributionNotice":"Identify HHS as the authority and link to the current official source; no HHS content bytes are bundled under this record.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html","contentUsePermission":"REQUIRES_ADDITIONAL_RIGHTS","metadataCitationAuthorized":true,"requirementRef":"source-requirement:hhs-security-transmission-confidentiality","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:paul-cayon-assurance-owner","rightsRef":"rights:hhs-reference-only-v1","sourceRef":"source:hhs-hipaa-security-rule","sourceTitle":"HIPAA Security Rule"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_GUIDANCE","canonicalLocator":"https://doi.org/10.6028/NIST.SP.800-66r2","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-66-transmission-confidentiality","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-66-rev-2","sourceTitle":"Implementing the HIPAA Security Rule: A Cybersecurity Resource Guide"}],"intent":"Material a schema declares backend-only does not cross the client boundary, except at a single first exposure that is itself audited.","objectiveRef":"WILDO.DATA.CONFIDENTIALITY","title":"Keep backend-only material off the client boundary"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-information-integrity-verification","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-information-integrity-verification-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"A uniqueness or integrity control the schema declares is proven to exist in the datastore before the application serves traffic, rather than assumed to have been created.","objectiveRef":"WILDO.DATA.INTEGRITY_CONSTRAINTS","title":"Prove a declared constraint exists before serving traffic"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-erasure-with-retention-carve-out","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-media-sanitization-and-disposal","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-media-sanitization-and-disposal-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"Destruction of an identity, a tenant or its data is a deliberate, attributable, evidenced decision, reversible until its declared window elapses and then carried out on schedule; an erased-but-retained record is hidden from, and immutable to, every ORDINARY access path — the only door is an audited see-through read — and its derived copies are excluded by a live check against the parent row rather than by waiting for a sweep.","objectiveRef":"WILDO.DATA.SECURE_LIFECYCLE","title":"Destroy data deliberately, on a recorded schedule"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-shared-resource-isolation","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-shared-resource-isolation-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"A caller cannot widen its own query scope: tenancy narrowing is derived from the resolved execution context and never offered as a parameter — to a client, to an agent, or to a retrieval surface — and where the read is a similarity search the predicate is evaluated INSIDE the traversal rather than over its results, then re-checked by an authorized read of the owning row.","objectiveRef":"WILDO.DATA.TENANT_ISOLATION","title":"Derive tenancy from the caller, never from the request"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-transaction-recovery-integrity","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-transaction-recovery-integrity-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"An application keeps every resource it stores on its one transactional database: a configuration in which a resource declares another transactional store is refused when the registry is built rather than discovered under load, and no declaration admits it. A resource that is read through from another system or computed from the application holds no transaction and is not a second store.","objectiveRef":"WILDO.DATA.TRANSACTIONAL_INTEGRITY","title":"Refuse a configuration that cannot write atomically"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-entitlement-change-authority","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"Feature and entitlement writes are reachable only through an operator-gated door, so a principal cannot widen what it is entitled to.","objectiveRef":"WILDO.ENTITLEMENT.NO_SELF_GRANT","title":"Keep an entitlement write operator-gated"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-identify-service-identity-verification","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"A client identity is bound to a domain the client demonstrably controls, and both a client identity created by a party that authenticated to nothing and every refused client assertion are recorded.","objectiveRef":"WILDO.IDENTITY.CLIENT_IDENTITY_ASSERTION","title":"Bind a client identity to a verifiable assertion"},{"citations":[{"attributionNotice":"Identify HHS as the authority and link to the current official source; no HHS content bytes are bundled under this record.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html","contentUsePermission":"REQUIRES_ADDITIONAL_RIGHTS","metadataCitationAuthorized":true,"requirementRef":"source-requirement:hhs-security-credential-management","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:paul-cayon-assurance-owner","rightsRef":"rights:hhs-reference-only-v1","sourceRef":"source:hhs-hipaa-security-rule","sourceTitle":"HIPAA Security Rule"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-credential-state-transitions","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_GUIDANCE","canonicalLocator":"https://doi.org/10.6028/NIST.SP.800-66r2","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-66-credential-management","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-66-rev-2","sourceTitle":"Implementing the HIPAA Security Rule: A Cybersecurity Resource Guide"}],"intent":"Issuance, refresh, rotation, revocation and expiry of a credential are explicit attributable transitions; credential theft is detected and answered by invalidation; and a revocation actually terminates the sessions and tokens it names rather than merely marking a record.","objectiveRef":"WILDO.IDENTITY.CREDENTIAL_LIFECYCLE","title":"Make every credential state transition explicit"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-delegated-access-authorization","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"A third party acts for a user only on that user’s recorded authorization: approval, refusal, persistence and failure of the delegated exchange are each audited, proof of possession is enforced on the exchange, and the issued token carries no more than the grant declared.","objectiveRef":"WILDO.IDENTITY.DELEGATED_AUTHORIZATION","title":"Let a user authorize third-party access deliberately"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-automated-account-management","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-automated-account-management-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"Where an application opts in, a directory becomes the authority for accounts and for unit membership — which is an authorization grant, not a label — and the switches conferring that authority are declared explicitly rather than implied by the presence of a connection.","objectiveRef":"WILDO.IDENTITY.DIRECTORY_PROVISIONING","title":"Honour the directory as the provisioning authority"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-account-enable-disable-authority","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-account-enable-disable-authority-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"A change to whether a principal may authenticate runs through one guarded, evidenced authority: the status carrying it is excluded from ordinary updates, so the change cannot arrive as a side effect of an unrelated write.","objectiveRef":"WILDO.IDENTITY.LIFECYCLE","title":"Record every change to whether a principal may authenticate"},{"citations":[{"attributionNotice":"Identify HHS as the authority and link to the current official source; no HHS content bytes are bundled under this record.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://www.hhs.gov/hipaa/for-professionals/security/index.html","contentUsePermission":"REQUIRES_ADDITIONAL_RIGHTS","metadataCitationAuthorized":true,"requirementRef":"source-requirement:hipaa-security-authentication-controls","reviewedAt":"2026-09-01T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:hhs-reference-only-v1","sourceRef":"source:hhs-hipaa-security-rule","sourceTitle":"HIPAA Security Rule"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/63/b/4/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-63b-authenticator-activation-verified","reviewedAt":"2026-09-17T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-63b-4","sourceTitle":"Digital Identity Guidelines: Authentication and Authenticator Management"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/63/b/4/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-63b-distinct-authentication-factors","reviewedAt":"2026-09-17T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-63b-4","sourceTitle":"Digital Identity Guidelines: Authentication and Authenticator Management"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/63/b/4/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-63b-out-of-band-channel-separation","reviewedAt":"2026-09-17T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-63b-4","sourceTitle":"Digital Identity Guidelines: Authentication and Authenticator Management"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_GUIDANCE","canonicalLocator":"https://doi.org/10.6028/NIST.SP.800-66r2","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-66-authentication-controls","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-66-rev-2","sourceTitle":"Implementing the HIPAA Security Rule: A Cybersecurity Resource Guide"}],"intent":"Enrolled second factors are verified through one authority that is replay-resistant and timing-safe, so no caller builds a second, weaker door onto the same credential; and a session counts a second factor only when it proves something the first factor did not, so two methods reaching one channel cannot together satisfy a multi-factor requirement.","objectiveRef":"WILDO.IDENTITY.MULTI_FACTOR","title":"Verify enrolled second factors through one authority, and count only independent proofs"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-redirect-target-constraint","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"A registered OAuth redirect target is constrained to a safe absolute URL, closing the open-redirect and stored-XSS delegation primitive a permissive target would otherwise create.","objectiveRef":"WILDO.IDENTITY.REDIRECT_TARGET_VALIDATION","title":"Constrain a registered redirect target"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-govern-authentication-posture-change","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/63/b/4/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-63b-phishing-resistant-authentication","reviewedAt":"2026-09-17T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-63b-4","sourceTitle":"Digital Identity Guidelines: Authentication and Authenticator Management"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/63/c/4/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-63c-assertion-states-its-authentication","reviewedAt":"2026-09-17T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-63c-4","sourceTitle":"Digital Identity Guidelines: Federation and Assertions"}],"intent":"How principals may authenticate — the MFA, password, lockout, methods, step-up and session posture, whether single sign-on is enforced, which identity provider is trusted, and whether its assertions are actually verified — is explicitly configured, and every genuine change to that posture is detected at startup and evidenced once, from the runtime that puts it into effect.","objectiveRef":"WILDO.IDENTITY.SESSION_ASSURANCE","title":"Decide, and record changes to, the assurance a session carries"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-concurrent-session-control","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-concurrent-session-control-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"A principal holds a bounded number of concurrent sessions, and the eviction enforcing that bound retires the OLDEST refresh chain — the property that pushes a stolen chain out instead of a legitimate one.","objectiveRef":"WILDO.IDENTITY.SESSION_CONCURRENCY_LIMIT","title":"Bound the concurrent sessions a principal holds"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-cryptographic-key-establishment-and-management","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-cryptographic-key-establishment-and-management-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"A rotated signing key can be given an explicit retirement instant, after which it stops being advertised and stops verifying tokens — so an aged or compromised prior key need not stay trusted until someone edits configuration.","objectiveRef":"WILDO.IDENTITY.SIGNING_KEY_LIFECYCLE","title":"Bound the lifetime of a retired signing key"},{"citations":[{"attributionNotice":"Identify HHS as the authority and link to the current official source; no HHS content bytes are bundled under this record.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html","contentUsePermission":"REQUIRES_ADDITIONAL_RIGHTS","metadataCitationAuthorized":true,"requirementRef":"source-requirement:hhs-security-person-or-entity-reverification","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:paul-cayon-assurance-owner","rightsRef":"rights:hhs-reference-only-v1","sourceRef":"source:hhs-hipaa-security-rule","sourceTitle":"HIPAA Security Rule"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-reauthentication-for-privileged-action","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-reauthentication-for-privileged-action-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/63/b/4/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-63b-reauthentication-at-assurance-level","reviewedAt":"2026-09-17T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-63b-4","sourceTitle":"Digital Identity Guidelines: Authentication and Authenticator Management"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_GUIDANCE","canonicalLocator":"https://doi.org/10.6028/NIST.SP.800-66r2","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-66-person-or-entity-reverification","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-66-rev-2","sourceTitle":"Implementing the HIPAA Security Rule: A Cybersecurity Resource Guide"}],"intent":"A high-impact action requires a fresh re-proof of identity, over any factor the principal actually holds, and that ceremony cannot be satisfied by a credential presented for a different purpose.","objectiveRef":"WILDO.IDENTITY.STEP_UP_AUTHENTICATION","title":"Re-prove identity before a high-impact action"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-assertion-integrity","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"An ID token’s protocol and security claims are authored by the server alone, from one named reserved-claim set, so a caller cannot smuggle a reserved claim in through supplied extras.","objectiveRef":"WILDO.IDENTITY.TOKEN_INTEGRITY","title":"Author a token’s protocol claims on the server only"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-detect-outbound-connection-monitoring","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"Outbound traffic leaves through a single named egress per capability, and every physical call is recorded — provider, model, usage and outcome for a provider call, the initiating actor for an administrative probe — so a reviewer can enumerate what was sent and when.","objectiveRef":"WILDO.INTEGRATION.OUTBOUND_ACTIVITY_AUDIT","title":"Attribute every outbound connection the application makes"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-authority-not-inferred-from-state","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"A self-reported lifecycle stage confers no capability and cannot cross a scope boundary; authority comes only from a decision an authorized party actually made.","objectiveRef":"WILDO.LIFECYCLE.STAGE_IS_NOT_AUTHORITY","title":"Confer no capability from a self-reported stage"},{"citations":[{"attributionNotice":"Credit the OWASP AI Exchange and link to https://owaspai.org where practical; do not imply OWASP endorsement or use OWASP marks.","authorityKind":"COMMUNITY_GUIDANCE","canonicalLocator":"https://owaspai.org/","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:owasp-ai-exchange-external-agent-access-rate-limited","reviewedAt":"2026-10-20T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:owasp-ai-exchange-cc0-v1","sourceRef":"source:owasp-ai-exchange","sourceTitle":"OWASP AI Exchange"}],"intent":"An authenticated caller reaching the application from outside its own screens drives a bounded amount of work per window and is refused before anything is dispatched once it passes the bound: an agent's A2A turns and an MCP client's tool calls are counted against the principal's owner, the delegating person or the organization or application whose machine credential it is, never against the credential, so every credential an organization issues shares one window; a linked member's chat-platform messages, commands and searches are counted against that member, within the organization the delivery arrived in. An A2A or MCP caller over the bound is answered as a client error naming when it may retry, and the first such refusal of each window, and only it, is recorded as an audit row naming the transport, the owner counted, the window and the limit both as declared and as enforced, so a caller saturated for a whole window leaves one row rather than one per request; the row is written without holding up the refusal, and a failed write is logged, not retried. A chat member over the bound is answered with a refusal reply, a refused command or search being recorded as that command's run and a refused message not recorded. In development and test every bound is relaxed by a fixed factor; staging and production enforce the declared number. When the A2A or MCP counter store is unavailable the bound is enforced in each process instead of across the deployment, a caller past it there being refused and its first refusal recorded as above, a caller under it admitted, and the narrowing a warning log line; when a chat message or command counter cannot be read nothing is refused and the delivery is tried again, and when the search counter cannot be read the search fails and the person is asked to try again. An operation's own declared rate limit is a separate guard on every plane that dispatches it (an MCP tool call, an agent's function tool, a chat command, and the operation's own HTTP route once a signed-in person or machine is authorized), counted per client (the machine credential, else the person: through a client they delegated to, in the application, as a linked chat member, or signed in) in a bucket of each plane's own, and failing closed when its counter cannot be read; on the HTTP route a caller who is not a signed-in person or machine (a visitor, a public request, a link token) is counted per source address instead, a count whose refusals are not recorded, each request is counted once, and a request whose credential does not verify is counted by neither; the first refusal of each of its declared windows is recorded as its own audit row naming the plane, the operation, the subject counted and the window as declared and as enforced. It bounds a burst of requests, not what they spend.","objectiveRef":"WILDO.OPERATIONS.AUTHENTICATED_BURST_LIMIT","title":"Bound how fast an authenticated caller from outside the application may drive work"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-error-handling-diagnostics","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-error-handling-diagnostics-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"A constraint conflict is reported with the identity that was violated rather than as an opaque datastore failure, so an operator can tell a benign duplicate from an unexpected collision.","objectiveRef":"WILDO.OPERATIONS.CONFLICT_DIAGNOSTICS","title":"Report a conflict by the identity it violated"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-declared-interface-integrity","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"A declared, API-reachable operation stays reachable and is actually implemented: an interface must not report success for an action it did not perform, and a named verb must not silently widen into an unconstrained write over fields its resource never exposed for update.","objectiveRef":"WILDO.OPERATIONS.EXECUTION_INTEGRITY","title":"Never report success for an action that was not performed"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-denial-of-service-resource-bounds","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-denial-of-service-resource-bounds-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"An unauthenticated request consumes a bounded amount of resource, and an over-limit request is answered as a client error rather than surfacing as a server failure.","objectiveRef":"WILDO.OPERATIONS.RESOURCE_LIMIT","title":"Bound what an unauthenticated request may consume"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-bulk-disclosure-record","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.CSWP.01162020","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-privacy-disclosure-records","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-privacy-framework-1.0","sourceTitle":"NIST Privacy Framework: A Tool for Improving Privacy through Enterprise Risk Management, Version 1.0"}],"intent":"A bulk export of a resource collection is a recorded event naming the resource exported, the operation it was taken from, and the format it was rendered in.","objectiveRef":"WILDO.PRIVACY.COLLECTION_DATA_EXPORT","title":"Record a bulk export of a resource collection"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-consent-withdrawal-effect","reviewedAt":"2026-10-05T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.CSWP.01162020","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-privacy-individual-preference-enablement","reviewedAt":"2026-10-05T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-privacy-framework-1.0","sourceTitle":"NIST Privacy Framework: A Tool for Improving Privacy through Enterprise Risk Management, Version 1.0"}],"intent":"Processing that rests on a person's consent runs only while that consent stands: a purpose the application requires of its whole service, or that an operation declares it cannot run without, is checked on every user-initiated surface — REST, MCP, A2A and conversational turns, started or resumed — and a person who has not granted it is refused, the refusal recorded, with a consent that cannot be read counted as none granted; and a browser-side provider that rests on a consent purpose is started only once that purpose is granted and only if a withdrawal can stop it, so one that would inject a script nothing could stop is never started at all.","objectiveRef":"WILDO.PRIVACY.CONSENT_ENFORCEMENT","title":"Run processing that rests on consent only while the consent stands"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-consent-demonstrability","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.CSWP.01162020","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-privacy-processing-authorization-maintenance","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-privacy-framework-1.0","sourceTitle":"NIST Privacy Framework: A Tool for Improving Privacy through Enterprise Risk Management, Version 1.0"}],"intent":"A consent decision — given, changed or withdrawn — is recorded exactly once and never lost to a race, naming the previous and the resulting value; every verb able to change consent routes through one emission point, and resetting a subject’s privacy preferences is itself such a decision.","objectiveRef":"WILDO.PRIVACY.CONSENT_RECORD","title":"Record a consent decision exactly once"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-data-minimisation","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.AI.100-1","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-ai-rmf-privacy-risk-examined","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-ai-rmf-1.0","sourceTitle":"Artificial Intelligence Risk Management Framework (AI RMF 1.0)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.CSWP.01162020","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-privacy-selective-collection-and-disclosure","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-privacy-framework-1.0","sourceTitle":"NIST Privacy Framework: A Tool for Improving Privacy through Enterprise Risk Management, Version 1.0"}],"intent":"Only the data a declared purpose requires leaves its boundary: an external processor receives the payload and nothing identifying the requester or its row, observability surfaces receive summaries rather than the raw content, and a device-stored pseudonymous identifier is collected only under an explicit application opt-in — absent that policy, not at all — and can be withdrawn or narrowed afterwards.","objectiveRef":"WILDO.PRIVACY.DATA_MINIMIZATION","title":"Send only what the declared purpose requires"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.CSWP.01162020","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-privacy-deletion-communicated-across-ecosystem","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-privacy-framework-1.0","sourceTitle":"NIST Privacy Framework: A Tool for Improving Privacy through Enterprise Risk Management, Version 1.0"}],"intent":"A subject erasure accounts per store rather than returning one verdict for the request: each of the subject's dependent relationships — its direct dependents and every relationship below a dependent the erasure deletes, at any depth — is reported with the disposition its configuration declared and whether its teardown actually ran, a relationship nobody classified at any depth refuses the erasure before anything is written, and each registered external erasure effect is reported with its own outcome, where any outcome that may leave data live at a third party — including one the controller deliberately acknowledged — never reads as complete; a store whose records a system of record holds is reported as handled at that source, which answers requests about its own records, and a copy the application keeps of them beyond the source is erased as the application's own; and where erasure deletes rows in an external system or destroys the subject's own third-party credentials, it leaves a durable record naming that store. The accounting does not extend below a relationship whose rows the erasure retains, or to derived copies.","objectiveRef":"WILDO.PRIVACY.ERASURE_PROPAGATION","title":"Account per store for what a subject erasure reached"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-lawful-basis-per-purpose","reviewedAt":"2026-08-03T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"}],"intent":"Every purpose for which this application processes personal data declares the lawful basis it rests on, and a basis whose lawfulness depends on a balancing test carries that assessment rather than asserting a conclusion nobody reached; an application that has declared no basis at all is reported as not having answered, never as having nothing to declare.","objectiveRef":"WILDO.PRIVACY.LAWFUL_BASIS","title":"State the ground each processing purpose stands on"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-records-of-processing-categories","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.CSWP.01162020","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-privacy-data-element-inventory","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-privacy-framework-1.0","sourceTitle":"NIST Privacy Framework: A Tool for Improving Privacy through Enterprise Risk Management, Version 1.0"}],"intent":"The application declares, on the field itself, which CATEGORIES of personal data it holds — never inferred from the field’s name, because an inventory assembled by pattern-matching identifiers is a guess whose misses go silently undisclosed.","objectiveRef":"WILDO.PRIVACY.PERSONAL_DATA_INVENTORY","title":"Declare in the schema which fields hold personal data"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-compatible-further-processing","reviewedAt":"2026-10-05T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.CSWP.01162020","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-privacy-further-use-authorization","reviewedAt":"2026-10-05T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-privacy-framework-1.0","sourceTitle":"NIST Privacy Framework: A Tool for Improving Privacy through Enterprise Risk Management, Version 1.0"}],"intent":"A further use of a tenant's records of how its deciders decided on agents' proposals — exporting them as evaluation data — runs only while the tenant holds an active authorization naming the documented basis it rests on, either its controller's documented instruction to a processor or a controller's assessment that the further use is compatible with the original purpose: an authorization is never left active without its basis, a granted one is withdrawn only by revoking it, and every change to it is recorded; a case subject the tenant excluded (a client, a patient, an account), and a privileged case, or one holding special-category or criminal-offence data, without its subject's recorded consent, leave in no export, and while any case subject is excluded a case whose subject cannot be read is left out rather than assumed to have none; every refused export is recorded; and withdrawing the basis, or erasing a case, marks every dataset already exported under it as no longer usable. It marks the export ledger and cannot recall a dataset already delivered.","objectiveRef":"WILDO.PRIVACY.SECONDARY_USE_AUTHORIZATION","title":"Rest every further use of client work on a recorded authorization"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-storage-limitation","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.CSWP.01162020","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-privacy-destruction-according-to-policy","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-privacy-framework-1.0","sourceTitle":"NIST Privacy Framework: A Tool for Improving Privacy through Enterprise Risk Management, Version 1.0"}],"intent":"Declared row-retention windows are enforced, and a configuration whose derived copies of subject text could outlive the row they came from — unreachable by the erasure seams — is refused at startup.","objectiveRef":"WILDO.PRIVACY.STORAGE_LIMITATION","title":"Keep data no longer than its declared window"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-subject-access-portability","reviewedAt":"2026-08-03T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.CSWP.01162020","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-privacy-data-access-for-review-and-transmission","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-privacy-framework-1.0","sourceTitle":"NIST Privacy Framework: A Tool for Improving Privacy through Enterprise Risk Management, Version 1.0"}],"intent":"Authorized subject access and portability exports are purpose-specific, resource-opted-in, subject-isolated and auditable: the export event names the purpose, the subject, the resource types included, the record count and the fields withheld as derived.","objectiveRef":"WILDO.PRIVACY.SUBJECT_DATA_EXPORT","title":"Export subject data safely"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-erasure-and-restriction","reviewedAt":"2026-09-01T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.CSWP.01162020","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-privacy-data-access-for-deletion","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-privacy-framework-1.0","sourceTitle":"NIST Privacy Framework: A Tool for Improving Privacy through Enterprise Risk Management, Version 1.0"}],"intent":"A subject’s erasure request is recorded on intake whether the subject or the controller raised it, may be withdrawn by the subject while it is pending, is executed on the declared schedule, and terminates the erased person’s sessions.","objectiveRef":"WILDO.PRIVACY.SUBJECT_ERASURE","title":"Execute a subject erasure request, and evidence it"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-processor-engagement","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.CSWP.01162020","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-privacy-third-party-role-inventory","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-privacy-framework-1.0","sourceTitle":"NIST Privacy Framework: A Tool for Improving Privacy through Enterprise Risk Management, Version 1.0"},{"attributionNotice":"Identify the PCI Security Standards Council as the owner of PCI DSS and link to its document library; never state or imply PCI certification, compliance or endorsement.","authorityKind":"PROPRIETARY_STANDARD","canonicalLocator":"https://www.pcisecuritystandards.org/document_library/","contentUsePermission":"REQUIRES_ADDITIONAL_RIGHTS","metadataCitationAuthorized":true,"requirementRef":"source-requirement:pci-dss-third-party-service-provider-list","reviewedAt":"2026-09-25T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:pci-ssc-reference-only-v1","sourceRef":"source:pci-dss-4.0.1","sourceTitle":"Payment Card Industry Data Security Standard: Requirements and Testing Procedures, Version 4.0.1"}],"intent":"Routing data to an external service makes that service a processor of it, so such routing is opt-in by construction: nothing leaves unless the application selects a provider for that capability, and with no selection the work is served locally with no egress at all.","objectiveRef":"WILDO.PRIVACY.THIRD_PARTY_PROCESSING","title":"Name the processors that data is routed to"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-risk-appetite-and-tolerance-statements","reviewedAt":"2026-08-03T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-risk-documentation-and-prioritization-method","reviewedAt":"2026-08-03T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-risk-response-options-direction","reviewedAt":"2026-08-03T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"The exposures an application carries are DERIVED from what it declares and implements rather than asserted by anyone — which capabilities are enabled, which providers are vendor-hosted, which resources have answered the personal-data question, what an external agent can reach — and each carries the treatment its operator chose with the reasoning for that choice. A treatment claiming an exposure is not taken at all is checked against the measurement and reported when the two disagree, so the register is a set of statements the product itself can contradict rather than a document about intentions.","objectiveRef":"WILDO.RISK.TREATMENT_DECLARED","title":"Say what the risks are, and what was decided about each"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-authenticator-storage-protection","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-authenticator-storage-protection-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"The shape of a provider’s secret contract is tracked so that drift in it is detectable, without ever persisting the secret values themselves.","objectiveRef":"WILDO.SECRETS.CONTRACT_INTEGRITY","title":"Detect drift in a values-free secret contract"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-authenticator-disclosure-record","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"The first disclosure of server-minted secret material is an attributable, audited event.","objectiveRef":"WILDO.SECRETS.DISCLOSURE_AUDIT","title":"Audit the first disclosure of minted secret material"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-fail-secure-behaviour","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"A control that cannot be evaluated refuses what it guards, and stays diagnosable while doing so: untrusted input is rejected whole rather than partly sanitized, and a validator whose dependency is unavailable fails closed without its degradation being mistaken for a rejected signature.","objectiveRef":"WILDO.SECURITY.FAIL_CLOSED","title":"Refuse rather than degrade when a control cannot run"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-malicious-code-protection","reviewedAt":"2026-08-03T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-malicious-code-protection-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"Content uploaded into the application is inspected for malicious code before it is servable, and the inspection reaches a member of the file's own status vocabulary — clean, infected, quarantined or failed — rather than an opaque success, so a file that was never inspected and a file that passed are distinguishable.","objectiveRef":"WILDO.SECURITY.INGESTED_CONTENT_INSPECTION","title":"Inspect ingested content before it can be served"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.SP.800-218","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-218-code-access-least-privilege","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-218","sourceTitle":"Secure Software Development Framework (SSDF) Version 1.1"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.SP.800-218","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-218-development-environment-separated","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-218","sourceTitle":"Secure Software Development Framework (SSDF) Version 1.1"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.SP.800-218","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-218-development-toolchain-specified","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-218","sourceTitle":"Secure Software Development Framework (SSDF) Version 1.1"},{"attributionNotice":"Credit the OWASP AI Exchange and link to https://owaspai.org where practical; do not imply OWASP endorsement or use OWASP marks.","authorityKind":"COMMUNITY_GUIDANCE","canonicalLocator":"https://owaspai.org/","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:owasp-ai-exchange-coding-brief-indirect-prompt-injection-screening","reviewedAt":"2026-10-19T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:owasp-ai-exchange-cc0-v1","sourceRef":"source:owasp-ai-exchange","sourceTitle":"OWASP AI Exchange"}],"intent":"Code a coding agent writes into the application is produced inside the permission ceiling and write scope the application declares, by coding-agent vendors it declares with an established compliance profile, and only in the environments its execution profile admits, which never include production, and every change accepted through the creation lane's accept door is attributed to whoever accepted it: the host answers every permission request the agent raises and refuses a declared edit outside the task's scope even under an unrestricted ceiling; an agent that cannot be held to a narrower ceiling, because it never asks before writing or asks only when the host supplies its escalating configuration, runs only under a ceiling declared unrestricted; what a run changed outside its scope inside the application, a shell command's writes included, is recorded after the run, except a new file a shell command creates outside the application, which nothing lists; an acceptance the system makes under the autonomy posture is committed under the companion's own identity, never a person's, so the history says which accepted changes a person accepted; and a commit an agent makes itself through a shell command carries the local identity and is not attributed to the agent. What a coding agent's brief carries from outside the repository (what a research step brought in from the web, and the specification elements a step filled from it) travels only in sections marked third-party. The classifier the application binds in its build-time companion scope screens it, and a flagged element is withheld from that brief; it stays in the specifications, and the `wildo context elements` door screens it the same way before it answers. A research step's evidence is screened the same way where it is produced, before the generation steps beside it read it, and the outcome is recorded on the run. With no classifier, or one that cannot answer, the text travels marked as unscreened, never unmarked. Which text came from the web is recorded per family and aspect, never per statement. Text a step writes after reading research-informed input travels as trusted, and that input is screened the same way before the step's model reads it; a previous attempt's check outputs and closing report, and an assembly repair's failing check output, are screened before a brief carries them; and a brief composed with no classifier bound says its trusted text was derived from input nothing screened. When the catalog cannot say which elements came from the web, the served and website-plan elements are routed as third-party, marked and never blocked.","objectiveRef":"WILDO.SOFTWARE.AI_PRODUCED_CHANGE_CONTROL","title":"Produce AI-written code inside declared bounds and attribute every accepted change"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-configuration-settings-enforcement","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/a/r5/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53a-configuration-settings-enforcement-assessment","reviewedAt":"2026-09-24T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53a-rev-5-release-5.2.0","sourceTitle":"Assessing Security and Privacy Controls in Information Systems and Organizations"}],"intent":"A server-owned field has exactly one named authority that writes it, and that authority is proven at boot rather than assumed — so no second path can set the field and no reader has to work out which value is current.","objectiveRef":"WILDO.SOFTWARE.AUTHORITY_INTEGRITY","title":"Give every server-owned field exactly one named authority"}],"mappingRef":"assurance-external-mapping:wildo-safe-baseline-v1","mappingVersion":1,"normativeSourceContentIncluded":false,"tailoringCaveat":"A control catalog requires tailoring, implementation and assessment; catalog inclusion is not proof of operation. This mapping records which external source each Wildo objective was reviewed against. It is not a conformity assertion, it claims no operating effectiveness, and it reproduces no normative source text.","unmapped":[{"objectiveRef":"WILDO.ACCESS.SEGREGATION_OF_DUTIES","reason":"The assurance authority basis states no expectation for this objective, so no source requirement has been reviewed against it. An objective the framework has not bound cannot honestly cite an external source (#207).","title":"Require a second person for an act nobody else can check"},{"objectiveRef":"WILDO.AUDIT.TAMPER_RESISTANCE","reason":"The assurance authority basis states no expectation for this objective, so no source requirement has been reviewed against it. An objective the framework has not bound cannot honestly cite an external source (#207).","title":"Let a named runtime principal append to the audit trail and never alter it"},{"objectiveRef":"WILDO.BILLING.PROVIDER_RECONCILIATION","reason":"The assurance authority basis states no expectation for this objective, so no source requirement has been reviewed against it. An objective the framework has not bound cannot honestly cite an external source (#207).","title":"Reconcile local billing state against the provider"},{"objectiveRef":"WILDO.BILLING.USAGE_REPORTING","reason":"The assurance authority basis states no expectation for this objective, so no source requirement has been reviewed against it. An objective the framework has not bound cannot honestly cite an external source (#207).","title":"Report metered usage to the billing provider"},{"objectiveRef":"WILDO.DOCUMENTS.APPROVAL_BEFORE_PRESENTATION","reason":"The assurance authority basis states no expectation for this objective, so no source requirement has been reviewed against it. An objective the framework has not bound cannot honestly cite an external source (#207).","title":"Show or ask a person to accept a governed document only once it is approved"},{"objectiveRef":"WILDO.NETWORK.OUTBOUND_TARGET_CONTROL","reason":"The assurance authority basis states no expectation for this objective, so no source requirement has been reviewed against it. An objective the framework has not bound cannot honestly cite an external source (#207).","title":"Reach only an admitted address from a destination someone else chose"},{"objectiveRef":"WILDO.SECRETS.CREDENTIAL_SCOPING","reason":"The assurance authority basis states no expectation for this objective, so no source requirement has been reviewed against it. An objective the framework has not bound cannot honestly cite an external source (#207).","title":"A configuration cannot choose which secret a vendor or an agent receives"}]}
|