How to Add an Adapter Without Expanding the Blast Radius

New adapters should be introduced with explicit blast-radius boundaries so failures stay local while parity is still being verified.

The safest adapter rollout is the one that can fail locally. Blast radius expands when new paths inherit production authority before their failure behavior is understood.

Keep the rollout contained

• Limit scope to one workflow or tool class first.
• Preserve separate audit visibility for the new adapter.
• Make rollback immediate if parity checks fail.

Use the adapter system, AuthGuardian, and integration guide to define containment rules.