GlossaryGlosarium
What is the opt-in-auto rung?What is the opt-in-auto rung?
opt-in-auto is the rung where the fleet may run a class on its own — but only while a live grant covers it. It is opt-in twice over: someone has to grant it, and the grant can be revoked. With no live grant, the class falls back to a card for the human seat.opt-in-auto is the rung where the fleet may run a class on its own — but only while a live grant covers it. It is opt-in twice over: someone has to grant it, and the grant can be revoked. With no live grant, the class falls back to a card for the human seat.
Glossary / What is the opt-in-auto rung?
`opt-in-auto` is the middle rung of the autonomy ladder, and it is the one most often misread as "the agent works on its own". It does not mean that. It means: the fleet is allowed to run this class without a card for every instance, but only for as long as a live grant covers it.
The grant is the second opt-in. A grant is issued by the human seat for one action class and comes in two kinds. An `allow_once` grant is consumed the first time it is used. An `allow_always` grant keeps covering the class, and it has to name its scope — which lane, and for a cross-promotion, which partner and which window — because "always" without a stated boundary is not a grant, it is a blank cheque. Both kinds can be revoked, and an always-grant that is still live is enumerable, because if it cannot be listed it cannot be governed.
When no live grant covers the class, the runtime does not improvise. It refuses with `grant_not_found` and the work becomes a card for the human seat. When the organiser did issue a grant and only its time window has closed, the refusal says exactly that — `grant_window_expired` — rather than claiming there was no grant, because a time-bounded grant is one the organiser chose and has to renew, and telling them otherwise would send them looking in the wrong place.
Two things `opt-in-auto` does not do. It does not override member protection: a member's stop, their quiet hours and their per-day cap are checked before delivery, and a member's stop beats any grant. And in version 0 it still does not send — the transport refuses, and what comes back is a hand-off for the organiser to deliver.
Related
| Term | |
|---|---|
| What is per-action autonomy?Per-action autonomy means every class of work gets its own rung on a three-step ladder — draft, opt-in-auto, or never — instead of one switch for the whole agent. An unset class behaves as never, never is a floor, and the narrower of the pack and the organisation always wins. | Read → |
| What are once-vs-always grants?A grant is a permission the human seat issues for one action class. It comes in two kinds: allow_once, consumed after a single use, and allow_always, which must name the scope it covers. Collapsing the two is the bug that turns a helper into an unattended bot. | Read → |
| What are member quiet hours?A window — 21:00 to 07:59 in the member’s own timezone — during which the fleet refuses to commit anything member-facing. The cadence and the hours belong to the recipient, not to the organiser’s clock, and not to the server’s. | Read → |
By Filbert Then · Last updated · Suggest a correction
See the fleet runLihat armadanya berjalan
Run the seeded cycle, decide the proposals, then read the audit trail.Jalankan siklus contoh, putuskan usulannya, lalu periksa audit trail-nya.