Skip to content

119. Steer a running cycle with admitted entity updates ​

Date: 2026-11-02

Status ​

Accepted

Partially supersedes two sentences of ADR 0141, for the steer path only. Every other ADR 0141 rule stays current.

  • "An explicitly configured host-side extension may fetch a kind outside the snapshot": the host-side steer path may also fetch newer revisions of the snapshot's own kinds for the bound entity during a cycle, through the same pipeline and fail-closed rules, exposing no raw payload. Sandbox forge reads stay denied.
  • "requires a versioned schema that lists its path in the manifest": "the manifest" there is the snapshot's index.json. Steer output is listed instead in its own manifest, steer envelope v1, under the same filtering, digest, permissions, exact-path, and cleanup rules.

Reason: a steer carries newer revisions of what the snapshot holds, and the snapshot, whose digest is the cycle's admitted input, cannot change mid-cycle.

Context ​

ADR 0106 coalesces later events into one pending follow-up, and ADR 0144 runs it as a new cycle in the same fullsend run process. Neither reaches a running sandbox, so a turn that started on old state posts output the entity has moved past, such as a review of a replaced head (#1207), and a person who adds direction mid-run waits for the next cycle. On GitHub Actions, event-only harnesses get no wake listener from ADR 0144, so their follow-up starts only after the current job ends.

Any answer keeps per-record admission with no data-only lane (ADR 0133) and wakes that never consume pending work (ADR 0144).

This ADR aims to let a running sandbox cycle take in admitted entity updates without weakening those rules.

Options ​

OptionWhy not chosen
Rely on ADR 0144 cycles aloneThe stale turn still finishes and may post; nobody can redirect work in flight
Ask the agent to re-check the entity at turn endAdvisory, reads the forge from the sandbox (ADR 0141 denies it), and still pays for the stale turn
Steer the running cycle (chosen)— see Decision

Decision ​

We adopt steering, the delivery of freshly admitted, filtered entity records into a running sandbox cycle, to let the agent's next turn work from the entity's current state.

Steering is an optional fast path inside one ADR 0144 cycle; the next cycle stays the correctness backstop.

Place in the cycle ​

  • A steer is one delivery into the current sandbox, not a cycle.
  • A steer never takes, fills, consumes, or replaces the newest-pending slot or the pending platform execution. The prompting notification still schedules the follow-up cycle, which runs CEL and the pre-script as usual. Telling it what was absorbed is ADR 0120 (proposed).
  • A declined or unacknowledged steer leaves the cycle as if none was attempted. A lost runtime session fails the cycle.
  • A steer never changes the cycle's platform-verified result revision. It stays the revision of the cycle's admitted input, as ADR 0144 records it.

When a steer is attempted ​

A notification for the cycle's serialization key while its sandbox runs (an ADR 0144 event or wake, or an ADR 0118 (proposed) signal) prompts an attempt, unless Fullsend's own App identities caused it; that filter is routing, not admission. Each attempt runs on the host, in order:

StepWhat happensIf it fails
1. EligibilitySteering is enabled (ADR 0121, proposed), the entity is a forge entity, and the runtime can steer within its cap and time budget (ADR 0117, proposed)No steer
2. Still selectedRe-resolve the entity, check ADR 0149 source membership for entity-source harnesses, and evaluate harness CEL (see below)False or unknown: no steer
3. AcquireFetch records new or changed since the snapshot and earlier steersFetch error: no steer
4. Filter and admitADR 0141 pipeline, then the admission rule belowDropped records are counted, never delivered
5. ReleaseUnder the sandbox write lock: the release check per record, write the steer files, append the envelope, wait for the acknowledgementA failing record is dropped; nothing left: no steer
6. RecordAdd a child event to the cycle's span. Steers count toward the ADR 0106 and ADR 0144 circuit breakers and do not change run status—

Still selected. CEL runs over the current entity with the cycle's retained prompting event (null for an eventless cycle). The event is reused only so an event-only harness, whose CEL needs one, stays eligible; it is never authority. The event actor's role is resolved fresh in the same step, and a role below the threshold means no steer. This is not a new ADR 0144 check: it runs inside the cycle that consumed the event and can only decline, so ADR 0144's rule that later checks "do not reuse" the event is unchanged.

Admission ​

A steer release is a "Fullsend-controlled capability invoked after sandbox initialization", so each release runs the contract's check, which "MUST resolve authorization immediately before releasing each result to the model" (Authorization v1 and v2), on each record's current-revision actor.

  • Humans must meet the harness's human_min_role (ADR 0151), or the Authorization v1 thresholds on legacy non-CEL routes. Bots need a recognized ADR 0107bot_role.
  • Records that fail, or cannot be attributed or verified, are dropped and counted as omissions.
  • Event-carried evidence, the route job's verdict, earlier CEL results, and the ADR 0148 role cache never satisfy the check.

Content ​

Records take the ADR 0141 host-side path and filter pipeline; the sandbox-visible format is steer envelope v1. A steer is content, never capability: it cannot change tools, role, model, credentials, routing, or network policy.

Dependencies ​

Steering stays off, whatever ADR 0121 sets, until ADR 0151 role loading with per-record admission, the ADR 0141 filter pipeline and host-side extension path, and the ADR 0144 cycle lifecycle are in place. Delivery is correct without ADR 0120 receipts; each steered cycle is then followed by a full cycle.

Forge scope ​

  • GitHub: GitHub Actions, through the ADR 0118 signal and ADR 0144 wakes.
  • GitLab and Forgejo: not supported; no running-cycle signal source is wired, so runs behave as ADR 0106 and ADR 0144 describe.
  • Jira and other non-forge entities: steering declines, since entity-context-snapshot v1 does not stage them.

Consequences ​

  • Updates during a cycle reach the running agent, so fewer outputs are built from replaced state.
  • A steered sandbox stays up longer, and each release adds a fresh permission lookup per actor.
  • Steered records reach the model before any pre-script sees them; the next cycle's pre-script sees them afterwards.

Open questions ​

  • A head move needs the new Git objects inside the running sandbox. Which provisioning path supplies them mid-cycle? Until one exists, a steer omits the head and the follow-up cycle handles it.