Your brief to start the day.

I run commercial at a product studio, and the hardest part of a launch is the morning triage. The board, the calendar, and the inbox all shout at once, and the one thing that actually moved sits three tabs deep. I wanted a chief of staff who reads the whole surface before I am up and hands me one brief, ranked and in plain language, with whatever keeps slipping already flagged. So I built Roy. He drafts and he flags. He never acts for me.

Every morning Roy reads the launch surface and hands back a single brief. Each screen does one job. The most important thing sits at the top in plain language, and everything else waits a tap deeper. He ranks the day, shows the reasoning behind the top call, drafts the messages you would have written, and marks what to leave alone.

Roy also remembers. He tracks what has been slipping across the countdown to launch and carries it forward. When the same blocker sits three mornings running, he says so and escalates it, marked in the color the design holds back for exactly that. The brief on Tuesday already knows what stalled on Monday.

It generates live via the Anthropic API. One forced tool call returns the whole brief as structured data, guarded for shape and retried if it drifts, with the voice rules enforced on the way out. The system prompt Roy runs on is shown to you verbatim, the same text the engine sends, so what you read is what ran. The world is synthetic and the key stays on the server. Inference is the product, so every visit starts clean.

stack  Anthropic API · forced tool use · shape-guard + retry · runtime voice enforcement