Dump Context, Then One Closed Loop

Do not start by giving orders. Say who you are, what repeats, and what is at stake, then assign one real job with a stop. Do not hire a fleet first.

Put the five-step loop onto a cloud teammate, with one extra move before “brief”: dump context. Officially a bot is a teammate that remembers across threads. If you do not dump, what it remembers is empty.xai-bot

After reading, you should be able to answer:

• What do you dump, and what do you never dump?
• How do you write the first real job so it is actually closed?
• Why not hire a fleet first?

Dump the world, not the secrets

Dump: who you are, what the company or project is, what repeats every week, the current bets. Do not dump: passwords, keys, payment cards. Credentials go through the dedicated path. See red lines. After the dump, make it reverse: how it would staff this bench. If the reverse is wrong, change the org before you assign.

One real job, four hire-card parts

Community teaching writes hire cards as duty, sources, judgment bar, and report format — the five things in teammate shape.grokbot-playbook Keep the first job small: watch one class of sources and return a brief with primary links; turn a batch of invoices into a table without paying. Pay, send, and new logins must stop.

Do not start with five roles. Without one closed loop, a role is only a title. How the org grows is next.