com.atproto-crates.pds.policyAcceptance
A record of the account holder accepting a policy document set presented by their PDS. Written to the account's own repository so the acceptance travels with the identity: it survives a migration to another host, and can be read by anyone the holder shows it to rather than only by the server that asked.
Details · record, key tid
| Kind | record |
|---|---|
| Record key | tid |
| Authority | pds.atproto-crates.com |
| Indexed |
Record
record · key tidProperties
When the holder accepted. Set by the PDS at the moment the acceptance was recorded.
Identifier of the policy document set that was accepted. Opaque to this lexicon; the operator chooses the form. A dated content hash — `2026-08-05-bafkrei...` — names a specific immutable set, so a later revision is a different value and needs its own acceptance.
maxLength: 512
policyUrl
string · uriWhere the documents were published at the time of acceptance. Recorded because the identifier alone does not say what was read, and the URL may later move or stop resolving.
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
A member's acceptance of a space's policy, in the same content space. The member has accepted the current policy while their newest acceptance there names its URI and CID; older acceptances stay as the record of what they agreed to and when.
-
An identity's acceptance of a Lexicon Garden deployment's site policies. The record key is the deployment's hostname; the acceptance counts while subject names the policy site's current version.
-
A user's affirmative acceptance of an exchange's terms of service / privacy policy. Published on the user's PDS so the record is portable + auditable + survives the user disconnecting from any one exchange. Clients prompt for re-acceptance whenever the active exchange policy's `termsVersion` doesn't match the version on the user's most recent acceptance for that exchange.
-
A community's attestation that it accepts a post. Written only by the community's key holder, automatically once admission checks pass - machine attestation, not human approval. The community is implicit in the repository this record lives in. The record key is deterministic: the unpadded lowercase base32 encoding of the SHA-256 digest of the canonical subject AT-URI (fixed 52 characters, always rkey-safe), so a post has exactly one acceptance rkey per community, concurrent writers converge idem