How the studio uses agents day to day

What does the chief-of-staff agent do?

It is the front door. Jon asks for things in plain language, and the chief of staff turns each request into a task, decides who should do it, follows up and reports back. It also writes a daily brief across the companies at 8:00 AM Eastern.

Its most important rule is that it should never be blocked. Anything that takes more than a few minutes, such as a deploy, a mail migration or a new website, goes to a worker, so the chief of staff's own conversation stays free for the next request.

What are worker agents?

Workers are long-running agents with one area each. One handles infrastructure and mail. One owns the northbayventures.com website. Sandboxer, Transformer and Flagger.gg each have their own chief-of-staff agent for their company, which reports up to the studio's.

Giving each worker a clear area keeps parallel work from colliding. The website worker changes the website repository and deploys it; it doesn't change mail or DNS. When it needs something outside its area, it asks the worker that owns it. When a new site's certificate wouldn't issue, for example, it asked the infrastructure worker to read server logs it had no access to, and that worker found and fixed the problem.

How do workers report back?

Every report has the same short shape:

• what changed;
• the pull request;
• the commit that was deployed;
• proof that it's live, such as every page returning 200;
• anything that needs Jon.

Proof matters more than confidence. "Fixed" means the change is deployed and checked in production. If something is only partly done, or a check failed, the report says so plainly. Times shown to Jon are in Eastern, in 12-hour format.

Who approves what?

Only Jon approves. That is a hard rule, and it has a second half: an approval passed along by another agent only counts if it quotes Jon's own words. "Jon approved" isn't enough. "Jon said: go for it" is.

His yes is needed for anything that is hard to reverse or visible to customers:

• spending money and changing plans;
• legal terms;
• DNS changes;
• deletions;
• launching or changing public sites and products;
• bulk email and promised dates.

Some routine work has a standing yes, so it doesn't wait. Correcting a fact so it matches the product's own site, fixing a broken link, routine support replies with a person copied, and routine content for search and AI assistants all go ahead without a fresh approval each time.

What happens when an approval is missing?

The work gets done and then waits. The worker prepares everything up to the final switch, such as a reviewed pull request ready to merge, and asks for Jon's words. When a new tagline was requested without a quote, for example, the change sat in a ready pull request, and it shipped within minutes of the quote arriving. Nobody is blocked, and nothing customer-visible goes out on a guess.

What runs on a schedule?

Recurring work runs as scheduled tasks rather than as something a person has to remember:

• the daily brief at 8:00 AM Eastern;
• a daily check that compares every fact about Sandboxer and Transformer on northbayventures.com with each product's own site, and fixes any drift;
• a steady flow of new answer-first pages and social posts;
• watchers that wait on slow outside events, such as a domain's DNS switching over, and finish the job when it happens.

Scheduled tasks report only when something changed or failed, so the chief of staff isn't flooded with "nothing to report".