Signed join
Each worker joins with a signed profile, declared lanes, and a time-limited heartbeat.
Local Worker Fabric
Network multiple high-end PCs into one private coding workbench.
Mainely Code Buildroom can be positioned around local, private worker fabric: a coordinator routes bounded coding jobs to trusted PCs, then collects diffs, checks, and proof before handoff.
Local-first topology
Coordinator plus workers, all on a private network.
The coordinator is the only place a job becomes a work order. Workers advertise capabilities, accept signed tasks, run inside local worktrees, and return proof artifacts. The system should reject any worker that tries to act outside its lane.
1coordinator
5+worker lanes
0public model ports
100%proof required
Minimum network posture
Private LAN or private encrypted overlay
Signed worker enrollment
Heartbeat and stale-node detection
No secrets in logs or proof bundles
Egress allowlist for external services
Workers never self-merge or self-approve
Public-safe config concept
Show the shape without exposing private infrastructure.
The site now includes a downloadable example config using fake addresses and placeholder names. It communicates the differentiator without revealing your real machines, subnets, secrets, or topology.
This is the kind of language a serious customer understands: capabilities, enrollment, heartbeat, work-order policy, file boundaries, diff-before-apply, and proof bundles.
coordinator: name: buildroom-coordinator bind: 10.42.0.10 require_signed_workers: true reject_public_model_ports: true network: mode: private_lan_or_private_overlay allowed_subnets: [10.42.0.0/24] heartbeat_seconds: 20 egress_policy: allowlist_only work_order_policy: require_owned_paths: true reject_unowned_file_changes: true require_diff_before_apply: true require_proof_bundle: true
Worker safety rules
The controls are what make the fabric sellable.
Local hardware is powerful. The product has to prove that power is governed, bounded, and reviewable.
Owned-file locks
Workers receive owned paths and blocked paths. Changes outside the boundary fail closed.
Diff before apply
Every candidate is reviewed as a diff before handoff. No diff means no done claim.
Proof store
Checks, failures, artifacts, and rollback notes live in the proof bundle for review.
Safe stops
Repeated failure classes stop the run instead of burning cycles or hiding drift.
Privacy posture
Keep source close, keep secrets out of prompts/logs, and use only approved connectors.
Role routing
Send the right job to the right node: patch, bug hunt, architecture, heavy lift, proof review.
Cloud burst later
Cloud can remain an option for overflow, not the default place customer code must live.
Pilot framing
For a customer with multiple strong PCs, this is the conversation.
“We can map your local hardware into a private build constellation, run a bounded repo task, and deliver a proof-backed pull-request candidate or a clear safe-stop.”