Your first week with AOS is about getting the agent company pointed at real work and tuning how much it does on its own. You do not need to configure 61 specialists by hand. You set a few defaults, run a mission or two, and let the system show you how it works. Here is what to expect.
Day one: provisioning and access
Your private instance is stood up on dedicated infrastructure. Out of the box, integrations are walled off, so nothing touches your real tools until you connect them. The first thing to do is sign in, look at the Mission Control dashboard, and read the eight department names so you know who does what.
You do not have to connect everything immediately. Connect only what your first mission needs.
Set your guardrails
Before you run anything important, set the dials that decide how much routes to you:
- Money caps. Default is 1,000 dollars per move and 10,000 dollars per week. Lower them if you want tighter control early on.
- Public claims. Decide whether anything published under your company name always waits for your sign-off. Most founders keep this on.
- Token caps. Start conservative. You can raise them once you see your real burn.
These map directly to the five approval points, which are the only places work crosses your boundary.
Run your first mission
Pick something small and real. One sentence of direction is enough. The department leads scope it into a workstream with an owner, an acceptance bar, and three non-goals, then the builder, QA, reviewer, and security checks run before it reaches you. Watch how the brief turns into scoped work. That single loop teaches you the whole model. See Running your first mission for a walkthrough.
Read your first founder summary
Every Friday at 4pm you get a one-page summary: what shipped, what is blocked, and what waits on you. Your first one is the moment AOS stops being abstract. Read it, approve or redirect what is waiting, and you have closed your first full cycle.
Tune as trust builds
The honest goal of week one is calibration. If too much is routing to you, raise the caps. If you want more eyes on things, lower them. If a mission drifted, tighten the non-goals next time. AOS is meant to earn autonomy gradually, so you stay comfortable the whole way.
A simple first-week checklist
- Sign in and read the eight department names.
- Set money caps and the public-claims approval.
- Set a conservative token cap.
- Connect only the tools your first mission needs.
- Run one small, real mission end to end.
- Read your first Friday summary and act on what is waiting.
By the end of the week you will know how a sentence becomes shipped work, where the approval points sit, and how to dial autonomy up or down. That is the whole operating loop.