socialweb.computer

Request and provide VMs on an atproto compute market.

lexicons and xrpc

reference

XRPC

The 36 XRPC methods (queries, procedures, subscriptions) the market's services serve at /xrpc/<nsid>, generated from lexicons/. Records and objects: lexicons.

com.publicdomainrelay.temp.cluster 10

controlPlaneDownprocedureThe gateway takes the named cluster's control plane down: it flips its desired state to not-running and dematerialises the process group.
controlPlaneUpprocedureThe gateway brings the named cluster's control plane up: it flips the Cluster's desired state to running and materialises its process group and objects, in order.
createClusterprocedureThe gateway creates the named cluster of the calling account and leaves it RUNNING, in one call.
deleteClusterprocedureThe gateway begins the teardown of the named cluster of the calling account.
getKubeconfigprocedureThe gateway returns a kubeconfig for the named cluster of the calling account.
listClustersqueryThe gateway lists the calling account's clusters.
listKubeconfigsqueryThe gateway lists the kubeconfigs issued for the named cluster of the calling account: one ClusterClientCertificate record per kubeconfig, revoked ones included.
revokeIdentityprocedureThe gateway revokes the calling identity's access: it writes the deny record FIRST, then deletes the ServiceAccount and the name-keyed artifacts, and leaves the grant record in a terminal Revoked state rather than deleting it.
revokeKubeconfigprocedureThe gateway revokes one kubeconfig of the named cluster of the calling account: it sets spec.revoked on its ClusterClientCertificate record.
subscribeClusterssubscriptionThe gateway streams the calling account's cluster state as an atproto event stream (binary WebSocket frames, each a DRISL-CBOR header then a DRISL-CBOR payload).

com.publicdomainrelay.temp.compute.guest 1

subscribeEventssubscriptionServed by the bidder's GuestControlPlane to a guest holding a workload identity token (in the Authorization header only): streams the requester-authored compute.events.guest.* payloads for that guest's contract, in order, after cursor.

com.publicdomainrelay.temp.compute.secrets 1

getSecretsqueryThe requester serves a contract's secrets bundle to its guest, whose setup-secrets.service fetches it at boot and again after a guest.secretsUpdated.

com.publicdomainrelay.temp.keepalive 1

pingqueryThe did:key ingress relay's keepalive: on a timer it sends each connected subscriber a request frame for GET /xrpc/com.publicdomainrelay.temp.keepalive.ping (no params, headers or body) through its com.fedproxy.temp.xrpc.subscribe socket, and ignores the answer.

com.publicdomainrelay.temp.market 4

submitAcceptprocedureA requester submits its accept of a bid to the bidder, which records a provisioning intent and answers 202 at once.
submitBidprocedureA bidder submits a bid it wrote to the requester.
submitEventprocedureA contract party submits a market.event it wrote to the other party.
submitRfpprocedureA requester submits an RFP to a bidder.

com.fedfork.exec.ops 7

getBidderqueryA bidder answers its readiness: its MarketIdentity (status phase, pendingAction kind and reason only, conditions type, status and reason), its Bidder component (spec.policy) and its MarketBidder root (status phase and did); each null when absent.
getHealthqueryA bidder answers its core's health since its process started: its unit, start time, ERROR line counts (all, and in its first 10 minutes), automatic restarts, VM processes, the last three ERROR lines and its guest image readiness.
getLogqueryA bidder answers how many lines of its core's log since its process started hold one known message, optionally with one subject, and the first 50 of them as fixed fields.
getRequesterLogqueryThe ssh gateway answers its core's log lines of one DID since a time whose message is one of: requester_session_atirc_revoked, requester_release, requester_released, requester_release_settled_by_termination, requester_contract_records_deleted, requester_submit_accept_declined.
getVmqueryA bidder answers one of its VMs by name: its ComputeVM (as listVms) and its FirecrackerVM (status phase, lostReason, image sha256 and fetched); each null when absent.
getVmMemoryqueryA bidder answers the memory cgroup figures of one of its VMs' units.
listVmsqueryA bidder answers its ComputeVM objects in a fixed projection: name, deletionTimestamp, spec vm.cpus, requester.did, contract.receipt.uri, status phase and lostReason.

computer.socialweb.cicd.process 6

execproceduresocialweb-guest-agent runs a command with /bin/sh -c as root in the guest and answers when it ends.
killproceduresocialweb-guest-agent sends a signal to a job's process group; a job that already exited is left alone.
listproceduresocialweb-guest-agent lists the jobs it holds, oldest first; an exited job stays listed until a new job needs its place among the 128.
readproceduresocialweb-guest-agent answers a job's interleaved stdout and stderr from a byte cursor, waiting up to waitMs for more.
startproceduresocialweb-guest-agent starts a background job, a command with /bin/sh -c as root in the guest, and answers its id at once.
writeproceduresocialweb-guest-agent writes to a running job's stdin and can close it.

computer.socialweb.k8s 2

getJobqueryThe gateway reads the status of one batch/v1 Job in the named cluster of the calling account, with the pods it owns and the tail of each container's log, without a kubeconfig.
kubectlApplyServerSideprocedureThe gateway server-side applies one Kubernetes object to the named cluster of the calling account, as `kubectl apply --server-side` would, without a kubeconfig.

network.attested 1

verifyqueryVerify the attestations on a record.

com.fedproxy.temp.xrpc 3

getRegistrationNonceprocedureIssues a registration nonce: served by the did:key ingress relay on its own hostname, called by a subscriber (bidder or requester) as a POST right before it opens com.fedproxy.temp.xrpc.subscribe.
subscribesubscriptionThe subscriber's WebSocket to the did:key ingress relay (the Go relay `socialweb-computer internal ingress-relay`, at xrpc.fedproxy.com): a bidder or requester holds it open so that HTTP requests and WebSocket subscriptions sent to its host, <did label>.<relay hostname>, are carried to it and answered over this socket.
tunnelsubscriptionA TCP tunnel to a subscriber through the did:key ingress relay: a caller opens a WebSocket to /xrpc/com.fedproxy.temp.xrpc.tunnel on the subscriber's host (<did label>.<relay hostname>, or a custom-domain alias of it), and the subscriber connects it to its configured TCP target or in-process stream handler.