Purpose
- Feature name: CV page (
/cv)
- Why this feature exists: Present an evidence-first CV that connects experience to verifiable artifacts.
Scope
In scope
- timeline entries with role summaries
- proof links to dossiers, ADRs, runbooks, and threat models
- reviewer guidance callouts
Out of scope
- projects registry management (covered in evidence-first content model)
- global navigation and theming
- CV data source populated (timeline entries and proofs)
- docs base URL configured
Procedure / Content
Feature summary
- Feature name: CV page (
/cv)
- Feature group: Core pages and reviewer journey
- Technical summary: Renders timeline data into sections, with proof links built from configured docs URLs.
- Low-tech summary: A resume page that links each claim to evidence.
Feature in action
- Where to see it working:
/cv in the deployed app or http://localhost:3000/cv during pnpm dev.
Confirmation Process
Manual
- Steps: Open
/cv, scan timeline entries, click at least two proof links.
- What to look for: Evidence links resolve correctly and match the described capability.
- Artifacts or reports to inspect: Optional E2E route coverage in CI.
Tests
- Proof links route to incorrect docs sections.
- Timeline entries are missing or render out of order.
Long-term maintenance notes
- Keep proof links current as documentation moves.
- Update timeline entries as experience changes to avoid stale claims.
- Next.js App Router
- React
- Tailwind CSS
Source code references (GitHub URLs)
ADRs
Runbooks
Additional internal references
External reference links
Validation / Expected outcomes
- CV timeline renders without missing sections.
- Evidence links are functional and relevant to each capability.
Failure modes / Troubleshooting
- Broken evidence links: update proof URLs in the CV data source.
- Missing timeline entries: validate data export and rebuild.
References