Currently occupying RAM
What I’m exploring now.
What I’m building, testing, and trying to understand right now. The stages are honest: building means shipping, experimenting means small runs, exploring means reading and sketching.
Updated
Currently exploring
Questions driving my work right now.
Experiments, questions and technologies currently occupying my brain.
- From specs to execution graphsExperimenting · Turning a specification into work with explicit dependencies, inputs, outputs, and checks before any agent touches it. “The agent will figure it out” is not a plan.
- Coordinating coding agentsExperimenting · Small runs with Gas City routing the work and Beads keeping task state: what is ready, what is blocked, and what counts as evidence that something is done.
- Context that earns its placeExploring · Task-sized context instead of the whole repository by default, including symbol-level code navigation with Serena over MCP.
- Verification beyond “done”Exploring · Verifiable acceptance criteria, regression checks, and what they cost. Reading about affected-only runs and reproducible pipelines; nothing adopted yet.
- Building my own productsBuilding · Lukre, personal finance through WhatsApp, in production. Also this site.
- A publishing flow with a human in the loopExperimenting · Agent-assisted research and writing, with WhatsApp as the channel I want, where a human reviews everything before it goes out.
Building
Turning ideas into real things.
LukreLive
Conversational personal finance through WhatsApp: record an expense in a message, and let deterministic software keep the records, totals and reminders.
Reading / researching
Topics on my mind.
Gas City and Beads, on a small synthetic setup
Research topicSerena for symbol-level code context
Research topicNx project and task graphs (reading, not adopted)
Research topicDagger for reproducible checks (reading, not adopted)
Research topic
Questions I’m thinking about
Good questions lead to better work.
When does a graph solve real coordination, and when is a plain list enough?
Where does orchestration reduce manual coordination, and where does it just create another system to operate?
How little context can a task get and still be done well?
What evidence should closing a task require?
Outside the terminal
Making room to think.
Making room for slower mornings, writing, and a little perspective away from the screen. A calmer brain builds better things.
This page changes as the questions change.