Policies and Decisions

The current governance model uses separate human management roles and virtual-key inference policy. Effective API access is catalog ∩ Team allowance ∩ key policy, with current owner/credential checks and canonical budgets. The former policy-bundle/Project binding screens are retired.

• Roles and permissions describes bounded human administration.
• Teams describes allowance and membership sources.
• Virtual keys describes API policy and lifecycle.
• Managed deployments describes secretless execution policy and publisher funding.
• Observe Requests provides canonical decisions and separate financial/telemetry evidence.

Current database policy changes take effect on subsequent checks. Reviewed YAML remains startup-loaded; see Configuration.