marfrit/x11-session-research
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Campaign-contained data discipline + repo notice

Browse Source 
Operator directive 2026-05-03: this campaign acquires all its
own measurement data from scratch. Predecessor numbers are
documented for context but never imported as binding cells,
comparison targets, or success thresholds. The lesson the
predecessor (kwin_overlay_subsurface) closed-without-patch on
is exactly that: phase 1 cells anchored to a single historical
ohm_gl_fix Phase 0 measurement, three weeks of phase planning
on a baseline that didn't reproduce in-session.

The strongest version of feedback_replicate_baseline_first.md:
"don't import predecessor data, acquire it fresh." The discipline
is now documented as a governing rule in three places:

- README.md § "Campaign-contained data discipline"
- phase0_findings.md § "Campaign-contained data discipline
  (governing rule)"
- worklist.md § "Governing rule (every phase)"

Concrete consequences:
- A1 baseline (Phase 0 task) is now mandatory at N=3 reps.
  Single-rep wasn't enough to surface session variance in the
  predecessor; doing 3 up front makes the baseline robust to
  the same kind of session-state drift that ate the
  predecessor's premise.
- Phase 1 thresholds are drawn against the A1 baseline measured
  in this campaign, not against any predecessor number.
- metrics.csv (when it lands) only carries data from this
  campaign's reps. No predecessor rows imported.

README.md additionally:
- Adds the predecessor chain (ohm_gl_fix -> kwin_overlay_subsurface
  -> this campaign) with explicit "what stays valid for source-
  reading" vs "numbers that don't" separation.
- Calls out durable substrate available from predecessors:
  KWin scanout-promotion archaeology, measurement-protocol
  template, WAYLAND_DEBUG parser. All structural; none
  measurement-numerical.
- Carry-over predecessor system state on ohm (governor pin,
  baloo disabled, fourier packages) is explicitly distinguished
  from measurement data. System state inherits; data does not.
- Repository line points to the gitea remote
  ssh://gitea@git.reauktion.de:2222/marfrit/x11-session-research.git

phase0_findings.md additionally:
- Reframes the predecessor-close-out summary section header to
  "(context, not data)" and rephrases past-tense numbers so
  none are stated as "the baseline."
- Adds the discipline lesson narrative in-line before the
  predecessor close-out: a 30-minute N=3 same-session baseline
  on day 1 of the predecessor would have made the campaign
  different — and that's the move this campaign starts with.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Markus Fritsche
