Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Phase 01 — Tighten real-vs-synthetic prose and finalize cross-modality framing

Working tree

Repository root. All edits under article/sections/. This phase is independent — it can run first (immediate value) or as a final consistency pass. It owns results.tex and the synthetic-data wording in methods.tex; it must not touch supplementary_figures.tex (Phase 03’s captions), discussion.tex Limitations (Phases 02/05), or bio/*.tex (Phase 05). If Phase 04 has already landed its methods.tex subsection, git pull/rebase article/ before editing methods.tex.

Goal

Every sentence in the manuscript body that touches benchmark or federation evidence makes an honest, unambiguous claim: production results are called production, synthetic results are called synthetic, and federation correctness (real, CF03) is never conflated with federation latency (synthetic, CF15). The cross-modality claim reads as a capability with a cited example, not a completed demonstration.

Why this matters now

The review flagged that the manuscript’s credibility rests on the real/synthetic boundary being airtight. One concrete defect remains: the “Scaling and performance” and federation sections describe the production query path (CF05) and the summary-only federation equivalence (CF03) — both real — in proximity to synthetic scaling/federation controls, without a sentence that fences the two. The strongest quantitative claim in the paper (federation matches centralised computation to numerical precision) must not be tainted by association with the synthetic latency panels. The cross-modality paragraph added in the prior session is correct but should be cross-checked for consistency with the abstract/intro wording.

Out of scope

  • Regenerating any figure or changing any figure caption (that is Phase 03).
  • Editing the Limitations list (Phases 02 and 05 own their bullets).
  • Touching biology numerals or bio/*.tex (Phase 05).
  • Adding the import/export Methods subsection (Phase 04).
  • Any change that alters a numeral — this phase is wording only.

Plan

  1. Read article/sections/results.tex §“Data-minimising federated meta-analysis” and §“Scaling and performance”. Add one sentence (in the federation subsection) that explicitly states: the federation correctness/equivalence result (CF03 D–G) is from production-cache replay, whereas networked federation latency is characterised only by the labelled synthetic supplement (CF15) and is not production evidence.
  2. In results.tex, audit every use of “benchmark”, “scaling”, “performance”: confirm each points at the right evidence class (CF05 = live; CF14/CF16/CF04/CF11 = synthetic supplement). Fix any sentence that implies a synthetic supplement is production.
  3. In article/sections/methods.tex §“Synthetic data generation” and §“Benchmark configuration”: confirm the wording already scopes synthetic benchmarks as supplements; tighten any sentence that could be read as describing production data. Do not add new subsections.
  4. Cross-check the abstract (sections/abstract.tex) and sections/main.tex for the phrase “imaging modality”: ensure the cross-modality claim is stated as a platform capability, consistent with the Discussion “Cross-modality integration” paragraph (capability + cited example + per-spine ingestion as near-term). Adjust abstract/intro wording only if it currently over-claims a completed cross-modality result.
  5. Build gate: cd article && lualatex -interaction=nonstopmode -halt-on-error --shell-escape SynDB_Manuscript.tex (×2). Confirm 0 errors, 0 undefined refs, page count unchanged ±1.
  6. Commit (signed) with a message scoped to “prose: real/synthetic and federation correctness/latency separation”.

Acceptance criteria

  • A sentence in results.tex federation subsection explicitly separates federation correctness (CF03, production-cache) from federation latency (CF15, synthetic) — verifiable by grep for both fig:federation_accuracy and fig:benchmark_systems_supplement in adjacent prose.
  • No sentence in results.tex/methods.tex describes CF04, CF11, CF14, CF15, or CF16 as production/live data.
  • Abstract + intro state cross-modality as a capability, not a completed result (no claim of a cross-modality measurement comparison in the abstract).
  • lualatex ×2 exits 0 with 0 undefined refs; page count within ±1 of 38.
  • No numeral changed in this phase (diff contains only prose).

Files likely touched

  • article/sections/results.tex — federation framing sentence; benchmark wording.
  • article/sections/methods.tex — synthetic-data wording (no new subsection).
  • article/sections/abstract.tex — cross-modality wording (only if over-claiming).
  • article/sections/main.tex — intro cross-modality wording (only if over-claiming).

Pitfalls

  • Symptom: build breaks with “Undefined control sequence” after editing. Cause: accidental deletion of a \cref/macro mid-sentence. Recovery: git diff the section; restore the macro.
  • Symptom: merge conflict on methods.tex. Cause: Phase 04 already added its import/export subsection. Recovery: rebase article/; your edits are in different paragraphs — re-apply.
  • Anti-pattern: “improving” the science wording into new claims. This phase removes over-claims; it does not add claims.

Reference

  • Gap inventory item 4-note (“separate federation correctness from latency”).
  • article/NARRATIVE_AUDIT.md (real/synthetic figure classification).
  • Discussion “Cross-modality integration” paragraph (the consistency target).