See the code.
Understand the system.

A verified map of your repository, readable by people and queryable by agents.

Explore SRM

SRM / GRAPH01 — 04

DesktopLab / actual captureRecorded on this Mac

Scroll to explore

01 / GRAPH

Beyond the tangle.
A structure you can read.

From repository to files and relationships, context stays recognizable as you move closer.

DesktopLab Graph with visible directed routes and the open Visual key identifying intra-directory, sibling, branch, and cross-root connections — DesktopLab · exact route categories, visible in the open Visual key

Chromium / from repository relationships to nested source groups

02 / CITY

The system
takes shape.

The same map, seen as a territory. Zoom from source districts to exact files. Building footprints reveal the source language.

Go further

DesktopLab City at closer scale, with the open Visual key showing exact source-language shapes of building footprints — DesktopLab · source districts and language-specific building footprints

DesktopLab / real zoom, movement and camera tilt recorded in SRM

03 / AT SCALE

Not a toy map.
Real codebases.

Explore verified Linux and Chromium maps on the same Mac. Move between source territory and relationships without losing the connection to exact code.

Linux v7.2 open in SRM City, zoomed until its source districts are fully colored and legible — **Linux v7.2**89,392 source files · 42.3 million code lines

Verified Chromium map open in SRM City on this Mac — **Chromium**169,888 source files · 33.9 million code lines

Linux v7.2 open in SRM Graph, with its source groups and visible relationships across the repository — **Linux v7.2 / Graph**Relationships remain navigable at repository scale.

Chromium repository open in SRM Graph, showing source districts and visible magenta cross-root routes — **Chromium / Graph**The same verified codebase, seen through its relationships.

04 / PEOPLE

Complexity grows.
Clarity remains.

New to the project?

Start with the structure, recognize boundaries and find an entry point before opening dozens of files.

Know it by heart?

Follow relationships, verify context and move from the overview back to exact source.

SRM Graph with the apps source district selected and its inspector showing exact source-file and code-line counts — One selection, from map to exact repository facts.

Chromium / select a file, open its source, keep your place in the map

05 / AGENTS

Agents with context,
not just files.

SRM exposes search, symbol bodies and relationships through MCP. The shell remains part of the workflow.

01srm_search_many

02srm_get_symbol_bodies

03srm_find_callers

Responses declare map coverage. A partial absence is never presented as certainty.

06 / PROCESS

From repository to
verified map.

SRM captures, analyzes, verifies and publishes a persistent representation of code.

01Capture
02Analyze
03Verify
04Publish

SRM Activity showing DesktopLab map creation at code analysis, with completed preparation, source capture and inventory — DesktopLab · actual analysis in progress

LOCAL BY DESIGN

Your code stays
on your machine.

SRM maps and explores repositories locally. To discuss a demo, tell us a little about your codebase—never send source code.

Every product visual shown here is a real SRM capture from a MacBook Pro with Apple M4 Pro and 24 GiB of unified memory.

See the code.Understand the system.

Beyond the tangle.A structure you can read.

The systemtakes shape.

Not a toy map.Real codebases.

Complexity grows.Clarity remains.