id(world): F12.12 many worlds per node: 1,000 idle / 100 active with a per-world memory budget #557

Activity

1. dezren39

   added

   enhancementNew feature or requestNew feature or request

   on Oct 22, 2026
2. github-actions

   assigned

   dezren39

   on Oct 22, 2026
3. dezren39

   added

   kind/featureNew feature or capability requestNew feature or capability request

   source/humanFiled directly by a humanFiled directly by a human

   status/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first look

   priority/normalOrdinary priority (the default)Ordinary priority (the default)

   effort/lLarge: multi-day or open-ended; expect staged check-insLarge: multi-day or open-ended; expect staged check-ins

   app/idPackage/app: id (pkgs/ or apps/ in this repo)Package/app: id (pkgs/ or apps/ in this repo)

   meta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedIntake review done: acceptance criteria, links, and normalized labels added

   on Oct 26, 2026
4. dezren39 commented on Oct 26, 2026

   

   dezren39

   on Oct 26, 2026

   MemberAuthor

   More actions

   Intake review

   Fleet-monitor intake pass (2026-10-26). Body already carries a full ## Acceptance criteria section, so this pass is label normalization plus a liveness check — no body edit.

   Verified live on main e3467560 (2026-10-26): no per-world total memory budget exists — git grep -i 'memory_budget\|per-world.*memory' origin/main -- pkgs/id/src finds nothing; the per-guest linear-memory cap the body cites is still the only memory bound. The measurement half is also untouched (no harness run recorded). Still live; the body's "Partial" status assessment still holds.

   Related: prerequisite #539 (F11.8 benchmark harness with committed baselines) is still open and unenriched — the 1,000-idle/100-active measurement cannot be recorded without it. The metrics from #553 would make the budget observable once enforced.

   Risks / notes: a per-world budget needs a defined refusal behavior when a world exceeds it (refuse new allocations vs. evict vs. poison) — that semantic choice should be made in the implementation plan, mirroring how the sandbox handles guest memory exhaustion.

   Suggested approach: define and enforce the per-world budget with refusal tests first (verifiable without the harness), then run the scale measurement once #539's harness exists and record the numbers on this issue.
5. dezren39

   added

   nextOrg Project gate: queued next — orchestrator adds to the boardOrg Project gate: queued next — orchestrator adds to the board

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   and removed

   status/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first look

   on Oct 27, 2026
6. 326 remaining items

   Load more

   Load more actions
7. dezren39

   added

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   and removed

   queue/parkedQueue task is parked (waiting on CI, time, or an event)Queue task is parked (waiting on CI, time, or an event)

   on Nov 6, 2026
8. dezren39 commented on Nov 6, 2026

   

   dezren39

   on Nov 6, 2026

   MemberAuthor

   More actions

   🤖 Agent note · handed off

   • Agent: queue worker (repo-worker-code), lane code-f
   • Session / ID: task 8988
   • Found via: queue claim
   • Task: task 8988 for issue id(world): F12.12 many worlds per node: 1,000 idle / 100 active with a per-world memory budget #557 — execution lane assigned opencode; handing off to the opencode claimant per worker instruction §1b. Issue id(world): F12.12 many worlds per node: 1,000 idle / 100 active with a per-world memory budget #557 verified OPEN, no hard-stop labels. Note: task 8988 is at attempt 23/24 — cap risk if the claimant does not bind before park expiry.
   • Expectation: effort/l — claimant launches the bound opencode session to profile the F11.8 many-world run and route scoped fixes.
   • Links: issue id(world): F12.12 many worlds per node: 1,000 idle / 100 active with a per-world memory budget #557
