Open source · MIT · MCP-native

A grand hotel, run by AI. This is its brain.

The Pemberton Grand is a fictional five-star house where every role — the GM down to the night porter — has its own agent. They all boot from one graph: the structure, the memory, and the law of the house. It's floating behind these words, live.

Nodes
2,414
Departments
9
Agent roles
62
Licence
MIT

01 — The one idea

One brain: the structure, the memory, and the law.

Every agent at the Pemberton boots from the same graph — who it reports to, which rules bind it, which memories it may reach. Declare a rule once at the top and every role beneath inherits it. It's all one small JSON file: emit it, and the 3D view, the API, the MCP server and the markdown vault come free.

  • Postgres
  • Supabase
  • JSON
  • Your adapter
booboo.json one rooted graph
  • 3D viewer
  • REST API
  • MCP server
  • Markdown vault

02 — The house, live

Five alarms are burning. Go and click one.

This is the running brain, not a picture of one. Drag to turn the house, click any node for its dossier, press / to search 2,414 of them. The ringed beacons are the flags — the red one is the Room 407 water leak.

Same engine as the full viewer — nothing is faked. Open it full-screen

03 — Three faces, one brain

Look at it, govern it, or just ask it.

Same graph underneath. Which face you use depends on the question you're holding.

04 — The model

Five ideas. That's the whole contract.

Booboo isn't a schema you learn, it's five nouns. Everything on this page — the 3D view, the staff board, the answers — is those five, rendered.

Layer a band of the house
A horizontal stratum: the GM, the department heads, the staff, the ledger. Layers stack, and a department reads as one vertical column through all of them.
Agent a role, not a person
Roles are durable; the model behind them is disposable. Whatever boots into "Housekeeping" becomes Housekeeping — with its persona, its reach, its rules.
Bucket a walled memory
Where an agent may read and write. Housekeeping sees Housekeeping's ledger. The guest registry is sealed — visible as a wall, never as contents.
Rule law that flows down
Declared once, inherited by everyone beneath. The GM amends the House Standard; every department is bound by the next morning.
Boot what an agent loads first
One call returns identity, chain of command, rules in order, and bucket reach. That slice is the whole point: the agent knows its place before it does anything.

This is a real boot slice from the house, unedited:

// booboo_boot("housekeeping")
{
  "agent": { "id": "housekeeping", "role": "Precise, spares no linen, escalates before apologising." },
  "chain":   [ "gm", "housekeeping" ],
  "rules":   [ "rules/HOUSE_STANDARD.md", "rules/sop/HOUSEKEEPING.md" ],  // ancestors first
  "buckets": [ "house", "executive", "housekeeping" ],
  "children": 6 roles
}

05 — Ask the house

It answers questions. Real ones.

The brain behind this page is a live MCP endpoint. Point Claude at it and ask — these are genuine answers from the Pemberton's ledger:

What are the major failures this week?

Three: the Room 407 water leak, the Lift E2 entrapment, and the gala power failure. Engineering is running amber.

answered from the ledger · booboo_search over /mcp

Who's been off sick most in five years?

Room Attendant 07, Housekeeping — 98 absences, seven times the next highest. The house knows.

answered from the ledger · booboo_search over /mcp

Try it yourself — these run against the live house, right now:

Pick a question — the answer comes back from /mcp, not from this page.

Or add the house to claude.ai as a custom connector and ask it anything:

https://booboo.fractionalhq.uk/mcp

06 — Run it on yours

One command. No database, no config, no signup.

See a synthetic brain running on your own machine before you point it at anything real.

npx @booboo-brain/cli view --demo --nodes 1000000

When you want it reading your own stack:

npx create-booboo my-brain

07 — What ships

  1. 01

    A graph your agent can actually query

    Point Claude, Cursor or Claude Code at the MCP server. Stats, search, node dossiers, neighbours, pathfinding — your agent stops guessing at how your own system is wired.

  2. 02

    Readable at any scale

    One draw call, deterministic layout, no force simulation. The structure you see at 2,400 nodes survives at a million — see it hold at a million →

  3. 03

    Privacy walls before anything is written

    Sealed namespaces never reach the snapshot. What you don't emit cannot leak into a viewer, an API response or a vault file.

  4. 04

    Your brain as plain markdown

    The same snapshot renders to a wiki-linked vault. Open it in Obsidian, grep it, commit it. No lock-in, because the format is a file you own.

Nothing to sign up for.
It's a file, a renderer — and it answers.