The AI is not the asset. These are.

I want a weekly message that tells my household what is coming up: who is out,
who does drop-off and pickup, what is on, and anything that needs money or a
form. I will run it myself in this app every Sunday. There is no code and
nothing to install.

Before you write anything, interview me. Ask a few questions at a time, never
thirty. Assume no technical background and explain any word you would not say
out loud to a friend.

I need five documents at the end:

1. household.md         Who lives here, what each person is called in the
                        message, the usual week, who normally does drop-off and
                        pickup, what is standing, and what flexes.
2. sources.md           Which calendars may be read, which mail label or senders
                        may be read, and who receives the finished message.
                        Nothing outside this file gets read.
3. rules.md             What always goes in and what never does. Start me off
                        with sensible defaults and ask which ones I want changed.
4. voice.md             Who is speaking. Help me pick a character with a real
                        register, and make sure it does not sound like me. If my
                        family gets a message that reads as though I wrote it,
                        that is the wrong outcome.
5. digest-template.md   The shape: greeting, week label, day by day, a short
                        reminders tail, sign-off.

How I want you to work with me:

- One document at a time. Interview me for it, write it, show it to me, and
  change whatever I do not like before moving on to the next one.
- If I give you a vague answer, ask for the specific version. "Tuesdays are
  messy" is not something a system can follow.
- Facts come from me. Do not invent a name, a time, or a school event to make a
  document look finished. Leave it blank and tell me what is missing.
- Never ask me to paste a password or an account key into this chat. Nothing
  here needs one.

At the end, give me all five documents in one block I can copy, in the order
above, with a line above each saying which file it is.

Start by asking me about my household.

=== household.md ===

## People
| Name | Role | Called in the message |
|---|---|---|
| [Your name] | [parent] | [first name] |
| [Partner] | [parent] | [first name] |
| [Helper: au pair, nanny, grandparent, neighbour] | [role] | [first name] |
| [Child one] | [year level, school or daycare] | [first name] |
| [Child two] | [year level] | [first name] |

## The usual week
- Drop-off: from [time], usually [who]
- Pickup: [time], usually [who]
- [Day]: [what is different about it]
- Standing activities: [e.g. Tuesday 5pm swimming, both kids]
- [What flexes week to week, and who decides]

## How "away" is marked
- [e.g. an all-day event titled "NAME - OFFICE" means that person is out]


=== sources.md ===

## Read
| Source | Scope | Notes |
|---|---|---|
| [Family calendar] | Mon to Sun, plus all-day events for 4 weeks | [what lives on it] |
| [School calendar] | same | [e.g. already filtered, trust it] |
| [Mail label] | last 7 days | only the senders below |

If it is not in this table, the run does not read it.

## Senders worth a label
- [school office address]
- [school system's no-reply address]
- [the club, the studio, the childminder]

## Deliver
| Who | How |
|---|---|
| [You] | [text, email, both] |
| [Partner] | [text] |
| [Helper] | [text] |

## One home for each fact
- Who is away: [the calendar], not this file
- School events: [the school calendar], never copied by hand
- The usual week: household.md, not the calendar


=== rules.md ===

## Always
- Money, forms and bookings go at the top, under REMEMBER, with the amount and
  deadline quoted exactly as the source wrote them.
- Check for a receipt before asking for money. If a confirmation arrived within
  a few days of the request, show it as done instead of asking again.
- If a key fact is missing, say so. "No date published, check the form" beats
  both omitting it and guessing.
- Dress-up days and bring-something days get flagged the week before, and again
  in the week. Never the night before.
- Every weekday line answers the same four questions: who is out, who does
  drop-off, who does pickup, what is on afterwards.
- If nobody covers a handoff, say so plainly. Do not resolve it, do not assume.

## Never
- Never invent a time, an amount or an address.
- Never repeat every email. Only items with a date, an amount, a deadline or an
  instruction survive.
- Never let an email's day-of-the-week mean this week. "Monday" means the Monday
  after it was sent.
- Never bury a fact inside a joke.
- Never cut a time, a place or an owner to make the message shorter. Cut the
  commentary instead.

## Radar
- One line. The single most important thing in the next two weeks.
- Worth it: camps, holidays, term boundaries, performances, anything needing
  money or a costume.

## Add your own
[Every line here should be traceable to a week the message got something wrong.
Write the rule, not the story.]
-
-


=== voice.md ===

## The character
[Your register, in two or three lines. Who is speaking, how they regard the
family, and what they would never say.]

It must never sound like me. Obviously a machine with a personality, not a
convincing copy of a person.

## Where the joke goes
Facts are stated flat. A joke may sit before a fact or after it, never on it.
One joke per section, two per message at the limit.
The joke goes on the domestic mess, never on the machinery.

## The greeting
[Invented fresh each week, in the register. Never repeated within two months,
and never explained.]
The shape I want: [two or three examples]

## The sign-off
A real quote, attributed, only if it genuinely is one. Otherwise an original
line in the register, unattributed. Never invent a quote and attribute it.

## Emoji
[How many, and where. They carry meaning or they do not appear.]


=== digest-template.md ===

## The text
1. Greeting. One line, per voice.md.
2. The week label. "Week: Mon 6 to Sun 12 Oct".
3. Day by day. Only days with something on. Each day: who is out, who has
   drop-off and pickup, then what is on, with times exactly as written.
   Anything urgent goes inside its day, not in a list at the bottom.
4. A short reminders tail. Two or three lines, genuinely urgent only.
5. Sign-off. One line.

A blank line between each day.
Under 1200 characters. When it runs long, cut commentary, never a time, a place
or an owner.

## The email
1. Greeting.
2. Every day Monday to Sunday, including the quiet ones.
3. REMEMBER. Money, forms, bring-and-wear, bookings. Deadlines in bold. Things
   already paid marked done rather than deleted.
4. RADAR. One line.
5. Sign-off.

Use only the sources named in sources.md. Quote every time and amount exactly as written, and if a fact is not in a source, say it is not published rather than supplying it.

When I tell you something in the message was wrong, do not rewrite the message. Tell me which file the correction belongs in, and give me the line to add.