Thoughts
Short notes, fragments, and pieces published elsewhere.
-
Routing model choice by surface
· spine.argonode.studio
How we use Opus, Sonnet, and Haiku in one product. The shipping question is not "can we use Opus?" - it is "where does Opus actually pay ...
-
Why a novel deserves a git log
· spine.argonode.studio
A literary critic's mental model and a senior engineer's mental model are the same shape. Spine makes that shape visible.
-
On agents bidding on tenders
· x.com
A thread on Agenlon - the orchestration layer I'm exploring where specialised agents bid for work in a competitive marketplace, with repu...
Currently tinkering with
Active exploration threads (recent first).
Recent projects
-
Rodyr - Ody
Ody is Rodyr's flagship product - the skills runtime for AI-native companies. It observes how a team actually works (coding sessions, Slack threads, pull requests, calls), distills the stable parts of that graph into versioned, agent-callable Skills with typed inputs and an evidence trail, and learns from every run. Same artifact, three audiences - an MCP tool any agent invokes, a CLI any human runs, and a procedure any new hire follows. Internal benchmarks show agent-with-Ody beating agent-alone on real engineering tasks.
Visit Ody -
Argonode Studio
A small studio building instruments for working writers, editors, and manuscript holders - tools that carry the operational weight without taking the voice. Home for Spine and a growing line of writer-focused craft software. Visit at argonode.studio.
Visit Argonode Studio -
Spine
Treats a manuscript like a codebase - scenes are commits, plotlines are branches, characters are contributors with line-level blame. Subplots branch off main, weave back together at merges, or quietly die in the margins, visibly. Built under Argonode Studio with Senem Dilli.
Quick profile
I've been building things between hardware and software for the last 8 years. The first few were spent designing embedded systems, building an electric supercar, retrofitting classic sports cars, and developing futuristic HMIs. These days I'm more focused on interfacing with knowledge in all its forms, especially through AI - building Ody, a knowledge runtime for teams; and Spine, an IDE for literary editors and publishing houses. Every so often, external consulting for Applied AI and rapid prototyping.