Regular case · derived from the record · Content
3 merges over 1 days on the blog surface, #2407 to #2415. Arc 16 of 136 by length.
The arc, on its own days
The surface's whole history, this arc's weeks in indigo
75 merges on blog in the corpus; this arc is 3 of them.
Blog cover: film the leaking feature, not a title card
#2407 · 2026-09-19 · feature
Blog: fix the broken hero and the day-early date on the erratum post
#2414 · 2026-09-20 · bugfix
Blog dates: fix the four early-morning stamps, and drop the guard's allowlist
#2415 · 2026-09-20 · 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-05-20
2 merges · 2026-06-08
2 merges · 2026-06-08
3 merges · 2026-06-11
2 merges · 2026-06-21
2 merges · 2026-06-29 to 2026-07-01
3 merges · 2026-07-21 to 2026-07-28
www.jakelawrence.xyz/research/case-study-library/arc/2407
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 →