Pattern computation cost
Loading implementation status…
· Connecting live updates…Current delivery gate
Validation evidence
Implementation
Stages are not equally sized. “In review” means implemented and locally verified, but not landed.
What does one vote read?
Explore an actual run: 14 options, eight same-space voters, 74 keyed votes. The vote update changes one green vote to yellow while the poll UI stays demanded.
| Computation | Runs | Accesses | Link hops | Document-runs | Dependency-runs |
|---|
Recorded measurements, not a live benchmark. Rows show the original top ten; totals include all completed runs. Reactive action bodies only: event dispatch, commit work, and diagnostic reruns are excluded. Document and dependency counts are sums across runs.
The existing tally already uses grouping and memoized lookup. These counts demonstrate visibility into work, not an optimization achieved by this PR. Browser measurements appear below.
Run this fixture
Recorded command
Demo milestones
A vote with the tally on screen
Remote row updates · C1/C3
Four synthetic browser cases pass for nested filters and mapped rows, with same-space and cross-space profiles. Assertions cover remote color changes, profile-only edits, membership additions, removal/restoration, ranking, and first materialization after remote writes.
The runtime fix landed in PR #7265 after CI and review. Reconnect verification remains. No live poll was accessed.
Same functional result, different read budget
Outstanding questions
Reply in our conversation using the question ID. Each question states what, if anything, it blocks.