Understand a specific behaviour
Follow the part of the request or policy you are investigating. Each topic links to its complete reference.
On this page
How a public version is admittedDefaults, rule order, exceptions, and ecosystem differences.
Why private reads behave differentlyCaller credentials, trusted copies, and digest conflicts.
What happens when advisory data is missingFreshness, skipped checks, partial fixes, and readiness.
When a mirrored version becomes readableWhole-version completion, partial uploads, and public outages.
Why a denied version is still availableAdmission versus revocation, retained copies, and policy rollout.
How configuration resolvesDefaults, file values, environment overrides, and role validation.
Which identity needs which permissionCloud roles, caller credentials, and deletion authority.
Protocol detailsSupported endpoints, metadata fields, and ecosystem limits.
Security and design evidence#
The rendered threat model remains the security reference. It includes operation-specific diagrams, threats, controls, and accepted assumptions.
The architecture documents explain design choices. The generated API reference covers contributor interfaces.