121. Steering on by default, with per-harness and per-repository opt-out
Date: 2026-11-02
Status
Accepted
ADR 0106 refers to this ADR as the decision that turns steering on by default.
Companion decisions:
- ADR 0117 (proposed): runtime delivery.
- ADR 0118 (proposed): the GitHub Actions change signal.
- ADR 0119 (proposed): what a steer is and what it may carry.
- ADR 0120 (proposed): receipts for absorbed steers.
Context
ADR 0119 (proposed) defines steering as an optional fast path inside an ADR 0144 cycle. It leaves open whether a harness steers when it says nothing.
The origin issue for this work, #6957, describes harness.steer as off by default. ADR 0106 records that this criterion is replaced by the default-on decision in this ADR.
This ADR aims to choose the default and the switches that turn steering off.
Options
Opt-in per harness (rejected)
Absent means off, and each harness names itself in. It keeps the stale-output cost on every harness that says nothing, which is most of them.
On by default, with opt-out (chosen)
Every eligible harness steers unless it, or its repository, turns steering off. A harness whose agent ignores the envelope must be found and opted out.
Decision
We adopt steering on by default, with a per-harness and a per-repository opt-out, to give every eligible harness the steering gains without a per-harness edit.
After ADR 0144, what steering still adds is avoiding stale output from a turn that finishes on old state, redirecting work in flight, and covering event-only harnesses on GitHub Actions where ADR 0144 opens no listener; those gains apply to every harness.
| Switch | Where | Effect |
|---|---|---|
steer: {enabled: false} | Harness | Steering off for that harness |
steer: {enabled: false} | Repository .fullsend/config.yaml | Steering off for every harness in the repository |
- Any
falsewins. An explicitenabled: falseat any layer (a base harness, a child harness, a forge override, or the repository) turns steering off, and no other layer can turn it back on. - Tuning never re-enables. A
steerblock that sets only tuning fields, such asmax_steers, leavesenabledas the other layers set it. Absent everywhere means on. - Not before readiness. The default applies only once the ADR 0119 dependencies are in place.
A harness opts out when its agent definition does not act on the steer envelope (proposed with ADR 0119), or when its pre-script gate must see every update before the model does.
Forge scope
The default applies wherever ADR 0119 supports steering, which is GitHub on GitHub Actions. On GitLab and Forgejo no running-cycle signal source is wired, and Jira entities are not staged by entity-context-snapshot v1, so steering is unavailable there and the switches have no effect.
Consequences
- Every eligible harness steers on the release that enables steering, without a per-harness edit.
- Harnesses whose agents ignore the envelope must opt out before that release, or updates delivered to them are acknowledged but not acted on until the next cycle.
- A steered sandbox stays up longer, so the default adds VM time on every harness that has not opted out.
- The new
steerfield needs entries in the harness and config references when it is implemented.
