*nods* narphorium.com/blog/decision…

Ha! Yeah, I can see it. Cozy retro vibes

Jev can't reason. So I built an interpreter that reasons for it. It runs a logic language where the facts and rules are plain English.

really enjoying this setup for syntopic reading with Fable

My transparent Creator Micro keys arrived from @work_louder, so now I can make atelier.dev decision points map to physical buttons

Anything can be a walkthrough. It's just a views: walkthrough entry in the Markdown front matter and then every ## Subheading becomes its own step

Atelier walkthroughs can use the Chrome MCP in Claude Code to build UI walkthroughs with live screenshots of the app. Grounding the walkthrough in execution exposes gaps in the implementation that you wouldn’t catch with code review.

You can verify any task on the atelier.dev kanban board and it will automatically build a walkthrough of the acceptance criteria grounded in deep links back into the code that it wrote.

Every time an agent explores your code base it builds up its own mental model of how the code works, and then throws that model away when the session ends. Code walkthroughs turn that model it into a step-by-step guide to bring you up to speed on any part of the system.

I feel like over the years, we've sort of given up documenting our mental models of code and just accepted that everyone who reads the code builds their own model from scratch.