Codebase map ("where does X live")
Generated from
mcp/patterns.registry.json— do not edit by hand; change the registry and runbun run patterns:build.
Index card — the docs below are the canonical explanation; deep-tier pattern pages additionally carry invariants and emulation notes.
Category: Architecture & Request Pipeline · Tier: light · Risk: low — structural pattern, no external services
Provides a spatial quick-reference table mapping each kind of code (business logic, route adapters, schemas, components, state) to its canonical directory.
When to use: Reach for it when deciding where a new file should live or trying to locate an existing concern in the repo.
Docs
Code
Machine-readable record: architecture-codebase-map in mcp/patterns.registry.json.