Skip to content
FlareDispatch

The flare-dispatch substrate

The substrate is where agentic work runs: containers under deny-all egress, ticket-gated admission that owns the account’s Containers ceiling, artifacts on R2, and metered model access. It executes; it never decides what to run and never renders an outcome. Consumers — the dispatcher in this repo, fractalbot from its own — reach it through one service-binding facade and nothing else.

Where the substrate sits Flowchart, left to right. 7 nodes, 6 edges. dispatcher DispatcherFacade → facade one service binding facade one service binding → admission D1 pool slots; → Sandbox DO ticket gate, exec fence fractalbot FractalbotFacade → facade one service binding Sandbox DO ticket gate, exec fence → container deny-all egress; → R2 artifacts, snapshots dispatcherDispatcherFacade facadeone service binding fractalbotFractalbotFacade admission D1pool slots Sandbox DOticket gate, exec fence containerdeny-all egress R2artifacts, snapshots
Where the substrate sits
Diagram source
flowchart LR
  accTitle: Where the substrate sits
  disp["**dispatcher**<br/>`DispatcherFacade`"] --> fac["**facade**<br/>one service binding"]
  fb["**fractalbot**<br/>`FractalbotFacade`"] --> fac
  fac --> adm[("**admission D1**<br/>pool slots")]
  fac --> sdo["**Sandbox DO**<br/>ticket gate, exec fence"]
  sdo --> box["**container**<br/>deny-all egress"]
  sdo --> r2[("**R2**<br/>artifacts, snapshots")]
  class fac accent

These four documents are what a consumer or an operator needs; none of them requires reading the substrate’s source.

Document For Answers
Consuming the facade Consumer authors How to bind, what the call sequence is, how every failure arrives
Facade API reference Consumer authors Every exported type, generated from packages/substrate-contract
Authoring a grant profile Substrate and consumer maintainers How egress is granted, how a profile is written and reviewed, how it graduates to enforcement
BYOC upgrade runbook Operators Provisioning, the overlay, deploy order, version floors, rollback
Contract versioning policy Both What bumps CONTRACT_VERSION, and what a consumer migration costs

Design records live under apps/substrate/specs: the platform spec states what, the ADRs carry why. These guides state how, and cite the ADR wherever a decision is load-bearing.