Diagram, Loop and computers

From a diagram to merged, reviewed and deployed code: chunks, computers, the gate and deploys.

How a project goes from a drawing to merged, reviewed and, if you want, deployed code, with agents doing the work and people deciding what only people should.

1. Draw the diagram

• A diagram is a set of chunks. Each chunk has an interface contract, done criteria a machine can check, dependencies and the paths it may write.
• An architect agent can draft it (diagram tool or /v1/diagrams); a person confirms it and freezes the baseline. After that it changes only through a change a person decides.
• A chunk whose dependencies are not merged waits as BLOCKED with the reason, and is dispatched automatically when they merge.

2. Connect computers

npx veynod --run-tasks --repo owner/name

• One approval in the console connects the computer; Claude Code or Codex on it does the work. Running the command again upgrades and keeps its settings.
• Work reaches a computer over its own socket with two receipts: received within 0.2 s, started within about 5 s. A computer that misses either is taken off and the work goes to another one.
• Each task runs in its own worktree, never the shared checkout. Add --supervisor on one computer to have it look after the Loop.

3. The gate and the merge

A finished chunk goes through the Kernel's five checks (write-set boundary, AST scope, contract hash, static typecheck, unit tests); the Kernel merges what passes, the chunk turns merged with its commit, and the chunks waiting on it are released. The builder never reviews or merges its own work.

4. Deploys (optional)

• Settings → Deploys: a target names the deploy computer on your server (npx veynod up --deploy --compose-dir DIR), the branch and the trigger: every release, inside a time window, or only when a person starts it.
• CI posts a release for each merged commit with every service's image digest. A run restarts only what changed, checks health and rolls back on failure.
• The deploy computer dials out; Veynod holds no SSH key and opens no port.

What still comes to you

The automation mode decides how much agents settle on their own. In every mode, money, identity, legal matters, deleting data and outside commitments come to a person, and anything that waits for you is listed under Loop → "needs you".