| 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 |
Two entries. #44's lesson is the one worth mining later: wiring six working checks into one caller found two of them dead, because every check had been verified once, interactively, by a human who supplied the missing piece without noticing. A human types `zsh tools/foo.sh` out of habit and never learns the file is not executable. An orchestrator has no habits. #114 records that the overnight constraint list did real work rather than being ceremony: "never write to a setlist .tidal" is what kept three ranked-"needed" tasks off the queue, and drawing that boundary first is why the night was productive instead of risky.
| 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... |