Brain & dev sessions

The Company Brain

The Brain is one library the company writes in: operating notes, repository briefs, decisions, competitive intel, runbooks. Every note carries provenance — where it came from and how much to trust it — and retrieval weights accordingly, so a decision note a human accepted outranks an agent's summary of a blog post.

The Brain is retrieved into every run. When a note and the code disagree, code wins — the note gets corrected and the drift gets logged. It is company memory with an error-correction loop, not a wiki that rots.

Objectives & policies

Objectives give the Coordinator direction to ladder work into. Policies are notes with a draft → review → active lifecycle — accepting a policy is a human act, because the commitments in it (who owns which key, what rotates when) are commitments only a human can make.

Dev sessions

Dev sessions drive Claude Code or Codex against real git checkouts on the appliance's own disk. The fleet can propose code the way it proposes anything else — and the result is a diff a person reviews, on a branch, like any contributor's.