You are running one round of the this-or-that decision flow: the user can't articulate their taste, but they can pick between two things all day. Turn the question below into an Elo-voted decision with a durable record.
Question to decide: {{ _question }}
Subject / content source (hold constant across every option): {{ _subject }}
authoring-lab/ and 07-variations/template-lab/)<slug>-lab/ at the repo root. Copy compare.html
and server.py verbatim from 10-this-or-that/kit/. Write options.json
({title, modes: true, options: [{id, name, src}]}). Write one shared base
stylesheet all options link, so theme stays constant; support
html[data-mode="light|dark"] (light default, prefers-color-scheme +
data-mode override) — the harness stamps it and records the mode on every vote.server.py; grep-audit
(zero external requests, no absolute home paths, no secrets); render both light
and dark; POST a smoke vote to /vote, confirm it lands in votes.jsonl,
remove it.python3 server.py <port> in the
background and give the user the compare.html URL. Controls: ←/→ pick ·
↓ both bad · d flips light/dark · s skip · f finish · the note field
saves with each vote (tell the user: one note outweighs ten votes).votes.jsonl — ranking, per-mode W-L
splits, both_bad lines, and especially notes. State the user's taste as
explicit, quotable rules backed by vote evidence (head-to-heads, splits,
quoted notes). A user note that makes a decision IS the decision.votes-round<N>.jsonl, write RESULTS.md (standings
table, the decision with quoted evidence, taste rules, ship plan), update
agent memory so it is never re-litigated. Then propose round 2 from the
winners — or ship.@../authoring-lab/RESULTS.md
@../07-variations/template-lab/RESULTS.md
---
description: Run one this-or-that Elo voting round — generate structurally distinct options over a constant subject, stand up the duel harness, wait for votes, then bank the taste as explicit rules
_inputs: [_question, _subject]
_interactive: true
---
You are running one round of the **this-or-that decision flow**: the user can't
articulate their taste, but they can pick between two things all day. Turn the
question below into an Elo-voted decision with a durable record.
**Question to decide:** {{ _question }}
**Subject / content source (hold constant across every option):** {{ _subject }}
## The process (exactly as proven in `authoring-lab/` and `07-variations/template-lab/`)
1. **Frame the axis.** Name the ONE thing options vary on (theme, format, copy,
API shape). Everything else — subject content, visual theme — is held constant
so votes measure only that axis.
2. **Scaffold the lab.** Create `<slug>-lab/` at the repo root. Copy `compare.html`
and `server.py` **verbatim** from `10-this-or-that/kit/`. Write `options.json`
(`{title, modes: true, options: [{id, name, src}]}`). Write one shared base
stylesheet all options link, so theme stays constant; support
`html[data-mode="light|dark"]` (light default, `prefers-color-scheme` +
`data-mode` override) — the harness stamps it and records the mode on every vote.
3. **Generate 9–13 structurally distinct options.** Same subject, different
approach; if two could be confused at arm's length, replace one. Include the
incumbent as a control when one exists. Write one exemplar option yourself,
then fan out parallel subagents, each authoring 2–3 options from one tight
shared brief (subject digest + format rules + per-option spec + the exemplar
path). Real content only — never lorem ipsum, never invented names.
4. **QA before handing over.** Every file HTTP 200 through `server.py`; grep-audit
(zero external requests, no absolute home paths, no secrets); render both light
and dark; POST a smoke vote to `/vote`, confirm it lands in `votes.jsonl`,
remove it.
5. **Hand over and get out of the way.** Start `python3 server.py <port>` in the
background and give the user the `compare.html` URL. Controls: ←/→ pick ·
↓ both bad · `d` flips light/dark · `s` skip · `f` finish · the note field
saves with each vote (tell the user: one note outweighs ten votes).
6. **When the user says "done":** read `votes.jsonl` — ranking, per-mode W-L
splits, `both_bad` lines, and especially notes. State the user's taste as
explicit, quotable rules backed by vote evidence (head-to-heads, splits,
quoted notes). A user note that makes a decision IS the decision.
7. **Bank it.** Archive as `votes-round<N>.jsonl`, write `RESULTS.md` (standings
table, the decision with quoted evidence, taste rules, ship plan), update
agent memory so it is never re-litigated. Then propose round 2 from the
winners — or ship.
## Accumulated taste record (injected fresh each run — read before generating options)
@../authoring-lab/RESULTS.md
@../07-variations/template-lab/RESULTS.md