| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| api | ||
| escales | ||
| manifeste | ||
| semaphore | ||
| tasks | ||
| tide-table | ||
| ui | ||
| .gitignore | ||
| DESIGN.md | ||
| PRODUCT.md | ||
| README.md | ||
| ardour_faders.json | ||
| serve.py | ||
| setlist_opal2026.txt |
Three tasks that turned 'can PLN play from another laptop' from a question into a procedure, archived long-form because the learnings are the blog material. The through-line worth reading later: every one of the three had a structural flaw that only appeared when you asked where the tool would RUN. sample-pack was designed as two bundles until PLN reframed it as one parameterized query over the mapped list. rig-doctor was green at home and structurally incapable of naming absence on a fresh box, because it resolved against the machine it ran on. rig-install would have created an empty quark directory that the next run reads as 'already installed'. None of the three was caught by a test; all three were caught by asking what happens on a machine that has nothing.
| 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... | |
| ardour_faders.json | Loading commit data... | |
| serve.py | Loading commit data... | |
| setlist_opal2026.txt | Loading commit data... |