Docs

Architecture

Trace any route to its handler in one click. The living architecture map - every route, every module, every flow, every convention worth knowing. Backed by architecture-map.json: its route list is generated from server.mjs plus the lib/routes/ modules and gated by CI, its narrative sections are hand-maintained, updated in the same PR as the change so the map never lies.

See it in motion

Where to find it

  • Desktop: localhost:4000, then Attribution in the sidebar, then Architecture under All tools, in the Pull requests, blame and graphs group.
  • Hosted: repoops.ai/team/reference, from Memory in the sidebar, then Reference index under All tools, in the Lessons, wiki and patterns group, which lists it.
  • Keyboard: ⌘ K, then type “Architecture”.
  • On disk: .claude/brain/architecture-map.json + its HTML twin

What it does for you

See the system end-to-end on one screen.Server entry route table handler module downstream lib. The whole request graph, drawn from the actual code.
Know the conventions before you touch the code.Naming rules, file conventions, next-agent entry points - captured once, read by every fresh session.
The map updates in the same PR as the change.CLAUDE.md hard rule: any PR that changes routes, flows, or steps updates architecture-map.json in the same commit. Stale maps are a defect.

Configure

The routes list is generated from server.mjs and the lib/routes/ route-table modules by scripts/gen-architecture-map.mjs, and a CI gate fails the PR if it drifts, so do not hand-edit routes. The narrative sections (stack, entry points, modules, flows) are hand-maintained: edit them in the JSON by hand. The generator rewrites only the routes array, so a narrative edit needs no regeneration, and the HTML twin at .claude/brain/architecture-map.html is hand-curated as well, so update it in the same PR. The structure is open (no schema enforced) - keep it readable.

Use it well

Open Architecture before adding a new route or refactoring a flow. The existing conventions are right there - match them, don't invent new ones. After your PR, update the map. The next agent walks in already knowing the new flow exists.

Read more

Last updated