Point your AI
(Codex recommended)
at this site.

You are helping with a Pioneer DJ CDJ-3000 Gate Cue + preprocessed Stems research project. Proceed only after the user confirms they own or control the deck and authorizes this research; this copied prompt is not write authorization. Do not write to the deck until you have completed a read-only inventory and the owner has approved the exact next stage.

KNOWN RESULT
- Gate Cue was validated on one physical CDJ-3000 running exact OEM firmware 3.22.
- Target: EP122 revision 15034.
- EP122 SHA-256: 33c093bdc4fbdaeb191942fa39fe1ca5ca8426440981b93d785d517934af52bc.
- This did not transplant CDJ-3000X firmware. Research found dormant behavior in CDJ-3000 EP122 and enabled the tested hold/release and PLAY-to-latch interaction through three guarded behavior hooks, then added one guarded native player-info paint hook for an on-screen Gate Cue toggle. Full 3000X parity is not claimed.
- The native UI is physically validated: a stock-like blue/dark GATE CUE pill toggles the behavior on and off, and the enlarged full-width touch target works over nested stock child components.
- Firmware 3.14 was the validated root entry point, not the Gate Cue target. The successful deck was rooted on official 3.14 and then updated with the untouched OEM 3.22 updater; root survived on that deck.
- The R16 Stems prototype was physically validated on the same research deck with one prepared track. It is not on-device AI separation and is not a universal track workflow.
- Separation happens off-device. The exported media contains the normal Rekordbox full track, an exact sample-aligned 96 kHz floating-point vocal sidecar, and prepared vocal waveform analysis.
- Runtime mixing is lightweight: BOTH = full mix; VOCAL = sidecar; INSTRUMENTAL = full mix minus the aligned vocal sidecar. The rear USB connection supplies no audio processing or compute.
- Critical media-path finding: the front USB may mount at /media/usb/sda1 or /media/usb/sdb1. Discover and validate the actual mount; never hardcode one. Hardcoded sdb1 rendered the Stems tab but left it unresponsive when the physical deck used sda1.

FIRST QUESTIONS
1. What exact firmware does the deck display?
2. Is root/SSH already working, and how was that verified?
3. Is this unit covered by AlphaTheta's hardware notice requiring firmware 3.17 or later?
4. Does the owner have stable power, backups, recovery media, and the lawful OEM update inputs?

ROUTING RULES
- Rooted 3.22: candidate only; create a fresh private unit profile and new build, then follow the staged validation sequence.
- Official 3.14: cdj3k-root v3.14 is the known root prerequisite, provided the hardware is eligible. After backup/root verification, remove experiments, use untouched OEM 3.22, boot stock, and verify root survived.
- Unrooted 3.22: STOP. This project has no validated root or installation path and does not validate downgrading to 3.14.
- Any other firmware, revision, hash, or affected newer hardware: STOP. Report the unsupported state and perform new research; do not reinterpret nearby versions as compatible.

NON-NEGOTIABLE CHECKS
- Confirm CDJ-3000 / OEM 3.22 / EP122 rev 15034 / the full SHA-256 above.
- Confirm all four vtable slots, original targets, and 16-byte function guards from the guide before patching.
- Abort on any mismatch. Never use another deck's DSO or private profile.
- Derive DSO hook-symbol offsets from the newly built artifact; prior offsets are not portable constants.
- Never create W+X memory. Patch transactionally RX→RW→RX and roll back on failure.
- Default to stock. Disabled beats persistent; malformed or missing state means disabled; unexpected exit persists disabled; keep a maintenance bypass.
- Keep serial, eMMC CID, SSH/owner keys, host keys, activation tokens, and device dumps private and gitignored.
- Require the owner to supply lawful OEM inputs and local extraction capability. This guide supplies neither firmware nor keys.
- Do not distribute OEM firmware, extracted EP122, decrypted rootfs, keys, music, Rekordbox data, or a unit-bound binary.

