Savings overlay: "$X reclaimable"

WITHOUT OVERLAYS:
  Sankey shows flow size only
  Each flow's color = neutral
  User sees composition; must navigate elsewhere to act

WITH SAVINGS OVERLAY:
  Flows with recorded savings get a red stripe
  Hover any flow: inspector shows "$X reclaimable" if any
  Click the callout (on a type or account node): deep-link
    to filtered Recommendations

WITH UNATTRIBUTED OVERLAY:
  Flows into the Unattributed team bucket (resources with no
    team assignment) are highlighted yellow
  Distinguishes "where the money goes" from
                "where the money has no owning team"

BOTH OVERLAYS ON:
  Red-and-yellow striped flows = double signal
  (no team + reclaimable)

RECLAIMABLE (as the overlay computes it) =
  SUM of the savings recorded on the flow's cost records
  (each record's savings = its 24/7 cost minus its actual cost)
  split across teams by share count, exactly like cost

For a flow showing "prod-aws-us-east-1 → EKS → team-platform":
  Reclaimable = SUM(savings) over the cost records in that flow

USER CLICKS the "$2,400 reclaimable" callout on a flow

OPENS Recommendations (/recommendations/cost) with ONE filter
pre-applied, taken from the node you clicked:
  resource_type = EKS      (for a type node)
  or cloud_account = …     (for an account node)

RESULT:
  Recommendations list shows the EKS recommendations, ready to
  triage directly.

NO MANUAL FILTER CONSTRUCTION required.

SUPPORTED DEEP-LINK FILTERS (one at a time):
  resource_type
  cloud_account   (URL parameter; the node's dimension is the
                  cloud account)

NOT SUPPORTED (the node's callout is hidden):
  team_id
  provider
  region
  service_name
  purchase_type

WHEN A CALLOUT IS HIDDEN:
  The savings still show on hover in the inspector
  Workaround: open Recommendations and filter manually

SEPARATE OVERLAY: Unattributed teams highlight

When toggled on:
  Spend whose team resolves to the Unattributed bucket (no
    team assignment) is highlighted in yellow
  Flows that feed that bucket show the yellow tint
  Hover: inspector shows the unowned amount and share of spend

USE CASES:
  - Ownership audits
  - Identifying which dimensions carry the most unowned spend
  - Finding orphan resources (often the ones nobody assigned)

BOTH OVERLAYS ON SIMULTANEOUSLY:

  Red-striped: recorded savings (reclaimable)
  Yellow-highlighted: spend with no owning team
  Red-and-yellow: both

INTERPRETATION:
  Red only: savings in play; check the recommendations
  Yellow only: ownership gap; assign the resources to a team
  Red and yellow: double opportunity: no owner AND savings in
                  play. Often orphan resources from departed
                  users; assign + act, or just delete.

The red-and-yellow flows are usually the highest-leverage.

SCENARIO                                  USE OVERLAY?
──────────────────────────────────────────────────────────────────
Weekly Operate review                     Yes: find this week's
                                          action items

Monthly cost review for leadership        No: overlay adds noise to
                                          executive view; show the
                                          number separately

Quarterly optimization sprint              Yes: primary tool for
                                          finding savings

Anomaly investigation                      Maybe: sometimes the
                                          anomaly is from open recs
                                          not yet applied

Initial onboarding / exploration          Yes: surfaces value
                                          immediately

COST FLOW with savings overlay, BY SERVICE layout:

  Provider →  Account →  Service →  Team

  AWS →     prod-us →    EKS →       team-ml-infra
             ████░░░░     ███████░    ████░░░
             ▒▒▒▒▒▒▒▒     ▒▒▒▒▒▒▒▒    ▒▒▒▒▒▒▒  (red stripes: $4.2K)

  AWS →     prod-us →    RDS →       team-platform
             ████░░░░     ███░░░░░    ██░░░░░
             (red stripes: $1.1K)

  GCP →     dev →        Compute →   Unattributed
             ██░░░░░░     █░░░░░░░    █░░░░░░░
             ░░░░░░░░     ░░░░░░░░    ░░░░░░░░  (yellow: $480)
             (red+yellow: $480 from unowned compute,
              also has recorded savings)

LEGEND:
  ▒▒▒ = red stripe (reclaimable savings)
  ░░░ = yellow tint (no team assignment)

WEEKLY (20 minutes):
  T+0     Open Cost Flow, default layout, this-week scope
  T+1     Toggle savings overlay
  T+2     Identify the largest red-striped flow
  T+3     Click the callout → filtered Recommendations
  T+5     Triage 3-5 recommendations
          (apply / dismiss / investigate further)
  T+10    Repeat for next red-striped flow
  T+18    Document acted recommendations in team wiki
  T+20    Close loop

OUTCOME over time:
  Reclaimable savings decline as recs are applied
  The Unattributed share shrinks as resources are assigned
  The overlay becomes "the thing I scan weekly"

TIME: Monday morning, 9:15 AM
GOAL: This week's recommendations to triage

T+0       Open Costs → Flow
T+5 s     Toggle "Savings overlay" → on
T+10 s    Scan the Sankey for red-striped flows

          Three biggest:
          1. AWS → prod-us → EKS → team-platform   $2,400
          2. AWS → prod-us → RDS → team-product    $1,100
          3. GCP → prod → BigQuery → team-data      $750

T+30 s    Click the callout on the EKS node ($2,400)
T+35 s    Recommendations page opens filtered:
          resource_type=EKS
          Sees 8 open EKS recommendations

T+1 min   Triage:
          - 5 right-sizing recs (low risk) → apply now
          - 2 idle-cluster recs (need owner approval) → assign
          - 1 spot-instance switch (medium risk) → defer

T+3 min   Apply the 5 right-sizing recs (one-click each)

T+5 min   Switch back to Cost Flow; click the RDS callout ($1,100)
T+5:30    Recommendations opens for RDS in prod-us
          Triage: 4 recs; 3 apply now, 1 defer

T+8 min   Click the BigQuery callout ($750)
T+8:30    BigQuery recs (snapshot lifecycle, query optimization)
          Triage: 2 recs; both deferred (need data team owner)

T+10 min  Switch on Unattributed overlay; notice yellow on flow:
          GCP → dev → Compute → Unattributed
          12 compute resources with no team assignment

T+11 min  Hover the flow to see the unowned amount
          Identify the resources
          Assign them to a team or flag for cleanup

T+15 min  Document in team wiki:
          "This week: applied 8 recs (5 EKS, 3 RDS) of the
          $3.5K/mo flagged across those two flows; the rest are
          assigned or deferred. Assigned 12 GCP compute
          resources to teams."

ELAPSED: 15 minutes to act on most of $3,500/mo of flagged
savings, plus ownership hygiene.

OPEN Costs → Flow → toggle Savings overlay

LARGEST RED-STRIPED FLOWS (top 3 you see):
  1. __________  Reclaimable: $__________
  2. __________  Reclaimable: $__________
  3. __________  Reclaimable: $__________

TOTAL VISIBLE RECLAIMABLE: $__________

PICK ONE FLOW; click its callout:
  Recommendations opened? Yes / No
  Filter scope: __________
  Number of recommendations: _____

ACTION you can take this week:
  □ Apply N recommendations (low-risk)
  □ Assign owner for high-risk recs
  □ Defer specific recs (note why)
  □ Combine with team meeting

UNATTRIBUTED OVERLAY:
  Toggle on. Largest unowned flow:
  __________  Unowned amount: $__________
  Assignment plan: __________