Bring a project with a past under the Hypergraph protocol - import an existing hosted graph as legacy history (mode A) or author honest prehistory from the repo itself (mode B), draw the adoption epoch, distill a real state graph, and install the AGENTS.md onboarding. Use hypergraph-init only for day-zero projects.
Dispatch an agent at a target in a Hypergraph project - a frontier state slug, a prose goal, or a region of the state graph - work a bounded budget of units, and record everything as a causally-parented dispatch lineage. Reads live lane claims to avoid double work. Never reconciles, never writes state nodes.
Initialize the Hypergraph two-graph protocol (record graph + state graph) for a day-zero project. Creates both roots, seeds a state skeleton mirroring the architecture, writes .hypergraph/config.yml, and generates STATE.md. Use hypergraph-adopt for a repo that already has a history.
Cold-start orientation for a Hypergraph project - land on the state graph, read the frontier (open/broken/blocked), and produce an orientation brief with provenance slugs for deep dives. Read-only, a handful of file reads.
The single-writer librarian pass for a Hypergraph project - folds declared State Impacts from unreconciled record nodes into the state graph, advances the high-water mark, regenerates STATE.md, and runs the invariant checker.
Commit a unit of research/engineering work to a Hypergraph record graph with a State Impact declaration. Use during or after any meaningful unit of work in a project with .hypergraph/config.yml. Never writes state nodes.
AGENTS.md instructions for theo-kirby/cadex, covering agents.md — agent entry point, read this first (doc index, in order), repo map, commands and far, but the engine is not.