-
docs(tasks): archive #44/#114 — the orchestrator as adversarial user · 29ce99d3
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.
PLN (Algolia) authored29ce99d3
×