at.atjam.signup
Declares the record creator's intent to participate in the referenced round.
Details · record, key any
| Kind | record |
|---|---|
| Record key | any |
| Authority | atjam.at |
| Indexed |
Record
record · key anyProperties
invitation
refStrong-ref to an at.atjam.invitation that authorizes this signup. Required by readers when round.joinMode is 'hosted' or 'network'; ignored when 'open'. The invitation's invitee DID MUST match this signup's creator DID — consumers validate this relationship.
note
stringOptional note from the participant (e.g. what they plan to do).
maxLength: 3000maxGraphemes: 300
Strong-ref to the at.atjam.round record.
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
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.
-
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.
-
An invitation for someone to join Agora
-
at.atjam.submission
recordA participant's submission to a round. atjam does not host the deliverable; it points at it. The strong way is `payload` — a strong-ref to a record on whichever ATProto app owns the data (plyr.fm track, standard.site post, etc.), which is content-addressed, verifiable, and portable. The fallback is `url` — a plain link, for deliverables that don't live on ATProto yet (an itch.io build, a hosted doc). Prefer payload; `url` is the humble alternative. The lexicon can't express "one-of" across field
-
pics.2bit.challenge.join
recordThe author taking part in a challenge. Joining is how a challenge comes to be offered wherever the author posts - nobody is signed up for a challenge they didn't join - and it's public, like a follow, so a challenge can show who's taking part before anyone has entered. Entering a prompt joins too. One join per person per challenge is enforced by this app's AppView rather than the record key: its write path won't write a second, and where another client leaves several, they count once. Leaving de