Guest Child Profiles
A visiting cousin gets a temporary child profile that expires on its own and stays out of the family leaderboard.
Set Guest and an end date on a child (is_guest, guest_expires_on).
- Guests don't compete. They're excluded from the leaderboard — a cousin here for a week shouldn't win the month, and their leaving shouldn't read as a loss for everyone else.
- No end date means no expiry. You may not know how long the visit is, and silently archiving someone mid-stay would be worse than leaving the profile up a bit too long.
- Expired guests are archived, not deleted. The visit's completions stay in history, and next summer the same guest can be reactivated rather than rebuilt from scratch.
- Promoting a guest to a family member clears the end date and un-archives them. Someone who moves in shouldn't stay invisible.
Archiving reuses the existing availability plumbing, so every chore and streak path already treats an archived guest as away — the same way vacation mode does. There is no separate code path that could disagree with the rest of the integration about whether a child is present.
Archiving fires taskmate_guest_archived.
- Add the child, tick Guest, set the end date to the day they go home.
- Assign them a couple of chores — they earn points like anyone else.
- They stay off the leaderboard throughout.
- On the end date they are archived automatically. Their history remains.
- Next visit, reactivate the same profile.
- Children — adding and managing children
- Leaderboard Seasons — which guests are excluded from
- Vacation Mode — the same availability mechanism, for family members
- Automations — every TaskMate bus event