# How it works A spec and its implementation for atproto accounts to request and advertise compute. It is for you if you run an organization and want decentralized identity to give your members, and their workloads and agents, access to your compute. The flow is: Request For Proposal -> Bid -> Accept -> Receipt. Each step is a signed record in its author's own atproto repo; the other side reads it from the firehose, a Jetstream, or the XRPC call that names it. ```mermaid sequenceDiagram autonumber actor Alice as Alice (requester) actor Bob as Bob's bidder Alice->>Alice: compute.vm (cpus, mem, disk, cloud-init user_data) + market.rfp Alice->>Bob: discover (market.offering, market.heartbeat), submitRfp Note over Bob: policy: does Bob vouch for Alice? Bob->>Bob: market.bids.free + market.bid Bob->>Alice: submitBid Note over Alice: policy: does Alice vouch for Bob? Alice->>Alice: market.accept Alice->>Bob: submitAccept Note over Bob: capacity, then provision the VM Bob->>Bob: market.receipt, then market.event (vm.hostKeys, vm.onNetwork) Bob->>Alice: submitEvent Note over Alice: Held: ssh over iroh Alice->>Alice: compute.events.vm.delete + market.event Bob->>Bob: compute.events.vm.terminated + market.event ``` ## Who is who | actor | is | example | | --- | --- | --- | | requester | an atproto account that requests a VM | `aliceoa.bsky.social` | | bidder operator | an account that owns bidders | `bobvmbuilder.bsky.social` | | bidder | a host that provides VMs; its own DID, an agent of its operator (ident.link) | `did:plc:2l2wdry77c7jtucbslstagkj` | | guest | the VM; it holds no repo key: its bidder signs its events | - | | guest requester | a requester inside a requested VM, an agent of its requester for that contract | CI requesting a staging network | | release account | publishes the release channels | `socialweb.computer` | ## Who serves whom A bidder bids only for requesters its operator vouches for (`sh.tangled.graph.vouch`), and a requester accepts only bidders it vouches for, directly or through the bidder's operator: the default policy `tangled-vouch` on both sides. Agents count as their principal, up to 100 levels of ident.link associations. Requesters find bidders through relays (every repo with a `market.offering` and a fresh heartbeat), never from a pinned list. ## What reaches the guest The VM boots from the `compute.vm`'s cloud-init `user_data`; nothing else starts a guest. The requester reaches it over iroh (every guest), and per tunnel over https (opentunnel) or WebRTC. Secrets never go into `user_data`: the guest fetches them from the requester with a workload identity token its bidder issues. ## More - [protocol/flow.md](protocol/flow.md): one real contract, step by step, its records and its failure branches - [protocol/compute-contract-flow-map.md](protocol/compute-contract-flow-map.md): the end-to-end map of every layer, from the lexicons to the guest transport - [protocol/README.md](protocol/README.md): every record and XRPC method; [protocol/glossary.md](protocol/glossary.md): every NSID - [protocol/identity.md](protocol/identity.md): identities, keys, associations, guest requesters - [protocol/release.md](protocol/release.md): release channels and self-update - [SYSTEM.md](SYSTEM.md): the hosts and applications