Writing
The home page states what Graphban refuses and how to start. These are the pieces that wanted more room than a landing page should take — the objection worth answering properly, the evidence from building it with itself, and the bug that started all of it.
Nearest-neighbour search over a folder of notes cannot say "I don't know" — it returns the least-unrelated thing it has, with a score that looks like an answer. On absence rendered as a result.
Evidence · 5 min readGraphban was built by agents running Graphban. Then a person drove it by hand for two days. The number that matters is how many of the defects they found the suite had caught.
Argument · 4 min readThe most reasonable objection to all of this is that you already have a docs folder full of specs. It deserves a real answer, not a dismissal.
Origin · 2 min readAn agent reported success against a rule that had been written, tested and green for weeks — and had never once fired. Every mechanism here traces back to that afternoon.
The mechanisms themselves live under Product — spec to done, the fleet, the living graph, memory, and the technical deepdive. Those are reference; these are argument.