01 Request
Stated outcome
Name the result. It is not a command and not a grant.
Dispatch / governed intent and action
Ask for the outcome. Keep the engineering controls.
Dispatch is where a requested outcome becomes an inspectable proposal. The product that owns the work still decides and realizes it. This host does not run a visitor console.
Intent enters through Dispatch. Authority stays with the domain.
01 / Request to proposal
See the path before anyone treats it as work.
A request can be narrowed or refused. Confirmation is not Dispatch approving the work. Handoff is to the owning domain's gates.
02 Context
Missing facts
Identifiers and gaps stay visible. Dispatch does not invent sibling state.
03 Proposal
What would happen
An inspectable action the domain can accept, revise, or refuse.
04 Confirm
Human checkpoint
Product-layer confirmation. Domain gates still evaluate the change.
05 Handoff
Owner realizes
Repave, Overpass, or Toll keep realization, evidence, and refusal.
Hosted Repave generate example
“Create a service from the approved blueprint with these inputs.”
Available through the hosted Repave experience today. Repave evaluates gates and realizes the repository. Dispatch is not an alternate apply path.
Not an executable Dispatch action
“Restore the last approved governed files.”
Restore and remediate stay with the owning delivery product. This page does not offer that action, and Dispatch does not mint or route a platform environment identifier.
02 / Domain authority
Four products. Authority stays put.
Dispatch coordinates a request. It does not own repository lifecycle, infrastructure state, economics, or platform Environment. It does not evaluate another product's gates.
Dispatch
Intent and proposal
Governed interaction. Not the store of record. This host. Not Environment.
Delivery
Repository lifecycle, gates, realization. Environment stays here.
State
Infrastructure custody and relationships.
Economics
Utilization evidence and FOCUS custody.
This host
Identity and health
Public identity, liveness, and readiness on a Dispatch-owned workload. Operator-only tooling is not a visitor action.
Now
Repave-hosted interaction
The governed experience visitors can use still runs in Repave. Confirm-to-act for repository work lands on Repave gates.
Planned
Standalone runtime
An independent governed interaction runtime is direction, not current availability on this host.
There is no Ask, Confirm, or Apply control on this page. /intent is operator-authenticated and is not linked here.
02b / Policy-governed delegation
Delegation can be decided. Dispatch does not yet enforce every control.
Policy-native delivery asks who or what may invoke a capability, at what scope, with which confirmation, dry-run or execute authority, required evidence, and time-bounded exception. That is the intended contract. It is not the current Dispatch host.
Present
Identity, hosted confirm, and refusal to self-approve
This host is public identity. The hosted confirm path for repository generation still runs in Repave. Dispatch does not evaluate the shared policy-decision port and does not approve its own work.
Foundation and direction
Actor, scope, and exception as decision context
The family decision contract can already carry actor, capability, and exception facts. Wiring those from Dispatch into a decision — and enforcing them — remains product direction, labeled separately from what this page can prove today.
03 / Capability maturity
Current truth before product direction.
Statuses describe Dispatch specifically. They do not relabel sibling work as independently delivered here.
available
Public identity and health
This Dispatch-owned host serves its public identity, health, and readiness endpoints.
production validation
Governed interaction model
The intent, proposal, confirmation, and domain-authority model is defined; product extraction from the hosted experience is incremental.
production validation
Hosted governed experience
The hosted experience remains in Repave today while Dispatch and the internal runtime are extracted.
in development
Cross-domain experience
Capability exposure across delivery, state, and economics is being separated without moving domain authority.
planned
Independent governed interaction runtime
The Dispatch-owned workload is independently deployed today. The governed interaction experience and its internal runtime remain hosted in Repave while extraction continues.
04 / Evaluate
Talk, or ask for hosted access through Repave.
This host has no deploy-now path, no visitor console, and no Environment control. Early conversation and the Repave waitlist are the truthful next steps.