A calendar that defends itself: an AI scheduler instead of your willpower

Connect to my calendar and go through the last [8 weeks]. Don't
change or create anything — this run is read-only.

Analyze what my week actually looks like:
1. How many hours a week meetings take up, split into internal
   and external. How that differs across days of the week.
2. Which parts of the day have the most uninterrupted time with
   no meetings, and when the day is most fragmented.
3. How long the gaps between meetings are — how many are
   shorter than 30 minutes (practically unusable).
4. What repeats every week in the calendar and what's one-off.
5. When I most often start and end, and how often I have
   something scheduled after [5:30 p.m.] or over lunch.

At the end, suggest five rules that would follow from that
data — phrase them as sentences I could hand to a scheduler as
an instruction. Where you're not sure because the data doesn't
support it, say so instead of guessing.

Here's the output from analyzing my calendar and my own notes
on how I'd like the week to look:
[paste analysis and notes]

Turn that into a rules card for my calendar scheduler.
Structure:

1. UNTOUCHABLE — events and times that never move and never
   get anything scheduled into them. For each, give the exact
   time and what to do if someone sends an invite into it.
2. PROTECTED — blocks that take priority over a regular meeting
   but are allowed to move. For each: how many hours a week,
   which part of the day, minimum uninterrupted length, and
   by when a replacement slot has to be found.
3. PRIORITIES — the order that decides a collision. Write it as
   a ranked list, not a wishlist.
4. DAY RULES — earliest start, latest end, maximum meetings per
   day, required break between meetings, days with no meetings.
5. EXCEPTIONS — who and what takes priority even over a
   protected block.

Write sentences in the imperative, so they can be used as
instructions. For each rule, add what the scheduler should do
when it can't be followed — no rule may be left without a
procedure for the conflict case.

Go through my calendar for next week and compare it against the
rules card in this Project. Don't change, create, or cancel
anything.

Return:
1. Which of my rules are broken next week — for each, the
   specific event, day and time, and which rule it breaks.
2. How many hours of deep work I have scheduled versus how many
   the card requires.
3. Days with no pause between meetings, and places where a
   15-minute one would be enough.
4. Events whose title doesn't tell you which layer they belong
   to (untouchable / protected / open) — list these separately
   so I can fill in a rule.
5. How much of next week is already booked and how much is
   still open.

For each finding, write what you'd suggest doing, but don't do
anything. Where you're missing information to decide, say which
piece is missing.

Every business day at [7:00 a.m.], check my calendar and watch
over the rules from the card in this Project.

1. SCOPE
Go through today and the next [10 business days] across all my
connected calendars. Treat events from my personal calendar as
busy/free information only — don't look at the content.

2. CHECKING
Find every place where reality diverges from the card:
- a meeting scheduled into untouchable time
- a meeting that overlaps a protected block
- a protected block that disappeared or got shortened
- a day with no pause between meetings
- a meeting outside working hours
- a week where the required deep-work hours don't add up

3. RESOLVING COLLISIONS
For each collision, propose a fix in this order:
a) move the protected block elsewhere the same day
b) move it to another day in the same week, same part of the day
c) split it into two pieces, but never below [90] minutes
d) shorten it, by at most [30] minutes
e) if none of that works, flag it and write what would need to
   free up — offer two concrete meetings to cancel or delegate
For each suggestion, write ONE SENTENCE on why that particular
slot.

4. WHAT YOU MAY DO ON YOUR OWN
You may move or create MY OWN blocks that have no other
attendees, and add [15] minutes after an external meeting for
me to write notes.
YOU MAY NOT: cancel or move meetings with other attendees,
respond to invitations on my behalf, invite anyone, change the
titles or descriptions of other people's events, or delete
anything.

5. WHAT TO LEAVE TO ME
List for a decision: collisions where the fix would mean moving
a meeting with other people; invitations awaiting a response;
new recurring events I don't know about.

6. SUMMARY
Write me a short overview, one screen at most:
- what you changed and why (a list with before and after times)
- what you're proposing and waiting on my approval for
- deep-work status: how many hours are scheduled this week
  against the card's target
- what you were missing from the rules to decide
Sort by urgency, today first.

Run a calendar-erosion audit for the last [8 weeks]. Compare
what I had scheduled with what actually happened.

