Regular case · derived from the record · Commerce
10 merges over 3 days on the graphmy surface, #212 to #256. Arc 1 of 136 by length.
The arc, on its own days
The surface's whole history, this arc's weeks in indigo
17 merges on graphmy in the corpus; this arc is 10 of them.
Add GraphMy: PDF-to-knowledge-graph pipeline with web UI
#212 · 2026-04-10 · infra
Fix import paths in GraphMy API routes
#215 · 2026-04-10 · bugfix
Fix GraphMy upload failing with "Internal server error" on Vercel
#237 · 2026-04-11 · bugfix
fix(graphmy): restore pdf-parse in production
#239 · 2026-04-11 · bugfix
fix(graphmy): polyfill DOMMatrix/Path2D/ImageData for pdf-parse on Vercel
#241 · 2026-04-11 · bugfix
fix(graphmy): pre-supply pdfjs-dist worker so Vercel uploads succeed
#243 · 2026-04-12 · bugfix
fix(graphmy): unstick d3 loader and fix mobile layout
#245 · 2026-04-12 · bugfix
fix(graphmy): per-stage pipeline runner, sidebar tabs, and mobile viz polish
#246 · 2026-04-12 · bugfix
Fix GraphMy entity extraction and Supabase flush errors
#255 · 2026-04-13 · bugfix
Fix GraphMy extraction timeout on Vercel Hobby plan
#256 · 2026-04-13 · bugfix
What this page is
No one has written this case yet. Everything on this page is derived from the pull-request record by the same deterministic rules as the corpus: a feature or infrastructure merge opens an arc, and bug fixes, refactors, tests, and docs on the same surface within forty-five days follow it. Titles are verbatim from GitHub. Nothing here is a claim beyond the record.
No premier case cites this arc yet. It is a candidate.
2 merges · 2026-07-01
www.jakelawrence.xyz/research/case-study-library/arc/212
Derived at build from the corpus snapshot of 2026-09-20; re-derives on every build. Base /research/case-study-library/arc.
I design and ship AI tools, full-stack apps, and data pipelines — end to end, to production. Tell me the problem in a sentence; I'll give you an honest read on fit within a day.
Work with me →