Skip to content

[Frontier] [CONT16-01] Continue original work automatically after needs-you hand-back #459

Closed

Description

@chayapats

Follow-up from ADR 0092 (#458, #410 slice 3, #442).

ADR 0092 makes computer_browser needs_you non-blocking: it enters the yield state, posts a "needs you" card and returns { state: "yielded", cardId, generation, expiresAt } at once; the turn ends normally (ADR 0037 pattern). The outcome (resumed / declined / expired) is recorded on the card and shown in the conversation. The Bot only continues when its next run starts (for example the owner's next message).

This issue: start the Bot's run automatically when the owner hands back from a needs_you takeover (and possibly on decline/expiry), so the owner does not have to send a message after signing in.

Open questions:

  • Which trigger starts the run (card outcome event, hand-back event) and under which run/topic.
  • Bounds: one automatic continuation per card; no continuation for routine runs (they use the needs_you occurrence state from s16-routines-v1).
  • How the continued run gets the new generation and the card outcome as context.

Out of scope for ADR 0092 by Tria's round-3 ruling on #458 (#458 (comment)).

Implementation contract (CONT16-01)

Parent: #410 / #442, under #392. Model tier: Frontier, because continuation shares existing work authority, charged budgets and private disclosure ancestry across durable scheduling boundaries.

Context to read: CONTEXT.md, S16 and retained S15, ADRs 0064/0084/0092/0094, and s16-computer-browser-v1.md. ADR 0094 resolves the engineering questions above: only durable yield_resumed schedules one continuation; decline and expiry do not. The outcome source remains ADR 0092's existing source, as confirmed by the owner comment.

Deliverable: automatically continue the original task after hand-back without another owner message, using the same grant, frozen intent, model pin, physical-computer/workspace affinity and remaining charged allowance, with fresh CHAT/VM-session/MODEL-step identities.

Implementation steps:

  1. Bind a durable screen-event cursor and one per-card continuation request atomically in the protected conversation journal.
  2. Recheck the original authority and prior memory/file/claim fences; recover only unclaimed queued requests and serialize with current conversation work.
  3. Supply bounded prior observations as data, keep the existing outcome channel/publication-only delivery, and coalesce a run that already consumed it.
  4. Project actual continuation facts in English/Thai cards and host-labelled transcript rows; attribute usage by exact work and MODEL step.

Acceptance criteria:

  • Real needs_you → owner takeover/hand-back → automatic observed result, with no new owner message.
  • One automatic continuation per card; ordinary takeover, decline/expiry and routines never trigger it.
  • Same original work, workspace/computer/model pin and cumulative finite allowance; another shared computer cannot take the signed-in session.
  • Queue/restart/claim/duplicate/coalescing behavior never replays a claimed model/tool/effect; failure and unknown remain visible.
  • Stop, revocation, owner/Bot/private scope, budget, file and memory withdrawal fences survive every send/tool/publication.
  • Existing outcome source and exact publication-only delivery; English/Thai, mobile, keyboard/focus and authentication-loss behavior verified.

Tests and evidence: deterministic production and fallback composition fixtures; reopened-journal and seeded interrupted-claim recovery; barriers for quick hand-back/forget; rollback and usage attribution regressions; native Chromium English/Thai login-form/cookie and automatic UI flows. No live-account/guest power-loss proof is inferred.

Requirements: S16-AC06/AC07/AC11, FR-10/14/15/35/38/40, NFR-07/14. Blocked by: #410 and #442 (both closed via #463). Contracts used/delivered: ADR 0092 outcome source plus additive s16-computer-continuation/v1 protected metadata and card projections described in ADR 0094.

Out of scope: live Linux/account/native-device adoption (#431), owner-host cutover (#432), another runtime/authority stack. Do not synthesize owner approval, reset work budgets, move workspaces, replay claimed loops, add another screen outcome channel, or treat MODEL completion alone as publication.

Definition of done: typecheck, upstream provenance, affected deterministic/native browser suites and complete required CI pass on the reviewed head; PR contains Closes #459 and passes review before integration. Integration follows the owner's standing autonomous merge instruction.

Integrated by #464, merge 48c29b9ccef7696f2415df790d270f27e5f07ba5, reviewed head a8d8630c2a2edb16998b2a62a28110a5f527a7f0. Complete immutable-head local suite: 5086 pass, 81 opt-in skips, 0 failures; native English/Thai: 2 pass / 116 assertions; all 15 CI checks and exact-head review approved. Live host/account/device and owner cutover remain separately tracked, not inferred from fixtures.

Activity

  1. chayapats commented on Nov 11, 2026

    @chayapats
    OwnerAuthor

    ADR 0092 (PR #458, head 47b5fc0, decision 7 "The next run gets the outcome as data") answers how the continued run gets the outcome. On hand-back, decline or expiry, the next work run in the conversation that posted the card, with that computer in its admitted resources, gets one data-never-authority work-prompt source: { cardId, origin, reason, outcome, generation }. It is delivered once per card. Interpretation context is unchanged. An automatic continuation started by this issue should use the same source, not a new channel.

  2. self-assigned this
    on Nov 17, 2026
  3. changed the title [-]S16: continue the Bot's run automatically after a needs_you hand-back (follow-up to ADR 0092)[/-] [+][Frontier] [CONT16-01] Continue original work automatically after needs-you hand-back[/+] on Nov 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions