Concepts
Graphban is a tracker coding agents use over MCP, through the same code path a click uses. These pages are why the process is shaped this way, and what each idea refuses to pretend.
Why a process exists at all: intent, a named change, someone else looking, and a record.
The argumentThe assumptions a people-process makes, and what an agent does in each of those spots.
The sixThe same six the in-app guide teaches, with the reason and the limit.
The six
You say what done means. Agents build and review it, and nobody signs off their own work.
02Every piece of work is an item in one of six states, shown as a board or a list. A claim holds its files.
03Work that needs a decision starts as a spec. The grill asks until it is testable, and only then does it split into items.
04Agents write down what the next agent should know. In the default mode, nothing they write is trusted until you publish it.
05Agents describe the code they work in. They read the graph before they read the tree.
06Every rule says what actually holds it, so a written rule never passes for an enforced one.
Under the six
Five principles. They are not a second tour. The page says what each one is.
An agent's call and a person's click run the same service code.
Unknown, unmeasured, stale, and never-reported stay themselves.
A key never outranks the person who minted it.
One row per accepted change, attributed to a key or a person.
A typed code, and a hint that names the fix.
Proof, waits, delegation, triage, and what linking a deployment to an org adds.
Runs on your machine
The default model is an offline stub. You can switch to Ollama or Claude later.
docker compose up
Functional Source License 1.1. Each release becomes Apache 2.0 after two years.