Browse lexicons

• chat.atagents.agent.document record
• chat.atagents.agent.encryptedSessionArchive record
• chat.atagents.agent.encryptedSessionChunk record
• chat.atagents.agent.encryptedSpace space
• chat.atagents.agent.memory record
• chat.atagents.agent.message record
• chat.atagents.agent.session record
• chat.atagents.agent.sessionKeyGrant record
• chat.atagents.agent.space space
• chat.atagents.agent.summary record
• chat.atagents.chat.channel record DRAFT v0.1 candidate; not published or approved for production. See proposals/shared-workspace-v01.md.
• chat.atagents.chat.message record DRAFT v0.1 candidate; not published or approved for production. See proposals/shared-workspace-v01.md.
• chat.atagents.chat.space space Experimental workspace with shared Markdown documents and immutable assigned/tracking task records.
• chat.atagents.defs defs Shared reference to an exact record revision; author and Space context must be authenticated by the client.
• chat.atagents.document.document record Experimental shared Markdown document revision. Each editor creates an immutable record; previous pins the edited revision. Path is relative to the optional channel or the whole Space.
• chat.atagents.profile.account record DRAFT v0.1 candidate; not published or approved for production. See proposals/shared-workspace-v01.md.
• chat.atagents.profile.status record Experimental, unpublished agent-authored activity. Not liveness, authorization, or task completion. See proposals/agent-status.md.
• chat.atagents.task.task record Experimental task pilot: immutable assignments, tracking, and progress records. Execution requires runtime policy; no global claim lock.
• chat.atagents.task.update record Experimental task pilot: immutable assignments, tracking, and progress records. Execution requires runtime policy; no global claim lock.

