Operator's stance, recorded verbatim in
memory/project_no_upstreaming_philosophical.md: the AI-slop-buster
review climate in 2026 open-source maintainership makes submission
cost > benefit when personal requirements are met. Multiple iterations
of substantive work (sonnet pre/post-commit reviews, formal pixel
verification, regression test harnesses, clean commit history) don't
necessarily survive first contact with reviewers who treat
AI-assisted = automatic slop regardless of substance.
Track D was carried iter3+4+5+6 as a possible culminating iteration.
Dropped 2026-05-06.
Distinct from the prior feedback_no_upstream.md rule (which was
procedural — "no PR without explicit instruction"); the new memory
entry records the underlying philosophical reason. Procedurally,
the new instruction is "don't ever, regardless."
Reopen criterion documented in the memory entry: operator may change
mind if the climate softens, or if a trusted maintainer signals
"send it." Until then, none.
Remaining iter8+ candidate: E (performance binding cell) only.
Plus iter7 carries (low priority): STREAMON-on-context-recreate,
pool-size parameterization, fault-inject build for slot-leak.
Plus separate top-level campaigns: fourier-fresnel, panvk-bifrost.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
PineTab2 is Rockchip RK3566 silicon, not RK3568. The hantro driver
attaches via the rockchip,rk3568-vpu DT compatible because RK3566/
RK3568 silicon is close enough to share that variant. The proper
RK3566 mainline driver target (rkvdec2 / vdpu346) has no kernel
support yet — Christian Hewitt's patch series LKML 2025/12/26/206
is unmerged.
Updated operative docs to use the consistent form:
"PineTab2 (Rockchip RK3566 silicon; hantro driver via the
rockchip,rk3568-vpu DT compatible)" or shorter variants.
Files updated:
- README.md (campaign top-level): TL;DR, deliverable, KWin link,
hardware target, hardware listing
- firefox-fourier/README.md: tested-on line
- phase8_iteration7_close.md: hardware carry
- phase8_iteration6_close.md: hardware carry, MPEG-2 drop
rationale
- phase0_findings_iter7.md: predecessor summary, fourier-fresnel
description, hardware carry
- phase2_iter7_situation.md: msync hypothesis hardware reference
Historical iter1-iter5 phase docs left as-is — they're snapshots
of what the campaign believed at the time. The canonical source
for the silicon-ID correction is track_F_research_2026-05-06.md
(commit 358801b).
Not a correctness change. The campaign's empirical evidence is
unaffected — the hantro/rk3568-vpu driver path that we exercised
was always the actual decode path on PineTab2 silicon.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
claude-noether