Add a write-up checklist to ETHOS and the READY template (GST-2755) (#4381)

* Add a write-up checklist to ETHOS and the READY template (GST-2755)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* Fix a mid-sentence colon in the write-up checklist changelog note

Review-Finding: p1/adversarial-native#1 reader=adversarial-native
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

---------

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
This commit is contained in:
Garry Tanandcapy-ai[bot] authored and GitHub committed 2026-11-16 02:53:22 +00:00
1 parent 984a268306
commit 2c0e07886b
3 files changed
+23

No files matched your search

+18
View File
@@ -282,11 +282,29 @@ reason, helping builders or letting others reproduce a published finding. None
of this bends the rules above: no number is rounded in our favour and no caveat
is dropped.
### Write-up checklist
Before a post or write-up goes out, check three things. The second also holds for every
ready or status report.
1. **The words match the page.** Every claim the text makes, the page it links makes too,
at the same strength. If the page says the other side won by a few points, the post
doesn't say "as good as". Readers repeat the post, not the page.
2. **Every number, "green" and "ready" names its source, read at the current head.** Give
the run id, commit, command or file it came from, and read it again on the tree you are
shipping. A number carried over from an earlier head, or taken from a list a tool
capped, is a guess until re-read; re-read it or mark it unverified.
3. **A fresh model reads it cold, once.** Give a model with none of the work's context the
finished text and the pages it links, and ask what the text claims and where it lost
the thread. Fix what it misread, then send. One read, not a loop.
**Anti-patterns:**
- A speedup from one run on each side.
- A pass rate without the trial count.
- "Faster" with no theory of what changed.
- A results file whose lesson, or whose null, sits under a page of run ids.
- A post that says more than the page it links.
- "Green" read from an earlier head.
---
+4
View File
@@ -51,6 +51,10 @@ tested. `none` means the lane looked for each of these and found none. A missing
asked for as a follow-up message: it never holds a PR out of a train, does not stale
READYs sent before the line existed, and needs no new `ready` or /ship run.
Every number, "green" and "ready" in the block names where it came from (a run id, a commit,
a command) and is read at the pinned head; anything carried over from an earlier head goes
under `Unverified:` until it is re-read ([ETHOS.md: write-up checklist](../../ETHOS.md#write-up-checklist)).
Optional lines a crew's rules file may require:
```text
+1
View File
@@ -0,0 +1 @@
- **A short write-up checklist in ETHOS.md.** Explain the Number now ends with three checks before a post or write-up goes out: its words match the page it links, every number, "green" and "ready" names its source and is read at the current head, and a fresh model reads it cold once. The READY template in `captain/templates/READY.md` points to the second check. Anything carried over from an earlier head goes under `Unverified:` until it is re-read.