Skip to content

investigate: which scheduled work classes can move to OpenCode sessions on quota plans #2018

New issue
New issue
Closed
Closed
investigate: which scheduled work classes can move to OpenCode sessions on quota plans#2018
Assignees
dezren39
Labels
priority/highImportant and time-sensitivesource/creatorFiled by the new-issue-creator jobtask/triageQueue packet kind: verify, reproduce, and route this item

Description

@dezren39
dezren39
opened on Oct 29, 2026

LIST 3. Assess each scheduled/recurring work class — the creators, issue creation, issue triage, and the orchestrator role itself — for execution by OpenCode sessions spending quota-plan capacity instead of Muse tokens. For each class: what it needs (tools, secrets, judgement depth), the stuck-session caveat (a stalled OpenCode session waits for a babysitter round — what latency does that impose?), and a go/no-go with reasoning. Include the near-term lever Drew asked for: raise the OpenCode share of implementation→PR work soon, by adding a couple of OpenCode lanes or switching existing lanes — name which.

Program: Drew's 2026-10-28 directive (full text: hatch-personal memory/topics/id-program-2026-10-28.md).
Working pattern: parallel investigations, then the named synthesis issue merges them into a full design. Route guidance: Workhorse by default; Specialist/Summit for synthesis and ramification-heavy work. A result that says "done" is not the endpoint — the orchestrator reviews it and may commission another round. Deliverables: a markdown design/investigation doc (mermaid/SVG diagrams welcome) linked from this issue, plus follow-up issues for anything buildable. Build a proof of concept where the design calls for one, but do NOT build the permanent feature on top of an unreviewed PoC.

