at.atjam.submission
Declares a submission by the record creator to the referenced round.
Details · record, key tid
| Kind | record |
|---|---|
| Record key | tid |
| Authority | atjam.at |
| Indexed |
Record
record · key tidProperties
note
stringOptional caption/description from the submitter.
maxLength: 3000maxGraphemes: 300
payload
refPreferred deliverable: a strong-ref to the record on its native ATProto app. The referenced record's $type SHOULD appear in the round's acceptedSubmissionTypes.
Strong-ref to the at.atjam.round record being submitted to.
url
string · uriFallback deliverable for work not on ATProto: a plain link (itch.io build, hosted doc, etc.). Unverifiable and mutable, so prefer payload when the deliverable is a record. Ignored when payload is present.
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
at.atjam.round
recordA single instance of a jam: an assignment with a deadline that participants sign up for and submit to. State (open / in-progress / closed) is derived from milestones, not stored as an enum.
-
at.atjam.jam
recordA recurring (or one-shot) creative challenge that contains rounds. Identity-bearing container: 'EPTSS-the-project' is one jam; a one-shot game jam is also a jam with a single round.
-
at.atjam.signup
recordA declaration of intent to participate in a specific round. The participant's DID is implicit (the record creator). When the round's joinMode is 'hosted' or 'network', a signup is only valid for readers when it strong-refs an at.atjam.invitation written by a valid inviter. Writers SHOULD key a signup by a hash of the round's at-uri (the first 32 hex chars of its SHA-256) and write it with putRecord, so a person has at most one signup per round; readers MUST still tolerate several signups from on
-
at.atjam.invitation
recordAn invitation to participate in a round, written by an inviter on their own PDS. The inviter's DID is implicit (the record creator). Required for participation in rounds where round.joinMode is 'hosted' (only the jam organizer can invite) or 'network' (the organizer or any current participant that meets networkGate can invite). Consumers MUST validate that the creator DID is a valid inviter for the referenced round before treating an invitation — and the signup it authorizes — as authoritative.