- com.publicdomainrelay.temp.agent.class record An agent class definition. Acts as a template that agents are instantiated from. The class is a named bundle of skills (strongRefs to com.publicdomainrelay.temp.agent.skill records) plus optional metadata. Instantiating an agent from a class means spawning a runtime (or sub-agent context) seeded with this skill set.
- com.publicdomainrelay.temp.agent.skill record An agent skill record that describes a capability the agent can perform, with examples and property references.
- com.publicdomainrelay.temp.auth.allowlist.rbacDid record not from the namespace authority Self-allowlist granting the record owner's DID access to their own account-scoped operations. Used by bidders and other automated actors to authorize AT Protocol writes (e.g. applyWrites) on their own repo via service-auth tokens.
- com.publicdomainrelay.temp.badgeBlueKeys record Associates a device key with a DID, enabling key→DID lookup for vouch graph traversal and service authorization.
- com.publicdomainrelay.temp.compute.config.wif.simple record Simple Workload Identity Federation parameters used by the requester to obtain a token authorized for the provider.
- com.publicdomainrelay.temp.compute.events.vm.delete record Requests that the provider delete/tear down a provisioned VM — e.g. because its workflow finished, or because its policy engine never came up. Sent by the requester, since the provider treats the VM as a black box and cannot observe these conditions itself.
- com.publicdomainrelay.temp.compute.events.vm.onNetwork record Reports that a provisioned VM has come up on the network and is reachable (e.g. it registered its SSH key / fedproxy route and its policy engine answered).
- com.publicdomainrelay.temp.compute.events.vm.started record Reports that a provisioned VM has started booting.
- com.publicdomainrelay.temp.compute.vm record Descibes a virtual machine
- com.publicdomainrelay.temp.gateway.deleteCompute procedure Tear down a compute resource identified by its receipt. Gateway submits a market.event with a compute.events.vm.delete payload to the winning bidder.
- com.publicdomainrelay.temp.gateway.requestComputeVM procedure Request a VM through the compute contract gateway. Gateway builds cloud-init from sshPublicKey, creates compute.vm and market.rfp records, discovers bidders, runs the full RFP protocol, submits accept, and verifies the receipt. Returns receipt refs and websocatUrl for SSH access.
- com.publicdomainrelay.temp.gateway.requestComputeWorkerEphemeral procedure Request an ephemeral Deno worker through the compute contract gateway. Gateway bundles source, creates workerManifest record, runs the full RFP protocol, and returns the worker instance ref for single-request execution.
- com.publicdomainrelay.temp.gateway.requestComputeWorkerPersistent procedure Request a persistent Deno worker through the compute contract gateway. Gateway bundles source, creates workerManifest record, runs the full RFP protocol, starts the worker, and returns the worker instance ref and execute URL.
- com.publicdomainrelay.temp.gateway.subscribeComputeEvents subscription Subscribe to lifecycle events for a compute contract. Gateway pushes events as they arrive from the bidder (vm.started, vm.onNetwork, terminated).
- com.publicdomainrelay.temp.market.accept record Acceptance of a bid on an RFP
- com.publicdomainrelay.temp.market.accepts.free record The requester's acceptance of a bid's free (no-cost) terms. Minted before settling and passed (by AT-URI + CID) to the grant endpoint named in the bids.free url; the bidder resolves it and mints a com.publicdomainrelay.temp.market.receipts.free in response. The free counterpart of com.publicdomainrelay.temp.market.accepts.x402.
- com.publicdomainrelay.temp.market.accepts.x402 record The requester's acceptance of a bid's x402 payment terms. Minted before settling payment and passed (by AT-URI + CID) to the x402 GET endpoint named in the bids.x402 url; the bidder resolves it, verifies payment, and mints a com.publicdomainrelay.temp.market.receipts.x402 in response.
- com.publicdomainrelay.temp.market.badgeBlueKey record Publishes the public half of a badge.blue attestation key that this repo signs market.* records with. The record key is the key's did:key, so a verifier can look up a key by did:key directly in the author's PDS repo — a PDS-native key registry complementing DID-document key binding.
- com.publicdomainrelay.temp.market.bid record A bid on an RFP
- com.publicdomainrelay.temp.market.bidderDiscovery record Published by a bidder in its own repo to announce availability. The bidder periodically updates `updatedAt` to signal liveness. The market registry polls this record to decide whether the bidder is still active.
- com.publicdomainrelay.temp.market.bidderRegistration record An index entry in the market registry's repo tracking a registered bidder. The registry creates one entry per (bidderDid, payloadNsid) pair when a bidder calls registerBidder. Liveness is determined by polling the bidder's own bidderDiscovery record — this index entry carries no heartbeat timestamps. When a bidder goes stale the registry deletes its index entries.
- com.publicdomainrelay.temp.market.bids.free record Bid payload offering compute at no cost
- com.publicdomainrelay.temp.market.bids.x402 record Includes pricing/payment terms and x402 endpoint for issuing a receipt against an accept.
- com.publicdomainrelay.temp.market.event record A lifecycle event reported against a receipt (e.g. a provider-opaque resource like a VM coming up, joining the network, or needing to be deleted).
- com.publicdomainrelay.temp.market.listBidders query List active bidders indexed by the market registry.
- com.publicdomainrelay.temp.market.offering record Declares that a bidder is willing to submit bids for RFPs whose payload NSID is in appliesTo. The bidder's market service DID reference (for submitRfp via PDS proxying) is given by endpointUrl.
- com.publicdomainrelay.temp.market.receipt record Receipt for acceptance of a bid on an RFP
- com.publicdomainrelay.temp.market.receipts.free record Proof-of-grant receipt minted by the bidder in response to a GET against the bids.free url. No payment is involved; the receipt is the bidder's verifiable record that it agreed to provide the resource for free. Returned (by AT-URI + CID) to the requester, which uses it as the payload of the higher-level com.publicdomainrelay.temp.market.accept so the bidder can verify the grant before provisioning. The free counterpart of com.publicdomainrelay.temp.market.receipts.x402.
- com.publicdomainrelay.temp.market.receipts.x402 record Proof-of-payment receipt minted by the bidder in response to a successful x402-gated GET against the bids.x402 url. Returned (by AT-URI + CID) to the requester, which uses it as the payload of the higher-level com.publicdomainrelay.temp.market.accept so the bidder can verify payment before provisioning.
- com.publicdomainrelay.temp.market.registerBidder procedure Register a bidder with the market registry. Called by bidders after they publish a bidderDiscovery record in their own repo and connect to the relay. The registry verifies the caller's service-auth JWT issuer matches the bidderDid, then indexes the bidder so it appears in listBidders queries. Liveness is determined by the registry polling the bidder's bidderDiscovery record — there is no separate heartbeat procedure.
- com.publicdomainrelay.temp.market.relays record List of AT Protocol relay URLs that the record owner recommends for market discovery. Requesters read this record via autoDiscoverRelayUrls to find relays to query for bidder offerings.
- com.publicdomainrelay.temp.market.rfp record Top-level Request For Proposal (RFP). Envelope that strongRefs a domain-specific payload (e.g. compute.vm).
- com.publicdomainrelay.temp.market.submitAccept procedure Submit the AT-URI and CID of an accept record directly to the bidder named in the winning bid's payload, settling the contract: the bidder resolves accept->bid->rfp->vm, provisions the resource, mints a market.receipt record, and returns a strong reference to it plus its submitEvent service DID reference. Must be called via PDS service-proxying (atproto-proxy); the receiver verifies the inter-service auth JWT and requires its issuer to be the DID that authored the referenced accept record. The r
- com.publicdomainrelay.temp.market.submitBid procedure Submit the AT-URI and CID of a bid record directly to the RFP issuer, bypassing the firehose. Used when the RFP includes a submitBid service DID reference. Must be called via PDS service-proxying (atproto-proxy); the receiver verifies the inter-service auth JWT and requires its issuer to be the DID that authored the referenced bid record. The receiver additionally verifies the bid's badge.blue attestations (network.attested.signature): at least one inline signature must verify against the attest
- com.publicdomainrelay.temp.market.submitEvent procedure Submit the AT-URI and CID of an event record directly to the counterparty, bypassing the firehose. Used when the accept or receipt includes a submitEvent service DID reference — e.g. so a requester can tell a bidder to delete a VM whose workflow finished, or whose policy engine never came up, since the bidder treats the VM as a black box. Must be called via PDS service-proxying (atproto-proxy); the receiver verifies the inter-service auth JWT and requires its issuer to be the DID that authored t
- com.publicdomainrelay.temp.market.submitRfp procedure Submit an RFP directly to a bidder whose offering record matches the RFP payload NSID. The bidder creates a bid and optionally calls submitBid back to the RFP issuer. Must be called via PDS service-proxying (atproto-proxy); the receiver verifies the inter-service auth JWT and requires its issuer to be the DID that authored the referenced RFP record. The receiver additionally verifies the RFP's badge.blue attestations (network.attested.signature): at least one inline signature must verify against
- com.publicdomainrelay.temp.requester.associateConfirm procedure Confirm requester association via PDS service-proxied XRPC call. The webapp calls this through the user's PDS with atproto-proxy header set to the requester's DID with #requester_associate service. The requester verifies the inter-service auth JWT, resolves the caller's handle, and presents a CLI confirmation prompt before proceeding with the RFP flow.
- com.publicdomainrelay.temp.tangled.spindle.trigger procedure Manually trigger a pipeline run on a Tangled spindle. Intended to be called via PDS service proxying (the 'atproto-proxy' header, pointed at the spindle's did:web service entry), so the user's PDS mints and signs the inter-service auth token; the spindle verifies the token's issuer against their DID document and requires it to match the trigger's 'actor'. Mirrors the sh.tangled.pipeline fields a knot dispatches on a push/PR event.