Make the authority boundary inspectable.

Configuration should explain which actions are governed, which need approval, what effect evidence is trusted and what can still bypass the boundary.

Policy

• prefer default deny for consequential paths;
• bind rules to narrow operation/resource identities;
• test allow and deny cases;
• review policy changes that invalidate earlier assumptions;
• do not put secrets in public configuration.

Effect Profiles

A profile is reviewed postcondition semantics, not a generic tool-name mapping. Routes without trustworthy effect semantics can remain policy-protected but should not claim effect-boundary readiness.

Approvals

Approval adds explicit authorization. It does not prove execution or effect and should not receive more sensitive context than necessary.

Evidence

Evidence is local by default. Protect the workspace with normal host/filesystem controls and define retention appropriate to your environment.

Network exposure