A harness, not an opinion
satelle is a harness: the binary holds only the mechanism, and each repo writes its own process as configuration.
satelle is a harness: the binary holds only the mechanism, and each repo writes its own process as configuration.
satelle puts a reviewer on every step of a change: plan, code, integration and release each have to be accepted before the work moves on.
The first post covered reviewers. This one asks the harder question: can Opus, running through pi on our Cursor subscription, do the coding itself?
satelle does not care which agent runs a step, so the real question was which harness and which models to put in each seat.