# account-subrouter

AWP `AccountProvider` adapter for current Subrouter account discovery and explicit force-account routing mechanics.

AWP remains authoritative for account/model/provider identity, authorization, policy and Attempt provenance. The adapter never treats user-attribution metadata as authorization and never exposes Subrouter credential material.

## Reuse / consumer proof

Lane B verified three distinct facts rather than inheriting historical Overdeck behavior:

- current public Subrouter source reviewed by AWP: `manaflow-ai/subrouter@1c5719c702e16d7f458a2b5e20be9084fa88d86b`;
- deployed/reference Overdeck consumer pin: upstream Subrouter `v0.1.81@29c7ebb306ac54739206f4752449e437047dd150` plus `modules/subrouter/patches/0001-overdeck-authority-safety.patch`;
- current Platform reuse gate: `platform-modules/mod@801cad34010b87ed58e6450bed31c59d12b8f21a` does not expose an AWP-suitable provider-account/mutable-token authority capability. Its AWP Step-0 upstream work covers realtime/config/logger and defers generic idempotency.

The Overdeck patch is **reference evidence only**. AWP does not copy its routes, state layout, grants, service-user mechanics or authority implementation. AWP consumes Subrouter only behind its own `AccountProvider`/Attempt/Connection contracts.