# ☕ Sunday 2026-08-02 — J-6, the one-before-last KRK rehearsal

Supersedes Saturday's file. `master` clean, **everything pushed** (0 ahead / 0 behind).
`tools/gig-up.sh` = **GO**, 10/10 cold checks.

**The KRKs go home after tomorrow.** Everything below that says "listen" is a thing only
you can settle, and this run plus one more is the whole remaining budget.

---

## The set is 15 tracks now, not 13

Your SSOT ruling got applied for the first time yesterday, and the backlog disagreed with
every tool in the repo. **`ouais_je_funk` and `lime_tacos` are in the set** and have never
been played in sequence. `you_my_sunshine` now comes **before** `mafia_sans_serif`.

That drift had already cost you something audible: preload was warming 50 banks where the
set needs 53, so `dr`, `gfunk_bass` and `h2ogmcy` were lazy-loading off disk on first play.
That is the crackle you heard on the `take_5_drops` transition — the same bug, still live,
just smaller. **Now 54/54 warm.** If you hear crackle on a first play today, it is
something new and I want to know.

`backlog.md` is now the only place you change the set. `gig-up --converge` regenerates the
list and the preload plan from it; a plain `gig-up` fails loudly if they have drifted.

---

## 15 tracks × 90 min = 6:00 each (was 6:55)

Worth feeling on this run specifically — the set got two tracks longer without getting
longer. If it runs over, the encore is the cheapest thing to cut.

---

## Per-track: what to listen for

**NEW** = added since your last run, never heard. Ten tracks have something new in them.

| # | track | bpm | what to listen for |
|---|---|---|---|
| 1 | bombe_dj | 124 | **NEW** riser on d10 |
| 2 | wap | 133 | **NEW** riser on d10 |
| 3 | do_it_right | 89 | the 133→89 drop — deliberate half-time, or does the arc sag? |
| 4 | take_5_drops | 124 | **d5 FIX.** `>\|` → `\|>`: the slice rhythm should now SURVIVE while ^57/^53 change pitch. Before, `slow 4` was replacing the rhythm with one event per 4 cycles. This is the "d5 steals structure" bug — TODO @PLN verify |
| 5 | piment_bresilien | 124 | d10 is Menace, not a riser (relocation deferred — see below) |
| 6 | **ouais_je_funk** | 120 | **NEW TO THE SET.** d10 SynMenace read `gF3 $ gF3`, so *nothing could mute it* — now `gF3 $ gM3`; check the mute actually drops it. 17 idle slots / 10 borrowed |
| 7 | **lime_tacos** | 110 | **NEW TO THE SET.** Cymbales sol moved **d6 → d12** — Tidal 12 is **+9.8 dB hotter** than Tidal 06, so ride the fader, don't re-gain the pattern. **NEW** riser d10. ^44 still linked to d3 on purpose. 23 idle slots, least integrated track in the set. Also the 110 BPM dip mid-block |
| 8 | perfect | 128 | all 12 orbits declared = your **free reset point**, anything can follow anything into it. No d10 riser possible |
| 9 | gimme_acid | 160 | no d10 riser possible (12 orbits). Leaves 3 ghosts behind |
| 10 | vague_de_crime | 120 | the reference riser. 160→120 is the second big drop |
| 11 | you_my_sunshine | 166 | **NEW** riser d10. Your `??TRANSITION???` seam is right before this |
| 12 | mafia_sans_serif | 160 | **NEW** riser d10. Your `?transition?` seam is right before this |
| 13 | desire | 129 | **NEW** riser d10, plus your own edit — lpf sweep out, room 0.4 / sz 0.5 / dry 1.1 in, crushbus 2.5→3.5 |
| 14 | the_revolution | — | no d10 riser possible (12 orbits) |
| 15 | electric_hammer | — | **NEW** riser d10 |

### The 7 new risers are all the same thing

Your designated safe idiom, copied verbatim from `vague_de_crime`:

