Wrappers, Routes, Networks: The Operating Model
Most agent stacks break because capabilities are discovered ad hoc and executed without deterministic controls. Anything.network standardizes the stack around three primitives: wrappers, routes, and networks.
1. Wrappers Are Capability Contracts
A wrapper is not just a function endpoint. It is a typed contract with required inputs, safety constraints, observability hooks, and version tags. Agents should choose wrappers by metadata, not hardcoded provider names.
2. Routes Are Outcome Programs
A route composes wrappers into an execution graph. It includes fallback logic, approval points, retries, and post-conditions. This turns agent intent into reliable behavior with measurable outcomes.
3. Networks Are Governance Surfaces
Networks define which wrappers are available to which teams and agents under what rules. They are operational boundaries for compliance, spend controls, and role-based access.
Implementation Pattern
- Pick one capability domain and define 3-5 wrappers with strict schemas.
- Implement one production route with explicit rollback and timeout behavior.
- Run in one network with per-wrapper policy and trace-based observability.
The objective is composability with reliability. If wrappers are clear, routes are deterministic, and networks are governed, agents can scale across domains without brittle integrations.