Files
Hermenix 4b5cb5197a docs+examples: log the cursor marker as open, and film each desk on its own
The marker is now written up as the *open* item rather than a research note: it
is not implemented, the video went out without it, and everything else about the
pointer is exact and readable.

proof-video.py is rewritten for desks, one command, no arguments. It films the
session's own output with `record --output` instead of the published socket --
with desks, the socket carries every output stitched together, so a viewer would
watch two thirds wallpaper. The scrolling beats are real pointer axis events,
down twice and back up once, so the movement cannot be mistaken for a page that
merely loaded a different part of itself.
2026-10-03 19:54:08 +00:00
..

TODO

Known, unfixed problems — each one real, none of them guessed at.

Each file answers three questions and stops:

  • The issue — what is actually wrong, with the evidence for it.
  • Ideas — more than one, and which one is the recommended route.
  • Why it matters — the impact, not the principle.
item severity state
cursor-visibility-in-captures high answered: the compositor draws no cursor for a virtual pointer. Needs a decision on an overlay marker
scroll-has-no-compositor-proof medium works live; unproven in a gate
reconcile-while-containers-are-off medium partly fixed: discovery now survives a restart; teardown still lives inside the feature
kill-can-leave-the-app-alive medium found by counting windows, not sessions

Closed since this folder was written:

  • "Containers do not bind" — fixed. Windows are assigned by the pid the compositor reports, moved onto their desk's workspace and read back. Two sessions now hold two outputs with a real browser on each.
  • "The pointer is unusable while containers are off" — fixed with it. The pointer aims at the session's desk, and desks hold applications.
  • "Discovery refuses when two compositor instances exist" — fixed. Each candidate is asked for its version and the one that answers is used.

Severity here means "how much of the feature is actually delivered", not "how loud the failure is". The highest is highest because a whole class of work is blocked on it: the pointer is exact and invisible, so nothing can show where anything happened.

When one of these is fixed, delete its file and the row — this folder is a list of what is still true, not a history of what was thought.