• chat.bsky.actor.declaration record A declaration of a Bluesky chat account.
• chat.bsky.actor.defs defs A current group convo member.
• chat.bsky.actor.deleteAccount procedure
• chat.bsky.actor.exportAccountData query
• chat.bsky.actor.getStatus query Get the authenticated viewer's chat status: whether their account is chat-disabled and whether their group-membership additions are restricted to accounts they follow.
• chat.bsky.authFullChatClient permission-set
• chat.bsky.convo.acceptConvo procedure Marks a conversation as accepted, so it is shown in the list of accepted convos instead on the request convos.
• chat.bsky.convo.addReaction procedure Adds an emoji reaction to a message. Requires authentication. It is idempotent, so multiple calls from the same user with the same emoji result in a single reaction.
• chat.bsky.convo.defs defs Event indicating the viewer accepted a convo, and it can be moved out of the request inbox. Can be direct or group.
• chat.bsky.convo.deleteMessageForSelf procedure Marks a message as deleted for the viewer, so they won't see that message in future enumerations.
• chat.bsky.convo.getConvo query Gets an existing conversation by its ID.
• chat.bsky.convo.getConvoAvailability query Check whether the requester and the other members can start a 1-1 chat. Only applicable to direct (non-group) conversations. If an existing convo is found for these members, it is returned. Does not create a new convo if it doesn't exist.
• chat.bsky.convo.getConvoForMembers query Get or create a 1-1 conversation for the given members. Always returns the same direct (non-group) conversation. To create a group conversation, use createGroup.
• chat.bsky.convo.getConvoMembers query Returns a paginated list of members from a conversation.
• chat.bsky.convo.getLog query
• chat.bsky.convo.getMessages query Returns a page of messages from a conversation.
• chat.bsky.convo.getUnreadCounts query Returns unread conversation counts for conversations that are unlocked, not muted, split by convo status. Direct convos are excluded when a block relationship exists between the actor and the other member, or when the other member's account is deleted or deactivated. Group convos are considered unread if they have unread join request counts.
• chat.bsky.convo.leaveConvo procedure Leaves a conversation (direct or group). For group, this effectively removes membership. For direct, membership is never removed, only changed to remove from enumerations by the user who left.
• chat.bsky.convo.listConvoRequests query Returns a page of incoming conversation requests for the user. Direct convo requests are returned as convoView; group join requests made by the user are returned as joinRequestConvoView.
• chat.bsky.convo.listConvos query Returns a page of conversations (direct or group) for the user.
• chat.bsky.convo.lockConvo procedure Locks a group convo so no more content (messages, reactions) can be added to it.
• chat.bsky.convo.muteConvo procedure Mutes a conversation, preventing notifications related to it.
• chat.bsky.convo.removeReaction procedure Removes an emoji reaction from a message. Requires authentication. It is idempotent, so multiple calls from the same user with the same emoji result in that reaction not being present, even if it already wasn't.
• chat.bsky.convo.sendMessage procedure Sends a message to a conversation.
• chat.bsky.convo.sendMessageBatch procedure Sends a batch of messages to a conversation.
• chat.bsky.convo.unlockConvo procedure Unlocks a group convo so it is able to receive new content.
• chat.bsky.convo.unmuteConvo procedure Unmutes a conversation, allowing notifications related to it.
• chat.bsky.convo.updateAllRead procedure Sets conversations from a user as read to the latest message, with filters.
• chat.bsky.convo.updateRead procedure Updates the read state of a conversation from, optionally specifying the last read message.
• chat.bsky.embed.joinLink object A join link embedded in a chat message.
• chat.bsky.group.addMembers procedure Adds members to a group. The members are added in 'request' status, so they have to accept it. This creates convo memberships.
• chat.bsky.group.approveJoinRequest procedure Approves a request to join a group (via join link) the user owns. Action taken by the group owner.
• chat.bsky.group.createGroup procedure Creates a group convo, specifying the members to be added to it. Unlike getConvoForMembers, this isn't idempotent. It will create new groups even if the membership is identical to pre-existing groups. Will create 'request' membership for all members, except the owner who is 'accepted'.
• chat.bsky.group.createJoinLink procedure Creates a join link for the group convo.
• chat.bsky.group.defs defs Preview for a disabled join link. Carries only the code so clients can correlate with the input and render a disabled state.
• chat.bsky.group.disableJoinLink procedure Disables the active join link for the group convo.
• chat.bsky.group.editGroup procedure Edits group settings.
• chat.bsky.group.editJoinLink procedure Edits the existing join link settings for the group convo.
• chat.bsky.group.enableJoinLink procedure Re-enables a previously disabled join link for the group convo.
• chat.bsky.group.getJoinLinkPreviews query Get public information about groups from join links. The output array matches the input codes one-to-one by position (and each view also carries its 'code'). Disabled codes return a disabledJoinLinkPreviewView, and codes that do not map to a previewable link return an invalidJoinLinkPreviewView.
• chat.bsky.group.listJoinRequests query Lists a page of request to join a group (via join link) the user owns. Shows the data from the owner's point of view.
• chat.bsky.group.listMutualGroups query Returns a page of group conversations that both the requester and the specified actor are members of.
• chat.bsky.group.rejectJoinRequest procedure Rejects a request to join a group (via join link) the user owns. Action taken by the group owner.
• chat.bsky.group.removeMembers procedure Removes members from a group. This deletes convo memberships, doesn't just set a status.
• chat.bsky.group.requestJoin procedure Sends a request to join a group (via join link) to the group owner. Action taken by the prospective group member.
• chat.bsky.group.updateJoinRequestsRead procedure Marks all join requests as read for the group owner.
• chat.bsky.group.withdrawJoinRequest procedure Withdraws a pending request to join a group. Action taken by the prospective member who originally requested to join.
• chat.bsky.moderation.defs defs A view of a conversation for moderation purposes. Unlike chat.bsky.convo.defs#convoView, it does not include viewer-specific data (such as muted, unreadCount, status, lastMessage, lastReaction), since the requester is a moderator and not a member of the conversation. The member list is not included; use chat.bsky.moderation.getConvoMembers to list members.
• chat.bsky.moderation.getActorMetadata query
• chat.bsky.moderation.getConvo query Gets an existing conversation by its ID, for moderation purposes. Does not require the requester to be a member of the conversation.

8 more under chat.bsky ›

• chat.firehose.authFull permission-set
• chat.firehose.getUserChannels query Get channels for the authenticated user.

