References — bi-02 Architecture & Process Model

Primary sources first. In-tree Chromium docs beat any external source, including these modules.

Primary

Multi-process architecture — the original design document. Still the clearest statement of why.
Inside look at modern web browser — Mariko Kosaka, 4 parts. The best illustrated explanation of process/thread responsibilities.
Process model and site isolation — in-tree, authoritative.
Site Isolation design — the security rationale, including Spectre.

Source

content/browser/ — the browser process
content/renderer/ — the renderer process
RenderFrameHost — the browser-side handle for a frame
Mojo IPC docs — how the processes actually talk

Security boundaries

Sandbox design
The Rule of 2 — untrustworthy input, unsafe language, no sandbox: pick at most two.
Post-Spectre web development — why COOP/COEP exist, and the constraint they place on SharedArrayBuffer (see fe-01 (sibling project)).

bi-11 — Blink scheduling — threads within the renderer
bi-06 — Chromium C++ — reading the process/IPC code
fe-01 — Execution model (sibling project) — the main thread this module puts in context
fe-25 — Frontend security (planned) — the application-level consequences

When a claim here proves stale, record it in PROGRESS.md section 7.