At this level
org.anthers · 11- org.anthers.comment record A comment somebody wrote about a work, a post, or another comment. It lives in the commenter's own repository, which is the honest answer to who wrote it: the words are theirs, they travel with them, and they go when the commenter goes. A comment whose subject is another comment is a REPLY — the distinction is hierarchy rather than kind, so there is one record type and not two. A service displaying these may decline to show one; it cannot unsay it.
- org.anthers.creatorPermissions permission-set
- org.anthers.creditAcceptance record A credited person's acceptance that they contributed to a work. It lives in the contributor's own repository, and is written only when the person Anthers names as a contributor agrees to be named there.
- org.anthers.creditConfirmation permission-set
- org.anthers.follow record One account following another on Anthers, meaning: show me what this person releases. Anthers mints this rather than adopting `app.bsky.graph.follow`, which it could. Following a creator for their releases is a different act from an edge in a microblog's social graph — somebody may reasonably want one without the other, and a creator may not be on that network at all — so conflating them would mean following a game developer here silently added them to a timeline somewhere else. Mirroring a foll
- org.anthers.post record A post by a creator — an announcement, a devlog, a note to an audience. Posts are written by creators; a user's contributions are comments, reviews and votes rather than posts of their own. A post is long-form: it may carry headings, lists, code, quotes and images, which is why its content is markdown rather than the plain text and facets a microblog post uses.
- org.anthers.project record A project — a container a creator groups related works and posts under. It deliberately carries NO list of what is in it: a record naming its own contents has to be rewritten every time a work is added or removed, which broadcasts a new version on every change and makes the record a worse copy of a query. Membership belongs on the other end, as an optional field on the work, which may be added later at no cost.
- org.anthers.review record A review of a work — whether the reviewer recommends it, and the words that explain why. It is a review rather than a rating because a verdict without reasons tells another user nothing about whether to trust it. A review attaches to a work and to nothing else: a post is an announcement, and recommending one means nothing. It lives in the reviewer's own repository. Editing a review rewrites this record in place rather than writing a new one, so a link to it keeps working — which also means a ref
- org.anthers.userPermissions permission-set
- org.anthers.vote record A vote on a work, a post, a comment or a review — the voter saying which way they want it to move. It is a vote with a direction rather than a reaction with a sentiment, because that is what the gesture actually does: it is the input to ranking. Both directions are published, deliberately. If votes decide what rises and what folds away, publishing only the ones pushing upward would describe the mechanism dishonestly. How a service DISPLAYS them is its own decision and no part of this record.
- org.anthers.work record One entry in a creator's Catalog — a game, video, album, essay, or other work they have released. This record is the public LISTING for that work: it says what the work is and where to reach it, and it never carries the work itself. It exists only while the work is publicly listed, and whether a particular person may open the work is decided by the service hosting it, never by this record.