← graph

v3-1-fanout-assemble

v3.1 fanout assemble: apply all fix specs to v3 → workgraph_google_application_FINAL_v3_1.md

Metadata

Statusdone
Assignedagent-201
Agent identity3184716484e6f0ea08bb13539daf07686ee79d440505f1fdf2de0357707034c3
Created2026-05-01T23:26:58.859060772+00:00
Started2026-05-02T00:10:46.055886645+00:00
Completed2026-05-02T00:25:03.651615172+00:00
Tagsgrant,urgent,v3,assemble, eval-scheduled
Eval score0.73
└ blocking impact0.70
└ completeness0.75
└ constraint fidelity0.70
└ coordination overhead0.70
└ correctness0.70
└ downstream usability0.65
└ efficiency0.75
└ intent fidelity0.89
└ style adherence0.90

Description

Description

The 12 per-criticism fix tasks have produced structured fix specs in ~/poietic.life/notes/v3-fixes/fix-*.md. This task applies them deterministically to v3 to produce v3.1.

What to read

  1. ALL fix specs in ~/poietic.life/notes/v3-fixes/:
    • fix-m1.md, fix-m2.md
    • fix-h1.md through fix-h7.md
    • fix-w1.md (the big one — likely multi-section)
    • fix-divergent-29.md (two options — pick the 'keep-honest' version unless its rationale is weak)
    • fix-optional-bundle.md (apply ALL polish items)
  2. workgraph_google_application_FINAL_v3.md at commit 70c8e7f on worktree wg/agent-77/v3-assemble-stitch. Use git show 70c8e7f:workgraph_google_application_FINAL_v3.md.
  3. ~/poietic.life/notes/v3-review-synthesis-20260501.md (for context if a fix spec is ambiguous)
  4. CLAUDE.md word limits

What to do

  1. Construct workgraph_google_application_FINAL_v3_1.md at project root from v3 + fix specs.
  2. Apply each fix spec's before→after replacement. If two specs touch the same section, integrate them carefully (likely fix-w1 + a smaller H/O fix in the same section — fix-w1 takes priority on structural changes; smaller fixes apply on top).
  3. Recount EVERY section's word count against CLAUDE.md word limits.
  4. Style sweep: no em-dashes, no PI/lead PI, founder order Erik / Luca / Vaughn, no v1 terms (KRAS, MRTX1133, pancreatic, Boltz, RFdiffusion, DiffDock), no 'wrote this proposal with WorkGraph' recursion claim, CRISPRme/Casgevy precise, DNA-Diffusion not in funded scope.
  5. Confirm budget sums to $1,500,000.
  6. Confirm Liverpool ack (§28 with H3 architectural divergence sentence).
  7. Confirm §30 'reviewers want science deliverable' risk preserved.
  8. Do NOT overwrite v2 or v3.

Output

  1. workgraph_google_application_FINAL_v3_1.md at project root.
  2. ~/poietic.life/notes/v3-1-fanout-assembly-summary-20260501.md (under 800w):
    • Table mapping each criticism (M1, M2, H1-H7, W1, divergent, O1-O5) to the section(s) edited and the result
    • Section-by-section final word counts
    • Any conflicts between fix specs and how they were resolved
    • Any TODOs left for Erik (M4 GitHub admin, §42/§47 form verification, etc.)
    • One paragraph 'how to choose v2 vs v3 vs v3.1' for Erik

wg log a one-paragraph summary.

Constraints

  • HARD: every word cap respected. Recount.
  • HARD: do NOT overwrite v2 or v3.
  • HARD: every fix spec listed above is applied (or the summary explains why one was deferred).
  • HARD: style sweep complete.
  • SOFT: when fix specs conflict, prefer the larger structural fix (fix-w1) and apply smaller fixes on top.

Validation

  • All 12 fix specs read
  • Each criticism mapped to a v3.1 edit (or explicit defer reason)
  • Every word cap respected (recount)
  • Budget sums to $1.5M
  • v2 and v3 untouched
  • No em-dashes, no PI, no v1, no recursion, no DNA-Diffusion-in-scope
  • CRISPRme/Casgevy framing precise
  • workgraph_google_application_FINAL_v3_1.md at project root
  • Summary at ~/poietic.life/notes/v3-1-fanout-assembly-summary-YYYYMMDD.md
  • Committed on worktree branch (not pushed)

Depends on

Required by

Log