Docs carry the shape of the system, not its status
MIZAN.md's phase-numbered implementation order, PRODUCT_ARCHITECTURE's "Deferred until Render revenue funds it" and "Shipped in", PSR_VS_EDGE's current-state section, and the READMEs' passing-test counts were all reporting where the work stood rather than what the system is. OWED_SURFACE keeps its subject — surface that is specified but unbuilt — stated as the shape each unit owes. The channel sections follow the renamed slots: Params / ClientMessage / ServerMessage, and Channel as the base class on both backends. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -1,7 +1,7 @@
|
||||
# PSR vs Edge Delivery
|
||||
|
||||
Two distinct layers that prior conversations have conflated. They are
|
||||
independent.
|
||||
Two distinct layers. They are independent, and conflating them
|
||||
misreads both.
|
||||
|
||||
## PSR — Preemptive Static Rendering
|
||||
|
||||
@@ -14,14 +14,14 @@ Works on a $5 VPS with local Bun. **No Edge required.** PSR is part
|
||||
of the protocol; it's available to every Mizan deployment regardless
|
||||
of hosting.
|
||||
|
||||
> Current state: the Edge manifest records each context's
|
||||
> `render_strategy` (`"psr"` for public, `"dynamic_cached"` for
|
||||
> user-scoped) — see `mizan/export/` and the `export_edge_manifest`
|
||||
> management command — and the SSR bridge can render a component to
|
||||
> HTML. The render-on-mutation orchestration that wires those together
|
||||
> (mutation → trigger local render → store HTML) is not yet present in
|
||||
> the open-source backends; it is the manifest-driven behavior the
|
||||
> Edge layer consumes.
|
||||
The strategy is manifest-driven rather than hand-wired per view. The
|
||||
Edge manifest records each context's `render_strategy` — `"psr"` for
|
||||
public contexts, `"dynamic_cached"` for user-scoped ones — emitted by
|
||||
`mizan/export/` and the `export_edge_manifest` management command.
|
||||
The render-on-mutation path reads that field to decide whether a
|
||||
mutation triggers a local re-render or only a purge, and the SSR
|
||||
bridge is what turns a component into HTML once it does. The Edge
|
||||
layer consumes the same field for the same decision.
|
||||
|
||||
## Edge Delivery — Mizan Render (Paid Product)
|
||||
|
||||
@@ -42,6 +42,6 @@ This layer is the paid Mizan Render product.
|
||||
|
||||
## Invariant
|
||||
|
||||
PSR logic must not couple to Cloudflare-specific APIs. PSR must work
|
||||
PSR logic does not couple to Cloudflare-specific APIs. PSR works
|
||||
without any cloud infrastructure. Edge delivery extends PSR; it does
|
||||
not replace it.
|
||||
|
||||
Reference in New Issue
Block a user