Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions {{cookiecutter.project_name}}/REVIEW_GUIDE.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,8 +41,10 @@ README's `Write-back` section is the only trace. The right subdirectory is not g

Agent work belongs in a task directory `analysis/<topic>/.../<name>_vN/`. Check that its README's content is real:
the actual input files, the deliverables agreed with the human, a short summary of each PR. An edit to an earlier
task's directory is a finding: analysis moves forward, and a new version names the one it follows. Writes to
`data/<dataset>/results/` or the central `figures/` are the human lane and are a finding.
task's directory is a finding: analysis moves forward, and a new version names the one it follows. A task is one
branch merged through one or more PRs, so a directory whose earlier PRs (its README lists them) came from this PR's
branch is this task's own, not an earlier one. Writes to `data/<dataset>/results/` or the central `figures/` are the
human lane and are a finding.

Every key committed to a shared object carries the task's version suffix **and** appears in that README: an
unrecorded key can't be traced back, an unsuffixed one collides with the next version.
Expand Down
Loading