Three interactive decision-support lenses computed from the live service catalog, plus a cross-cutting impact web. Reference views by their badge in discussions: 1A · 1B · 1C · 2A.
Turn 1 · Three decision-support directions
Reframing the platform views into decisions you can act on
Each direction targets one audience and one class of decision. Derived signals — blast radius, hub risk, migration priority, handoff coupling — are computed from the existing catalog data.
1ABlast Radius Explorer— dependency graph · for Platform / SRE
Change-Risk Map
"If I touch this, what breaks?"
Ranked by blast radius
Blast radius = services that transitively depend on this one.
1BMigration Cockpit— tech radar · for Eng Leads
Adoption Radar + Action Queue
click a blip to trace it
Prioritized action queue
1CHandoff Readiness Board— combined overview · for Decision-makers
01Own the IaC seamDoes Novamera inherit OpenTofu/Terragrunt blueprints as-is, or adopt its own structure? Blocks the whole handoff.
02Protect the Shared Data PlatformHighest blast radius — a schema change ripples through the QC↔GPR pipeline. Needs change-control + contract tests.
03Clear the observability pathPromote Managed Grafana to Adopt; unblocks prom-client + OpenObserve and lets Datadog stay retired (ADR-0003).
Turn 2 · Relationship & impact
Tie the dots: decisions → patterns → services → customers
Everything the platform builds is connected — an ADR governs a pattern, a pattern shapes services, services ship to a customer. Click any node to trace what governs it and who it impacts. Flip on Plan a new service to preview how a proposed service would wire in.