03 — Flows

Summary

The design as sequence diagrams (rendered below): the baseline publish → serve → browser read, where no server does any of the work; the static clone over plain GETs — verified end to end against a real GitHub Pages host; and the fork round trip. The diagrams are the review surface: each one is also a test cell.

Key concepts

• No server did any of the work — the browser walks refs and trees itself, decrypting client-side — the loader is a static file
• Layout sniffed once, then sticky — the clone flow's first read resolves the on-host layout

Key ideas

• The static clone is not aspiration — it is verified against a live Pages host today.
• Every diagram maps to a numbered test cell in 04.

Read the document