Hackathon build, 2026

Unread

A reader that will not let you move on until you have shown you understood the last part.

Problem: The hackathon theme was friction, where the obvious move is to remove it. Summaries have made it trivial to finish an article without reading it, and nothing in the tooling can tell having read something apart from having skimmed a summary of it.
What we built: An article becomes a locked reading room. One section opens, and the next stays shut until the reader puts the claim in their own words at a checkpoint, with the model pushing back on a vague answer rather than giving the point away. The completion report is built from what the reader proved, not from what the article said. Friction is the product here rather than a feature bolted onto one, which is the whole argument.
My part: I built the light and dark theme support across the app, replacing hardcoded colours with theme-aware variables on every page.
Result: Deployed and open to try, with a public reading room and author-side analytics on top of the checkpoints.
Stack: TanStack Start, React, TypeScript, Claude API