• chat.gel.assistant.conversation space A single chat with an assistant. The space holds the chat's info record and messages. When sharing a chat, the read access on the space must be updated.
• chat.gel.assistant.conversationRef record A single user chat entry, kept in their settings space. The record key is the chat's space key. When a chat is changed, update its entry with a new updatedAt so that the appview notices the change.
• chat.gel.assistant.defs defs The model's reasoning effort.
• chat.gel.assistant.info record Title and system prompt for a conversation.
• chat.gel.assistant.message record One message in a chat, from the user or the assistant. A reply's key is the user message's key plus '.r' and the attempt number, such as '.r0' or '.r1'. The app creates the reply with status 'pending' and no content, it fills it in when generation ends. Creating fails if the key is taken, so each attempt gets exactly one reply. Sort replies by attempt number rather than by key, since '.r10' sorts before '.r2'.
• chat.gel.assistant.permissions permission-set
• chat.gel.assistant.preferences record
• chat.gel.assistant.requestSync procedure Trigger a sync of the caller's chats from their PDS, and reply to any pending generation requests.
• chat.gel.assistant.settings space The user's chat preferences and conversation index.

• chat.sprk.actor.declaration record A declaration of a Spark chat account.
• chat.sprk.actor.defs defs
• chat.sprk.authFull permission-set
• chat.sprk.convo.acceptConvo procedure
• chat.sprk.convo.addReaction procedure Adds an emoji reaction to a message. Requires authentication. It is idempotent, so multiple calls from the same user with the same emoji result in a single reaction.
• chat.sprk.convo.defs defs
• chat.sprk.convo.getConvo query
• chat.sprk.convo.getConvoAvailability query Get whether the requester and the other members can chat. If an existing convo is found for these members, it is returned.
• chat.sprk.convo.getConvoForMembers query
• chat.sprk.convo.getLog query
• chat.sprk.convo.getMessages query
• chat.sprk.convo.leaveConvo procedure
• chat.sprk.convo.listConvos query
• chat.sprk.convo.muteConvo procedure
• chat.sprk.convo.removeReaction procedure Removes an emoji reaction from a message. Requires authentication. It is idempotent, so multiple calls from the same user with the same emoji result in that reaction not being present, even if it already wasn't.
• chat.sprk.convo.sendMessage procedure
• chat.sprk.convo.sendMessageBatch procedure
• chat.sprk.convo.unmuteConvo procedure
• chat.sprk.convo.updateAllRead procedure
• chat.sprk.convo.updateRead procedure
• chat.sprk.moderation.getActorMetadata query
• chat.sprk.moderation.getMessageContext query
• chat.sprk.moderation.updateActorAccess procedure

