v3-review-link

v3 review: link verification (mechanical web fetches)

Metadata

Statusdone
Assignedagent-98
Agent identity3184716484e6f0ea08bb13539daf07686ee79d440505f1fdf2de0357707034c3
Created2026-05-01T22:09:13.210638417+00:00
Started2026-05-01T22:12:11.518833675+00:00
Completed2026-05-01T22:17:46.760289256+00:00
Tagsgrant,urgent,review,v3,link-verification, eval-scheduled
Eval score0.86
└ blocking impact0.95
└ completeness0.85
└ constraint fidelity0.85
└ coordination overhead0.90
└ correctness0.90
└ downstream usability0.88
└ efficiency0.85
└ intent fidelity0.92
└ style adherence0.90

Description

Description

Mechanical fact-checking pass on every URL referenced in workgraph_google_application_FINAL_v3.md. Output is shared input for the four parallel reviewers (positive / skeptical / hostile / domain-expert) and the synthesizer.

This is not opinion. It's: does the URL resolve? Does the destination match what the application implies?

What to read

workgraph_google_application_FINAL_v3.md at commit 70c8e7f on worktree branch wg/agent-77/v3-assemble-stitch. Use git show 70c8e7f:workgraph_google_application_FINAL_v3.md to read it.

What to do

  1. Extract every URL from v3.
  2. For each URL, use WebFetch:
    • Status: 200 / 3xx / 404 / dead / parked / paywalled?
    • Content match: does the destination support what v3 implies? Or is it weaker, stale, irrelevant, embarrassing?
  3. Specific URLs to check at minimum (find more by reading v3):
    • poietic.life — landing page deliver on v3 framing? Public benefit statement present? Founder bios consistent?
    • github.com/orgs/poietic-pbc — repos visible? Look credible? Anything stale (the deep-research-competition KRAS scaffold)?
    • github.com/graphwork/workgraph — actively developed? README delivers what v3 implies? Recent commits?
    • graphwork.github.io — docs site loads? Substantive?
    • All cited paper DOIs, arXiv links, PubMed links, journal URLs — resolve to the right paper?
    • Any other URL in the application

Output

Write ~/poietic.life/notes/v3-link-verification-20260501.md:

A table with columns: URL | HTTP status | Brief summary of what loaded | Match assessment (matches / weaker than implied / mismatch / dead / embarrassing) | Recommended action (none / fix in v3 / fix the destination / replace URL).

Plus a short prose summary at the end: number of URLs checked, number passing, number flagged, biggest concerns.

wg log a one-paragraph summary on this task.

Constraints

  • USE WebFetch. Do not assume.
  • Be precise. 'matches' means the destination really supports the application's claim, not just 'page loads.'
  • No em-dashes.

Validation

  • Every URL in v3 extracted and checked
  • Each URL has a status, summary, match assessment, action recommendation
  • poietic.life, graphwork.github.io, all GitHub repos checked
  • All cited paper links resolved
  • Output at ~/poietic.life/notes/v3-link-verification-YYYYMMDD.md

Depends on

Required by

Log