Skip to content
Braver New WorldBNW docs

Routing by data handling

Providers declare how they handle invocation data on every offer they sign:

  • Egress: processed on their own machine, or sent on to a remote service. The egress comes from the registered backend: an inference registration’s payload egress, or an MCP registration’s remote-execution consent.
  • Region and retention: added with bnw capability offer … --region EU --retention-days 0, or the provider console’s offer form. Renewals keep them.

Requesters keep a local routing policy:

Terminal window
bnw routing --local-only --region EU --max-retention-days 0 --require-declared
bnw routing --show
  • Where it applies: every automatic choice of provider skips offers whose declaration does not satisfy the policy. That covers an agent’s model, a portable agent’s requirements, bnw mcp serve’s invoke_capability, and the web Invoke form’s default.
  • Configured providers too: a configured provider outside the policy is refused rather than used.
  • In the web client: the Capabilities screen shows each provider’s declared handling, marks those outside the policy, and edits the policy.
  • Trust: declarations are the providers’ own claims. The policy refuses providers that declare too little or the wrong thing; it cannot verify the ones that pass.