Four signed hops carry a machine from spec to receipt — RFP, bid, accept, receipt — each one an AT Protocol record anyone can verify.
Each arrow is a strongRef — a signed pointer to the record before it.
role: ml-inference-worker
role: batch-render-node
role: ci-runner
If your org already owns machines, it can act as a bidder for its own members — no shared root passwords, no internal ticket queue. A member's RFP is just another signed record, and your bidder decides whose it will even look at.
See how policy modes work →Just your own DIDs — an internal pool, nothing public yet.
Anyone your org mutually follows — reuse the social graph you have.
Anyone vouched for on Tangled's graph — revocable with a denounce.
Delegate the allow/deny call to your own policy server or CI, per request.