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 e371645
Browse filesBrowse the repository at this point in the historyBrowse files
fix(signals): a later mainline store setter that does not write a held key publishes on the mainline tick — a setter's written keys are its own set, so its notify visits only the keys it wrote (D-8, U-8, #3743)
Copy file name to clipboardExpand all lines: packages/signals/docs/OPEN-QUESTIONS.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ Each is pinned `it.fails`; the ruled screen is in `SCENARIOS.md`. Confirming her
19
19
|**U-5**| D-9 — a landing does not reveal a gate its stale reader re-derives onto a new flight (A15 reveal corollary) |`fuzz-findings-l2.test.ts`, fuzzer finding F2 | it reveals | not measured |
20
20
|**U-6**| D-26 — a stale reader of a held re-guess shows the revealed guess, not the unrevealed one (A17, #3460) |`fuzz-findings-l2.test.ts`, fuzzer finding F5b | shows `1,2` where `1,1` is ruled | needs a per-node slot for the revealed lane value |
21
21
|**U-7**| D-30 — a store row first read after an adoption derives nothing from the hold (#3706) |`adoption-unchanged-key-read-3706.test.ts:278`| built (#3986): the row is paired at that read by the family's key, as the adoption would have paired it; the pin is a plain `it`| not measured |
22
-
|**U-8**| D-8 — a later mainline setter that does not write the held key publishes on the mainline tick (#3743) |`store/unchanged-presence-no-hold-3743.test.ts:491`|it is held | not measured |
22
+
|**U-8**| D-8 — a later mainline setter that does not write the held key publishes on the mainline tick (#3743) |`store/unchanged-presence-no-hold-3743.test.ts:491`|built (2026-10-13): a setter's written keys are its own set, the batch's earlier chained behind (`touch`, store.ts); the notify visits this setter's keys, the fold keeps the batch's union| −41 B brotli / −14 B minified on `+ createStore`|
23
23
|**U-9**| D-14 — a held tree under a re-armed boundary re-derives without a redraw loop |`loading-fallback-in-flush-3540.test.ts:1020`| a redraw loop | Q-2 ruled 2026-10-09 (D-16); the loop is still the deviation |
24
24
25
25
**Answer format that is enough:**`U-1, U-3–U-9 stand, U-6 after 2.0` — or the line you prefer. U-2 is withdrawn with the direction rule's time half (once drafted as F-8; F-2). Q-1 through Q-5 are ruled and carried by the rules. C-1 is D-12. C-2 is D-7. C-3 is D-32.
Copy file name to clipboardExpand all lines: packages/signals/docs/RULES-DERIVED.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,7 +68,7 @@ An `action`'s writes are held until every body in the transaction has returned a
68
68
69
69
While a hold has a proposal for a slot (a staged, unrevealed value), a further write to that slot — the same value or another — is a second suggestion for the same slot, and the two cannot finish at different times: the writer's tick joins the hold and reveals with it. A tick whose writes net to the slot's committed value made no proposal: the slot is not held, pends nothing, and a later write to it is a plain mainline write. A held _derivation_ is not a proposal: a mainline write to a node whose held value is a pass result becomes `prev` for the hold's re-derivation and does not suppress it (`setB(101)` mid-hold, `b` re-derives to `200` under the hold; a `prev`-reading derivation folds the write); a second _write_ is still last-write-wins. Writes apply first, then derivations re-run.
70
70
71
-
**Collapses:**[A34](./SPEC-ASYNC-SEMANTICS.md#a34-a-write-is-a-proposal-one-on-a-held-node-entangles-its-tick-one-that-nets-to-the-committed-value-is-none) (1)–(3), rule B (#3733), #3743 (a store fold's notifications are diffs). **Status:** standing; one store shape pinned `it.fails` (`store/unchanged-presence-no-hold-3743.test.ts`, "a later mainline setter that does not write the held key publishes on the mainline tick").
71
+
**Collapses:**[A34](./SPEC-ASYNC-SEMANTICS.md#a34-a-write-is-a-proposal-one-on-a-held-node-entangles-its-tick-one-that-nets-to-the-committed-value-is-none) (1)–(3), rule B (#3733), #3743 (a store fold's notifications are diffs). **Status:** standing. The store shape — a later mainline setter that does not write the held key publishes on the mainline tick — is built (U-8, 2026-10-13: a setter's written keys are its own set, the batch's earlier setters' chained behind it, so the notify visits this setter's keys and the fold keeps the batch's union; `store/unchanged-presence-no-hold-3743.test.ts`).
72
72
73
73
### D-9. Entanglement is graph-driven; what shares an on-screen async derivation settles as one
0 commit comments