At this level
win.tomo-x.atventar ยท 8- win.tomo-x.atventar.calendar record not from the namespace authority An Advent calendar for December 1 through 25. The repository owner is the organizer.
- win.tomo-x.atventar.defs defs not from the namespace authority Current calendar record with AppView metadata.
- win.tomo-x.atventar.entry record not from the namespace authority A participant's registration for a day in an Advent calendar. The repository owner is the participant. URL and article reference may be provided independently or together, or omitted before publication.
- win.tomo-x.atventar.getActorEntries query not from the namespace authority List a participant's registrations, newest first by indexedAt, then URI ascending. An optional year filters the referenced calendar's year. Uses the same future-day article filtering and dynamic sheet assignment as getCalendar, including when requesting the caller's own registrations.
- win.tomo-x.atventar.getCalendar query not from the namespace authority Get the current calendar and all its indexed valid registrations across every day and sheet. Entries are ordered by day ascending, indexedAt ascending, then URI ascending. Match calendar membership by URI regardless of the originally referenced CID. This response is not paginated. Future-day registrations remain in the response, but their article URLs and article record references are omitted. Display sheet numbers are dynamically reassigned.
- win.tomo-x.atventar.getProfile query not from the namespace authority Resolve a DID or handle to the service profile. Profile source and storage are implementation details. Return a DID-only profile when the identity exists but display information is unavailable.
- win.tomo-x.atventar.listCalendars query not from the namespace authority List indexed calendars, newest first by indexedAt, then URI ascending. All supplied filters are combined with AND.
- win.tomo-x.atventar.searchCalendars query not from the namespace authority Search calendar titles and descriptions. All supplied filters are combined with AND. Order by relevance descending then URI ascending. Search matching and relevance ranking are implementation details; the cursor is bound to the query and filters.