From bcbda0f2f0acca7ad5bbffc92ea6a97668197b46 Mon Sep 17 00:00:00 2001 From: Marius1311 Date: Wed, 21 Oct 2026 11:33:49 +0200 Subject: [PATCH] Task path: analysis/// Co-Authored-By: Claude Opus 5.5 --- {{cookiecutter.project_name}}/.gitignore | 2 +- {{cookiecutter.project_name}}/REVIEW_GUIDE.md | 12 ++++++------ 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/{{cookiecutter.project_name}}/.gitignore b/{{cookiecutter.project_name}}/.gitignore index e0645da..71da4a7 100644 --- a/{{cookiecutter.project_name}}/.gitignore +++ b/{{cookiecutter.project_name}}/.gitignore @@ -159,7 +159,7 @@ data/** !data/**/.gitkeep # Directories to ignore. Unanchored, so they also match inside every analysis task directory -# (analysis//.../_vN/): the untracked half of a task, anchored to the main checkout. +# (analysis///.../_vN/): the untracked half of a task, anchored to the main checkout. **/figures/* !/figures/.gitkeep outputs/ diff --git a/{{cookiecutter.project_name}}/REVIEW_GUIDE.md b/{{cookiecutter.project_name}}/REVIEW_GUIDE.md index 434eed2..c80850e 100644 --- a/{{cookiecutter.project_name}}/REVIEW_GUIDE.md +++ b/{{cookiecutter.project_name}}/REVIEW_GUIDE.md @@ -39,12 +39,12 @@ README's `Write-back` section is the only trace. The right subdirectory is not g ### 3. The task contract -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. 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. +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. 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.