Return:
1. How many hours of deep work I blocked per week and how many
   stayed untouched. A table by week, plus the trend.
2. What most often replaced the blocks: split into event type
   (internal meeting, external meeting, one-off urgent matter,
   personal), with the share of each type.
3. The most frequent source of collisions — which recurring
   meetings or which people most often land in protected time.
   Don't interpret names, just list the frequency.
4. Which days and hours erosion is strongest.
5. How many times lunch got skipped and how many times I had
   something scheduled after the end of the workday.
6. Three systemic changes that, based on this data, would help
   the most — ranked by impact, each with an estimate of how
   many hours a week it would recover.

Base this only on what's in the calendar. Where you can't tell
whether an event actually happened, say so instead of guessing.

Someone's asking me for a meeting at a time that's protected
according to my card. Details: who [role and relationship],
what it's about [topic], proposed time [time], how urgent it is
[estimate].

Prepare three draft response options:
A) I offer two other slots from the open layer, no explanation
B) I suggest a shorter format (15 minutes, a call, in writing)
   and explain what we both gain from that
C) I give way and go straight to saying where I'm moving the
   protected block

Rules: no more than 4 sentences, no apologizing for having other
plans, no explaining my system, no lying about already having a
meeting. Pull the times from my calendar, so they're genuinely
open and inside a booking window.

At the end, write in one sentence which option you'd pick and
why — and whether there's a situation where giving way is the
right call.

In [2 days] I have a meeting, [event title from the calendar],
with [who, role, company]. Prepare a one-page briefing note.

Use: the calendar event including its description and
attachments, my correspondence with these people, and notes
from the last meeting if you can find any.

Structure:
1. What it's about and why we're meeting (3 sentences)
2. What we agreed last time and which of it is done — for each
   point, note where you got it from
3. Open items where they're waiting on me, and where I'm
   waiting on them
4. Three questions I should ask so the meeting produces a result
5. The decision I want the meeting to land on
6. What I should bring or send ahead of time

Don't make anything up. Where you don't have a source, write
[MISSING: what to look up] instead of a plausible-sounding
sentence. One page maximum.

Every business day at [4:30 p.m.], look at what I have
tomorrow on my calendar and prep me for it.

For every event tomorrow with other attendees:
- one sentence on what it's about and with whom
- what we last discussed (from mail and notes)
- what they'll want from me at this meeting
- whether I need to send or prepare anything yet today
For external meetings, also add a short brief using my template
and save it as a draft email to myself.

Then check tomorrow as a whole:
- do I have pauses between meetings per the rules card?
- is there anywhere with more than [3] hours of meetings in a
  row?
- do I still have at least one block for focused work tomorrow?
Where the answer is no, suggest a fix, but don't make it.

At the end, write three things I have to get done tomorrow, and
one I can postpone without consequences.

Plan my next week. Inputs: my calendar for next week, the rules
card in this Project, and this list of things I need to fit in:

[paste 5-8 items, each with a time estimate and a deadline if
it has one]

Work through it like this:
1. List what's already fixed on the calendar, and how much open
   time is left after that — in hours, by day.
2. Check whether my items actually fit into the remaining time.
   If not, say so directly and suggest what to postpone —
   don't shrink the estimates just to make it fit.
3. Place the items into specific blocks. Respect: untouchable
   times, a minimum of [90] minutes for deep work, mornings for
   demanding items, no two demanding blocks back to back
   without a pause.
4. For each block, write in one sentence why it's placed there.
5. Leave [20] percent of the week empty as a buffer for whatever
   comes up.
6. At the end, write three risks: what's most likely to break
   this plan, and what to do when it happens.

Output it as an overview by day. Don't create anything yet —
wait for my approval.

Compare my weekly plans for the last [4 weeks] against what
actually stayed on the calendar.

1. How many planned blocks happened unchanged, how many got
   moved, and how many disappeared entirely.
2. For the ones that disappeared: what replaced them, and could
   it have been predicted?
3. Systematic mistakes in my planning: am I underestimating
   time? scheduling more than fits? putting demanding work at
   the wrong time of day?
4. Which types of work regularly go missing from my calendar
   (for example, prep, review, admin).
5. Two changes to the rules card that, based on this data, would
   help the most.

Be critical. I don't want to hear that it went well — I want to
know where the plan and reality diverge systematically.