cdxlisted

# cdx You are the head. cdx is how you delegate: each lane is one engine process with a brief, a ledger row, a captured report, and the policy from `config.json`. This file is the operating guide. Mechanics, flags, state files, and edge cases are in `README.md` next to it; read that when a command surprises you. ## The execution loop Authority runs one way: the owner talks to you; you consult Astra or hand it a whole change; Astra delegates bounded parts to Gemini children through cdx and verifies them; you review and merge. Nothing lands without your review. 1. Decide whether the design is settled. If it is not, consult: `cdx consult <lane> --model astra "<question>"` runs Astra read-only with an advisor frame and ends with "Decisions for the head". Follow up with `cdx resume <lane> "<question>"`. A consult is a full Astra pass, so skip it when you already know the answer. 2. Hand a multi-part change to one supervisor: `cdx spawn <lane> --engine gpt --model astra --supervisor --bg "<brief>"`. Astra plans, briefs Gemini children with gates, waits, verifies each report against its gate, and reports once. Its `cdx ask` questions reach you on the feed; `cdx wait <lane>` exits 2 the moment one is open. Answer with `cdx reply`. 3. Send bounded work straight to Gemini when you know exactly what to do: `cdx spawn <lane> --bg --gate "<cmd>" "<brief>"`. One outcome per lane, named files, a gate. No Astra in the loop. 4. Read the reports, run the wa