Module sections 

One struct per [section], read from the real flag set and from didbot-serve/src/routes.rs’s constants — see the crate root for which of these a caller actually applies today.

Every struct here carries #[serde(deny_unknown_fields)] and every field is optional: a section an operator has not written is a section this binary decides on its own, the same as a flag nobody passed. What a section may not hold is a scope, a permission, or an allowlist of apps — see the crate root’s doc for why.

Structs

BlobsSection

What one blob, one account’s blobs, and every account’s blobs together may come to.

CapacitySection

How many accounts this deployment may hold at once, and other bounds on what this deployment keeps rather than what an agent may do.

CredentialSection

The bearer credential provisioning mints for a freshly created account.

DisclosureSection

Which bot.did.* routes this deployment has closed to a public, unauthenticated caller.

DnsSection

DNS provider selection, once dns-providers lands a second backend.

IntervalsSection

How often each background loop runs.

NamesSection

How agents are named.

OAuthSection

The authorization server’s own bounds: the scope ceiling every grant is narrowed to, how many decisions may sit undecided at once, and the resolver it finds a permission set’s authority through.

OidcSection

Which OpenID Connect issuers this server will fetch keys from, and how fresh a token has to be.

OperatorSection

The operator: how long their sign-in lasts, and how long their claim outlives a poll that cannot see it.

ParkSection

How bot.did.parkKey holds a key and bounds who may park one.

PolicySection

Which DID’s records this server reads as policy, once policy-store exists to read anything.

PoolSection

One named source of names: the zones and labels it holds, and how it makes a name. See plan/pools.md.

ProxySection

What one account may spend of atproto-proxy, which forwards a call to whatever service a DID document names, from this server’s address.

RelaySection

Which relays didbot announce and the dashboard’s POST /dashboard/api/relay/announce announce this server to, over com.atproto.sync.requestCrawl and notifyOfUpdate. Every relay named by either key is asked, hostname first, and a relay named twice is asked once.

ServerSection

Where the server binds and listens.

SessionsSection

The sessions this server issues from a proof.

TlsSection

TLS certificate sourcing, mirroring didbot-tls’s configuration surface.

TreeSection

The shape one creator may give the ownership tree, enforced by the server whatever policy says.

WritesSection

How fast one account may write, as two token buckets: one on write operations and one on request bytes. See didbot_serve::write_meter.

ZoneSection

The zones accounts are minted under, and who answers for them.