You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 24adaff
Browse filesBrowse the repository at this point in the historyBrowse files
| R1 | both orders show `[committed, true]`; not for the hold's own work | A10, D-25, D-27, #3884| D-25 (clarified 2026-10-28) |
28
-
| R2 | the parent waits for a lane's flights; the lane never waits for the parent | F-6, F-1, F-3, 2026-10-01 | F-6 (amended 2026-10-28, `d1b938d3c`) |
29
-
| R3 | an untracked read of a live guess sees the guess, lane held or not | F-11, A17 | F-1 gloss (clarified, `40cde2cd6`) |
30
-
| R4 | a pass reading two holds' display-ahead values is one reveal unit | A15 #3335| D-25 |
31
-
| R5 |`latest()` opens no hold; the pass re-derives once at a park | F-10, D-2, A10 | D-22 |
32
-
| R6 | E8 is an equivalence for render effects only | D-2, F-9 | no change |
33
-
| R7 |`v:0 l:1` through a memo as inline; verdict work shows the screen for plain reads | F-6, D-25, D-26 | D-26, A15 note |
34
-
| R8 |`latest()` of a held first answer reveals; the plain read still throws | D-22, F-9, S-40 | D-22, S-45 |
35
-
| D-27 | stands: a verdict mount is mainline; a plain read is never display-ahead | F-6, F-11 | D-27, Lane vocabulary |
36
-
| F-vlane | today (rebuild §7 reading A): a fallback that went up beside the held frame stays there until the landing (#3540, #4337); the posture, not verdict-lane membership, is the rule; the #3884 clause stands | F-6, D-17, D-25 (#3884) | D-25 — the general paragraph is not yet written: as drafted it contradicted D-25's standing #3884 clause (rebuild §7)|
37
-
| F-leaf | today (rebuild §7 reading A): a pass that read a born node joins, a render effect included, and a node it creates is born held | F-7, A29 ruling A, D-2, D-4 | D-27 (promoted from A29, 2026-10-28), A29 note |
38
-
| F-ahead-posture | today: a mount gated by a display-ahead read is mainline; it is not "ahead" by its creator's verdict posture — only lane work's children live in the lane | F-6, D-27 | no change — D-27 (clarified 2026-10-28) already rules it; rebuild §7 |
| R1 | both orders show `[committed, true]`; not for the hold's own work | A10, D-25, D-27, #3884| D-25 (clarified 2026-10-28) |
28
+
| R2 | the parent waits for a lane's flights; the lane never waits for the parent | F-6, F-1, F-3, 2026-10-01 | F-6 (amended 2026-10-28, `d1b938d3c`) |
29
+
| R3 | an untracked read of a live guess sees the guess, lane held or not | F-11, A17 | F-1 gloss (clarified, `40cde2cd6`) |
30
+
| R4 | a pass reading two holds' display-ahead values is one reveal unit | A15 #3335| D-25 |
31
+
| R5 |`latest()` opens no hold; the pass re-derives once at a park | F-10, D-2, A10 | D-22 |
32
+
| R6 | E8 is an equivalence for render effects only | D-2, F-9 | no change |
33
+
| R7 |`v:0 l:1` through a memo as inline; verdict work shows the screen for plain reads | F-6, D-25, D-26 | D-26, A15 note |
34
+
| R8 |`latest()` of a held first answer reveals; the plain read still throws | D-22, F-9, S-40 | D-22, S-45 |
35
+
| D-27 | stands: a verdict mount is mainline; a plain read is never display-ahead | F-6, F-11 | D-27, Lane vocabulary |
36
+
| F-vlane | today (rebuild §7 reading A): a fallback that went up beside the held frame stays there until the landing (#3540, #4337); the posture, not verdict-lane membership, is the rule; the #3884 clause stands | F-6, D-17, D-25 (#3884) | D-25 |
37
+
| F-leaf | today (rebuild §7 reading A): a pass that read a born node joins, a render effect included, and a node it creates is born held | F-7, A29 ruling A, D-2, D-4 | D-27 (promoted from A29, 2026-10-28), A29 note |
38
+
| F-ahead-posture | today: a mount gated by a display-ahead read is mainline; it is not "ahead" by its creator's verdict posture — only lane work's children live in the lane | F-6, D-27 | no change — D-27 (clarified 2026-10-28) already rules it; rebuild §7 |
39
39
40
40
Every thread on this area reads, before anything else: the precedence rule
41
41
at the top of `RULES-FUNDAMENTALS.md` (a fundamental beats a derived rule
Copy file name to clipboardExpand all lines: packages/signals/docs/RULES-DERIVED.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -206,6 +206,8 @@ An armed boundary catches a lane the same way it catches a transition (D-12, D-1
206
206
207
207
What is rendered from a display-ahead read reveals together with it: an async memo over `latest(x)` holds the `latest` view's reveal until it lands; a combined `isPending(() => [fast(), copy()])` over two async memos, one wrapped in a sync memo, stays `true` until both land, because a memo's value is one shared slot — it computes under its own hold posture, never under the posture of whichever reader pulled it. A node whose fetch a hold is waiting on is that hold's work, not a verdict reader: a pass that re-runs it while its fetch is in flight reads plainly — following the change it is fetching for — even if an earlier pass of it called `isPending` or `latest` (#3884). A memo's posture is what it reads: one that reads a verdict reader's value is a derivation of a display-ahead read, and a verdict reader itself — `createMemo(() => [held(), V()])` with `V = createMemo(() => isPending(x) && latest(e))` shows `V`'s verdict now, beside the screen's `held()`, as the inline probe and a render effect reading both do (#4050: a Provider's children memo over a router shell). **The probe decides the pass's posture in either read order (clarified 2026-10-28):** a pass that probes is a verdict reader whether the probe came before or after a plain read of the same held node — `[x(), isPending(x)]` and `[isPending(x), x()]` both show `[committed, true]` now and re-derive at the landing (A10) — unless the pass is the hold's own work: born in its world (D-27, #4341) or re-run by the write it holds (#3884 above). Those two read plainly; a probe does not rescue them. A pass that read two holds' display-ahead values is one reveal unit of both (A15 lanes corollary, #3335): it waits for either lane's flight, never showing one hold's `latest()` beside a half-computed derivation of the other's.
208
208
209
+
**A verdict posture outlives the pass that asked (ruled 2026-10-28):** a pass that asked (`isPending`, `latest`) is the hold's verdict reader on every later run of its node until one completes having asked nothing — that run still reads as a verdict reader; the next is an ordinary derivation. On each such run its plain read of a node the hold holds is the screen's (a frame reader, A10; re-derived at the landing as A15's stale reader) and it joins nothing, whoever dirtied it — a sync write, a boundary redraw, a landing. The hold's own work is not in this: a node whose fetch the hold waits on, or a pass born in its world, reads plainly whatever it asked before (the #3884 clause and D-27 #4341 above, unchanged). A boundary's display-ahead swap is this posture handed on: an `on` pass that read `latest`/`isPending` is a verdict reader, and the fallback swap it asks for runs as that reader's work — the output's pass reads nothing of the held frame (a pending tree is linked, not read) and its answer, the fallback, is shown now beside the held frame and stays the screen until the landing, instead of being staged with the write's frame as a plain `on`'s swap is (D-15): `[A] → [A + spinner] → [B + spinner] → [B + comments]`, never `[A] → [B + spinner]`. Only the `on` pass's asking counts: `latest()` inside the fallback is the fallback's own display-ahead, not the swap's — a plain `on` over an action-held input lands the swap with the frame whatever the fallback reads (#4337). Today two memories carry this — `CONFIG_VERDICT` left on the node by the pass that probed, and the node's listing in the hold's verdict lane (`fallback`'s `b._lane`, `recompute`'s head) — and the rule is the posture, not the membership. Pins: `tests/loading-on-rearm-3540.test.ts`, `tests/loading-on-frame-following-3540.test.ts` §4–5, `tests/loading-on-latest-fallback-4337.test.ts`.
210
+
209
211
**Collapses:**[A31](./SPEC-ASYNC-SEMANTICS.md#a31-a-memo-computes-under-its-own-lane-posture-never-its-pullers) (#3442), §20.1 question 3 ("Yeah definitely it is held. Consistent with any optimistic update"), OL-R24/R25/R34, recovery 6.2. **Status:** standing. A memo over a verdict memo: `tests/verdict-memo-under-held-memo-4050.test.ts`, `packages/web/test/held-shell-pending-feedback-4050.spec.tsx` (U-10).
210
212
211
213
### D-26. A `latest()`/optimistic reader mounted or re-run mid-hold shows the committed value and reveals with the lane
0 commit comments