The Keel Register

Revision 1Issued August 2026

A record of what has been built under the Keel name, what is building now, and what was lost for want of somewhere to build it.

1Registered
3On the ways
4Lost

The register

8 entries
VesselYearWorkClass

Registered1 entry

Reachable, and standing under the name. A thing is registered when a stranger can use it without being introduced to its author first.

01crucible202626 testsRegisteredA deterministic simplicity engine for Rust. Ranks a codebase against itself and refuses to grade it.

On the ways3 entries

Under construction. A hull on the ways is not a ship and is not counted as one.

02canopy2026390 commitsOn the waysA visual instrument for working on real codebases.
03ouros202696 commitsOn the waysAI governance framework.
04master-of-none202612 commitsOn the waysA Macro-MoE. Routes to small local specialists instead of one general model.

Lost4 entries

Begun in earnest, then abandoned. The bar is how long each stayed alive, and the descriptions are the ones their own readmes gave them. Only self-directed work is entered here; commissions are somebody else’s ship. None of it died of bad code.

05IL2+ chat app2026112 commitsLostSelf-hosted chat cleared for IL2+ workloads. Rust and Axum, Leptos on the front, Postgres in-cluster.4 days
06purple-range202648 commitsLostA self-hostable purple-team wargame range. Live network map, red and blue operations, an optional agent attack plane.20 days
07forge20268 commitsLostA personal AI workspace. Capture every idea, ask a model that already knows your context, keep projects and tasks in order.8 days
08cider-remote20268 commitsLostA remote control for Cider, the Apple Music client.died the day it began

What the register provides

  1. A name to release under, until you have one of your own.
  2. Partners. Post what you are building and what you are short of. Engineering, security, business, growth, design.
  3. Release. When you outgrow the register you leave and take the work with you. That is the design, not a consolation.

What registration requires

  1. Ship. Any size, but real.
  2. Work in channels. If it happened in a direct message it did not happen.
  3. Answer when asked. Ten minutes from you is a day off someone's week.
  4. Say when you are out. Leaving is fine. Vanishing is not.

What the register is not

Not a hangout. No levels, no memes channel, no bots to poke at.

Not a course. Nobody here is selling anything.

Not open. However you arrived, two stewards read your application before you are admitted.

Application for a berth

  1. What you build, and one thing you actually finished.
  2. What you are working on now, and what you are short of.
  3. How you found the register. Name the person, if someone sent you.
Apply for a berth

Sixteen and over. Read for whether you build, not for polish. You will hear back either way, including no.

I opened this register because I kept building things nobody ever saw. The last four entries are mine. Every one is a thing I meant to finish, and not one died because the code was bad. They died because there was nowhere to put them and nobody to answer to.

If that reads familiar, the berths are open.

O. Murphy · Keeper