Research Backlog
Purpose
Use this backlog to track future improvements that need research before becoming guide content.
High-priority backlog
| Topic | Why it matters | Suggested output |
|---|---|---|
| React Compiler production adoption | Changes memoization and performance guidance. | Expand Part VI with compiler profiling, migration fixtures, and rollback criteria. |
| Server Actions and mutation boundaries | Affects form, data, and security architecture. | Initial Part III chapter added; next pass should add framework-specific worked examples and tests. |
| AI eval infrastructure | Required for production GenUI and agents. | Deepen Part XIII and GenUI capstone. |
| MCP security patterns | Tool integrations are becoming a browser/product risk. | Expand MCP/A2A chapter and review packet. |
| Browser privacy and attribution | Impacts funnels, analytics, experiments, and SSO. | Initial Part VIII chapter added; next pass should add a completed measurement registry example. |
| Local-first sync | Important for offline and collaboration products. | Initial Part III chapter added; next pass should add a capstone or completed sync design. |
| Frontend platform adoption | Determines whether architecture guidance becomes team behavior. | Initial Part IV chapter added; next pass should add scorecard examples and migration plans. |
| Part 0 foundation exemplars | The foundation section is stronger with maps and baselines, but needs completed example artifacts. | Add completed route architecture note, state ownership map, readiness packet, and weakness-diagnosis example. |
Medium-priority backlog
| Topic | Why it matters | Suggested output |
|---|---|---|
| WebGPU in product UIs | Enables advanced visualization but adds complexity. | Future radar update and advanced platform exercise. |
| View Transitions API | Changes route transition architecture and accessibility. | Add design-system recipe. |
| Passkey UX | Auth architecture increasingly includes WebAuthn. | Expand auth/session chapter. |
| Module federation maturity | Still relevant for microfrontend decisions. | Refresh Part IV microfrontend chapter. |
| Edge AI inference | Could affect personalization and GenUI latency. | Add future radar item after source verification. |
| Session replay privacy controls | Common source of accidental sensitive-data capture. | Add completed incident drill and masking/blocking test examples. |
| Web storage durability and quota | Local-first products need realistic browser storage assumptions. | Add browser-storage appendix with failure modes and test strategy. |
| Completed artifact library | Readers need calibrated examples, not only blank templates. | Add completed ADRs for RSC migration, third-party script governance, design-system API, and GenUI launch. |
| Architecture operating model case study | Teams need to see how governance changes over time. | Add 90-day and 180-day operating-model case studies with scorecards and exception registers. |
| Client-side security monitoring | OWASP client-side risks include logging/monitoring gaps and JavaScript drift. | Add CSP report triage, script drift detection, and sensitive-event rejection examples. |
| Full capstone solution depth | All capstones now have solution-pack coverage, but three are lighter than the SaaS/account packs. | Expand performance funnel, design-system, and GenUI solution packs with full ADR bundles and review packets. |
| System design worked answers | The answer playbook exists, but prompt-specific completed answers are still thin. | Add full worked answers for SaaS dashboard, observability, offline field app, and GenUI copilot. |
| Remaining worked system design answers | SaaS dashboard, observability, and GenUI now have worked answers. | Add worked answers for lead funnel, offline-first field app, and enterprise design system. |
| Case-study cleanup | Several case studies still read like short prompts rather than incident-grade narratives. | Rewrite Part XI case studies with timeline, symptoms, root cause, decision points, and prevention controls. |
| Docs QA automation | docs:check now covers short chapters, placeholder markers, frontmatter/title/sidebar position, duplicate slugs, broken local markdown links, and missing practice/review/source sections. | Future improvement: add source-lens coverage reports by section and optional strict mode for CI. |
| Docs QA warning cleanup | npm run docs:check is currently clean after the warning cleanup pass. | Keep it clean as new chapters are added. |
Backlog acceptance criteria
A backlog item can become guide content when it has:
- primary sources or strong local source material
- clear architecture implication
- decision criteria
- failure modes
- verification method
- at least one exercise or review prompt