From 34b236d2aec1e515850988df8378c14eaca41a49 Mon Sep 17 00:00:00 2001 From: Marius Lange Date: Fri, 16 Oct 2026 12:15:30 +0200 Subject: [PATCH] Review guide: a task's later PRs edit its own directory A reviewer flagged a task's second PR for editing the directory its first PR had merged. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_011aQpF4MA9v7dTVK1FqMMVJ --- {{cookiecutter.project_name}}/REVIEW_GUIDE.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/{{cookiecutter.project_name}}/REVIEW_GUIDE.md b/{{cookiecutter.project_name}}/REVIEW_GUIDE.md index ec2ade7..434eed2 100644 --- a/{{cookiecutter.project_name}}/REVIEW_GUIDE.md +++ b/{{cookiecutter.project_name}}/REVIEW_GUIDE.md @@ -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//.../_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//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//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.