X-Ray
Turn a repository into a living map. Explore your codebase as a graph across Architecture, Domain, and Knowledge views, then launch modernization jobs straight from it.
X-Ray scans a connected repository and renders it as an interactive graph instead of a file tree. You see how the codebase is layered, which domains it splits into, and where the knowledge lives, then select part of the map and hand it to a squad as a modernization job. It's the bridge between "understand this codebase" and "change this codebase."
X-Ray lives at /{workspace}/x-ray in the app.
Connect a repository
X-Ray needs read access to a repo before it can scan.
Go to X-Ray in the workspace sidebar and choose Connect repository. Authorize GitHub (or paste a token) so Concierto can read the repo, see GitHub integration for how access is scoped.
Select the repository to map. Concierto clones it, analyzes the structure, and builds the graph. The first scan can take a moment on a large codebase.
Code moves. Re-run the scan to refresh the graph; the higher-level Domain and Knowledge layers are backfilled after the base Architecture layer, so they may light up a little after the first pass.
A repository in X-Ray is attached to a project. Modernization jobs you launch from the graph are filed under that project, so the work stays organized next to everything else for that codebase.
The three views
A segmented control at the top of the canvas switches between three lenses on the same graph. Each answers a different question.
Architecture
The default view. Nodes are grouped into layers (entry points, services, data, and so on) and colored by layer, so the shape of the system is legible at a glance. Click any node to open the inspector and see its connections, then drill in for detail.
Domain
A higher-level map that clusters the graph into domains. The business areas the code serves, rather than its technical layers. Use it to answer "what does this system actually do, and where does each capability live?"
Knowledge
A knowledge-oriented view that surfaces the concepts and entities woven through the codebase. Useful for onboarding and for finding the right place to make a change when you don't yet know the file.
Domain and Knowledge are derived layers. If a tab is disabled with a "regenerating" spinner, a scan is still building those layers. Give it a moment and they'll come online.
Read the map your way
X-Ray adapts the graph to how you're reading it:
- Persona, switch the framing of labels and emphasis for the kind of reader you are (e.g. a newcomer vs. someone planning a refactor).
- Intent, re-rank what the graph foregrounds based on what you're trying to do.
- Tour, a guided walkthrough that steps you through the most important nodes.
- Search, jump straight to a node by name from the rail.
These are reading aids. They change how the graph is presented, not the underlying scan.
Launch a modernization job
This is where X-Ray stops being a diagram. Select one or more nodes to define a scope, then open the modernization job dialog from the refactor rail.
Click the nodes (a layer, a domain, a cluster of modules) you want the work to cover. The selection becomes the job's scope snapshot.
X-Ray surfaces the modules your scope is likely to affect. Accept the impacted modules you want pulled into the job so the agents get the full picture.
Pick what kind of modernization this is and which workstreams it breaks into, Concierto recommends roles per workstream so the work is split sensibly.
Modernization jobs become ordinary Tracks once created. They run, report, and review exactly like any other agent work. X-Ray is just the launchpad that scopes them against the real structure of your code.
Next steps
- Squads, the assignees that pick up modernization workstreams
- Projects, where a connected repo and its jobs are filed
- GitHub integration, how repository access is granted
- Canvas & blueprints. Compose new work visually, the complement to mapping existing work