diff --git a/CLAUDE.md b/CLAUDE.md index 98696c1..23524c6 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -25,7 +25,7 @@ Don't narrate the transition in a doc ("this used to be X"); write the current s ## Conventions - **Wrap runs in duct.** Every run should carry con/duct usage/resource logs alongside its outputs; `con-duct` is a dependency of every campaign environment. - The wiring is tracked, not yet built: duct-wrapping each `iterate` step is #53, and duct inside the babs jobs is #16 (tracks `PennLINC/babs#356`). + Every recorded transition is wrapped by `dispatch()`, so a new recorded verb gets it for free; duct inside the babs jobs is #16 (tracks `PennLINC/babs#356`). - **No untracked-local paths in upstream-facing stuff** (issues, tracked docs). A gitignored path means nothing to a reader on GitHub — **strip the path, keep the intent** (e.g. "the resample question in our fmriprep meeting notes is stale", not the path); remove it at filing time. - **Configs are the user's, never the tool's.** `examples/` are starters to copy; real site paths never land there, and nothing in the package resolves a config by name. diff --git a/docs/interventions.md b/docs/interventions.md index 7d0d23c..7ace5c0 100644 --- a/docs/interventions.md +++ b/docs/interventions.md @@ -19,6 +19,18 @@ Nothing is written; the flag is this iterate's reading of babs's live counts, an `mechababs status` shows the cell as `FAILED`, and `mechababs jobs --failed` lists each failed job with its subject, SLURM id, and the directory its logs are in. Read the log, decide what happened, then pick one of the two repairs below. +A transition itself can also fail or refuse: a `babs init` that dies partway, a member study whose lock copy is behind the superstudy's, a recorded command rerun by hand against a cell that has moved on. +The `datalad run` then saves nothing, and the con/duct records of the attempt are left untracked in the campaign dir's `duct//`, so the next `iterate` refuses to start on the dirty study until you have looked. +Its `stderr` and `stdout` files hold what the transition printed; `info.json` holds its exit code, wall time and peak memory. +Keep them, so the study records that the attempt happened, or delete them; either way the reconciler resumes. + +```bash +datalad save -r -d . -m "duct records of the refused scaffold" .mechababs/campaigns/