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 ce92b78
Browse filesBrowse the repository at this point in the historyBrowse files
Allow fresh mainline computations to publish a coherent committed first frame while a foreign transaction holds their inputs. After publication, continue those inputs through the new computation under the source transaction, including any downstream async work. Preserve normal entanglement for existing computations and mounts without a committed answer.
or authoritative `resolve`/`until` readers. Inputs without a committed answer
91
+
still suspend and follow the born-held/boundary machinery described below.
92
+
Separate new subtrees over separate transactions remain independent. A shared
93
+
continuation that reads multiple held transactions still follows normal memo
94
+
entanglement. This is not a general propagation boundary or a parallel-futures
95
+
implementation. Pinned by `tests/mount-propagation-seam.test.ts`, updated
96
+
creation-time visibility tests, and the compiled nested-Show preview test.
97
+
77
98
**Status:****ruled, amended in place** 2026-09-13 (#3408) — maintainer ruling, Cluster 4 triage: a value derived from the held world is that transaction's work, whichever path first read it; amended 2026-09-14 (creation-time form — "born held"; the entry is the pass's, never the mainline block's); amended 2026-09-18 (#3540, maintainer ruling — boundaries are exempt: a pass under a loading boundary that has not revealed is born held into the transaction and the boundary shows its fallback now)
78
99
**Pinned by:**`tests/held-conditional-memo.test.ts` (#3408: a memo whose branch flips mainline and starts reading a held signal reveals with it, not before); `tests/born-held.test.ts` (creation-time form: fresh memo + effect held, fresh direct effect shows committed, unrelated write after the mount stays mainline, untracked read throws until commit); `tests/visibility-oracle.test.ts` (published column, held and superseded states); `tests/boundary-not-born-held-3540.test.ts` (boundary exemption: a `Loading` mounted mainline over a held value shows its fallback and reveals at the commit; content created behind a fallback is collected, not published; the `on` key lands where its change lands)
79
100
**Mechanism (index, 2026-09-14; boundary exemption 2026-09-18):** `enterStagedRead` on each of `read()`'s value selections that return `_pendingValue` (both fast paths and the slow path) → `globalQueue.initTransition(el._transition)`; no-op for the ambient batch (`_transition` null), the active transaction, and a probe read (`pendingCheckActive`). Creation-time form: outside a flush `enterStagedRead` records the transaction (`stagedEntry`) instead of entering; `recompute` stages the pass's node into it (`_transition` stamped, pushed to its `_pendingNodes`, `STATUS_UNINITIALIZED` kept), adds an effect to its `_gatedSubs` and skips the synchronous first run (`effect()`); `commitPendingNode` initializes it; `read()` holds readers of a node with a staged value and no committed one. Optimistic-posture nodes keep the entering path; verdict pulls (`GlobalQueue._verdictPull` — `latest()`/`isPending()` companions and their pulls) are observations and never enter from mainline (a `latest()` call that entered captured the caller's block, 2026-09-15). Boundary exemption (#3540): `enterStagedRead` takes the staging path inside a flush too when the pass is under a fresh loading boundary (`underFreshLoadingBoundary` — the nearest pending-collecting queue up its chain is uninitialized); `recompute` tells that boundary (`queue.notify` with a `NotReadyError` sourced at the node), which collects the node and shows its fallback; `CollectionQueue._checkSources` keeps a source collected while it is born held (staged, `STATUS_UNINITIALIZED`) and releases it at the commit that initializes it. The boundary's priming read of its tree is a `spectate` read: it records nothing on the mounting pass — no link, no entry — and a born-held tree is simply not ready to it.
0 commit comments