← graph

manuscript-revision-02-operating

Manuscript revision 02: operating rules for wg fanout and cluster jobs

Metadata

Statusdone
Assignedagent-2460
Agent identity3577bc75d6ed4f1947509aa5c086c91ce7c997c7806dab6bf6affac647452647
Created2026-06-17T14:43:26.053910279+00:00
Started2026-06-17T15:18:53.154568758+00:00
Completed2026-06-17T15:21:04.095397039+00:00
Tagseval-scheduled
Eval score0.95
└ blocking impact0.97
└ completeness0.95
└ constraint fidelity0.70
└ coordination overhead0.90
└ correctness0.97
└ downstream usability0.95
└ efficiency0.91
└ intent fidelity0.81
└ style adherence0.96

Description

Create the operating rules that all downstream manuscript-revision workers must follow. This is a coordination artifact, not a manuscript edit.

The rules must state explicitly:

  • Workers are authorized to create their own wg subtasks when a task naturally decomposes into data discovery, script writing, Slurm submission, job polling, result validation, and synthesis.
  • For larger data processing, workers should prefer workgraph subtasks over monolithic hidden work. Subtasks should have clear artifacts and dependencies.
  • Workers may submit Slurm jobs as needed on compute/tux nodes, but must not run heavy matrix scans, large RDS loads, or multi-core compute on the head node.
  • Workers must log Slurm job IDs, commands, resource requests, stdout/stderr paths, and output artifacts.
  • Judgment tasks still must not silently edit manuscript claims; they should create decision records with author-decision points.
  • Mechanical tasks may propose exact patches, but integration happens in a later fan-in task unless the task explicitly says it can edit.

Write paper_prep/manuscript_revision/02_operating_rules.md and register it with wg artifact.

Validation

  • Artifact exists
  • Explicitly authorizes child wg tasks for complex analyses
  • Defines Slurm logging requirements
  • Repeats head-node safety constraints
  • Preserves J-task decision-record rule

Depends on

Required by

Log