P6 spec §5.2: amend E8 to its capacity and realism arms (moca half of moca-experiments#10)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- documentation
Research direction
Read docs/specs/2026-09-08-p6-vm-process-manager-design.md §5.2 and the referenced sections in docs/specs/2026-09-09-p4-microvm-sandbox-design.md. Amend P6 §5.2 with the capacity and realism arms, their knee meanings, and the moca-experiments driver reference; then update the three E8 references in deploy/vm/README.md. Done means the spec assigns sandbox capacity to P4 and no longer points to a nonexistent local driver.
Written by the indexing model from the issue text.
Description
The moca half of rossoctl/moca-experiments#10, formerly #254, which moved with the other experiment issues on 2026-10-02.
That issue splits E8 (VM density and saturation) into two arms:
- a capacity arm: the supervisor and worker tier's turn concurrency and throughput, with the sandbox tier deliberately non-binding;
- the existing realism arm, with calibrated tool duty.
It says itself that this is "a scope change against P6's spec as written, not just a driver tweak". docs/specs/2026-09-08-p6-vm-process-manager-design.md §5.2 deliberately keeps the sandbox tier as a watched variable. The driver work belongs in moca-experiments now, but the spec lives here, so the amendment is this repo's.
Scope:
- Amend P6 §5.2 to describe the two arms, and what each one's knee means.
- Say that the sandbox tier's own capacity is P4's subject (
docs/specs/2026-09-09-p4-microvm-sandbox-design.md§7.2 E10, §7.3 E11), so E8 stops competing with it. - Point the spec at moca-experiments for the driver. Today no E8 driver exists on moca's
mainor in moca-experiments. deploy/vm/README.mdmentions "E8 rungs" in three places (lines 61, 618 and 629), for a driver that isn't in either repo. Reword them to point at moca-experiments, or drop them.
Related: rossoctl/moca-experiments#11 (the E8 run) and #12 (E9).
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 9
- Avg merge
- 9h 31m
- Merged PRs (30d)
- 139
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from rossoctl/moca
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
lyswhut/lx-music-desktop#3026 ·
-
area: ci type: test
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
schlessera/brain-kit#2769 ·
Maintainers usually reply within 1 day
-
Read a vector index's quantization back on Neo4j 2026.10, which reports vector.quantization.typeOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
liberation-data/drivine#231 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
alveusgg/alveusgg#2502 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day