Skip to content

refactor(tui): give the workspace one motion clock, with the effort rail its first user - #44

Merged
benjipeng merged 1 commit into
mainfrom
feat/motion-owner
Sep 22, 2026
Merged

benjipeng merged 1 commit into
mainfrom
feat/motion-owner

Conversation

@benjipeng

Copy link
Copy Markdown
Contributor

What

Stage 34, slice 3: the workspace gets one motion clock.

The effort rail owned its own 67 ms deadline, and the activity line was about to need a second. The clock now belongs to the workspace: one deadline, each moving thing answering only whether it is visible, the phase held at the top of view state where any renderer reads it. The effort rail moves exactly as before, and an idle workspace still wakes for nothing.

MOT-1 to MOT-3 move from stage 34's plan into a new motion spec, because code now cites them; EFF-4 and FR-1 point at it instead of naming a clock of their own. MOT-2 stays marked unproven until the activity line moves.

Verified

Local: workspace tests 1618 passed (unsandboxed), clippy -D warnings, fmt, the pre-commit gates, and scripts/smoke-tui.py. No frame changed. CI not yet observed.

…ail its first user

The effort rail owned its own 67 ms deadline, and the activity line was about to need a second.
The clock now belongs to the workspace: one deadline, each moving thing answering only whether it
is visible, and the phase held at the top of view state where any renderer reads it. The effort
rail moves exactly as before. MOT-1 to MOT-3 leave stage 34's plan for a motion spec, because code
now cites them; EFF-4 and FR-1 point at it instead of naming a clock of their own.
@benjipeng
benjipeng merged commit fa8e938 into main Sep 22, 2026
3 checks passed
@benjipeng
benjipeng deleted the feat/motion-owner branch September 22, 2026 20:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant