CodeRadius DocsSystem Registry
The auto-generated service catalog — a live inventory of every repository, service, and team in your architecture graph.
System Registry
The System Registry is the default tab of the Architecture Dashboard. It is an auto-generated, queryable catalog of every repository, service, and team that CodeRadius has ingested — a live replacement for manually maintained Backstage catalogs, spreadsheet inventories, and tribal knowledge.
# Open the full dashboard (System Registry is the first tab)
cr ui
# Focus exclusively on the System Registry
cr ui --focus inventoryWhat It Shows
The System Registry is organized into three sub-tabs:
Repositories
A sortable, filterable table of every repository in the graph.
| Column | Description |
|---|---|
| Repository | Full org/group/repo path, clickable link to the source |
| Branch | The ingested branch (e.g., main, master) |
| Depth | The depth of analysis performed: CONTRACTS, SEMANTIC, or STRUCTURE |
| Stack | Programming languages detected in the repository |
| Teams | Teams that own services stored in this repository |
| Pulse | Liveness indicator: commit velocity over the last 12 months |
Analysis Depth
| Badge | Meaning | How to Get It |
|---|---|---|
CONTRACTS | Full semantic extraction — intent, dependencies, capabilities, API call graph, data contracts (produced/consumed payload schemas) | cr analyze code --depth contracts |
SEMANTIC | Semantic code scan — intent, infrastructure dependencies, capabilities, API call graph via LLM analysis. Skips payload field extraction. | cr analyze code |
STRUCTURE | Structural scan only — repository registered, agentic context and structural files detected, no code analysis | cr analyze code --depth structure |
Pulse (Liveness)
The Pulse column shows commit velocity over the last 12 months, with a tooltip displaying the exact commit count and unique author count:
| Level | Badge | Commit Range |
|---|---|---|
| High | Green, pulsing dot | 100+ commits |
| Active | Cyan, pulsing dot | 20–100 commits |
| Low | Yellow, static | 1–20 commits |
| Dormant | Dim, static | 0 commits |
Dormant repositories are still listed in the System Registry for completeness, but they are excluded from aggregated metrics in the Agentic Radar to prevent skewing maturity distributions.
Services
A table of every service extracted from the graph, with ownership and complexity metrics.
| Column | Description |
|---|---|
| Service | The service name as detected from project structure or configuration |
| Owner | The team that owns this service (from Backstage catalog or git org) |
| Stack | Programming languages used by this service |
| Repository | The repository that contains this service, clickable |
| Functions | Total number of functions indexed by CodeRadius |
| APIs | Number of exposed API endpoints detected |
| Dependencies | Total package dependency count |
Dim em-dash (—) values indicate missing data — for example, a service with no declared team owner or a repository with no detected API endpoints.
Teams
A table of every team in the graph with their aggregate ownership metrics.
| Column | Description |
|---|---|
| Team | The team name as registered in the graph |
| Type | Team classification (e.g., Stream-aligned, Platform, Enabling) |
| Services | Number of services owned by this team |
| Repositories | Number of repositories owned by this team |
| Stack | Aggregate programming languages across all owned services |
Header Stats
When the System Registry is active, the header stats bar shows:
| Metric | Description |
|---|---|
| Repositories | Total number of repositories in the graph |
| Services | Total number of services extracted |
| Teams | Total number of teams detected |
| Deep Scan | Count of repositories with full semantic extraction (with tooltip breakdown) |
Filtering and Searching
Every table in the System Registry supports:
- Global search — A search bar that filters across all visible text content and hidden
searchValuefields (e.g., repository URLs, hashes) - Column filters — Clickable filter icons on supported columns that show a dropdown of unique values for that column
- Sorting — Click any column header to sort ascending/descending
- Export — The Export button downloads the currently filtered table as a CSV file
Relationship to cr sync
The System Registry is populated during the sync pipeline:
cr analyze code --depth structure— Scans repositories for metadata (team ownership, agentic configs, structural files). CreatesSTRUCTURE-level entries.cr analyze code— Full LLM-powered semantic analysis: intent, infrastructure dependencies, capabilities, API call graph. CreatesSEMANTIC-level entries.cr analyze code --depth contracts— ExtendsCODEwith data contract extraction: produced and consumed payload schemas (field names and types) for every I/O boundary. CreatesCONTRACTS-level entries.
Each subsequent analysis level builds on the previous one. A repository can be upgraded from STRUCTURE → SEMANTIC → CONTRACTS by re-running analysis with a higher depth.
Further Reading
- Architecture Dashboard — The unified dashboard that contains the System Registry
- CLI Reference —
cr sync— Sync commands that populate the registry - Agentic Radar — AI-specific maturity analysis built on top of registry data
Architecture Dashboard
The unified visual intelligence layer — a single-page report for architectural health, AI adoption, dependency governance, and blast radius analysis.
SPOFs & Data Gravity
Identify Single Points of Failure, data monoliths, and service bottlenecks across your architecture — ranked by a 0–100 SPOF score.