Skip to content
Atlas docs

Read the governance scorecard

The /control view is the bird’s-eye read of your portfolio — one page, four numbers, a module breakdown, and a top-risks list. Read it before a review, after a release, and on Monday mornings.

Anatomy of /control COMPLIANCE 82% C2 bindings acrossopen cases CLEAN-CORE COVERAGE 68% extensions on BTP vs.in the core DEPRECATED APIS 14 in active use acrossthe portfolio RELEASED COVERAGE 91% modules with at leastone A_ candidate MODULE BREAKDOWN MODULE COMPLIANCE CLEAN CORE DEPRECATED SD 88% 74% 3 in use MM 72% 61% 6 in use FI 94% 81% 1 in use CO 68% 52% 4 in use TOP RISKS BLOCKER BAPI_SALESORDER in 4 cases MAJOR P_OrderExtras binding MAJOR FI migration gap · 2020→2023 MINOR Pushdown regression on ZC_… INFORMATIONAL BlogPost citation (tier 4) Every tile and every row is a graph traversal. Expanding one shows the cases and evidence behind the number.
The governance scorecard — four tiles, module breakdown, top risks.

The four top-line numbers

Section titled “The four top-line numbers”
  • Compliance % — the fraction of bindings across all open cases that land on released APIs (C2) rather than private (C0) or system-internal (C1). See SAP API stability tiers for what the tiers mean.
  • Clean-core coverage — the fraction of cases whose extensions live on BTP rather than modifying the core. See Clean core for why this matters.
  • Deprecated APIs in use — a count Atlas derives from Resolve findings across open cases. Clicking the tile deep-links to an Investigate view scoped to deprecation intent.
  • Released coverage — per-module percentage of modules with at least one A_ (C2) replacement candidate for the custom code the cases touch.

The module breakdown

Section titled “The module breakdown”

Below the top strip each module gets a row: module name · compliance % · clean-core % · deprecated-API count · top risks for the module. Expand a row to see which cases drove the numbers; click a case to jump into its object view.

Modules with no active cases render in muted grey — they exist in Atlas’s model but have no cases open.

Top risks

Section titled “Top risks”

The panel at the right surfaces the highest-severity atlas:RiskSignal nodes across the portfolio. Each risk has:

  • category — clean-core, release-gap, legal, performance, auth
  • severity — blocker / major / minor / informational
  • affected cases — one or many; click to jump

A risk stays on the list until a MigrationDecision node resolves it (atlas:resolvedBy). Opening a risk shows the cases and artifacts it implicates and the guidance Atlas has attached to it.

How to use the scorecard in a review

Section titled “How to use the scorecard in a review”

Start from the top-line tiles, drill into the module row with the weakest number, and from that row jump into the case that is driving the miss. Every number is a graph traversal — expanding any tile or row shows the nodes behind it, so a review is grounded in the same evidence Atlas used to compute it.