Capstone Solution Pack Map
Purpose
Use this map to turn every capstone from an assignment into a portfolio-grade architecture package.
Required solution-pack structure
Every completed capstone should include:
- architecture summary
- system context diagram
- route or workflow matrix
- data and state ownership map
- ADR bundle
- risk and failure matrix
- quality gates
- observability plan
- rollout and rollback plan
- operating ownership
- final review score
Capstone-to-artifact mapping
| Capstone | Must include | Completed examples to reuse |
|---|---|---|
| Production SaaS Dashboard | route rendering matrix, state ownership, modular boundaries, performance budget, export reliability | completed-route-architecture-note, capstone-solution-pack-production-saas-dashboard |
| Performance-Critical Lead Funnel | Core Web Vitals budget, third-party register, experiment policy, attribution uncertainty, rollback plan | completed-performance-budget-example, completed-third-party-script-register |
| Enterprise Design System Platform | component API review, token strategy, accessibility contract, adoption scorecard, migration plan | completed-design-system-api-review, frontend-quality-scorecard |
| Secure and Reliable Account Portal | browser threat model, CSP rollout, sensitive mutation lifecycle, third-party denylist, incident runbook | completed-client-side-security-privacy-review, capstone-solution-pack-secure-account-portal |
| GenUI AI Full-Stack Copilot | component registry, eval matrix, tool policy, trace model, kill switches, launch review | completed-genui-eval-matrix, completed-genui-launch-review |
Grading model
| Area | Weight |
|---|---|
| Decision quality and tradeoffs | 20% |
| Runtime/rendering/data architecture | 15% |
| Security/privacy/accessibility/reliability | 20% |
| Performance and observability | 15% |
| Artifacts and diagrams | 15% |
| Rollout, ownership, and communication | 15% |
Passing bar
A capstone is portfolio-ready when:
- decisions are explained through constraints, not tools
- rejected alternatives are named
- diagrams match the written design
- quality gates are measurable
- failure modes are specific
- launch and rollback are credible
- ownership continues after release
- the final artifact could be reviewed by product, backend, security, design, and platform partners