Moot · Company Brain on FalkorDB · Graph Hacks, Company Brain track · tour for judges

Ask an organisation whether a decision still holds, and who answers for it.

Moot reads decisions, people and teams into a FalkorDB graph with dates on every edge. Kubernetes is in it: every SIG Auth, Node, Network and Storage proposal and every SIG lead since 2018. Each answer shows the path and the Cypher behind it.

Ask Kubernetes See how it works ›

Straight to the proof: KEP-3130: retired, by what, who answers for it · the Cypher FalkorDB ran · a demo company, eight people deep · what leaves when someone does · a real GitHub repo, audited

Larkspur, month by month. Each token is a standing decision. When a reason dies, it sinks below the line.

Graph Hacks · WeMakeDevs × FalkorDB · Company Brain track

A tour for judges.

Three minutes of video, then seven stops, each one a place you can check yourself.

A whole organisation in one graphKubernetes: KEPs as decisions, SIGs as teams with their leads over time, authors, documents, the reasons each KEP states Does it still hold, who answers for it today, and whyA retired KEP, the KEP that replaced it, the SIG that answers for it and who leads that SIG now The exact Cypher, quotes and spansEvery answer's read-only queries with rows and milliseconds; every stated reason's quote with its character span The graph changes as the agent worksPost a change in your own sandbox and watch verdicts move; approved Findings; a coding-agent hook that blocks edits Correct by construction, and labelled so2,000 random worlds against an oracle, NetworkX cross-checks, remembered answers revoked when evidence changes The honest results table, losses includedHeld-out real decisions, precision on real history, the backtest, the router; registered before they ran Check it all in one commandmake judge-check: tests, every README number re-derived from committed inputs, the held-out gold hash

How it works

Every rule has a reason. Reasons expire.

The blast radius

One reason breaks. Every rule on it falls.

The drawing

Every verdict comes with its drawing.

The decision, its reasons and the evidence, drawn from the rows FalkorDB returned. The cable to the expired reason is unplugged. Drag to turn it.

Open D01 in the ledger

On real history

Proof

For agents

Agents ask first.

Before an agent enforces, relies on or renews a rule, it asks the graph. The answer is Allow, Deny or Revalidate, with the path that decided it.

Try it

Ask why a rule exists.

This box asks the live Larkspur graph. The answer comes with the path that decided it.

Press Ask to see the verdict, the reason that decided it and the evidence behind it.

Real world

Checked against public decision records.

Each tool choice rests on reasons nobody wrote down: still maintained, still open source, no known vulnerability.

Go further

Your people, your repositories, real history.

The same path queries, on who knows what, on any GitHub repository's decision records, and on decisions real teams later abandoned.

What leaves when someone doesWho knows why each decision was made, bus factor, bridges (betweenness) and knowledge islands (WCC)Every query behind one answerThe read-only Cypher FalkorDB ran for D01, with rows and milliseconds