This document defines the workflow for Sam, GPT‑5, and Codex when collaborating on smoo.
The goal is to keep a clean, comprehensible codebase while safely harnessing LLM acceleration.
- Final decision‑maker
- Provides architectural direction
- Writes manual commits where needed
- Prepares Codex prompts as markdown attachment files
- Design reasoning, critique, clarification
- Produces small sketches but not large hunks of code
- Helps refine Codex prompts and architecture
- Emits large diffs, modules, entire files
- Must follow HACKING.md precisely
- Must produce compilable Rust and pass
cargo build --workspace --locked
- Sam prepares a prompt
- GPT‑5 reviews the prompt and ensures architectural correctness.
- Codex is invoked with that prompt.
- Codex returns a diff or new file.
- Sam reviews and commits.
- Code must be formatted with
rustfmt --edition 2021. - Codex output must compile.
- Agents must refer back to HACKING.md for protocol, invariants, and architecture.
- Prefer async‑only code; blocking must be justified.
This workflow is intentionally strict to maintain project integrity while allowing rapid iteration.
- Prefer small, reviewable diffs; add brief rationale in the PR/commit message body when applicable.
- Unless explicitly impossible, do not end a turn without running and passing
cargo fmt,cargo check --workspace, andcargo clippy --workspace(or explaining why it failed/was skipped). - Avoid introducing new tools/dependencies without a short justification and a confirmation from the Developer.
- If instructions in this file conflict with user directions, ask for clarification before proceeding.