mfowler
7f237a522c
A self-contained examples/builder-adversary/ that distills the cc-ci production loop pair into a tiny, fully-local task (build a `wc` CLI in two phases): - agents.toml: builder + adversary loops, persistent orchestrator, on_complete reporter, cleanlogs service; phase machine with a per-phase model override - prompts/: kickoff template + builder/adversary roles carrying the load-bearing protocol (claim()/review() handoff, machine-docs file-location rule, WHAT+HOW+EXPECTED+WHERE=STATUS / WHY=JOURNAL anti-anchoring, WAITING-UNTIL liveness) - plans/: two phase plans (wc, json) each with a cold-verifiable Definition of Done - README: how to run, the work-repo two-clone isolation model, how to adapt Verified: `agents.py status --config agents.toml` parses and lists all agents. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
44 lines
2.3 KiB
Markdown
44 lines
2.3 KiB
Markdown
# Phase `wc` — a word-count CLI
|
|
|
|
**Mission.** Build a small, dependency-free `wc` clone in Python: a script `wc.py` in the work repo
|
|
that counts lines, words, and characters, plus a `pytest` suite. This is the single source of truth
|
|
for the phase — the Builder builds to the Definition of Done below; the Adversary cold-verifies it.
|
|
|
|
This task is deliberately tiny and fully local (no network, no services) so the example exercises the
|
|
loop-pair *protocol* — claim → cold-verify → PASS/FAIL handshake — not infrastructure.
|
|
|
|
## Definition of Done
|
|
|
|
Each Dn is an independent gate. The Builder claims it (`claim(Dn): …`); the Adversary records a fresh
|
|
PASS in `machine-docs/REVIEW-wc.md` after re-running the check from its own clone.
|
|
|
|
- **D1 — default output.** `python wc.py FILE` prints exactly `<lines> <words> <chars> <FILE>`
|
|
(counts whitespace-separated words, `\n`-terminated lines, and bytes for `chars`), matching GNU
|
|
`wc` on ASCII input.
|
|
- **D2 — flags.** `-l`, `-w`, `-c` restrict the output to that single count (e.g. `wc.py -l FILE`
|
|
prints `<lines> <FILE>`). Flags may combine; output order is lines, words, chars.
|
|
- **D3 — stdin.** With no FILE argument, `wc.py` reads stdin and prints the counts with no filename.
|
|
- **D4 — tests green.** A `test_wc.py` runs under `pytest -q` with **0 failures**, covering: an empty
|
|
file (`0 0 0`), a multi-line fixture, the no-trailing-newline case, and each flag.
|
|
|
|
## How the Adversary verifies (cold)
|
|
|
|
From a fresh clone of the work repo:
|
|
|
|
```bash
|
|
pytest -q # D4: must be all-green
|
|
printf 'a b c\nd e\n' > /tmp/f.txt
|
|
python wc.py /tmp/f.txt # D1: expect "2 5 10 /tmp/f.txt"
|
|
python wc.py -l /tmp/f.txt # D2: expect "2 /tmp/f.txt"
|
|
printf 'a b c\nd e\n' | python wc.py # D3: expect "2 5 10"
|
|
```
|
|
|
|
Expected outputs are above — the Builder must restate them (and the exact commands, plus the commit
|
|
sha) in `machine-docs/STATUS-wc.md` so the Adversary can re-run without reading the Builder's
|
|
reasoning. Any mismatch is a FAIL with repro steps in `machine-docs/REVIEW-wc.md`.
|
|
|
|
## Out of scope (defer to a later phase or DEFERRED.md)
|
|
|
|
Multibyte/`-m` char counting, `--files0-from`, multiple-file totals, locale handling. JSON output is
|
|
the next phase (`plans/json.md`).
|