Available
Tenant isolation
Server-derived scope, API authorization, FORCE RLS and negative tests protect every boundary.
Security & trust
A system that can block traffic must earn that authority.
Tenant isolation, scoped provider credentials, deterministic guardrails, minimal telemetry and reversible enforcement are release gates, not optional features.
01
What this capability is responsible for
Each function has a narrow operating boundary and a state derived from evidence.
Available
Auditable action
Every decision records actor, reason, evidence, scope, TTL and rollback state.
Available
Data minimization
Bodies, credentials and session tokens are not collected by default.
02
How the operating flow works
The visitor path remains short while control, evidence and rollback stay explicit.
- 01
Verify ownership
No scan or active control starts without explicit scope.
- 02
Limit authority
Credentials and actions are scoped to one provider, tenant and service.
- 03
Prove rollback
Release gates include failure and recovery, not only the happy path.
Start with observation. Promote only measured controls.
Every traffic activation requires ownership, certificate, origin and rollback checks.