The first rule is what never lives on the computer

The first hire decision is not the model. It is what never lives on the machine.

A computer is useful because work continues when your laptop is shut. That is also the blast radius. Treat the disk like a contractor laptop you do not get to wipe at 6pm.

Write the never-list on day one. Personal banking. The god password. A client's folder sitting next to another client's folder. Production keys pasted into a thread "just this once." If you would not hand it to a freelancer in a coffee shop, it does not go on the shared computer.

Octopus puts secrets in a vault. A teammate reads a key at run time. It does not print the key back into chat. Access is per teammate, not a shared junk drawer. Receipts log who called what, and when. That is the floor. The never-list is still yours.

One Chief. Everyone else has a lane.

Chief routes. That is the job. Chief does not also chase invoices, because then you have a manager who is also the intern, and you cannot tell which hat failed.

Clerk, Mail, Maker, Scout, Watch each hold one lane. You can read the board and know who is late. You can fire one without restaffing the company.

The jobs people actually hire already look like this. Do not invent a seventh personality because the first six felt quiet. Quiet is the product working.

Write the job. Do not vibe it.

"Be helpful" is not a job. "Be a killer closer" is also not a job. A job is a sentence a new hire could fail.

Chase unpaid invoices every weekday at 9. Draft the reminder in our voice. Never CC legal on the first nudge. Stop before send.

Sort the overnight inbox at 7. Answer the four routine ones. Flag anything that names a contract, a refund, or a person who sounds done with us.

If you cannot write it that way, you are not ready to hire. You are ready to prompt. Prompting is fine. Calling it a teammate is how you get surprised on a Thursday.

Keep the brief in a file the teammate can reread. When the output is wrong, you do not "give it more personality." You fix the sentence in the brief. The artifact is the product. The vibe is how people stall.

Human yes before send or spend

Research, numbers, a draft: go. Money out, a customer, a vendor, your team on copy: wait.

That is the whole control system. Caps help (how many outbound a day). Approvals are the lock. A teammate that is unsure parks the work in Needs you. A teammate that is sure and still waits is the one you keep.

Do not train yourself to tap yes without reading. The drafts get good. Your thumb gets lazy. Read the two that would embarrass you.

Spending is the same rule. A teammate can build the cart. It cannot check out until you do.

Only split when the rules fight

People split too early. They hire five teammates for one job and then wonder why nothing has an owner.

Split when two instructions cannot live in one head. Brand voice wants warm. Legal wants cold. Books should be read-only for Clerk and unreachable for Scout. Outreach should never see the support inbox.

Until the rules fight, one teammate, one clock, one artifact. Add Chief when you have three lanes and you are the one dragging cards across the board at midnight.

Routines on real clocks

"When I remember" is not a schedule. Weekdays at 9 is a schedule. Mondays at 7 is a schedule. After every call is a schedule if the calendar actually fires it.

Put the clock on the job, not in your head. Laptop shut, work still starts. That is the only reason the computer exists.

Overnight work comes back as a draft, a brief, a flagged thread. You do not wake up to a customer who already got a letter you did not see.

Iterate the artifact, not the mascot

The brief. The sheet. The reminder template. The competitor one-pager. Those are the things you improve.

A bad Monday report is a gift if you mark it up and put the markup in the file. Next Monday inherits it. A teammate with no file starts over, and you are the memory again. That is not a hire. That is an intern with amnesia you keep paying.

Same for Watch. The value is the running log of what changed, not a fresh essay every week that forgets last week.

Know the limits out loud

A teammate cannot be the relationship. It cannot walk the site. It cannot smell that the deal is dead. It cannot hold a secret you refused to put in the vault, and it should not.

It cannot choose a model you did not give it. If you only bring one vendor, you get that vendor's ceiling, their outage, and their usage cap. Octopus lets you bring ChatGPT, Claude, Gemini, Grok, or the OSS models in the $99 plan, and stack accounts so a job continues on a fallback mid-task. Use that. One pipe is a single point of "sorry, try tomorrow."

It cannot invent isolation you did not buy. Dedicated workspace is the default. Dedicated VM for agencies is a conversation. Do not run two clients on one disk and call it a process.

We never train on your data. You still decide what the machine can reach.

A Tuesday you can inspect

Ask to see a Tuesday. Who ran. What they touched. What waited. What it cost. If the answer is a chat transcript, you bought a prompt.

Then hire. Sign up. Put Clerk or Mail on a clock. Require the yes. Fix the brief. That is the practice. Everything else is a thread with a job title.