Repository navigation
docs(server-components): A0, the frames rulings and prior art, the plans — with the overnight pass's defaults and the server-half drafts - #3834
Closed
ryansolid wants to merge 7 commits into
Conversation
…ency reds and the size audit's duplicates share (proposed) Draft, marked "proposed — maintainer ruling pending"; no engine changes. The frames/hydration consistency contract (spec/frames-consistency-contract) found thirteen reds across C2, C3, C4, C5, C6, C7, C12 and C17; the SC size audit (size/sc-audit §4) listed the layer's duplicated seams. This document tests the hypothesis that they are the same seams seen from two sides, and drafts the rulings — numbered one-sentence statements in the L2 section's voice, each with the mechanism that carries it today, the state it lives in twice, and the reds it decides — grouped by the three questions the reds cluster on: - Response identity (C5, C6, C17): a response owns what it delivered; a `data` chunk lands in its own response's table or nowhere; a record resolves its refs through its own response's table wherever the frame is bound; a bump drops what the previous version never applied; the shell gate is the bound address's; a switch keeps on screen what was on screen. - Applied state per version (C7, C2, C4): the store is the truth and the applied state is a cache of it keyed by version; a bump re-applies a byte-identical root; a reveal is an apply; applied means shown. - Hydration-done accounting (C3, C12, S1's C3b and `.fails`): done counts every occurrence the document delivered; every frames hold is counted once per frame; a claim owns the fragment's outcome; the client consumes the ids the server consumed. For each: the fix shape as one collapsed carrier (response-owned data cells, records carrying their resolver, one shell gate, one applied record, one hold counter), a byte estimate (− collapse / + carrier) read off the audit's function table, the pins that flip, and what touches public surface or the server half. Two-readings items for the maintainer: 1.4 (narrow/full), 1.6 (per-address gate value vs holds-latest), 3.1 (done counts the page vs the root pass — S1's pin and the contract's contradict). What the rulings do not decide (plain bugs, product questions, the wire) and an order of work gated by the contract's pins and scripts/size. Co-authored-by: Claude via Cursor <noreply@cursor.com>
…19 under seam 3; gate is #3813 Co-authored-by: Cursor <cursoragent@cursor.com>
… data; a frame is one async value outward, its inner boundaries are the server's; 3.1 ruled Co-authored-by: Cursor <cursoragent@cursor.com>
… hold model governs; axioms annotated with the Solid 2 rules they restate Co-authored-by: Cursor <cursoragent@cursor.com>
Per-reading comparison (1.3, 1.4, 1.6, 2.3, 3.1, 3.3, 3.5, 3.6) and per- product-question comparison (C12 (c), settles-once projections, live containers, slot-trails-html) against RSC/Flight+Fizz, Next.js, React Router/Remix, Turbo/htmx, Phoenix LiveView, Qwik, Astro server islands, Marko, Vue and Solid Router. Adds an addressing section (content-keyed vs tree-shaped vs DOM-addressed vs connection-tree) for the maintainer's A3/A4 model, a summary table, and a list of mechanisms the references have that we don't. Primary-source citations; verified vs inferred marked. Co-authored-by: Claude via Cursor <noreply@cursor.com> Co-authored-by: Cursor <cursoragent@cursor.com>
…plan onto the rulings branch (from size/frames-a0-reattribution @ 1e0be39) The plans tonight's correctness pass implements (frames-savings-pass.md Phase A: A0–A6), carried with the code per the maintainer's preference. Squashed from the branch's nine commits; content unchanged. Co-authored-by: Claude via Cursor <noreply@cursor.com> Co-authored-by: Cursor <cursoragent@cursor.com>
…ts, the server-half drafts, the as-landed table What the rulings do NOT decide: the nine readings the 2026-10-06 pass took by default (first flush not start; warm switch-back shows the committed value; the name decides the class on every sync; 2.3's interim with S-flush; 1.2 by the version guard; 3.2 via initBoundaryResume keyed sc:<fid> while in progress; 3.3's dev report; S-adopted documented; the harness's C3 dispose exemption), each with its alternative. The server half: C13's delimiter with the client's one-write status, the plain-response streaming bound (complete.bound), C12 (c)'s error template located in finalizeError/the done closure with the two decisions the server PR must make. Order of work: the as-landed table (#3830–#3833), what each step left undone. Public surface: landing, hold, holdBoundary, the behaviour notes. Co-authored-by: Claude via Cursor <noreply@cursor.com> Co-authored-by: Cursor <cursoragent@cursor.com>
|
Member
Author
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Draft — frames correctness pass, step 6 (docs). Stacked on #3830 so the A0 documents ride with the first code PR rather than alone (the maintainer's preference). Seven commits: the four
spec/frames-rulingscommits cherry-picked as they are (frames-rulings.md; the A0 axiom and annotations inserver-components-principles.md), thespec/frames-rulings-prior-artcommit cherry-picked (frames-rulings-prior-art.md), the two plan documents fromsize/frames-a0-reattribution@1e0be39d9brought over as one commit (frames-a0-reattribution.md,frames-savings-pass.md— content unchanged), and one commit of tonight's additions toframes-rulings.md(201 lines; no reformatting of the existing text — the repo's prettier does not run on markdown, so the first attempt's*→_churn was reverted):start(C17 a); the warm switch-back shows the committed value; the occurrence's name decides its class on every sync; 2.3's interim landed with S-flush (and why — the accidental poll); 1.2 by the version guard; 3.2's registration keyedsc:<fid>while hydration is in progress (and its ≈ +59 B cost); 3.3's dev report; S-adopted documented; the harness's C3 dispose exemption.complete.bound: "yields" | "time", additive, RFC 11 addendum); (iii) C12 (c)'s error template — the gap located inserver.ts'sdoneclosure andsolid/src/server/hydration.ts'sfinalizeError, the shape (render the nearest server<Errored>'s fallback into the<Loading>'s position; with none, the frame's:error), and the two decisions the server PR must make (the position rule; hydration ids and head/asset handling of the rendered fallback).preview/stage's client half;hydrateWindow/R.claim; the 3e port; R.reveal's readiness model; the per-response cell, S-ref, S-record; S-adopted).FrameHost.landing,FrameOptions.hold,sharedConfig.holdBoundary, the behaviour notes, and what stays untouched pending 1b.No code.
rules-index --checknot run (no signals rules cited).Decision made by default: the plan documents (
documentation/plans/frames-a0-reattribution.md,frames-savings-pass.md) were brought as one squashed commit rather than nine cherry-picks — they are plans, not rulings; the brief named only the rulings and prior-art documents, and these are the plans the pass implements. If the maintainer prefers their own history, the branch issize/frames-a0-reattribution.