What to verify before adding another adapter

Adapter count is only meaningful when every adapter has clear boundaries and observable failure modes.

New adapters look like momentum on a changelog. They only become real progress when the control plane can explain how they behave under denied access, malformed inputs, and partial failure.

The wrong question is whether an adapter works once. The right question is whether its operational boundaries are obvious enough to trust in a shared system.

Verify these three things

• Routing is deterministic when more than one compatible adapter exists.
• Failures stay local instead of contaminating unrelated workflow state.
• Capability claims match the code that actually ships.

Adapter breadth is useful only when the control layer can keep all of that breadth legible.