The first week

Seven days of setup work you mostly do not see.

Your Chief of Staff does not just sit there waiting after the first conversation. It runs a scripted first week: one piece of setup work a day for seven days, from the day it is created.

The important part is what you do not get. Every one of those seven days is silent. None of them messages you, and none of them opens a second conversation. The work surfaces through your next daily brief instead, so the first week reads as a teammate getting up to speed rather than as an assistant asking you questions.

What happens on each day

1. 1Day 0, get wired. Writes itself a Week-1 checklist to work from, then researches your company from public sources only, deliberately not touching your mail or calendar yet even if they are already connected. Drafts a company profile and an owner profile, with provenance on every fact, framed as a first draft for you to correct.
2. 2Day 1, show initiative. Turns what it found into one sharp brief rather than a list of things it could do.
3. 3Day 2, learn your voice. Reads how you write in public: your site, your posts, anything under your name. It records that this is your public voice and says so, because it is not how you write a private email.
4. 4Day 3, priorities and routines. Confirms what actually matters and sets up the routines to match. At most one approvable card, with everything it wants confirmed folded into that single card rather than stacked into several.
5. 5Day 4, synthesis to action. Takes a real recorded meeting, if you have a call recorder connected, and turns it into something finished enough to use.
6. 6Day 5, attune. Records how you actually work: terse or detailed, act or ask first, what you want surfaced and what you want left alone. Then adapts to it. If you have been trimming its messages, it gets shorter.
7. 7Day 6, wrap. A short, honest recap of what is now running for you. It is instructed to state only what is literally true and to invent no metrics, so you will not get an "I saved you six hours" number.

Two things worth knowing

It suggests connectors early, and deliberately few. Calendar first, because it is low risk and it powers what the next day can do, then a call recorder, because meeting transcripts are where most of the useful detail lives. One or two suggestions, not a setup checklist.

It states its operating contract up front, in its own words, on the first day: it drafts rather than sends, suggests rather than changes your calendar, and shows you everything before it counts. Everything it produces that week is a draft for you to approve.

If your machine was asleep when a day was due, that day is skipped rather than queued up to fire late. The week is paced to your calendar, not to uptime.