Chokepoint Remediation Plan

This review frames the system as a chokepoint problem: a shared weakness enables several qualified paths from retrieval to tool use, from prompt to delegated action, and from service identity to external effect. Rather than treating each path independently, the remediation plan targets controls that interrupt the common authority boundary and reduce overbroad consequence-bearing capability. The prioritized response is to narrow action scope, require contextual approval for sensitive transitions, and retain decision and execution evidence so residual risk remains visible and auditable. The expected outcome is that Path A is blocked, Path B is blocked, and Path C is reduced to residual risk pending retest. A named implementation owner and explicit retest criteria anchor accountability and make verification concrete.