Architecture decision records

Decisions that settle a direction the rest of the repo then assumes. One file per decision, numbered, never edited after acceptance — a superseding decision gets a new record that names the one it replaces. Format: Status / Context / Decision / Rationale / Consequences / Revisit triggers.

A record is only binding once its Status reads accepted. Treat proposed rows as under discussion — in particular, do not implement against a proposed record’s interfaces or assume they exist.

ADR	Status	Decision
0001	proposed	How runs use Cloudflare Workflows: one instance per dispatch, hibernation reserved for bounded human decisions, entity lifecycles keep state in the system of record
0002	proposed	Org context is an optional, total memory capability with MCP-speaking adapters; runs consume, never produce
0003	proposed	Context backends ingest GitHub directly; FlareDispatch builds no relay, export, or pull endpoint for them
0004	proposed	A run may declare a serialization group: one execution in flight, newest waiter wins, never cancel the running one; state in D1