Dispatch
Intent. Proposal. Gate. Action.
- Problem
- Intent that cannot be proposed or refused with evidence.
- Input
- A request toward a domain product that already owns the work.
- Outcome
- A proposal, a confirmation boundary, or a refusal — not a new store.
- Availability
- Emerging. Public identity exists; the hosted assistant still runs in Repave.
by OpsDevCode
Job
Ask, propose, and where allowed act across engineering domains without moving policy authority into the agent.
Dispatch is the governed interaction product: intent to proposal to allowed action. It consumes Repave, Overpass, and Toll; those products remain authoritative. It is not a fourth data domain.
The public Dispatch host is identity, not the hosted assistant. Today the assistant still runs in Repave. Generate is the wired write. Reads can surface other capabilities. Dispatch never evaluates the shared policy-decision port or approves its own work. This is not a standalone four-product interaction product.
Direction — not current enforcement — includes who may invoke a capability, permitted scope, approval boundaries, dry-run versus execute, required evidence, and time-bounded delegation. Present capability is the hosted confirm path and identity host.
Current state
Emerging. Public identity exists. The hosted assistant still runs in Repave. Dispatch does not approve its own work and is not a generally available agent product.
Owns
- Intent capture into a proposal
- Trust-ladder policy of use
- Capability-backed tools without taking domain stores
- Evidence-bound action where a domain product allows it
- Refusal when policy or evidence is missing
- A public identity distinct from the current hosted assistant
Boundaries
- Gate or policy evaluation (stays in domain products)
- Domain stores for delivery, state, or spend
- Approving its own work
- General autonomy or a generally available agent product