Blog

Notes from the lab.

What we’re building, the decisions behind it, and what is still rough.

  1. Lumbridge App in its default layout: spaces and agents on the left, three terminal panes, and the changes panel showing a diff on the right.Lumbridge App in its default layout: spaces and agents on the left, three terminal panes, and the changes panel showing a diff on the right.4 minIntroducing LumbridgeThe open engine for agentic organizations: what it is, what state it is in, and when the source opens.
  2. 3 minWhy Apache-2.0We considered a license that banned malicious use and chose plain Apache-2.0. Here is the reasoning.
  3. 3 minOpening all twelve partsAll twelve repositories open together on November 13, 2026. The test each one has to pass, and where the most work is left.
  4. 3 minWhat we are standing onCredit to the projects Lumbridge is built on and learned from: Ubuntu, Rust, GPUI, Ratatui, Herdr, Omarchy and Orca.

Lab notes

Month by month.

What we built each month, what went wrong and what it led to.

  1. One name for every partThe first ten days of November: a second factory, two more Herdr forks, a rename to Lumbridge, and a website that changed three times.
  2. Four websites, three shippedMostly the website: versions two to five in five days. Also our first software factory and our first fork of Herdr.
  3. Seventeen repos in a weekOur first desktop app, a phone companion, a notebook, an editor and the first website, all started in the last week of September.
  4. A refusal emptied the boxOne repository, twenty-nine commits. We made the memory governor read the machine, and a bug stopped every model twice in a day.
  5. A governor for one GPU boxThe oldest commit we can find: a small Rust program that keeps a GPU box from running out of memory. Twelve commits.

Want a gated part early?

Say which part you want and what machines you have. A person replies.