You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Bounded delegation: cap in-flight workers by shared host memory, not only coordinator capacity #238
What: Bounded delegation should tell a coordinator to size parallel workers by the shared host's free memory when all children run on one machine. Why: On 2026-10-19 00:07 Warsaw, a Chromeria backlog coordinator ran about 20 delegated workers on bestia (31 GB), most running test suites; systemd-oomd killed the shared Codex scope (664 processes) and eight runs were lost and had to be restarted. So what: An agent edits skills/operations/references/bounded-delegation.md ("Prove and size the workflow") with one sentence; no user decision needed.
Outcome
Coordinators check shared-host memory and other running agents before each parallel wave.
Problem Statement
Current guidance: "Bound in-flight work by the coordinator's capacity to validate and integrate, not the host's maximum worker count." It names coordinator capacity only; nothing prompts checking host memory or other coordinators sharing the host. Evidence: bestia load average 31, available memory near zero; journalctl --user: t3code-codex-754631c5.scope: systemd-oomd killed 664 process(es).
Solution
Add to "Prove and size the workflow": when children share one host, also bound concurrency by that host's free memory and the agents already running there; check before each wave and shrink after a resource kill.
Elon record
Requirements and who asked: the user's 2026-10-18 backlog request ran many parallel workers; this run's OOM exposed the gap.
Deleted: a new tool or scheduler; one sentence suffices.
Bottleneck: shared host memory, not coordinator review capacity.
Checked myself: read bounded-delegation.md in full and the bestia journal entries above.
Acceptance criteria
The sentence lands in bounded-delegation.md without duplicating it elsewhere.
Non-goals
Per-model worker limits, automation or a scheduler.
Blockers
None.
Required proof
The edited reference reads correctly in context; real-world effect stays unverified until a later parallel run.
Filed by the Chromeria backlog-clearing coordinator (Claude Opus 5.5 in T3 Code).
Prepared on branch fix/17.3.1-small-docs at 852d9dc (stacked on #242, 17.3.0 → 17.3.1, together with #234, #238 and #244). versionctl doctor --ci passes; versionctl release-check reports VERSION_CONFLICT until the v17.3.0 tag exists. Next: after #242 merges and tags, rebase onto main, rerun release-check and the full suite, open the PR, Luna review. Not pushed as a PR yet; no test suite run yet.
Implemented in #246 at d8261669a5e9ed493a39a82fdb5731bb037856e0, rebased onto main after #242. Version remains 17.3.1; the confirmed #245 commit is retained.
Proof on this exact head: tools/versionctl/bin/versionctl doctor --ci --base origin/main, tools/versionctl/bin/versionctl release-check, and release-check --sha HEAD pass; python3 -m unittest discover -s tests -p 'test_*.py' passes all 444 tests, and python3 -m unittest discover -s tools/versionctl/tests -p 'test_*.py' passes all 7 tests, run sequentially. git diff --check is empty; git grep -i karpathy -- ':!CHANGELOG.md' is empty (expected exit 1). Full diff and hook coverage were inspected; the shared-machine sentence appears only in bounded-delegation, and MISSION.md says “compatible harnesses”. Force-push with explicit lease succeeded and the remote SHA was verified.
Luna's independent review is pending, then the user merges because merging to main publishes 17.3.1. Not merged or released. Behavioral Live Verification remains pending real use; the Cursor copy for #234 follows at the next authorized marketplace promotion.
Activity
lukemaj commentedon Oct 19, 2026
Prepared on branch
fix/17.3.1-small-docsat852d9dc(stacked on #242, 17.3.0 → 17.3.1, together with #234, #238 and #244).versionctl doctor --cipasses;versionctl release-checkreportsVERSION_CONFLICTuntil thev17.3.0tag exists. Next: after #242 merges and tags, rebase ontomain, rerun release-check and the full suite, open the PR, Luna review. Not pushed as a PR yet; no test suite run yet.lukemaj commentedon Oct 19, 2026
Implemented in #246 at
d8261669a5e9ed493a39a82fdb5731bb037856e0, rebased onto main after #242. Version remains 17.3.1; the confirmed #245 commit is retained.Proof on this exact head:
tools/versionctl/bin/versionctl doctor --ci --base origin/main,tools/versionctl/bin/versionctl release-check, andrelease-check --sha HEADpass;python3 -m unittest discover -s tests -p 'test_*.py'passes all 444 tests, andpython3 -m unittest discover -s tools/versionctl/tests -p 'test_*.py'passes all 7 tests, run sequentially.git diff --checkis empty;git grep -i karpathy -- ':!CHANGELOG.md'is empty (expected exit 1). Full diff and hook coverage were inspected; the shared-machine sentence appears only in bounded-delegation, and MISSION.md says “compatible harnesses”. Force-push with explicit lease succeeded and the remote SHA was verified.Luna's independent review is pending, then the user merges because merging to main publishes 17.3.1. Not merged or released. Behavioral Live Verification remains pending real use; the Cursor copy for #234 follows at the next authorized marketplace promotion.