Lexicon Garden

chat.yakka.role

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).

Repository @yakka.chat did:plc:wpjoy2orkqq5m65vq7gg7liz namespace authority
Details · record, key tid
Kindrecord
Record keytid
Authorityyakka.chat
Indexed
Compare Edit in builder → Fork →

Record

record · key tid

Properties

color

string

Display colour as #rrggbb. Presentational only.

createdAt

requiredstring · datetime

name

requiredstring
  • maxLength: 512
  • maxGraphemes: 64

Similar lexicons

semantic match

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

  • 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.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).

  • social.colibri.role

    record

    A named bundle of permissions assignable to community members. Lives on the community repo.

  • fyi.opensocial.role

    record

    Declares that a role exists, in the members space. The record key is the role id, of 64 characters at most. A role is deleted only once no member holds it and the permissions record grants it nothing.

  • tech.tokimeki.forum.role

    record

    A moderator role the community grants to a member. Written by the community account (the space authority) into its OWN repo within the server's public space, so any reader of the space can verify who may moderate (e.g. whose tech.tokimeki.forum.hide records to honour). rkey is derived from the subject DID ('m' + base32lower(sha256(did))[0:26]) so one record exists per member; delete it to revoke. Plain membership is not a record.