| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| api | ||
| escales | ||
| manifeste | ||
| semaphore | ||
| tasks | ||
| tide-table | ||
| ui | ||
| .gitignore | ||
| DESIGN.md | ||
| PRODUCT.md | ||
| README.md | ||
| serve.py | ||
| setlist_opal2026.txt |
Captain's-log entry for the 2026-07-29 session, written while it is fresh (the armada/tasks discipline: these logs are the raw material for posts and video narration, not bureaucracy). Two findings, one class: a machine check stayed green while the instrument was broken. One was Tidal's (xfadeIn turns the outgoing pattern down but never off, and a gain-0 event still broadcasts its cut group). One was mine, shipped the previous evening (the button remap assigned cells in reading order, inverting 32 gate/gesture pairs that only PLN's ear caught). The shareable core, for later: a gain of zero is not the absence of an event. In a system where events carry side effects — voice stealing, global FX bus writes — the silent ones still act. Plus the green-check problem twice in one day, convergence as a bug report, and the honest limit of verdict-equality checking.
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| api | Loading commit data... | |
| escales | Loading commit data... | |
| manifeste | Loading commit data... | |
| semaphore | Loading commit data... | |
| tasks | Loading commit data... | |
| tide-table | Loading commit data... | |
| ui | Loading commit data... | |
| .gitignore | Loading commit data... | |
| DESIGN.md | Loading commit data... | |
| PRODUCT.md | Loading commit data... | |
| README.md | Loading commit data... | |
| serve.py | Loading commit data... | |
| setlist_opal2026.txt | Loading commit data... |