Source Lens and Citation Standards
Purpose
The guide uses local books, official documentation, case studies, and current web research. A source lens should explain how a source changes architecture judgment. It should not be a bibliography dump.
Source lens format
Use this format at the end of substantial chapters:
| Field | What to include |
|---|---|
| Local sources | Which local book families or guide chapters informed the topic. |
| Current sources | Official docs or standards needed for fast-moving claims. |
| Architecture takeaway | What the sources mean for frontend architecture decisions. |
| Verification need | What must be rechecked before updating the chapter. |
Example source lens
## Source lens
- Local performance and browser-networking sources reinforce that latency, main-thread work, request shape, and field reality matter more than framework labels.
- Current platform guidance should be checked for Web Vitals thresholds, React rendering behavior, and browser API support before changing recommendations.
- Architecture takeaway: choose rendering and delivery strategies by route cost, cache safety, and user-perceived quality.
- Recheck when: Web Vitals guidance, framework caching behavior, or browser support materially changes.
Citation rules
- Prefer primary sources for current platform claims.
- Use local book-derived content as synthesis, not copied text.
- Cite fast-moving AI protocol or framework claims only after current verification.
- Do not cite sources for obvious guide-internal recommendations unless the source materially shaped the decision.
- Avoid long quotations; rewrite into architecture guidance.
Fast-moving topics requiring current verification
- React Server Components, React Compiler, server actions, and framework caching.
- Web Vitals thresholds and measurement guidance.
- Browser APIs such as WebGPU, View Transitions, WebAuthn/passkeys, storage, workers.
- CSP, Trusted Types, cookie, CORS, and browser privacy behavior.
- WCAG and accessibility standards.
- AI SDKs, MCP, A2A, AG-UI, A2UI, RAG/eval tooling, and model behavior claims.
Quality checklist
- Does the source lens explain architecture implications?
- Are current claims based on primary sources?
- Are local books used as source material without book-summary phrasing?
- Does the chapter say when not to use the pattern?
- Does the chapter include verification and failure modes?