76826e95

3. Account creation

Creating on-demand accounts for agents, hosts, and pipelines

⟦a placeholder plate where the nightjar diagram goes⟧

PDSes are designed for multitenancy, and they're good at it. It's not a technical challenge for a PDS to support tens of thousands of accounts on even a moderately sized server.

But most PDSes are designed for human users: onboarding flows, emails, and 2FA. And they use `did:plc`, which is an immutable ledger operated as a shared resource. These limits on account creation are poorly suited to creating large numbers of automated accounts.

`did:web` is an alternative that uses control over a website to establish identity. Roughly: if it's a hostname, and it can serve a `.json` file, then it can be an account.

It's easy to set up one `did:web` account, but `did.bot` specializes in the combined DNS and TLS bookkeeping required to maintain _thousands_ of them.

A surprising consequence is that if you have your own DNS resolution and TLS issuance stack, you can operate `did.bot` entirely disconnected from the Internet.