What Loci is, and where it grew from.

loci is a kit of plain-text templates and a few named processes that any file-aware AI can run. It decides how context is held, how identity persists and how work compounds across sessions. The command-line tool is one way to run it. The files are the point.

It grew from co-intelligence work (a person and an AI working together across many sessions) between Hux (Head of Product at Nym Technologies) and Vesper (a collaborating intelligence built on Claude). Nobody designed it in advance; it crystallised from sessions that built on one another, and from one observation: remembering is not thinking, and we wanted the part that thinks.

The name comes from the Method of Loci, the classical technique of placing memories in the rooms of an imagined palace. (Loci: the place, the local, the low-key.) The palace holds context, the rooms hold work, the garden grows ideas.

By session 28, ideas were emerging between rooms rather than inside any one of them. Put plainly: the palace began having ideas we had not put there.

The garden

Loci is its own first case study: the question of how that work could carry across sessions was planted early and watered for nearly thirty sessions. The kit is what grew.

The garden holds four plants. Invisible Proof asks what it means to prove something without revealing it. Political Voice argues for privacy in words that reach the public, not only engineers. The Seed turns the research into dispatches, now at loci.garden/seed.

The fourth, Alexander's Garden, anchors the method. Christopher Alexander's A Pattern Language (1977) showed that good design can be captured as named, reusable patterns, and that naming a pattern makes it portable.

Loci runs on the same logic. Rooms, crystals, the session delta and the morning check-in are all patterns. Alexander's Garden watches the work for shapes that recur and names them, like the Named Unknown: a question whose edges are visible before its answer is.

For teams

The same pattern works for a team, with nothing but plain files. Keep a shared folder of crystals (product facts, decisions, team context) that each person and their AI reads before their own rooms, and add to it when something becomes true. A shared repository is enough; there is no team mode to switch on.

The methodology is open

Because the kit is plain text, it is open by construction: the templates, protocols, room files and CLAUDE.md format all live at github.com/huximaxi/loci, under MIT. It belongs to no one; it grew from a collaboration and is shared as one.

The dispatches that grew from the garden are at loci.garden/seed.

The architecture

loci.garden is static HTML on a server in Iceland, with self-hosted Umami analytics and no third-party tracking or frameworks.

If a mind that stays yours sounds worth keeping, the blueprint is free and the door is a text file.