The mission, in one line.
Give a stateless model durable, verified contact with state and range.
A model forgets everything between sessions, and it cannot reach past its own window to check what is true. Telos is the engine that gives it both. A durable hold on state it can return to. Reach across a surface far larger than one window. And, the load-bearing word, a way to verify that contact rather than trust it. Everything on this page is built on that one idea.
Three flagships. Peers, built to compose.
Each one stands alone and runs on its own, with its own focused purpose. They are easily compatible, and together they are the larger project. Telos takes the stage because it is the most groundbreaking of the three, not because it outranks them.
The atlas: every release, and where it sits.
The whole body of work, mapped by its role. The three flagships lead. Under them sit the meatier substrates they plug into. Under those, the small sharp tools, the bricks. The full grouped catalog lives on Flagships.
Flagships the three that lead
Secondary substrates the meatier repositories that plug in
Bricks small, sharp, composable tools
The release and provenance tools, the agent tools, and the kernels. Each is a small utility you can adopt on its own. The shipping discipline behind them is the release toolkit.
Wherever someone hands work to a model, or hands a model's work to someone else, the same gap opens: you cannot see what it saw, and you cannot check what it claims. The same gap, in a clinic, a courtroom, a newsroom, an audit, a repo. Here is what closing it looks like.
Radiology.
Your codebase.
Newsroom.
The honest version of who’s behind it: I’m not really a programmer. I think in systems, and fast, a brainstormer who throws off more ideas than he can keep track of, ideas that won’t sit still or keep themselves honest on their own. So the first thing this harness ever held was me. I built the discipline I needed for my own head, and only later noticed it worked on everything else. There’s no computer-science degree behind any of it. My path ran through eleven years of commercial arboriculture in the family business, a contract diagnosing Xbox Live networking, then a long, largely private sprint across compilers, real-time graphics, color science, security, and AI accountability, the offensive side and the defensive one, because you learn how a system holds by learning how it breaks. With no institution to vouch for me, I learned early to let the work answer for itself or go unread. Independent since 2023, out of Seattle.
The closest title is forward-deployed systems architect, turned around. Not embedding with a customer to build on a platform that’s already there, but going onto the platform that isn’t there yet, the accountable layer the rest of this will one day stand on.
One standard runs under all of it, and it’s the one I’m asking you to hold me to: judge the action, never the worth of who took it. That is the only thing that lets a thing be wrong without being worthless, the only thing that lets the fool become the scholar.
That’s the short version. The longer one, how this actually came to be, who it’s really for, and the person still working it out, is its own page now, kept apart on purpose so the work never leans on it. The person behind it →
Contact.
For collaboration, evaluation, or the long argument, reach me directly. No funnels; no forms pretending to be people.