Opening the local map
Run Iris Code: Open Code Map from the command palette in VS Code or from Find Action in JetBrains IDEs, or select Open Code Map in the Workspace tab. Each file in the Workspace tab’s Ranked lists has a map button beside it, which opens the map with that file in view. Selecting the file name itself still opens the file. Folders can be expanded and collapsed. Selecting a file opens it in the editor. Each row has ten separate health-score markers and a numeric score. Green is healthy, amber needs attention, and red is failing. A folder score is the ordinary average of its measured files, matching the workspace score. Line count is shown as context, not used as a score weight.Files that Iris Code cannot measure are labelled Not measured. They are not shown as failing, because the absence of a score is not evidence that code is unhealthy.
Files below the minimum
An average can hide the file that fails. Ten files at 98 and one at 60 average 94, so the folder reads as healthy, while the gate blocks the push on the file at 60. Code Map keeps the folder average and marks the failing files separately. A red caution badge appears beside any file that would fail the gate’s score rule, showing how many points it is short. Each folder above it shows a badge with the number of failing files inside it. Hovering a folder’s badge lists those files, furthest below first, with each one’s score against its minimum; hovering a file’s badge shows its score, the minimum and the shortfall. The header shows the total for the whole map, and hovering it lists every failing file. The minimum is the one the gate uses:minHealthScore from .irisconfig.json, or 70 when it is not set. With gateBaselineMode on, each file is compared against its own locked baseline, so a file scoring 90 carries the badge if its baseline is 95. Scores are rounded down before the comparison, as they are in the gate, so 69.9 is below a minimum of 70. Files that are not measured never carry the badge.
The caution appears in the local map in VS Code and JetBrains, and in the cloud map. The cloud map uses the minimum that audit was scored against, which may come from a fallback preset or your workspace standard rather than the repository’s own config. Audits run before the cloud map could record a minimum show a note saying failing files are not marked; running a new audit adds them.
Scan states
Code Map always shows which result it is displaying:- Not scanned yet: the repository structure is visible and the map provides a Scan button.
- Scanning: the current workspace scan is in progress.
- Scanned: scores come from the last completed scan.
- Stale: the saved scan is more than a day old. Run a new scan before treating it as a current picture of the repository.