platform · AVC

Trust boundaries before convenience.

AVC is local-first, capability-scoped and fail-closed around consequential operations.

Capability	Authority	Risk	Evidence
operator.status	Observe	R0	Health snapshot
mission.prepare	Prepare	R1	Proposal receipt
external.execute	Approved execution	R3	Approval + result receipt
root.modify	Forbidden	R4	Blocked event

Security posture

Trust grows only after independent controls agree.

The system remains fail-closed around missing or stale evidence.

Identity
Resolve the actor and workload before evaluating the request.
passed
Least privilege
Match the exact capability, resource, environment and risk ceiling.
passed
Data classification
Apply access, retention and redaction rules before persistence.
active
Side-effect containment
Use idempotency, bounded retry and circuit breaking.
active
Recovery evidence
Do not restore normal authority until mitigation is verified.
pending

Trust boundary

Loopback interfaces, short-lived session tokens, least privilege and capability checks still separate operators, clients and runtimes.

Data discipline

Classification, retention and access evidence govern what may be stored and who may read it.

Containment

Idempotency, circuit breakers, dead-letter handling, rollback and recovery prevent a failing worker from becoming an infinite side-effect machine.