Skip past the film

Five people. Three kinds of agent. Every session starts blind.

It fragments across people.

The missing information lives on someone else's machine, in someone else's head, or in a session that already ended.
failure 2′ · 12-teams.md §1
None of this is an intelligence problem. The next model will not fix it.
One goal
Many hands.
in onerepository
EDIFY for teams.
The shared brain of a team.
RATIFIED 2026-09-26
DECISIONS D-1 TO D-4
Every agent will start where the team left off. Plain files in your repository, synced by git.
Change the unit of work↔
01One developer02One team03Any agent
Plan hard once. Now across people.
Read the blueprint↘

The brain is the repository.

P9 · 01-principles.md
.edify/team/
  goal.mdthe shared goal. humans edit it
  profile.mdthe team questionnaire's answers
  tasks/<id>.mdthe definition, never the state
  journal/<who>/append-only. claims, progress, done, how
  playbooks/how it is done here. a human admits each
journal · one file per event · unique path per author and second
+journal/sg/20260926T101100Z-T-sg-12-claim.md
+journal/mr/20260926T102847Z-T-mr-9-progress.md
+journal/cl/20260926T141502Z-T-cl-4-done.md
+journal/rl/20260926T150210Z-T-rl-2-note.md
State is never stored, so state never conflicts.
architecture/03-sync.md §3

A pure function over files. The same bytes on every machine.

edify team statusspecified output · not built yet
edify team status
goal one unassisted lap of the Varsity track by 2027-03-15 goal.md, edited 2d ago
in flight
T-sg-12 fuse lidar+camera in tracker sg · claude-code progress 40m ago
T-cl-4 brake ECU CAN bring-up cl · human progress 2h ago
T-mr-7 sim sweep: steering gains mr · codex no progress 5d · stale
contested
T-sg-15 replay harness for bags sg vs mr both claimed · earliest: sg
blocked
T-cl-6 HIL rig for brake controller "waiting on harness from EE subteam"
ready
T-mr-9 data-collection run, wet track experiment · perception
authors sg 40m ago · cl 2h ago · mr 5d ago ← git pull to refresh
architecture/02-team-cli.md · status and brief are plain text on stdoutno model is called
machine A · sg · claude-code
HEAD 3f9a1c2 → edify team status
machine B · mr · codex
HEAD 3f9a1c2 → edify team status
= same commit, same output. no server between them.
edify team done T-mr-9
refused. kind experiment requires a How
with parameters, a result and a link to the data.
enforced · done refuses without a How
advisory · claim warns, never refuses
06-customisation.md §3 · as specified

Agents propose. A human admits.

A wrong journal entry misleads one person once. A wrong playbook misleads every agent until someone notices.
architecture/04-learning-loop.md §1
journal · How
cl/…T-cl-4-done.md
learn
evidence + skeleton
_proposed/can-bench-bringup.md
agent fills
the door
a human reads it
admit
trusted context
playbooks/can-bench-bringup.md
reject → a note entry with the reason
admitted by cl · 2026-09-27
deliberately not built · 12-teams.md §8
A server. A sync service. A database. Embeddings. Consensus. Telemetry.

Git is the server.

Coordination is a file an agent reads, never a protocol agents negotiate.
EDIFY
for teams · specified 2026-09-26
The shared brain of a team. Specified in full. The build is next.
design partners: U of T design teams and research labs · free for 12 months · 12-teams.md §7
The commands · specified

Each answersone question.

Plain text on stdout, so any agent that can run a shell command can use them: Claude Code, Codex, Cursor, and whatever you run next. Stdlib only, offline.

architecture/02-team-cli.md · 05-agents.md
Set up the brain and ask the team questionnaireteam init
A new task on the board, from anyone, at any timeteam add
I am on it, I am off it, it is done, it is stuck and whyclaim · release · done · block
Who, person and agent, is on what; what is ready, blocked or staleteam status
How I did it: commands, rig, parameters, dead ends, frictionteam log
Everything a fresh agent session needs, on one pageteam brief
Turn journal entries into a proposed playbook; a human admits itteam learn · admit
Who it is for

Design partners improve it. Startups pay for it.

MIT · no account
Public edition
Freeedify-agents-cli
Every command, every graph query, every check
Any graph size, any number of projects
One server in the registry, the only cap
By licence
Team edition
Licenceedify-agents-teams
The team brain, edify team, and unlimited servers
partner licences are free for U of T design teams and researchers
No payment and no price: a licence is issued on request
The first milestone

Two machines. No server.

Two people on two machines, one using Claude Code and one using Codex, share a repository. After git pull, each runs edify team status and sees the other's claimed task and last journal entry. That is the check the first week has to pass.

The design and the amendmentsratified 2026-09-26
edify team, the CLIspecified · the build is next
The team plan and design-partner tokensspecified