STEMS PROTOTYPE CONTRACT
- Treat R16 as a one-track proof of concept, not a release-ready stem engine or universal compatibility claim.
- Preprocess on a computer. Require the exact normal Rekordbox full track, exact sample-aligned 96 kHz float vocal sidecar, and prepared vocal waveform data expected by the build.
- Gate loading on exact media identity/hash, unit binding, OEM 3.22 / EP122 rev 15034 fingerprint, sidecar format/length, and safe readable paths. Any mismatch means stock/full-track behavior and a clear diagnostic—not a best guess.
- Discover removable media under both /media/usb/sda1 and /media/usb/sdb1, then prove the selected root contains the expected track and sidecar. Do not create a temporary alias as a permanent fix.
- Diagnose tab-rendered-but-unclickable by checking media readiness first: sidecar discovery, hash, format, mount path, and state flags. On the physical deck, the wrong hardcoded mount was the cause.
- Emulator first: test Both, Vocal, Instrumental, waveform swaps, pause/play, tab switching while playing and paused, media missing/malformed, hash mismatch, and rollback before staging hardware.
- Stage disabled first; use a separately authorized one-shot physical test; prove stock return; only then discuss persistence. Keep Gate Cue independently reversible.
- Do not redistribute the test track, sidecar, Rekordbox database, waveform analysis, or any other copyrighted/private media artifact.

NATIVE UI IMPLEMENTATION CONTRACT
- Add the UI only to the exact EP122 profile above. Hook NormalPlayerInfoWidget paint at slot 0x216e990, expected target/guard address 0x166f178, guard fd7bbca9e2fffff042803f91fd030091. Call stock paint first.
- Exact embedded JUCE entry points for this build: Graphics::setColour 0x01aed0d0, Graphics::fillRect 0x01aed610, Component::internalRepaint(Rectangle<int>) 0x01bc4300, Component::addMouseListener(MouseListener*, bool) 0x01b7c590. Treat these as guarded firmware-profile facts, not portable JUCE ABI.
- In the 1280x240 player-info strip, draw x=752, y=32, width=104, height=40; for the full layout when component height is at least 600, use y=478. Use a rounded blue active pill (ARGB 0xff007de1) and a dark bordered inactive pill. Render compact GATE CUE text without depending on a new font.
- Use an enlarged centered touch rectangle x=726, y=12, width=156, height=80. It must stay above the overview waveform. Do not infer the hit target from the visual rectangle alone.
- Register a process-lifetime MouseListener once with wantsNestedChildren=true. A parent-only mouseUp hook is insufficient because stock tempo/player-info children intercept part of the button.
- Translate MouseEvent coordinates from eventComponent through the parent chain before hit-testing. Validated EP122/JUCE object offsets are Component parent +0x18, local x/y +0x20/+0x24, width/height +0x28/+0x2c; MouseEvent x/y +0x08/+0x0c and eventComponent +0x28. Bound traversal depth and refuse unknown geometry.
- Store the UI enable state atomically. On OFF, reset any active gate session and route Hot Cue change/release and PLAY exactly to stock. On toggle, repaint the visual button rectangle explicitly.
- Test the UI in the emulator at left, center, right, top, and bottom edges, including clicks delivered by nested children. Then use disabled-first staging and a separately authorized one-shot physical test before persistence.

REQUIRED PHYSICAL SEQUENCE — DO NOT COLLAPSE APPROVALS
1. Build and test off-device with user-supplied inputs.
2. Stage overlay disabled.
3. Reboot and prove normal stock operation.
4. Ask separately before arming one atomic one-shot boot.
5. Owner tests Gate Cue and baseline controls.
6. Restore disabled, reboot, and prove stock return.
7. Ask separately before enabling persistence.
8. Document and test complete removal before any later OEM update.

Start by reporting the detected state and whether it is supported. If it is unsupported, stop safely rather than proposing a downgrade or bypass.