9. dezren39

   added

   queue/parkedQueue task is parked (waiting on CI, time, or an event)Queue task is parked (waiting on CI, time, or an event)

   status/parkedDeliberately paused with a recorded resume conditionDeliberately paused with a recorded resume condition

   and removed

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   on Nov 6, 2026
10. dezren39 commented on Nov 6, 2026

    

    dezren39

    on Nov 6, 2026

    MemberAuthor

    More actions

    🤖 Agent note · handed off

    • Agent: queue worker (repo-worker-code), lane code-a
    • Session / ID: task 8988
    • Found via: queue claim
    • Task: triage for issue id(world): F12.12 many worlds per node: 1,000 idle / 100 active with a per-world memory budget #557 — execution-lane assigned opencode; handing task 8988 to the opencode claimant, who launches the bound session
    • Expectation: claimant launches bound opencode session for task 8988; parked 1800s for that launch window; attempts 23/24
    • Links: issue id(world): F12.12 many worlds per node: 1,000 idle / 100 active with a per-world memory budget #557
11. dezren39 commented on Nov 6, 2026

    

    dezren39

    on Nov 6, 2026

    MemberAuthor

    More actions

    🤖 Agent note · handed off

    • Agent: queue worker (repo-worker-code), lane code-l
    • Session / ID: task 8988
    • Found via: queue claim
    • Task: triage for issue id(world): F12.12 many worlds per node: 1,000 idle / 100 active with a per-world memory budget #557 — execution lane assigned opencode; handing task 8988 to the opencode claimant per worker instruction §1b. Issue id(world): F12.12 many worlds per node: 1,000 idle / 100 active with a per-world memory budget #557 verified OPEN fresh, no hard-stop labels (held / user/owned / do-not-merge / do-not-auto-edit absent), no open PR owning this work. WARNING: task 8988 is now at attempt 24/24 — AT CAP. If the claimant does not bind and drive it to a terminal state before this park expires, it will become unclaimable.
    • Expectation: claimant launches the bound opencode session to profile the F11.8 many-world run at 100 active worlds and route scoped fixes; this lane parks task 8988 for 1200s for that launch window.
    • Links: issue id(world): F12.12 many worlds per node: 1,000 idle / 100 active with a per-world memory budget #557
12. dezren39 commented on Nov 6, 2026

    

    dezren39

    on Nov 6, 2026

    MemberAuthor

    More actions

    🤖 Agent note · handed off

    • Agent: queue worker (repo-worker-code), lane code-e
    • Session / ID: task 8988
    • Found via: queue claim
    • Task: Handed off task 8988 (triage) for issue id(world): F12.12 many worlds per node: 1,000 idle / 100 active with a per-world memory budget #557 to the opencode claimant — execution lane assigned opencode. Fresh check: issue id(world): F12.12 many worlds per node: 1,000 idle / 100 active with a per-world memory budget #557 OPEN, no hard-stop labels.
    • Expectation: claimant launches the bound opencode session and drives task 8988 to a terminal state
    • Links: issue id(world): F12.12 many worlds per node: 1,000 idle / 100 active with a per-world memory budget #557
13. dezren39

    added

    queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

    status/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first look

    and removed

    work/assignedQueue worker lifecycle stateQueue worker lifecycle state

    on Nov 6, 2026
14. dezren39 commented on Nov 6, 2026

    

    dezren39

    on Nov 6, 2026

    MemberAuthor

    More actions

    🤖 Agent note · handed off

    • Agent: fleet monitor (repo-fleet-monitor)
    • Session / ID: task 8988 · repo-fleet-monitor run 2026-11-05 22:12 CST
    • Found via: monitor reconciliation
    • Task: Claim evaporated — the previous holder's claim on task 8988 ended without a terminal verb and the task is queued unclaimed (attempts 24/24, last checkpoint stage: handed_off). Labels reset to the truth: queue/queued + status/needs-triage. The attempt cap (24/24) is at or above the monitor's self-repair ceiling of 24, so the cap was NOT raised — this task is flagged for operator repair in the run summary.
    • Expectation: the next queue claimant picks up task 8988 from the handed_off checkpoint; no work was lost.