Trust Boundary
Maps where untrusted input enters a codebase, for the new engineer who's about to touch it. Built for Pair Programmer's Apprentice — use lumen forge to build a tool for developers who are new to a codebase. Entry-point detection across HTTP handlers and queue consumers. The interface is deliberately narrow: one path, done properly, rather than a broad surface that half-works at the deadline.
Gallery
Screens
Trust Boundary — main view
Trust Boundary — result state
On the clock
What shipped, what didn't
Completed in time
Entry-point detection across HTTP handlers and queue consumers.
Unfinished / faked
No taint tracking — it finds doors, not paths.
Obstacles
Lost four minutes to an auth redirect loop that turned out to be a trailing slash.
Lessons learned
Test the demo path once at minute 25. I didn't, and it showed.
Process
Prompting approach
Started from a single system prompt describing the user and their constraint, then iterated with the assistant on the Trust Boundary data model before writing any interface code. Full prompt log is in the repository under /prompts.
Fairness
Disclosures
Declared by the builder at submission time, visible to judges before scoring.
Started from the official framework starter template, unmodified.
Judging
Public feedback
Judges' private notes stay private — this is what they chose to say publicly.
Elena Voss
VP of Engineering, Harbor Compute
Solid build with a clear user in mind. The interface is doing less than it could — a second pass on hierarchy would lift this considerably.
Marcus Bell
Founder, Bellwether Studio
The idea is strong and the execution is most of the way there. The demo path broke once, which is what separates this from the top three today.
Hana Kobayashi
Principal Research Engineer, Independent
Solid build with a clear user in mind. The interface is doing less than it could — a second pass on hierarchy would lift this considerably.
Discussion
0 comments
No comments yet.