```haskell
d10 $ gF1 $ gM3 $ mask "<t f!7>" $ "risers:8"
```

1-in-8, so it cannot run away; `gM3` mutes it, `gF1` filters it. **d10 = riser** is now
true in 10 of 15 tracks. The one thing to judge: 1-in-8 was tuned on a 120 BPM track — ask
whether it still reads at 160–166 (`you_my_sunshine`, `electric_hammer`).

---

## Ghosts: 9 of 14 transitions, 18 orphans

The two new tracks actually *helped* — `piment → ouais → lime → perfect` is four clean
transitions in a row, the longest clean stretch in the set.

```
  clean   bombe_dj       → wap
  GHOST   wap            → do_it_right      d7(wap), d9(acidOto3091, vec1_acid)
  GHOST   do_it_right    → take_5_drops     d6(daft)
  GHOST   take_5_drops   → piment           d11(take5), d12(take5)
  clean   piment         → ouais_je_funk
  clean   ouais_je_funk  → lime_tacos
  clean   lime_tacos     → perfect
  GHOST   perfect        → gimme_acid       d6(meth_bass), d7(acidOto3092)
  GHOST   gimme_acid     → vague_de_crime   d9(molotov), d11(vocal_bordel), d12(molotov)
  GHOST   vague_de_crime → you_my_sunshine  d7(crimewave)              ← your ??TRANSITION???
  GHOST   you_my_sunshine→ mafia            d6, d9, d11 (no_sunshine)  ← your ?transition?
  clean   mafia          → desire
  GHOST   desire         → REVOLUTION       d6(aeolian, superzow)
  GHOST   REVOLUTION     → electric_hammer  d7(FMRhodes1), d8(jungle_breaks), d12(like_sugar)
```

Under pressure the answer is `hush` between the two. Both seams you marked with `??` are
ghosting seams — probably not a coincidence, and worth knowing before you fix the order.

---

## What I want from your ears, ranked

1. **take_5_drops d5** — did the fix restore the rhythm, or change the feel in a way you
   dislike? It is the only change that alters an existing sound rather than adding one.
2. **lime_tacos cymbals at +9.8 dB** — fader ride, or does the pattern want re-gaining?
3. **The 7 risers** — right density at 160+?
4. **The two `??` seams** — sunshine before mafia is the truth now; does it play?
5. **Any crackle at all.** It should be gone.

---

## Deferred by choice, your call to overrule

**`piment_bresilien` d10 (Menace) and `ouais_je_funk` d10 (SynMenace) did NOT move.**
You asked me to consider it, and considering it turned up the cost: orbit N is
simultaneously the LCXL column, the Ardour track and the cut/crushbus group. Moving them
means two CC remaps (`^18` → `^17` / `^20`), a cut-group change, and both synths landing
**+8.2 dB louder** on hotter Ardour channels — on material you have not rehearsed since.

And the decider: `perfect`, `gimme_acid` and `the_revolution` use all 12 orbits, so
**d10 = riser caps at 12/15 no matter what**. Paying that cost to go 10 → 12 seemed wrong
six days out. ~20 min if you want it.

---

## Still open on my side

- **#122** — does Tidal resume by itself after a watchdog recovery, or does it need a
  ctrl+enter? Unverified. Until it is, treat watchdog recovery as *half* a recovery: if
  the music does not come back on its own, ctrl+enter in Pulsar.
- **#110** — the full 1h30 safety recording. If this run is being recorded, it may already
  be done.

## Not gig-blocking, but you named it

`python3 tools/set-coherence.py --suggest` already answers "what is this track missing" —
per orbit, with suggestions by role, including the d8 break stacks (`slice/chop`,
`loopAt + rev`). 153 idle slots across the set: `lead=51 perc=33 fx=33 bass=18 kick=12
breaks=6`. Your breaks are the *most* finished part of the set; the leads are where the
empty hands are.