• chat.yakka.ban record A member is barred from a server. Authority-written (ADR 0006). Enforcement is layered (ADR 0008): the mint refuses new credentials immediately and the realtime tier cuts the socket at once, but credentials already held live out their 2h TTL — the protocol has no revocation (Law 2). A ban is therefore effective within the TTL everywhere, and instantly where we serve.
• chat.yakka.channel.info record A channel's presentation and its gate. Authority-written into the directory space via the space host (ADR 0006). The gate here is the same policy the mint enforces (ADR 0007) — an open and a gated channel are structurally identical spaces, so toggling `allowedRoles` is a policy edit and never a data migration (ADR 0002).
• chat.yakka.defs defs Viewer state, kept apart from the channel because it changes on every read while the channel rarely changes.
• chat.yakka.getRealtimeTicket procedure Issue a short-lived, single-use ticket for opening the realtime socket (ADR 0034 §3). A browser cannot set headers on a WebSocket, and a cookie is the wrong instrument across origins — so the ticket goes in the socket URL, which is why it must be worth little: it authenticates one upgrade, once, within seconds. The socket is the appview's primary surface (ADR 0011), so this is not an afterthought but the only authenticated path for most of what a client does.
• chat.yakka.getSession query Who the caller is signed in as. The session cookie carries an opaque id and nothing else (ADR 0034 §2), so this is how a client learns its own DID — it cannot read one out of the cookie, by design. Answers 200 with `signedIn: false` rather than 401 for an anonymous caller: not being signed in is an ordinary state of the application, not an error in the request.
• chat.yakka.getSnapshot query Everything needed for first paint, in one round trip: the viewer's servers, the active server's channels and roster, and one channel's newest timeline page. One method rather than five because this is the server-rendered path — every extra round trip here is latency a reader sees before anything appears. Warm navigations do not call it at all; the client's store already holds the answer.
• chat.yakka.getTimeline query A page of a channel's timeline, newest first, ordered by view sequence (ADR 0012). Paging is by sequence and never by timestamp or record key: TIDs order a repo, never a channel, and two authors' clocks are not comparable.
• chat.yakka.getTimelineAround query A window centred on a sequence, for opening a permalink to an old message. Paging backwards from the tail to reach something linked from months ago would be many round trips, which is the entire reason this is a separate method rather than a parameter.
• chat.yakka.grant record One member holds one role. Authority-written (ADR 0006) — a member cannot grant themselves a role, which is why this is not self-written the way membership is. The mint reads these to decide gated-channel credentials (ADR 0007).
• chat.yakka.markRead procedure Advance the viewer's read marker for a channel. The marker is a `chat.yakka.readMarker` record in the viewer's own settings space (ADR 0017), so it follows them to any client rather than living in this appview's idea of them. Monotonic: a marker never moves backwards, so an out-of-order call from a second tab cannot un-read a channel.
• chat.yakka.member record Membership of a server, written by the member into the server's directory space. Join *is* the write (ADR 0005): there is no separate roster to keep in step, because the directory's writer set converges to the exact roster by construction. Leaving is deleting this record.
• chat.yakka.message record A message in a channel or DM space. The record lives in the *author's* repo within the space, so a message has no single owning collection to sort by — it is identified by (authorDid, tid). One collection serves channels and DMs alike (ADR 0016), which is what lets one pipeline carry both.
• chat.yakka.mute record Something the viewer does not want to hear from — a space, a server, or a person. Personal state in the viewer's own settings space (ADR 0017). A mute is a presentation preference, never access control: it hides, and hiding is not gating (Law 1).
• chat.yakka.postMessage procedure Write a message to the author's own repo, under their OAuth grant (Law 4: write admission belongs to the author's PDS, never to the appview). The appview is the caller's agent here, not an authority — a refusal from the PDS is reported as one rather than absorbed. Resolves once the record is ingested and sequenced, by which time the client has already shown a provisional copy and will reconcile on (uri, cid) (ADR 0011).
• chat.yakka.reaction record One reactor's reaction to one message. Written into the reactor's own repo within the message's space, so counts are an aggregate the view computes across the space's repos — never a mutable field on the message, which nobody but the author could write.
• chat.yakka.readMarker record How far the viewer has read in one space. Lives in the viewer's own chat.yakka.settings space, authority=self (ADR 0017), so read state follows the person across devices and into third-party clients.
• chat.yakka.resolveChannel query Resolve a URL's channel segment, which may be a name or a TID. Called by the client's route guard before anything renders. The five outcomes are distinct on purpose. Collapsing them would either lie about deleted channels or hide gated ones, and both are facts a reader is entitled to. `forbidden` deliberately reveals that a channel exists — which is safe only because channels are whole spaces and the credential mint has already made the same disclosure (ADR 0007).
• chat.yakka.resolveMessage query Resolve a permalink fragment's message ref within a channel. `ambiguous` is the case the explicit fragment form exists to avoid: two authors can in principle mint the same TID in one channel. Rare at any single channel's scale, not impossible across many — so it is a case, not an assumption.
• chat.yakka.role record A role that may be granted to members. Authority-written (ADR 0006). Roles carry no permissions of their own — they are named subjects that channel gates and the mint policy refer to (ADR 0007).
• chat.yakka.server.info record A server's own presentation. Authority-written into its directory space (ADR 0006), one per server, which is why the key is literal. Named `server.info` rather than `server` because `chat.yakka.server` is already the *space type* of a directory space. Reusing the NSID for a collection would leave two different things spelled the same, and this record is the exact analogue of `chat.yakka.channel.info` anyway: the presentation of a space, written by whoever holds authority over it.
• chat.yakka.toggleReaction procedure Add or remove the viewer's reaction to a message. A reaction is a record in the viewer's own repo, so this creates or deletes one — there is no shared counter to increment, and the count a client renders is the appview's tally of records it has ingested.