Build Log
ForgeKit v2 — the loop made visible
June 26, 2026
Instead of building a better OS, we asked what the OS looks like when someone else holds it. The answer was a three-file Markdown instrument. Then we ran it on a real task — Flyback source research — and it worked on the first try.
Timeline
What shipped
loop-runner/instrument/README.md — what the instrument is, how to use it, the one rule (Evidence ≠ Judgment)
loop-runner/instrument/SESSION_TEMPLATE.md — Shape / Run / Close structure with ARTIFACT section as the exit gate
loop-runner/instrument/EXAMPLE_SESSION.md — worked example of the instrument running on its own creation
loop-runner/instrument/sessions/dogfood_session.md — first real dogfood session: Flyback source expansion research
Flyback source research artifact — 7 sources evaluated, OGRIP/OSIP as best near-term, USGS EarthExplorer as best long-term, ODOT as most interesting Ohio-specific
Next.js scaffold at loop-runner/ — parked, not deleted. Future shell when the instrument earns its UI.
“The Markdown instrument tests whether the loop is useful at all. The app tests whether useful software can be built around it. Second question must come after the first.”