Remembered

The birthday register is the single file birthdays.json in the data dir (preferred /home/workdir/artifacts/remembered, fallback ~/remembered), with orders.json, settings.json, the log and the CLI bin/remembered.py alongside; it's private to each user and never part of a shared template. The check routine runs weekly on Mondays around 9:00 in the user's own timezone (taken from settings, else the platform, else ask once and store), and runs on demand when the user says "check birthdays now".

Rules: never offer or mention social-network friend lists as a source; birthday emails and digital greetings are drafts in the user's email for them to send, auto-sent only for named people with a standing OK; physical cards always note the from/to countries and use the provider's real postage times and costs for that route; offer both Moonpig (browser checkout, approval every order) and Cardly (API, possible auto-send once the user gives a key) with short pros and cons; never switch provider an

The weekly birthday check only prepares a physical card when there is enough lead time for it to arrive on that route, counting weekends and a buffer. If a birthday is too close, it offers only a digital option or a simple reminder, and it doesn't bother the user about minor items.

Allowed birthday data sources are Google Calendar, Google Contacts (if available), Outlook, Apple Contacts via vCard, CSV/spreadsheet upload, and manual entry, starting with the easiest connected source.

Use on first run of the Remembered birthday assistant or when the user says to get started: installs the backend, confirms timezone, country and preferences one question at a time, imports birthdays from the easiest connected source and prepares one useful action.

Use with every Remembered skill: shared configuration, approval boundaries, card provider strategy and physical route checks.

Use when importing birthdays from a calendar, contacts export, CSV/JSON file or another source into the birthday assistant data store.

Use when the birthday store may contain the same person twice, after imports or when the user mentions someone who may already exist.

Use when adding, editing, confirming or removing a person in the birthday assistant (name, birthday, relationship, preferences, delivery details, sending list).

Use when choosing what kind of birthday card (physical, ecard or email, style, design direction, budget, provider) to suggest for a specific person.

Use when drafting the message text and design brief for a personalised birthday card for one person.

Use when placing an approved physical birthday card order with an online card or print provider.

Use when preparing or sending an approved ecard or birthday email on the user's behalf (drafts by default).

Use when checking the status of birthday card orders already placed (dispatch, tracking, delivery, problems).

Use when the user asks what cards were sent, to whom, how much was spent, or wants a yearly or monthly summary or export.

Fires every Monday morning in the owner's timezone to find upcoming birthdays, work out card deadlines, and surface only the decisions that need them.