I3825 — A build refuses to start beside five others or below 35 GiB free

✕BLOCKED wave 1 · p2 · implementation profile · parallel safe

Part of ci-critical-path — The critical path from a change to its verdict, and from a merge to its verified deploy, runs under a minute warm.

Objective

The build guard holds the two machine limits of rule project.the-cooperation-model-is-the-owners-word clause 7: no build starts while five builders already run on the machine or while less than 35 GiB is free, each refusal naming the limit, the measured value and the override, so the limits stop being numbers a session has to remember.

Why

Version 2 of the rule replaced the landing seat's slot order with two machine limits, but lib/rust_bin.sh still refuses only below its own 5 GiB default and counts no concurrent builders; a limit stated in a rule and decided by nothing is the gap the repository refuses elsewhere.

Current state

lib/rust_bin.sh refuses a build below MAJORDOMUS_MIN_FREE_MB, default 5120 MiB, and has no count of concurrent builders. CI runners have far less than 35 GiB free, so the local floor cannot simply become the default everywhere.

Desired state

A local build counts the cargo builders already running on the machine and the free disk, refuses at five builders or below 35 GiB with the measured values and the override, and CI keeps its own floor; a case proves both refusals with stubbed measurements.

Scope

• lib/rust_bin.sh
• test/cases
• .ai/repo/project/issues/I3825.yaml

Dependencies

• I3824○READY The cooperation rule says a worker lands its own green head, and every bootstrap says the same

Acceptance criteria

• A local build with five builders running refuses, naming the count and the override
• A local build below 35 GiB free refuses, naming the free space and the override
• A CI build keeps the CI floor and is not refused by the local limits

Validation

• bash test/run.sh

Evidence required

• builder_cap_refuses
• disk_floor_refuses

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

Timeline

started

—

verified

—

completed

—

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I3825.yaml. Read it back with majordomus plan show I3825.