Every Tuesday · 18:00
Diets
2 vegan · 1 gluten-free · 1 nut allergy
Recurrence
When you create a Gathering, the recurrence picker offers none, daily, weekly, biweekly, monthly. Pick the cadence that matches reality. Common patterns:
- Weekly Council — Tuesday 18:00, every week, indefinite
- Monthly potluck — first Saturday of the month
- Daily compost turn — every day, no end date
If a single instance moves (the Council meeting got bumped to Wednesday this week), edit just that occurrence. ARA asks "this one only or all future?" before saving. Pick "this one only" so next week's Tuesday slot stays intact.
RSVPs over time
For a recurring Gathering, RSVPs reset for each occurrence. You don't have to re-commit to every weekly Council; the system assumes "no answer = no answer", not "no = no". Hosts see who's RSVP'd to this instance specifically.
If an event has a hard cap on attendees (a workshop with 10 spots), the system enforces it on the first 10 "Going" responses. Afterwards, additional villagers see the event as "full" and can't RSVP without the host bumping someone.
Dietary aggregation
For Social-type Gatherings (and Work or Ritual if the host enables it), the dietary restrictions you set in your Profile show up to the host as a count. Not as names — as totals. The host sees "2 vegan, 1 gluten-free, 1 nut allergy" without having to know which person each restriction belongs to.
This solves the most reliably awkward moment in community cooking: the cook makes the meal, the dietary thing comes up halfway through, the dietary person feels like a burden, the cook feels like they failed. Visible totals at planning time stop that.
Cancelling a single occurrence
Edit the instance > Cancel this occurrence. Invitees get a notification. The series continues normally next time.
Cancelling the whole series
Edit any instance > End series. Past occurrences stay (they happened, after all). Future ones disappear from everyone's calendars.
If RSVPs are quiet
Two interventions help. First, post a short Scroll comment on the linked agenda the day before, with one specific question for the group. Second, narrow the invite list — three people who said yes beats fifteen who didn't read the email.