# Work items — x11-session-research ## Phase 0 — substrate + research question framing **Status: IN PROGRESS.** Substrate doc landed (`phase0_findings.md`). Research question is provisional, awaits operator confirmation. Pre-question Phase 0 deliverables listed below are unblocked. - [x] Predecessor close-out summarised. Substrate doc (`phase0_findings.md`) lists what stays valid from `kwin_overlay_subsurface`, what's specific to Wayland and doesn't transfer, and three plausible outcome shapes (α/β/γ) for the candidate research question. - [ ] **Operator confirms the research question.** Three candidate framings + four alternates are listed in `phase0_findings.md` § "Research question (provisional)". Pick one (or correct the framing) before Phase 1. - [ ] State snapshot of ohm under current Plasma Wayland — the campaign-start *before* photo. Unattended-tractable. - [ ] Inventory of available X11 paths on ohm: installed packages, SDDM-advertised sessions, alternate WMs, XWayland availability. Read-only. - [ ] Inventory of measurement instruments that work under X11. `xtrace`, frame-timing tooling, perf on Xorg PID, etc. Read-only. - [ ] A1 baseline: 1× `kwin_timing_nodebug`-equivalent run on current Plasma Wayland session, captured into `phase0_evidence/wayland_baseline_rep1/`. Same-session anchor for any future X11 comparison. ## Phase 1 — locked research question + binding cells **Pending operator confirmation of the Phase 0 question.** Phase 1 lock will produce `phase1_lock.md` with binding cells specific to whichever framing is locked. ## Phase 2-onwards Pending. ## Discipline carry-overs from `kwin_overlay_subsurface` - *Replicate the baseline first* — per `feedback_replicate_baseline_first.md`. Phase 0 task "A1 baseline" exists specifically because of this lesson; do not skip it. - *Phase discipline* — no patches before source-read is documented. Re-scoping must be honest about deferral target. - *Non-upstreaming default* — bug reports + MRs are explicit operator-tasked decisions. - *Memory persistence rule* — when this campaign reaches its diagnostic terminal state (success or honest closure), update `project_campaign_overview.md` and add any new feedback memory worth carrying forward to the next campaign.