← Library · AI-OS cookbook · 06
A designed week instead of a reactive one: a fixed morning that protects revenue and family before anyone can book over them, meetings chained back-to-back at 30 minutes max, zero standing 1:1s — and an AI agent that audits the calendar against the rules and proposes the fixes.
The calendar fills itself. Recurring 1:1s nobody questions, meetings scattered across the day with 15–30 minute holes between them, private admin leaking into every afternoon — and the best hours go to whoever booked first.
The week is designed before it starts: the first three hours are pre-built for revenue, focus and family, meetings run back-to-back at 30 minutes max, admin lives in one bundled slot — and an AI agent audits next week against the rules, flags violations, and proposes the moves.
The day's highest-leverage hours are spoken for before the first meeting request arrives. The architecture starts at the real wake time — not an aspirational one — and nothing gets scheduled into the protected window. Ever.
| Block | What happens | The rule |
|---|---|---|
| 06:00–06:45 · Revenue block | Async revenue motion only: outbound, follow-ups, pitching for stages | No building, no admin — this block is the income motor |
| 06:45–07:00 · Weekly-focus read | Re-read the week's top-5 priorities | They live in a recurring calendar event's description — the week's frame, visible daily |
| 07:00–09:00 · Family block | Family — phone in focus mode | Fixed, non-negotiable. Never schedule work here |
| From 09:00 · The workday | Deep work and calls | Meetings chained flush, 30 minutes max |
The recurring weekly 1:1 is a default, not a decision. Delete the series. Instead, derive the conversations that are actually needed from team-channel signal plus current priorities and goals — then schedule them ad hoc, when there's something to decide.
Fifteen- and thirty-minute holes between meetings are dead time — too short for deep work, too long to waste. When several meetings land on one day, chain them flush (e.g. 15:00 / 15:30 / 16:00) so the rest of the day stays whole.
The default meeting length is a convention, not a law. Cap every call at 30 minutes. What doesn't fit in 30 minutes usually needed a briefing doc, not a longer meeting.
Recurring private obligations — property, paperwork, errands-by-email — get one bundled 2-hour slot per week (e.g. a late-week afternoon). Everything beyond the cap gets delegated or automated. It's not the income motor; don't let it graze the week.
Before proposing a slot, the agent checks the other attendee's availability. Caveat from practice: some people keep a blanket all-day "busy" block — treat that signal as unreliable, book anyway, and note that they'll confirm or reschedule.
A recurring weekly-focus event carries the week's top-5 priorities in its description. It's re-read every morning in the 06:45 slot — so the frame for every ad-hoc scheduling decision is already open when the day starts.
Rules decay unless something checks them. With the calendar connected via MCP, an AI agent reads next week, compares it to the rules above, flags every violation, and proposes the move that fixes it — propose, never silently move.
Write the rules as a short standing instruction (or point the agent at this cookbook). The fixed blocks themselves become recurring calendar events, so the agent can tell "designed" from "drifted".
Once a week, the agent reads the coming week and checks every event against every rule: anything inside the protected window, any recurring 1:1, any gap between meetings, any call over the cap, any admin outside the bundled slot.
The agent returns a violation list — each with the rule it breaks and a proposed fix (move, shorten, chain, decline, bundle). The operator approves in one pass. The calendar only changes after the yes.
"Read my calendar for next week via the calendar MCP and audit it against my operating rules: nothing scheduled 07:00–09:00; the revenue block 06:00–06:45 intact every weekday; no recurring 1:1 series; meetings chained back-to-back with no 15/30-minute holes; no call longer than 30 minutes; private admin only inside its single bundled 2-hour slot. List every violation with the rule it breaks and propose the move that fixes it. Do not move or delete anything until I approve."
Killing standing 1:1s only works if something else surfaces the conversations that are needed. That something is a scheduled agent:
Twice a week, the agent reads recent team-channel activity and holds it against each person's current goals and the operator's priorities.
It proposes a conversation only when something genuinely calls for one — a stalled goal, an unspoken decision, a thread going in circles. No proposal means no meeting.
The operator replies to the proposal in chat; on the OK, the agent schedules it — invite plus video link, chained back-to-back with whatever else is booked, 30 minutes max.
The radar runs on a schedule (e.g. Tuesday/Thursday late morning), independent of any open laptop session — the loop holds even in a full week.
| Wall | The fix |
|---|---|
| Standing-meeting creep | Recurring 1:1s accumulate "to stay in touch" and outlive their reason. Delete the series; let the radar propose conversations only when something triggers them. |
| The aspirational block | A 04:00 focus block that never actually happened sat on this calendar for months. It got deleted and rebuilt at the real wake time. Design for the operator you are, not the one you'd like to be. |
| Swiss-cheese days | Meetings scattered with 15/30-minute holes shred the day. Chain them flush — several short calls in a row beat the same calls sprinkled across the afternoon. |
| The ballooning call | Without a hard cap, every meeting defaults to the calendar tool's 60 minutes. Cap at 30 and hold it. |
| Admin sprawl | Low-leverage obligations spread themselves across the week if you let them. One bundled slot, hard 2-hour cap — delegate or automate the rest. |
| Tinkering inside the revenue block | The early block exists for revenue motion — outbound, follow-ups, pitches. Building systems and clearing admin there feels productive and isn't. Guard the block's purpose, not just its time. |
| Trusting blanket "busy" | Some attendees' free/busy shows busy all day, every day. Treat it as unreliable: book anyway, flag that they'll confirm or move it. |
Copy the bootstrap promptThe button below puts it on your clipboard.
Paste it into Claude CodeIn a session with your calendar connected via MCP.
Answer its questionsIt encodes your version of the rules, builds the fixed morning, and schedules the weekly audit.
No download needed — this cookbook is the rules + an AI audit loop you run on your own calendar.