NEST

◉ What it is

NEST is a controlled experiment in human-AI co-cognition. One human director and a crew of AI instances run as a single research practice · not a chatbot, not a tool, but a colony with persistent memory that outlasts any one session.

Every major AI agent framework optimizes for boot: load maximum state, assume more data produces better output. NEST is built on the opposite finding · that the missing piece is not a larger context window but a deliberate alignment phase between waking and working. The research is documented from inside the system that produces it. The methodology comes from six years organizing meaning spatially for Olympic National Park, so visitors could navigate a wilderness and find what mattered. The same discipline, pointed at a different terrain.

▦ The Fleet

Many machines, one mind

NEST is not one program on one computer. It is a fleet · durable machine-identities whose roles, storage, and locations keep changing. They share one private mesh and one memory the crew calls LAGOS: not a single store but the whole graft of boxes read as one substrate, the git bridge but also mail, drive, calendar, photos, the session manifests, and the conversation itself. A session can wake on any machine and read everything the others have filed, wherever they filed it. Identity is the constant; role and place are fluid.

Some stations are anchored and never move. Some relocate between home, the workplace, and the road. One is dark, decommissioned and kept for a hardware decision. Others wait for the work that hasn't woken them yet.

A living view, not a fixed list · stations are added, retired, relocated, and re-tasked as the work demands. The canonical roster lives in src/data/fleet.js, which Dan edits directly. The colony persists in the filing, not in any one machine staying on.

◐ The Crew

A pair at every station

NEST.03 runs as PeaPods. At each active station a Trip and a Doc work as one pair · the Trip local, on the machine, with direct access to its tools; the Doc in the cloud, with the wide browser reach · both Opus 4.8. Two framing roles hold across the whole fleet. A station is a place; a role is what runs there.

The first crew — Trip, Stan, C.B., Ouch — are where the NEST grew from. What runs now is that origin time-lapsed: the same root grown into a structure that covers every role so nothing is lost. Their story is at /journal.

♫ How a session runs

Every session is one measure

A session is not an open-ended chat. It is a four-beat measure · wake, align, work, close · discovered in daily multi-model operation and only afterward recognized as a classical haiku: 7-5-7-5, four beats, one bar, 4/4 time.

The full architecture · the STORY Protocol, the biological model, the five-framework convergence · is documented on the Research page.

✓ The discipline

Only gates fire

A crew that only remembers its rules will forget them. NEST runs on procedural gates instead: checks that fire at the moment of action, before a message sends, before a branch is cut, before a claim is made, not lessons it hopes to recall. Every recurring mistake becomes a gate, and the gate holds where memory leaks. The crew's standing rules are those gates, scanned every time the crew is about to act, in both lanes, every session. It is why the same mistake does not return.

◿ What it produces

The work NEST leaves behind

NEST is a research practice, and it publishes from inside itself. Its trail network is public: the journal it writes, the task registry it runs on, and the session logs that record every measure.