The protocol, in the wild.

A junior dev needed to get up to speed on a module he’d never touched. The usual path is senior time — pull up a chair, explain, unblock, repeat — and it burns the better part of a week.

Instead of a lecture, we sliced a work packet straight out of the repo’s .human/ workspace: the Comprehension brief, the Evergreen runbooks for that module, and one active Goal folder.

Not docs to read — a live working context he dropped an agent into and watched run the goal end to end, stopping to ask questions as they came up. He built real, hands-on understanding against real work, no senior hovering.

A non-technical founder wanted to know what we’d been spending hours on. Normally that means stopping the work to reconstruct a status update from memory and the git log.

I didn’t write one. I pointed an agent at the dated Goals/ history and had it summarize the work in the language a founder reads: outcomes, not commit messages.

Because every Goal folder is timestamped and tied to a spec, the summary wasn’t a guess — it was a dated trail of what happened, when. A two-minute pass to tighten the wording, and it went out. Clarity in minutes instead of a meeting.

Two of us carried different halves of a build — I owned the backend and its gotchas; the other half lived in the frontend and the integration, which I know far less well.

Before opening an editor, I wrote a Goal doc with everything I knew going in — constraints, gotchas, locked decisions — and handed it over to be marked up with what they knew.

We caught a pile of integration conflicts on paper, before a line of code existed — cheap to reconcile there, brutal to pull apart inside a built feature. It saved real hours even though AI was writing the code fast.