Own the continuity, not the whole stack
Busy39 tried to own too much of the runtime. Studying a smaller orchestration system clarified the next goal: own the continuity.
Lynn Cole / Projects
Software, research projects, repositories, and published work.
Busy39 tried to own too much of the runtime. Studying a smaller orchestration system clarified the next goal: own the continuity.
After OpenClaw, the harder problem is continuity across hours, days and weeks. The opportunity is to let people bring their agents to better tools.
Context shaping is more than delegation: iteration, problem solving, manual rewrites and interfaces designed around people.
Build tools for the inference stack people already use: delightful software, a community and something worth returning to.
Shadow repositories protected project state, until the project’s tooling tried to use them. Moving that state outside the project changed the failure boundary.
A review of Claude Code’s layered context-control machinery: prompts, hidden reminders, tool serialization and parallel permission decisions.
A correct theorem about a narrow multi-agent abstraction does not settle the value of systems with persistent state, tools and fresh environmental feedback.
Copying an existing agent harness can be fast. Discovering and handling its real failure modes is where the engineering time goes.
One of the more interesting problems I’m working through in my coding agent app is scheduling.
Stripping project management down for agents reveals an interesting question: what is the irreducible minimum structure needed for coordinated work?
Python once felt like a doctrine of disciplined predictability. An architectural failure got me thinking about explicit contracts and where rigidity belongs.
A bounded coding evaluation pits BitNet against a smaller Qwen model. The results expose the difference between cooperative language and working code.