Proof · Hall of Investigations
Engineering case files—not marketing blurbs.
Each investigation documents what was wrong, how SiteLens helped discover it, the root cause, evidence we kept, and what changed afterward. Add case files to content/investigations.json as you close regressions and product gaps.
How to read a case file
Every entry answers four questions: what was wrong, how it was discovered, what caused it, and what changed afterward. Optional impact tags note why the investigation mattered beyond the immediate fix.
- Summary — why this case file matters at a glance
- Root cause — what was ultimately broken (highlighted when present)
- Evidence — screenshots with explicit Before / After labels on comparisons
- Outcome — bug fix, product improvement, workflow change, or roadmap item