Shipping Clio Coder

v0.3.7 went out on August 24. I am working on typed dispatch intent and host-run verification, live worker views in the terminal, user-programmable verifiers for other languages and toolchains, and the eval track that keeps a 20B local model honest. Install it with npm and tell me what breaks.

The Clio Coder story Repository

Holding the CLIO architecture together

Core, Kit, Agent, Relay, and the terminal front end are moving at different speeds and are owned by different people on the team. My job is the contracts between them: what is durable, what can be discovered, what needs a receipt, and where a person must approve.

The CLIO story

Opening more of my private prototypes

Protoneo, Argus, ctx-rm, AutoTLDR, ClaimTree, Notient, and the agentic survey harness have been private experiments. I am cleaning them up for public release now that this site can hold their stories.

The project atlas

Mentoring through real systems

The most useful mentoring happens when a student owns a consequential piece of the work. Right now that means CLIO components with real users and real release pressure.

How I work with people

Open questions

What I am turning over

  1. How strong does the harness have to be before a 20B model on one GPU is genuinely useful for scientific software?
  2. Which parts of an agent's receipt must be sealed at runtime, and which can be reconstructed afterwards?
  3. What is the smallest typed contract between an orchestrator and a worker that still lets the worker fail loudly?

Recent changes

The notebook moves

Dates make staleness visible. They also make returning worthwhile.

  1. Relaunched this site as an editorial studio with CLIO and Clio Coder at the center.
  2. Released Clio Coder v0.3.7 with typed dispatch intent, host-run verification, fleet contract v5, and council mode.
  3. Published Clio Coder to npm as @iowarp/clio-coder.
  4. Started Clio Coder.