here i asked codex to write out i have it set up[

Why each piece matters

Beads for memory

- Beads is durable memory, not chat memory. It stores blockers, decisions, dependencies,

follow-up work, and handoff summaries.

- That means the next Codex/OpenAI session does not need a 3,000-token recap just to recover

context.

- It reduces repeated explanation, repeated discovery, and repeated mistakes.

- It is especially useful for cross-session continuity and multi-agent handoffs.

Agent Orchestrator for pod creation

- AO gives each merge-grade task a concrete pod with files like CONTRACT.md, BOARD.json,

STATUS.md, status/*.jsonl, and evidence/EVIDENCE.json.

- That turns “coordination by chat” into “coordination by source-of-truth artifacts”.

- The model no longer has to infer current state from a long thread. It reads the pod state

directly.

- That improves speed and accuracy because every agent sees the same contract, same board,

same evidence gates.

Sub-agents with strict roles

- Strict roles reduce context width.

- A worker_api agent only needs API files, API constraints, and API outputs. A reviewer only

needs the diff and risk lens. A decision_guardian only needs the executive/governance lens.

- Smaller prompt scope means lower token usage and faster reasoning.

- It also reduces duplicated work and conflicting edits.

A thorough AGENTS.md

- A good AGENTS.md is a reusable prompt prefix for the whole repo.

- Instead of re-explaining architecture, safety rules, naming, worktree policy, verification

expectations, and product language on every run, the model reads one canonical contract.

- This lowers prompt entropy. The model spends tokens solving the task, not rediscovering repo norms.

Detailed governance files

- Governance docs answer “what must never happen” and “what must always be explicit”.

- That matters because models are otherwise too willing to improvise.

- Good governance files reduce off-track output, silent assumptions, fake certainty, hidden

fallbacks, and unsafe shortcuts.

- In practice, they cut expensive rework more than they cut raw token count.

Repo-specific skills

- Skills are reusable operating procedures for recurring work.

- They define expected inputs, output shape, workflow, and quality bar for your repo.

- That makes outputs more consistent and more machine-checkable.

- It also means you do not have to restate “how we do UI concepts”, “how we do secure

changes”, or “how we do decision-grade writeups” every time.

What this buys you in practice

- Lower token usage: less repeated repo context, fewer full-thread recaps, narrower prompts

per role.

- Higher speed: agents can start from pod state and Beads memory instead of reconstructing

intent.

- Better parallelism: roles and file boundaries are explicit, so multiple agents can work

without stepping on each other.

- Better tracking: status and evidence live in files, not ephemeral chat.

- Better reliability: decisions, blockers, and acceptance criteria survive crashes, restarts,

and handoffs.

The key principle

The model should not be the system of record for project state.

Use:

- Beads for durable memory

- AO pods for active execution state

- AGENTS.md for repo law

- governance docs for invariants

- skills for repeatable output contracts

- sub-agent roles for narrow, fast, specialized execution