Problem
The product is feature-first and provenance-forward, burying its actual value: ~10 nav destinations, and on Dependency Graph / Engineering Review the first thing the eye hits is Snapshot ID / Manifest Digest / Canonical Graph Hash in large mono caps. No surface leads with "here are the 3 things you need to understand about this repository."
Proposed Behavior
After analysis, lead with a concise, evidence-backed summary (what it is, key structure, the headline thing to understand) before graph/provenance detail. Keep hashes/schemas/manifest as a one-click "verify" affordance, not the landing strip. Reduce navigation emphasis on non-flagship surfaces.
Scope
Dashboard / repository primary view, Dependency Graph and Engineering Review headers, navigation emphasis. Surfaces that require a snapshot show the consistent "run analysis / no sealed snapshot yet" state.
Acceptance Criteria
- A repository's primary view leads with understanding + decisions, evidence-backed.
- Snapshot identity is reachable via a "Verify / Provenance" control, not shown front-and-center by default.
- Navigation distinguishes the flagship workflow from secondary/upcoming surfaces; "Upcoming" surfaces stay honestly labelled (AGENTS.md).
- Authentic-data rule preserved: no invented summaries; every claim traces to the sealed snapshot.
- Frontend test(s) for the landing layout and provenance toggle.
Priority
P1 - High
Risks and Dependencies
Aligns with the owner's "outcome-first, not feature-first" direction; pairs with #178. No schema change expected.
Problem
The product is feature-first and provenance-forward, burying its actual value: ~10 nav destinations, and on Dependency Graph / Engineering Review the first thing the eye hits is Snapshot ID / Manifest Digest / Canonical Graph Hash in large mono caps. No surface leads with "here are the 3 things you need to understand about this repository."
Proposed Behavior
After analysis, lead with a concise, evidence-backed summary (what it is, key structure, the headline thing to understand) before graph/provenance detail. Keep hashes/schemas/manifest as a one-click "verify" affordance, not the landing strip. Reduce navigation emphasis on non-flagship surfaces.
Scope
Dashboard / repository primary view, Dependency Graph and Engineering Review headers, navigation emphasis. Surfaces that require a snapshot show the consistent "run analysis / no sealed snapshot yet" state.
Acceptance Criteria
Priority
P1 - High
Risks and Dependencies
Aligns with the owner's "outcome-first, not feature-first" direction; pairs with #178. No schema change expected.