Lexicon Garden

support.supper.feed.post

Public, supporter-authored Supper feed post sidecar for a completed support event. This record is presentation/social context only: payment truth remains in the referenced attested payment record, and private checkout, order, fulfillment, buyer contact, commission brief, attachment, and DM data must stay off-protocol.

Repository @supper.support did:plc:mcsqdltevtjpu26xthzzmm2l namespace authority
Details · record, key any
Kindrecord
Record keyany
Authorityfeed.supper.support
Indexed
Compare Edit in builder → Fork →

Record

record · key any

Properties

bskyPostRef

ref

Strong reference to the author's Bluesky post sharing this support event. Mirrors site.standard.document's field: the referenced post is the public discussion anchor (replies and likes live on Bluesky), so clients can locate the thread without an app-specific lookup.

Reference

createdAt

requiredstring · datetime

When this public feed post was created.

kind

requiredstring

Supper surface that produced the feed post. This is display context, not payment settlement state.

  • maxLength: 32
  • knownValues: tip | subscription | shop-purchase | commission-purchase

listing

ref

Optional public listing or entitlement reference related to the support event, such as a money.atmosphere.product, support.supper.commission, or support.supper.entitlement record.

Reference

payment

requiredref

Versioned reference to the attested payment record that authorizes this public feed post. This should point to a network.attested.payment.* record in the payer's repository.

Reference

recipient

requiredstring · did

DID of the creator or project whose Supper feed should display this post.

text

string

Optional public supporter-authored message for the Supper feed. Do not put private checkout notes, commission briefs, fulfillment details, contact information, addresses, phone numbers, emails, or attachment URLs here.

  • maxLength: 3000
  • maxGraphemes: 300

viaProject

string · did

Optional project DID when the support was routed through a project distinct from the recipient account.

Similar lexicons

semantic match

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

  • support.supper.feed.getCreatorFeed

    query

    Get a creator's verified cross-repo support feed: support.supper.feed.post records authored on every supporter repo whose recipient is the named creator, newest first. Every returned post carries a payment strongRef verified against an active broker-attested payment; the AppView never re-derives amount/currency/status. Public read; unverified posts are never returned and outputs carry only public record bodies, never private metadata.

  • cv.atmos.feed.post

    record

    A post that lives on Atmos and is not shown on Bluesky. It sits in the author's own repo and is public like every record there: any AT Protocol app can read it, but apps that do not know this type do not show it, so it does not appear on Bluesky. When the author shares it to Bluesky, an app.bsky.feed.post is written at the same record key and crosspost names it; the two records are one post. Treat crosspost as the link between them, never the shared record key alone, and only when crosspost.uri

  • support.supper.entitlement

    record

    A Supper-owned entitlement anchor referenced from attested.network payment records. The record identifies what Supper should unlock or recognize; payment state remains in network.attested.payment.* records and private fulfillment details stay off-protocol.

  • support.supper.actor.listSupporting

    query

    List the creators a supporter has payment-verified support.supper.feed.post records for across all repos. The cross-repo inverse of feed.listSupporters. Self-authorship alone is not payment evidence. Public read; returns creator DIDs and aggregate counts only, never amounts, emails, or processor identifiers.