← graph

submission-readiness-audit

Submission readiness audit: Google.org application due TODAY

Metadata

Statusdone
Assignedagent-29
Agent identity3184716484e6f0ea08bb13539daf07686ee79d440505f1fdf2de0357707034c3
Created2026-05-01T18:35:38.670818853+00:00
Started2026-05-01T18:36:14.412458570+00:00
Completed2026-05-01T18:42:20.201520752+00:00
Tagsgrant,urgent, eval-scheduled
Eval score0.84
└ blocking impact0.90
└ completeness0.78
└ coordination overhead0.87
└ correctness0.85
└ downstream usability0.84
└ efficiency0.88
└ intent fidelity0.82
└ style adherence0.90

Description

Description

The Google.org Impact Challenge application is due May 1, 2026 (TODAY). The coordinator has no current visibility into where the application stands. Audit submission readiness immediately and produce a precise punch list.

What to do

  1. Read workgraph_google_application_FINAL_v2.md (the canonical v2 application).
  2. Read STATE.md §1 and §3 to see what was last recorded as outstanding for the application workstream.
  3. For EVERY question in the application:
    • Confirm an answer exists.
    • Count words and compare against the limits documented in CLAUDE.md (75 / 100 / 150 / 200 word caps per section; specifics in CLAUDE.md 'Word Limits' subsection).
    • Flag any section that is over limit, empty, marked TODO/TBD, or contains placeholder text.
  4. Check the budget table sums to $1,500,000 across the four categories ($900k / $300k / $150k / $150k).
  5. Check the team is presented as Erik / Luca / Vaughn in that order, no 'PI' language, no specific effort percentages.
  6. Check no stale v1 references survive: KRAS, MRTX1133, pancreatic cancer, Boltz, RFdiffusion, DiffDock, the 'wrote this proposal with WorkGraph' recursion claim, or attribution of CRISPRme directly collaborating with the Casgevy developer.
  7. Check no em-dashes (style rule).
  8. List anything Erik must do himself before submission: form fields that need his name/signature/contact info, attachments to upload, accounts to log into, or LoS still to gather.

Output

Write findings to .wg/submission-audit-20260501.md with three sections:

  • READY — sections confirmed submission-ready
  • MUST FIX BEFORE SUBMIT — blocking issues with exact section number and fix needed
  • ERIK MUST DO — manual steps only Erik can perform (form submission, account login, attachments)

Also wg log a one-paragraph summary on this task before marking done.

Validation

  • Every section of the application has been checked
  • Word counts verified against CLAUDE.md limits
  • Budget arithmetic verified
  • No v1/KRAS references remain
  • Punch list distinguishes content fixes from Erik-only manual steps
  • Output file written to .wg/submission-audit-20260501.md

Depends on

Required by

Log