com.emdashcms.experimental.publisher.verification
A signed claim that the issuing repo's DID vouches for `subject` as a trusted publisher of EmDash plugins. The official EmDash identity publishes these as the trust root; trusted issuers may delegate by issuing further verification claims of their own. Clients consume the resulting graph via the standard atproto-accept-labelers mechanism. The record key is a TID. Verification is bound to the subject's handle and displayName at the moment of issuance: a change to either invalidates the verification until the issuer re-attests. This matches Bluesky's app.bsky.graph.verification semantics and defends against handle reuse and identity drift.
Details · record, key tid
| Kind | record |
|---|---|
| Record key | tid |
| Authority | publisher.experimental.emdashcms.com |
| Indexed |
Record
record · key tidProperties
When the verification was issued.
Subject's `displayName` from their `com.emdashcms.experimental.publisher.profile` record (rkey `self`) at the moment of issuance. The verification is only valid if the subject's current publisher profile displayName matches this value byte-for-byte. A subject without a publisher profile cannot be verified: the issuer MUST require the subject to publish a publisher.profile before issuing the claim, and clients MUST reject verifications whose subject has no publisher profile resolvable at issuance check time.
maxLength: 1024maxGraphemes: 100
expiresAt
string · datetimeOptional expiration timestamp. If absent, the verification has no automatic expiry. Clients SHOULD treat the verification as not in force after this time, regardless of whether the issuer has revoked it.
Handle of the subject at the moment of issuance. The verification is only valid if the subject's current handle (resolved from their DID document) matches this value byte-for-byte. Any handle change invalidates the verification until the issuer re-attests.
DID of the subject the verification applies to.
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
Record declaring a verification relationship between two accounts. Verifications are only considered valid by an app if issued by an account the app considers trusted.
-
app.bsky.graph.verification
recordRecord declaring a verification relationship between two accounts. Verifications are only considered valid by an app if issued by an account the app considers trusted.
-
A verified creator attestation issued by Babesky. Records are written by Babesky's service DID (did:plc:qtapiembzpxlzsiagnc7eyy3) into its own repository, pointing at the subject's DID. Validity is dynamic: the handle and displayName must still match the subject's current values. Records must be deleted when a creator is removed from Babesky's database.
-
Identity-level metadata for a plugin publisher. One record per publisher DID, located at rkey `self`. Optional: a DID may publish packages without ever publishing a publisher.profile, in which case clients fall back to the publisher's handle and per-package metadata for display. EXPERIMENTAL: this NSID is part of the experimental phase of the EmDash plugin registry. The stable namespace target is com.emdashcms.publisher.profile.
-
A Cartridge-specific verification record for studios, developers, publishers, and games. Written by the Cartridge verifier account.