2026-05-03 06:59:06 +00:00
parent ac301b4e48
commit e8bae670d3
3 changed files with 215 additions and 57 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+121 -28
View File
@@ -5,7 +5,8 @@
> "Research question (LOCKED 2026-05-03)". Phase 1 still
> requires the four pre-question Phase 0 deliverables
> (state snapshot, X11 path inventory, browser-overlay-path
> inventory, baseline anchor) before binding cells lock.
> inventory, **own** baseline anchor) before binding cells
> lock.
**Research question:** Does cutting out the KWin compositor
enable faster video display of Brave, chromium-fourier, and
@@ -27,35 +28,117 @@ The matrix is 3 browsers × 2 decode paths × 2 sessions = 12
cells (some N/A where libva isn't supported). See
`phase0_findings.md` for the full table.
## Predecessor
## Campaign-contained data discipline
This campaign exists because
[`../kwin_overlay_subsurface/`](../kwin_overlay_subsurface/)
closed 2026-05-03 without patch (`phase8_handover.md`). Its
diagnostic loop terminated at "Phase 0 cage = 0 post-warmup
drops floor not reproducible at N=3." The natural next move
across the design surface is to vary the display server (X11
instead of Wayland) on the same hardware and the same client
binary, but the operator has not yet confirmed that as the
campaign's specific question.
**This campaign acquires all its own measurement data from
scratch in this session. Numbers, baselines, and verdict
thresholds from predecessor campaigns are NEVER imported as
binding cells, comparison targets, or success criteria.**
## Hardware target (provisional, same as predecessor)
Predecessor campaigns are documented for *context* — what
question was asked, what file:line pointers stay valid for
source-reading, what tooling/state on ohm carries over. But
their *measurement numbers* (drop counts, perf percentages,
Δ_present medians, kwin %CPU values) **are reference history
only, not data this campaign relies on**.
The discipline lesson is concrete:
[`../kwin_overlay_subsurface/phase8_handover.md`](../kwin_overlay_subsurface/phase8_handover.md)
closed 2026-05-03 without patch because its Phase 1 binding
cells were anchored to a single historical measurement
(`ohm_gl_fix` Phase 0: cage = 7 drops total / 0 post-warmup).
That baseline was treated as a stable property of the
hardware × software stack and the campaign's whole phase
plan was built around closing the gap to it. When the same
condition was re-measured at N=3 in the closing session of
the campaign, none of the three reps reached 0 post-warmup
drops; the median was 26. The campaign's premise didn't
hold up to in-session replication, three weeks of phase
planning ended at Phase 8 close-out, and the lesson is now
[`feedback_replicate_baseline_first.md`](../kwin_overlay_subsurface/.claude/projects/-home-mfritsche-src-kwin-overlay-subsurface/memory/feedback_replicate_baseline_first.md)
in this session's memory.
This campaign acts on that lesson by stronger discipline:
- Every Phase 1 binding cell anchors to data acquired in
this campaign's session.
- Predecessor *measurements* never appear in
`metrics.csv`. Predecessor *file:line source-reads,
protocol designs, parser scripts* may be referenced or
re-used as durable substrate.
- The Phase 0 "A1 baseline" rep is not optional. It is the
Wayland-with-KWin reference rep acquired at the start of
this campaign, against which the X11 cells of the matrix
will be compared. The predecessor's matching numbers are
not used as a substitute even if they look identical.
- If a measurement instrument behaved one way in a
predecessor campaign, that behavior is re-verified here
before being relied on (see Phase 0 X11 measurement-tool
inventory).
If a measurement in this campaign happens to match a
predecessor's number, that's a useful corroboration of
reproducibility — but it cannot substitute for in-session
acquisition.
## Predecessor campaigns
This campaign is the third in a chain on the same hardware
target:
1. [`../ohm_gl_fix/`](../ohm_gl_fix/) — closed 2026-05-02.
Diagnosed and patched the Step 1 (`libva-v4l2-request`)
and Step 2 (Chromium `WaylandBufferManagerHost`
overlay-route) issues. Spun off the Wayland-compositor-
path question into a separate campaign because that
question had a different code surface, upstream, and
reviewer culture.
2. [`../kwin_overlay_subsurface/`](../kwin_overlay_subsurface/)
— closed 2026-05-03 without patch
(`phase8_handover.md`). Diagnostic loop terminated at
"Phase 0 cage = 0 post-warmup drops floor not
reproducible at N=3" — the inherited baseline turned
out to be N=1 historical and didn't replicate in-session.
3. **This campaign** (`x11-session-research`) — opened
2026-05-03. Tests whether bypassing the KWin compositor
via X11 + non-compositing WM avoids the forced
NV12 → RGB GL-composite step the predecessor identified
as a structural Wayland constraint on rockchip-drm.
Durable substrate from the predecessors that this campaign
*may* read (not import-as-data):
- `kwin_overlay_subsurface/phase2_source_findings.md` —
KWin scanout-promotion archaeology (Plane 39 / Plane 45
format/modifier table on rockchip-drm RK3568); Phase 2-prime
Shape C source-read of `Display::dispatchEvents` and
`TransactionFence` (Wayland-side, doesn't transfer to X11
but illustrates the per-frame dispatch shape).
- `kwin_overlay_subsurface/phase3_protocol_prime.md` — the
measurement-protocol structure (operator-vs-Claude split,
pre-registered hypothesis, falsification table, evidence
layout). The structural template is reusable. The specific
numbers and threshold values **are not**.
- `kwin_overlay_subsurface/scripts/wayland_debug_to_csv.py` —
parser for libwayland WAYLAND_DEBUG output. Useful for the
Wayland cells of this campaign's matrix; an X11 equivalent
is yet-to-build.
## Hardware target (same as predecessors)
ohm — PineTab2, Rockchip RK3568 (4× Cortex-A55, Mali-G52 MP2,
hantro G1/G2 VPU). Kernel `6.19.10-danctnix1-1-pinetab2`.
Mesa 26.0.5. Currently runs KDE Plasma 6.6.4 Wayland.
For an X11-session campaign, ohm needs an Xorg + Plasma X11 (or
similar X11 desktop) install path verified. As of 2026-05-03,
the only confirmed display path on ohm is
`startplasma-wayland`. **Whether Plasma X11, an alternate X11
desktop (XFCE, openbox, lightweight WM), or Plasma running
under a Wayland-Xorg shim is in scope is part of the research
question to be locked.**
For an X11-session campaign, ohm needs an Xorg + non-compositing
WM install path verified. As of 2026-05-03, the only confirmed
display path on ohm is `startplasma-wayland`. Phase 0 inventory
will catalog what's installed, what'd need installing, and
what SDDM-advertised sessions exist.
## Carry-overs from predecessor (still active on ohm)
## Carry-overs from predecessor (system state, not data)
Per `kwin_overlay_subsurface/phase1_evidence/ohm_tooling_revert_log.md`:
Per `../kwin_overlay_subsurface/phase1_evidence/ohm_tooling_revert_log.md`:
- `qt6-base-fourier 1:6.11.0-3` installed.
- `kwin-fourier 1:6.6.4-3` installed.
@@ -65,19 +148,29 @@ Per `kwin_overlay_subsurface/phase1_evidence/ohm_tooling_revert_log.md`:
- `drm-info 2.9.0-1` installed.
These were not reverted at the predecessor's close-out. This
campaign inherits them unless an explicit revert is part of
the design.
campaign inherits them as **system state**, distinct from
**measurement data**. A different system state (e.g. a fresh
Plasma session, or the same packages but different uptime)
might produce different measurements; this is exactly why
in-session baseline acquisition matters.
## Non-upstreaming default
Inherited from the predecessor and from `ohm_gl_fix`. Bug
reports + MRs are explicit operator-tasked decisions, not
background process steps.
Inherited from the predecessors. Bug reports + MRs are
explicit operator-tasked decisions, not background process
steps.
## File map (will grow)
| File | What it is |
|---|---|
| `README.md` | This file. |
| `phase0_findings.md` | Substrate from the predecessor + the candidate research question. **Awaits operator confirmation/redirect on the question itself.** |
| `worklist.md` | Phase-by-phase task list. Phase 0 only as of campaign start. |
| `phase0_findings.md` | Locked motivation + experimental matrix + open questions before Phase 1. |
| `worklist.md` | Phase-by-phase task list. |
| `phase0_evidence/` (created when first run lands) | Phase 0 inventory + A1 baseline rep. |
## Repository
`ssh://gitea@git.reauktion.de:2222/marfrit/x11-session-research.git`
(public). Cloned/pushed via SSH on port 2222 per the home-infra
gitea convention.