socialweb.computer

Request and provide VMs on an atproto compute market.

release: channels, versions, manifests

Records

NSIDrkey
software.release.projectsocialweb-computer
software.release.manifestsocialweb-computer:<rc version> as written today (the lexicon says tid)
software.release.versionsocialweb-computer:<version>; previous is the version it replaced
software.release.channelsocialweb-computer:rc, socialweb-computer:stable

software.release.project record key any

A released piece of software (plan 0040).

record

fieldtypedescription
name *string
descriptionstring
createdAt *string datetime

software.release.manifest record key tid

The artifacts of one build.

record

fieldtypedescription
project *string at-uri
commitstring
artifacts *array of software.release.defs#httpArtifact
createdAt *string datetime

software.release.version record key any

A named version of a project: its manifest. Key <project>:<version>.

record

fieldtypedescription
project *string at-uri
version *string
manifest *com.atproto.repo.strongRef
previouscom.atproto.repo.strongRef
An rc: the version its channel pointed at before it, where a rollback goes.
createdAt *string datetime

software.release.channel record key any

A pointer that followers track (rc, stable): the version it names. Key <project>:<name>.

record

fieldtypedescription
project *string at-uri
name *string
version *com.atproto.repo.strongRef
updatedAt *string datetime

software.release.defs defs

also: #httpArtifact #target

An artifact's cid is a CIDv1 raw sha2-256 of the file's bytes: the sha256 of the binary, checked after download.

Trimmed; artifact URL shortened:

{"uri": "at://socialweb.computer/software.release.channel/socialweb-computer:stable",
 "value": {"$type": "software.release.channel", "name": "stable", "updatedAt": "2026-11-19T03:22:08Z",
   "project": "at://did:plc:gmlkrhimoueejcertevr4hl3/software.release.project/socialweb-computer",
   "version": {"uri": "at://did:plc:gmlkrhimoueejcertevr4hl3/software.release.version/socialweb-computer:v0.0.0",
               "cid": "bafyreiciv2ovu65hcfceuvymnyvfswzfbvqfttqut7jh3jxqg4zgq4wwx4"}}}
{"uri": "at://socialweb.computer/software.release.version/socialweb-computer:v0.0.0",
 "value": {"$type": "software.release.version", "version": "v0.0.0", "createdAt": "2026-11-19T03:22:08Z",
   "manifest": {"uri": "at://did:plc:gmlkrhimoueejcertevr4hl3/software.release.manifest/socialweb-computer:v0.0.0-rc186",
                "cid": "bafyreiclhbqbq5deutuerkyevwq332knghnneg64vovwhm35qnvife7aua"}}}
{"uri": "at://socialweb.computer/software.release.manifest/socialweb-computer:v0.0.0-rc186",
 "value": {"$type": "software.release.manifest", "commit": "688c2105f8792f235a22ea84490e4e9fde22d3f9",
   "artifacts": [{"$type": "software.release.defs#httpArtifact", "name": "socialweb-computer-linux-amd64",
     "url": "https://socialweb-computer-kcp.sfo3.digitaloceanspaces.com/main/688c2105.../binaries/socialweb-computer-linux-amd64",
     "cid": "bafkreigusm4ugilrwp3obf5gwehfmwrup6gn5rgizwzmid7ggtrpdxyl6e", "size": 589676670,
     "target": {"os": "linux", "arch": ["amd64"]}}, "..."]}}

Channel rc pointed at socialweb-computer:v0.0.0-rc186 then. A stable version reuses the manifest of the rc it was cut from.

Following A Channel

diagram
bucketsocialweb.computer PDSfollower (install.sh, bidder)bucketsocialweb.computer PDSfollower (install.sh, bidder)getRecord software.release.channel socialweb-computer:<channel>1getRecord version (by the channel's strongRef, CID checked)2getRecord manifest (by the version's strongRef, CID checked)3GET the artifact url for this os/arch4sha256 of the bytes == the artifact cid, size equal5install (bidder: SelfCheck, swap bin/current, restart its units)6

rc, Stable, Promote, Rollback

A push to main runs release (the checks and the one build, published to main/<sha>/), then test (the staging gate), then promote. promote's release step has release-workload write the rc's manifest and version and move channel rc; scripts/promote.sh deploys the socialweb.computer droplets, waits until every bidder of deploy/release/rc-operators.json heartbeats that binary (updateWithin, 10 min), runs the prod gate, and copies main/<sha>/ to releases/<vT>/. Exit 0: release-workload moves channel stable to a new version vT (its manifest the rc's). Anything else, a cancel or a timeout (the workflow's stop) included: channel rc goes back to the rc's previous and scripts/promote.sh rollback puts the droplets and the rc bidders back on the previous binary. Detail: ../deploy.md, .knotless/workflows/promote.yml, scripts/promote.sh.

See Also