app.kalangitan.graph.accessGrant

Owner-authored acceptance of a follow-as-access-request on a gated persona. Written by the owner of the persona named in the referenced follow record. Effective access state = follow record exists AND matching grant record exists. NOTE: writing this record alone is not sufficient at the protocol level. The owner must also add the follower's DID to the Space's member list via the space host. Both actions are required; the AppView treats the grant as the app-layer signal and the member list as the enforcement layer.

Repository @iamtheno.name did:plc:2aalhpujw6kqsvraztyqlngu not from the namespace authority
Details · record, key tid
Kindrecord
Record keytid
Authoritygraph.kalangitan.app
Indexed

Record

record · key tid

Properties

createdAt

requiredstring · datetime

subject

requiredstring · at-uri

AT-URI of the app.kalangitan.graph.follow record being accepted.

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • app.kalangitan.graph.follow

    record not from the namespace authority

    Follow of a persona, identified by its profile record's AT-URI. This is both a follow and (for gated personas) an access request, one record type, not two. Lives in the follower's own public repo; only the follower can write or delete it. For a public persona, the follow record alone grants read access to the persona's content. For a gated persona, the AppView treats this record as a pending access request; effective access requires a matching app.kalangitan.graph.accessGrant written by the pers

  • Record declaring a social 'follow' relationship of another account.

  • Record declaring a social follow by the author.

  • A follow relationship. Author follows the subject DID.

  • A follow within Ask Everything. Deliberately distinct from app.bsky.graph.follow: the Ask Everything circle and the Bluesky feed are different social contracts, and neither implies the other.