Local clearance for parallel coding agents

One machine.Many agents.One clearance layer.

Two keys to start. Verified cleanup to release.

Gatehold blocks overlapping work, queues heavy jobs when the host is full, and releases a lane only after owned cleanup is verified.

Deterministic policy grants clearance.GPT-5.6 can only add a hold. It never grants clearance or overrides deterministic policy.

Clearance decision · Scene BHOLD

Agent 18 · light lane

Different words. Same workstream.

Exact workstream and scope checks see no match. In this bounded replay, GPT-5.6 detects the semantic overlap and adds a HOLD; it can never grant clearance.

Bounded replay · no repository access

Workstream keyOverlapCapacity keyHeadroom

REPLAY HOST METRICS · REPLAY SCENARIOBounded demo data.

CPU load44%Inside policy

Memory56%Headroom ready

Heavy lanes1 / 2Slot available

Active leases21 waiting

Bounded A–D scenario

Agent clearance lanes

3 replay lanes

Agent 07

Repair token refresh

RUNNING

auth/session · lane-07 · :49157heavy

Workstream keyOwner locked

Capacity keyHeadroom

Authoritative lease owner

Agent 18

Harden session renewal

SEMANTIC HOLD

identity/session · pendinglight

Workstream keyOverlap

Capacity keyHeadroom

Exact scope differs; meaning overlaps auth/session

Agent 12

Billing receipt tests

CLEARED

billing/receipts · lane-12 · :49158light

Workstream keyIndependent

Capacity keyHeadroom

Unrelated work continues