Activity

  1. developing-today commented on Oct 29, 2026

    @developing-today
    developing-todayBot
    on Oct 29, 2026 – with developing.today
    Contributor

    CODE-939

  2. dezren39 commented on Oct 29, 2026

    @dezren39
    dezren39
    on Oct 29, 2026
    MemberAuthor

    Parent epic: #2055 — fleet expansion & placement program (2026-10-28 directive).

  3. github-actions
    assigned
    dezren39
    on Oct 29, 2026
  4. dezren39
    added
    priority/highImportant and time-sensitive
    queue/queuedHas a queued task in the Supabase agent queue
    on Oct 29, 2026

  5. dezren39 commented on Oct 29, 2026

    @dezren39
    dezren39
    on Oct 29, 2026
    MemberAuthor

    Top priority — ID program wave-1. Drew directed this be picked up in the next runs (2026-10-29): enqueued directly as triage task 3337 in repo-health-code-pilot at queue priority 20 (only breakage-class work at priority 10 outranks it). Wave-1 is the ungated investigations and designs; syntheses and PoCs stay gated on their named inputs. Investigation route: Workhorse.

  6. dezren39
    added
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    status/in-progressQueue worker lifecycle state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Oct 29, 2026

  7. dezren39 commented on Oct 29, 2026

    @dezren39
    dezren39
    on Oct 29, 2026
    MemberAuthor

    🤖 Agent note · picked up

    • Agent: queue worker (repo-worker-code), Lane C
    • Session / ID: queue task 3337 (triage)
    • Found via: queue claim
    • Task: Triage investigate: which scheduled work classes can move to OpenCode sessions on quota plans #2018 — verify the premise against the live schedule inventory, give the per-class read, and route the full investigation/design as a follow-up in the same pass
    • Expectation: triage verdict + follow-up task enqueued this pass; the full design doc is the follow-up's deliverable (issue's own working pattern: investigation first, synthesis after)

  8. dezren39 commented on Oct 29, 2026

    @dezren39
    dezren39
    on Oct 29, 2026
    MemberAuthor

    🤖 Agent note · done

    • Agent: queue worker (repo-worker-code), Lane C
    • Session / ID: queue task 3337 (triage)
    • Found via: queue claim
    • Task: Triage verdict for investigate: which scheduled work classes can move to OpenCode sessions on quota plans #2018 — CONFIRMED, with the per-class read below and the full design routed as a follow-up task in the same pass
    • Expectation: done — verdict below; follow-up investigation/design task enqueued (packet queue-pilot/packet-2018-design.json), whose deliverable is the design doc + named lane lever + buildable follow-up issues

    Verdict: CONFIRMED — every scheduled class the issue names runs today as a Muse (Muse) cron agent; none runs on quota-plan OpenCode sessions yet, and an OpenCode path already exists to move them to.

    Evidence (live cron inventory read this run, 2026-10-29; all execution.kind=agent):

    • Creators: new-issue-creator-code-a/b (30m), -nix (2h), -openchamber (1h), -opencode (1h); pr-diff-review + pr-diff-review-b (2h); repo-design-architect (12h), -code (4h).
    • Issue triage / orchestration: orchestration-pass (1h), stewardship-cycle (1h), repo-fleet-monitor (2h), program-tending (daily), repo-queue-worker-shift* claim-side triage inside the workers.
    • Implementation→PR (for the lever): repo-queue-worker-shift lanes A–D (code) + nix/openchamber/opencode lanes (40m each), issue-sweep-rotating (1h).
    • The OpenCode path already exists: openchamber-dispatcher (15m) launches sessions for queued issues and openchamber-babysitter (20m) runs session rounds — so the stuck-session latency floor the issue asks about is measurable today: a stalled session waits up to ~20 min for the next babysitter round, plus the round's own runtime.

    Per-class triage read (full reasoning is the follow-up design's job; this is the route):

    • Creators (issue creation, PR-diff review, design architect): GO-first candidates. Bounded, template-driven, output is a filed issue/packet — judgement is real but checkable after the fact, cadences (30m–12h) dwarf the 20m stall latency, and they need only gh + queue helper + read access (secrets by name via Bitwarden, as today).
    • Issue triage: GO with a guardrail. Triage verdicts route real work, so a stalled or shallow triage costs a cycle, not a breakage; keep the packet-defect/block verbs as the escape hatch and sample-audit verdicts in the design's first phase.
    • Implementation→PR workers: GO — this is the near-term lever. Sessions already do this via the dispatcher. Triage recommendation for the design to confirm or overturn with fresh quota data: switch Lane D of repo-queue-worker-shift (code) to OpenCode sessions first — one lane changes the share measurably while A/B/C keep the Phase-2 Muse comparison intact; add no new lanes until the switched lane's throughput is measured. (Any actual switch is a schedule/rate change — Drew's call, per the fleet rule; this triage only names it.)
    • Orchestrator itself (orchestration-pass, stewardship, fleet monitor): NO-GO for now. These hold the widest authority (dispatch, escalation, label/queue reconciliation, decision surfacing to Drew) and the deepest judgement; a stalled orchestrator stalls every class under it, and the babysitter for the orchestrator would be another orchestrator. Revisit after the other classes have measured session track records.

    Binding constraints the design must honour (pool map, 2026-10-25): the OpenCode meta provider is the only door into the Muse High Usage pool (the OpenCode muse provider is disabled by Drew's order); DeepSeek direct is PAYG reserve, never routine; no placement without a pool quota read ≤60 min old; at a known 100% a pool is closed.

    Routing: follow-up investigation/design task enqueued this pass (packet-2018-design.json: design doc at files/opencode-placement-design-2018.md linked from this issue, per-class go/no-go table, the lane lever answered by name with fresh quota evidence, follow-up issues for anything buildable). This issue stays open at priority/high for that design.

  9. dezren39
    added
    queue/queuedHas a queued task in the Supabase agent queue
    and removed
    status/in-progressQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    on Oct 29, 2026

  10. 14 remaining items

  11. dezren39
    added
    status/needs-triageNot yet triaged; needs a first look
    task/triageQueue packet kind: verify, reproduce, and route this item
    on Nov 3, 2026

  12. developing-today commented on Nov 3, 2026

    @developing-today
    developing-todayBot
    on Nov 3, 2026 – with developing.today
    Contributor

    agent-note:v1
    state: reviewed (coverage loop-back)
    Coverage pass 2026-11-03, loop-back review: this issue was re-reviewed (drift / overlap / already-handled / stale / blockers / ordering) so every open issue in the four repos is reviewed and in the system. Verdict: still live; in the system as task 7261 (triage, queued, priority 50) in repo-health-code-pilot. Labels audited and synced. If it is already handled at current main, its triage closes it with evidence; if oversized, the triage files the split; blockers belong on this issue.
    Found via: coverage loop-back 2026-11-03

  13. dezren39
    added
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    status/in-progressQueue worker lifecycle state
    and removed
    status/needs-triageNot yet triaged; needs a first look
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 3, 2026

  14. dezren39 commented on Nov 3, 2026

    @dezren39
    dezren39
    on Nov 3, 2026
    MemberAuthor

    🤖 Agent note · handed off

  15. dezren39 commented on Nov 4, 2026

    @dezren39
    dezren39
    on Nov 4, 2026
    MemberAuthor

    🤖 Agent note · picked up

    • Agent: queue worker (repo-worker-code), OpenChamber scheduled lane 8ac61616-3815-4e7b-b33d-840a3829154a
    • Session / ID: queue task 7261 (triage)
    • Found via: atomic queue claim; resumed saved handoff checkpoint
    • Task: Triage investigate: which scheduled work classes can move to OpenCode sessions on quota plans #2018 — investigate scheduled work classes moving to OpenCode quota-plan sessions.
    • Expectation: verify current issue and prior work, name remaining blockers, then close with evidence if the requested investigation/design is already delivered. No schedule or lane changes are authorized by this triage.

  16. dezren39 commented on Nov 4, 2026

    @dezren39
    dezren39
    on Nov 4, 2026
    MemberAuthor

    🤖 Agent note · triaged — prior investigation/design already delivered

  17. dezren39
    closed this as completedon Nov 4, 2026
  18. dezren39
    removed
    status/in-progressQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    work/assignedQueue worker lifecycle state
    on Nov 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

priority/highImportant and time-sensitivesource/creatorFiled by the new-issue-creator jobtask/triageQueue packet kind: verify, reproduce, and route this item

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions