The week Friday (AI Chief of Staff) stopped starting from scratch

Every time I opened a new session with Friday, she started from zero. Friday is my AI Chief of Staff.

No memory of yesterday. No idea what I was working on. No clue who was on my calendar.

I'd spend the first few minutes re-explaining. The same projects, the same people, the same rules. Every session.

The real cost wasn't the minutes I lost. It was that Friday that quietly got things wrong. She'd draft in the wrong tone. Mention a project I'd paused last week. Miss context, I assumed she had.

A chief of staff who forgets everything overnight isn't a chief of staff.

What shipped

Six things. Each took an afternoon.

1. Auto-briefing on session start. Every new conversation, Friday reads my current state (what I'm working on, what's unfinished, what's in the inbox) before I type a word. No paste, no re-explain.

2. Auto-journal on session end. When we finish, Friday writes down where we left off. Tomorrow's session picks up from there.

3. A fixed briefing format. Focus. Calendar. Inbox. Tasks. Flags. Same structure every morning. And a firm rule: if a data source is unavailable, say so. Never guess.

4. Voice samples. Two files: one is me writing well, one is me writing badly. Friday calibrates against both, so "my voice" isn't a vague rubric. It's a worked example.

5. A memory self-check. Every session Friday tests whether her long-term memory is healthy. If it isn't, she tells me. No silent failures.

6. Real names. I replaced a list of auto-generated filler with the 37 actual people, projects, and products Friday would need. So "write to Jeff" doesn't come back with "which Jeff?"

What it unlocked

1. I stopped paying the re-briefing tax.

2. Friday woke up knowing where she was. She knew what I was working on. She knew who was who. She knew what yesterday's Friday had shipped.

3. I stopped getting quiet wrong drafts. When the memory was down, she said so. When context was missing, she said so. That no-hallucination rule caught more mistakes than I expected.

4. Everything I built after this sat on top of it. Without it, every sprint that followed would have started over.

Copy this if you're building your own

• Start with the wake-up layer. Before you bolt on clever agents or fancy tools, make sure your AI can open a conversation and tell you what it already knows about your world.

• Keep your current state in a plain text file you can read. On session start, your AI reads it. On session end, your AI updates it. That's the minimum viable memory. Everything else stacks on top of it.

• Add one rule, explicitly: "if you don't know, say you don't know. Don't guess." Sounds obvious. Most AIs still need to be told.

Episode 1 of 19. I'm walking through every sprint I ran to build Friday. New episode every Monday, Wednesday, and Friday through Episode 19. Next: how I made it impossible for Friday to sound like AI.

Want to start your own Friday? Grab it free at friday.amplifyais.com.