Skip to main content

UX Feedback 2026-02-22 : Overview Page

New design is in Stitch https://stitch.withgoogle.com/projects/13074478921113520827?node-id=852f5c7d7a0346a2b7ad3e8cd2eb0a92

Stitch design

Stitch design code (HTML)

Stitch design

Stitch design code (HTML)

Highlights vs the current version:

Task: Update Overview page UI to match Stitch target (Authority-first)

Context​

You have two references:

  • BEFORE (current app): Overview page titled “Autonomous Authority Posture” with section “Observed Autonomous Execution (30d)”, execution metrics, and “Priority Exposures” cards that are execution-centric and show % deltas, oldest finding, etc.
  • AFTER (target Stitch design): Overview page titled “Autonomous Authority Surface” with authority-first KPIs and “Top Risk Clusters” cards that prioritize Paths and treat executions as secondary “Observed runtime executions (30d)”.

Goal: Make the app UI match the Stitch target state. Keep existing layout system and components where possible; change copy, hierarchy, and what fields are displayed.

BEFORE → AFTER: Exact UI changes​

1) Page title + explanatory line​

BEFORE

  • Page title: “Autonomous Authority Posture”
  • No subtitle (or different).

AFTER

  • Page title: “Autonomous Authority Surface”
  • Add muted subtitle under title:
  • “Deterministic mapping of standing autonomous authority derived from observed execution.”
  • Keep “Last refreshed …” control in header as-is.

2) Replace top section (execution-first → authority-first)​

BEFORE

  • Section header: “Observed Autonomous Execution (30d)”
  • KPI cards:
  • “TOTAL EXECUTIONS” (120) with % delta
  • “EXECUTED AUTONOMOUS PATHS” (22) with % delta

AFTER

  • Remove the “Observed Autonomous Execution (30d)” section header.
  • Show two KPI cards (same layout position, two-up row), with new content:

Card A:

  • Label: “AUTONOMOUS AUTHORITY PATHS”
  • Value: 142
  • Subtext (muted): “Deterministically mapped”
  • Remove all trend arrows and % deltas.

Card B:

  • Label: “EXECUTED PATHS WITH INVALID OWNERSHIP”
  • Value: 38
  • Subtext (muted): “Observed runtime activity (30d)”
  • Remove all trend arrows and % deltas.

3) Replace “Priority Exposures” with “Top Risk Clusters”​

BEFORE

  • Section title: “Priority Exposures” with “View all”
  • Cards are exposure/execution-centric and include:
  • “Executions” as primary metric
  • % of total autonomous executions
  • paths as secondary
  • oldest finding
  • “New Findings” pill
  • trend deltas in some places

AFTER

  • Section title: “Top Risk Clusters”
  • Keep the section-level button on the right: “Export Report” (as shown in Stitch).
  • Replace the card set with 2-column grid cards that match Stitch hierarchy:

Each card:

  • Title (unchanged cluster string, e.g.):
  • “Sensitive + LLM + Active + No Owner”
  • “Sensitive + External + Active”
  • “Internal + Active + No Owner”
  • “External + Active”
  • Primary metric (large): “{N} Paths”
  • Secondary line (muted): “{X} Observed runtime executions (30d)”
  • Bottom-right small pill for new items:
  • “+3 New”, “+8 New”, “+5 New”, or “0 New” (match current data wiring; style as small muted chip/pill)
  • Remove from cards entirely:
  • % of total autonomous executions
  • % of total paths
  • “Oldest finding”
  • any trend arrows / % deltas

Layout intent:

  • Keep a clean card with title, big “Paths”, one secondary line, and a small “New” indicator.

4) Navigation label consistency (only if applicable)​

If the left nav currently says “Clusters”, rename to “Risk Clusters” (as in Stitch). Keep other items unchanged.

Acceptance criteria​

  • Overview page matches Stitch target visually and semantically:
  • Authority-first title and subtitle present
  • Top KPIs are authority paths + executed invalid-ownership paths (no deltas)
  • “Top Risk Clusters” section replaces “Priority Exposures”
  • Cluster cards prioritize “Paths” and show “Observed runtime executions (30d)” as secondary
  • No telemetry-style % deltas, no “Oldest finding”, no percentage-of-total lines
  • Minimal CSS churn: reuse existing components/styles; only adjust typography hierarchy and spacing as needed.

Notes​

  • Do not introduce new concepts like “configuration-derived”.
  • Keep language precise: “observed runtime executions” indicates execution-derived evidence without claiming full coverage.