Files
git.stella-ops.org/docs/qa
master 2b1ea0b1da Full product deep dive: 28 surfaces evaluated, 10 UX issues, 3 strategic recommendations
Walked through every product surface as a DevOps/Security engineer:

TIER 1 (Ship-ready, 10 surfaces):
  Triage workspace (10/10), Integrations Hub (9/10), Advisory catalog (9/10),
  Doctor diagnostics (9/10), Data Integrity (8/10), Disposition/VEX (8/10),
  Policy Studio (8/10), Evidence Overview (8/10), Replay & Verify (8/10),
  Export Center (8/10)

TIER 2 (Good, needs polish, 13 surfaces):
  Security Posture (6/10), SBOM Lake (7/10), Reachability (7/10),
  Supply Chain (7/10), Deployments (7/10), Hotfixes (7/10), Ops Hub (7/10),
  Feeds & Airgap (7/10), Promotions (7/10), IAM (7/10), Trust (7/10),
  Branding (7/10), Usage (7/10)

TIER 3 (Needs work, 5 surfaces):
  Dashboard (5/10), Security Reports (5/10), Release Health (5/10),
  Unknowns (4/10), JobEngine (5/10)

Cross-cutting findings:
  F-NAV: Navigation terminology doesn't match user mental model
  F-DATA: Seed data mixed with real empty state inconsistently
  F-FLOW: No clear happy path connecting scan→gate→release→evidence
  F-SEARCH: Command palette doesn't index security terms

Strategic recommendations:
  1. Make "Scan Image" the first visible action
  2. Connect the chain: Registry→Scan→Findings→Gate→Release→Evidence
  3. Eliminate all demo data — every number real or honestly "0"

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-16 12:25:53 +02:00
..
2026-02-12 10:27:23 +02:00