One-page reports, RCAs, dashboards and design artifacts. Each preview is a self-contained page hosted on Vercel (access gated by Lawhive team membership). Add yours by creating a folder under the appropriate category — see the README.
Root-cause analyses →
Post-incident investigations and "why did this break" write-ups, with companion architecture / fix proposals.
2 investigations
Sprint reports →
End-of-cycle reports per squad. Cycle metrics, goal status, narrative, what's next.
5 squads
Post-mortems →
Incident write-ups: timeline, impact, what went wrong, what we'd change.
no entries yet
Architecture & design →
Tech grounding docs, ADRs, RFCs, design comps. Anything spatial that doesn't fit a Notion render.
47 docs
Explainers →
Narrated, animated video walkthroughs — watch a system come together a piece at a time, with timestamped comments.
2 explainers
Code analysis →
Living hotspot dashboards — churn vs complexity, maintainability scoring — generated from Lawhive repos.
1 repo
Audits →
Quality & health assessments — design systems, tokens, governance, benchmarks. Scored by inspection, each with a prioritised action list.
1 audit
Service catalog →
Who owns which system, what depends on what, what's at risk. Auto-discovered from git, confirmed by humans. Dependency graph + health register.
42 systems
Research →
Competitive landscapes, market scans, external grounding. What exists outside Lawhive, mapped to what we build.
1 doc
Lean on this when authoring: spatial > linear · immediacy over imagination · user agency through parallel options · scanability through structure. Full framing in the README, with credit to Thariq's HTML effectiveness guide.