Source Map
Purpose
This source map records which parts of the guide depend on stable local source material and which depend on fast-moving platform or AI documentation. Use it before expanding or updating chapters.
Local source families
| Source area | Used for |
|---|---|
Books/Frontend/ browser, performance, security, accessibility, and networking books | Part 0, Part II, Part VI, Part VII, Part VIII. |
Books/Frontend/ React and UI architecture material | Part III, Part IV, Part VI, Part VII, Part XIII implementation patterns. |
Books/ broader architecture, reliability, system design, leadership, and engineering practice material | Part I, Part V, Part IX, Part X, Part XII, learning paths, rubrics, capstones. |
Books/ distributed systems, database, and systems material | Local-first sync, consistency, conflict, caching, durability, and failure-mode guidance in Part III and Part V. |
Resources/learning-notes/ books and papers | Platform engineering, governance, observability, product alignment, and architecture-review operating models. |
Degree-Plan/ curriculum and artifact patterns | Learning paths, capstones, assessment rubrics, review packets, and portfolio outputs. |
Fast-moving source families
| Topic | Primary source type |
|---|---|
| React Server Components, React Compiler, framework rendering behavior | Official React and framework documentation. |
| Web Vitals, performance budgets, browser performance guidance | web.dev and browser vendor documentation. |
| Web APIs such as WebGPU, View Transitions, WebAuthn, storage, workers | MDN and standards documentation. |
| WCAG and accessibility standards | W3C WAI guidance. |
| Browser security and privacy | MDN, OWASP, browser vendor guidance, relevant standards. |
| AI SDKs, GenUI libraries, MCP, A2A, agent frameworks | Official protocol, SDK, and framework documentation. |
| Browser privacy, attribution, cookies, storage partitioning, and measurement APIs | MDN, web.dev, browser vendor documentation, standards discussions, and product-specific compliance review. |
| Client-side security risks | OWASP Client-Side Security Risks, OWASP Top 10, MDN browser security controls, and product-specific threat models. |
Chapter dependency map
| Guide area | Source dependency |
|---|---|
| Part 0 | Local frontend, systems, security, performance, and engineering-practice sources plus current docs for platform/security references. The foundation chapters should stay broad: product/user reasoning, domain/state modeling, browser runtime, verification, production readiness, ownership, and senior-to-architect judgment. |
| Part II | Local browser/networking books plus current browser and protocol docs. |
| Part III | Current React/framework docs plus local architecture material. |
| Part III local-first chapters | Local distributed-systems material plus current browser storage, service worker, Web Locks, and multi-tab coordination docs. |
| Part IV platform engineering | Local engineering leadership and architecture material plus guide-derived governance patterns. |
| Part VI | web.dev/current performance guidance plus local performance books. |
| Part VII | Inclusive component/design-system sources plus current accessibility standards. |
| Part VIII | Security books plus current OWASP/MDN/browser guidance. |
| Part VIII privacy/measurement chapters | Current browser privacy, attribution, consent, analytics, and third-party script guidance plus local security/performance sources. |
| Part XIII | Current AI/GenUI/protocol docs plus architecture synthesis from local books. |
| Part XIII eval governance | Current AI framework/protocol docs plus guide-derived production controls for observability, accessibility, security, and incident response. |
| Learning paths, rubrics, capstones | Derived from the guide itself, Degree-Plan structure, and local architecture/leadership sources. |
| Operating model, maturity model, and scorecards | Derived from guide architecture principles, local engineering leadership resources, production feedback patterns, and current platform/security source synthesis. |
Update rule
When a chapter depends on a fast-moving source, verify the current source before making material claims about APIs, protocols, metrics, or support. When a chapter depends on local books, rewrite into architecture guidance and avoid book-summary phrasing.