
# NP WINGS Agent Team and Routing

The canonical NP sources define systems and workflows, not autonomous agents. The ten-agent registry is an implementation-generated, restrictive routing aid. All agents install `PERM-P0 Disabled`.

## Routing rules

- Choose no agent when offline/local controls can complete the task.
- Select one primary agent from the user's requested outcome and active task hat/workspace/context.
- Show the routing reason and allow owner override or no-agent mode.
- A second agent may review only under a frozen charter; it receives no hidden context.
- The independent auditor uses a separate control path and cannot approve the work it generated.
- No recursive delegation, shared hidden memory, background continuation or self-expansion.

## One-run charter

Freeze purpose, owner, active task hat/workspace/context, admitted data, exact sources, tools, model, time/token/cost/retry limits, output type, EDENA state, prohibited actions, human gates, stop/kill/fallback, expiry and receipt. P1 reads admitted context and explains. P2 drafts or runs a fictional simulation. Both permit one invocation, zero hidden retries and automatic return to P0.

P3, if implemented, is a separately approved deterministic local personal reminder after three supervised successes. It uses no model, connector, institutional data, surveillance, inference or external destination. P4 is absent.

See `config/NP-Agent-Registry.v1.json` for the exact ten IDs and ceilings.
