The token burn is real and the fix is a one-time context map. Right now
every query scans blind because nothing tells Claude where things live.

WHAT IT BUILDS
A my-context-map.md file listing every database and its purpose, saved
to your about-me folder and referenced in global instructions. Once it
exists, a query jumps straight to the right database instead of
searching the whole workspace.

  my-context-map.md
    ## Databases
    - Clients        → active + past engagements, one row per client
    - Content Calendar → scheduled posts, status, channel
    - CRM            → pipeline, deal stage, next action
    - Meeting Notes  → raw notes, one page per meeting
    - SOPs           → process docs
    ...

BEFORE / AFTER, IN TOKENS
  Before: "Which clients are overdue?" → scans multiple databases to
          find the right one, then queries. Two expensive passes.
  After:  reads the map (cheap), sees Clients is the target, queries it
          directly. One targeted pass.

WHY IT'S IN about-me + GLOBAL INSTRUCTIONS
The map has to be loaded for every session, not fetched on demand — the
whole point is that Claude already knows the layout before the first
query. Living in about-me and referenced globally is what makes it
always-on.

MAINTENANCE
Regenerate it when you add a database. A stale map sends queries to the
wrong place, which is worse than no map — so treat it as living, not
one-and-done.

Connect Notion and I'll generate the first version of the map from your
actual databases.