ai-employees 1.6.0 → 1.8.0

package/README.md

@@ -11,7 +11,7 @@
 <p align="center">
   <a href="https://club.reinventing.ai/ai-employees?utm_source=github&utm_medium=readme&utm_campaign=ai-employees&utm_content=nav-employees"><strong>The eight AI Employees</strong></a>
   &nbsp;&bull;&nbsp;
-  <a href="https://club.reinventing.ai/masterclass?utm_source=github&utm_medium=readme&utm_campaign=ai-employees&utm_content=nav-masterclass"><strong>Masterclass</strong></a>
+  <a href="https://club.reinventing.ai/?utm_source=github&utm_medium=readme&utm_campaign=ai-employees&utm_content=nav-club"><strong>Agent Ops Club</strong></a>
   &nbsp;&bull;&nbsp;
   <a href="https://club.reinventing.ai/events?utm_source=github&utm_medium=readme&utm_campaign=ai-employees&utm_content=nav-sessions"><strong>Live sessions</strong></a>
   &nbsp;&bull;&nbsp;
@@ -29,14 +29,18 @@
 </p>
 
 <p align="center">
-  <a href="https://club.reinventing.ai/pricing?utm_source=github&utm_medium=readme&utm_campaign=ai-employees&utm_content=btn-install-prompt"><img alt="Get my free install prompt in the Agent Ops Club" src="https://img.shields.io/badge/Get%20my%20free%20install%20prompt-0B7FC7?style=for-the-badge"></a>
-  <a href="https://club.reinventing.ai/register?utm_source=github&utm_medium=readme&utm_campaign=ai-employees&utm_content=btn-join"><img alt="Join the Agent Ops Club free" src="https://img.shields.io/badge/Join%20the%20club%20free-3FB950?style=for-the-badge"></a>
-  <a href="https://club.reinventing.ai/events?utm_source=github&utm_medium=readme&utm_campaign=ai-employees&utm_content=btn-sessions"><img alt="Agent Ops Club live sessions" src="https://img.shields.io/badge/Live%20sessions-D97757?style=for-the-badge"></a>
-  <a href="https://club.reinventing.ai/masterclass?utm_source=github&utm_medium=readme&utm_campaign=ai-employees&utm_content=btn-masterclass"><img alt="The Agent Ops Masterclass" src="https://img.shields.io/badge/Masterclass-475569?style=for-the-badge"></a>
+  <a href="https://club.reinventing.ai/pricing?utm_source=github&utm_medium=readme&utm_campaign=ai-employees&utm_content=btn-install-prompt"><img src="assets/btn-install.png" width="260" height="60" alt="Get my free install prompt in the Agent Ops Club"></a>
+  <a href="https://club.reinventing.ai/register?utm_source=github&utm_medium=readme&utm_campaign=ai-employees&utm_content=btn-join"><img src="assets/btn-join.png" width="199" height="60" alt="Join the Agent Ops Club free"></a>
+  <a href="https://club.reinventing.ai/events?utm_source=github&utm_medium=readme&utm_campaign=ai-employees&utm_content=btn-sessions"><img src="assets/btn-sessions.png" width="163" height="60" alt="Agent Ops Club live sessions"></a>
+  <a href="https://club.reinventing.ai/?utm_source=github&utm_medium=readme&utm_campaign=ai-employees&utm_content=btn-club"><img src="assets/btn-club.png" width="186" height="60" alt="Visit the Agent Ops Club"></a>
 </p>
 
 <p align="center">
-  ⭐ <em>Star this repo so more founders find the eight.</em>
+  <a href="https://club.reinventing.ai/ai-employees?utm_source=github&utm_medium=readme&utm_campaign=ai-employees&utm_content=harness-strip#install"><img src="assets/harness-strip.png" width="838" alt="Runs on the agent you use: Claude Code, OpenClaw, Hermes, OpenCode, Grok Bot, Codex, Antigravity, Pi, Cline, Qwen Code and DeepSeek"></a>
+</p>
+
+<p align="center">
+  ⭐ <em>Found something useful? Star the repo. It takes a second and helps the next person find it.</em>
 </p>
 
 ## AI Employees
@@ -49,16 +53,16 @@ Created by [Mark Fulton](https://www.reinventing.ai/?utm_source=github&utm_mediu
 
 | Employee | What it owns | Routines |
 |---|---|---|
-| <img src="https://club.reinventing.ai/img/employees/thumbs/gtm-engineer.webp" width="72" height="72" alt=""><br>[**GTM Engineer**](employees/gtm-engineer) | Your launch: positioning, the launch board, outbound drafts, directory and press forms, the weekly scoreboard | 8 |
-| <img src="https://club.reinventing.ai/img/employees/thumbs/seo-employee.webp" width="72" height="72" alt=""><br>[**SEO/AEO Employee**](employees/seo-employee) | Keyword research, one article a weekday, publishing, indexing, rank review and your visibility in AI answers | 8 |
-| <img src="https://club.reinventing.ai/img/employees/thumbs/web-dev-employee.webp" width="72" height="72" alt=""><br>[**Web Dev Employee**](employees/web-dev-employee) | Site health, error triage, small changes on a branch, dependency review | 8 |
-| <img src="https://club.reinventing.ai/img/employees/thumbs/social-media-employee.webp" width="72" height="72" alt=""><br>[**Social Media Employee**](employees/social-media-employee) | Posts drafted in your voice for each platform, a veto window, replies drafted for you | 7 |
-| <img src="https://club.reinventing.ai/img/employees/thumbs/ad-manager-employee.webp" width="72" height="72" alt=""><br>[**Ad Manager Employee**](employees/ad-manager-employee) | Account reads, creative sets, build sheets and the weekly change list. Money moves only when you approve | 7 |
-| <img src="https://club.reinventing.ai/img/employees/thumbs/sales-employee.webp" width="72" height="72" alt=""><br>[**Sales Employee**](employees/sales-employee) | Prospect sweeps, first touches into your own drafts, follow ups that never go quiet | 7 |
-| <img src="https://club.reinventing.ai/img/employees/thumbs/customer-satisfaction-employee.webp" width="72" height="72" alt=""><br>[**Customer Satisfaction Employee**](employees/customer-satisfaction-employee) | Inbox sweep, replies drafted hardest first, churn flags with evidence | 8 |
-| <img src="https://club.reinventing.ai/img/employees/thumbs/chief-of-staff.webp" width="72" height="72" alt=""><br>[**Chief of Staff**](employees/chief-of-staff) | Reads every other employee's run log, names what quietly stopped, brings you three moves | 7 |
+| <img src="https://club.reinventing.ai/img/employees/thumbs/gtm-engineer.webp" width="72" height="72" alt=""><br>[**GTM Engineer**](https://club.reinventing.ai/ai-employees?utm_source=github&utm_medium=readme&utm_campaign=ai-employees&utm_content=table-gtm-engineer#gtm-engineer) | Your launch: positioning, the launch board, outbound drafts, directory and press forms, the weekly scoreboard | 8 |
+| <img src="https://club.reinventing.ai/img/employees/thumbs/seo-employee.webp" width="72" height="72" alt=""><br>[**SEO/AEO Employee**](https://club.reinventing.ai/ai-employees?utm_source=github&utm_medium=readme&utm_campaign=ai-employees&utm_content=table-seo-employee#seo-employee) | Keyword research, one article a weekday, publishing, indexing, rank review and your visibility in AI answers | 8 |
+| <img src="https://club.reinventing.ai/img/employees/thumbs/web-dev-employee.webp" width="72" height="72" alt=""><br>[**Web Dev Employee**](https://club.reinventing.ai/ai-employees?utm_source=github&utm_medium=readme&utm_campaign=ai-employees&utm_content=table-web-dev-employee#web-dev-employee) | Site health, error triage, small changes on a branch, dependency review | 8 |
+| <img src="https://club.reinventing.ai/img/employees/thumbs/social-media-employee.webp" width="72" height="72" alt=""><br>[**Social Media Employee**](https://club.reinventing.ai/ai-employees?utm_source=github&utm_medium=readme&utm_campaign=ai-employees&utm_content=table-social-media-employee#social-media-employee) | Posts drafted in your voice for each platform, a veto window, replies drafted for you | 7 |
+| <img src="https://club.reinventing.ai/img/employees/thumbs/ad-manager-employee.webp" width="72" height="72" alt=""><br>[**Ad Manager Employee**](https://club.reinventing.ai/ai-employees?utm_source=github&utm_medium=readme&utm_campaign=ai-employees&utm_content=table-ad-manager-employee#ad-manager-employee) | Account reads, creative sets, build sheets and the weekly change list. Money moves only when you approve | 7 |
+| <img src="https://club.reinventing.ai/img/employees/thumbs/sales-employee.webp" width="72" height="72" alt=""><br>[**Sales Employee**](https://club.reinventing.ai/ai-employees?utm_source=github&utm_medium=readme&utm_campaign=ai-employees&utm_content=table-sales-employee#sales-employee) | Prospect sweeps, first touches into your own drafts, follow ups that never go quiet | 7 |
+| <img src="https://club.reinventing.ai/img/employees/thumbs/customer-satisfaction-employee.webp" width="72" height="72" alt=""><br>[**Customer Satisfaction Employee**](https://club.reinventing.ai/ai-employees?utm_source=github&utm_medium=readme&utm_campaign=ai-employees&utm_content=table-customer-satisfaction-employee#customer-satisfaction-employee) | Inbox sweep, replies drafted hardest first, churn flags with evidence | 8 |
+| <img src="https://club.reinventing.ai/img/employees/thumbs/chief-of-staff.webp" width="72" height="72" alt=""><br>[**Chief of Staff**](https://club.reinventing.ai/ai-employees?utm_source=github&utm_medium=readme&utm_campaign=ai-employees&utm_content=table-chief-of-staff#chief-of-staff) | Reads every other employee's run log, names what quietly stopped, brings you three moves | 7 |
 
-Sixty routines. Each employee's folder has its full schedule and a sample of its output.
+Sixty routines. Every kit, with its full schedule and a sample of its output, is in [employees/](employees).
 
 ## Install in two steps
 
@@ -93,6 +97,7 @@ You need an AI agent you are logged in to (Claude Code is what I use) and a brow
 - **They run on the agent you already use.** Claude Code and ten others, without a routine changing by one word.
 - **You can direct any of them in chat.** Open a session in the employee's folder and tell it what to do.
 - **Upgrades never overwrite your work.** `npx ai-employees upgrade` leaves every file you edited alone.
+- **They tell you when a newer kit is out.** Once a month, in the morning brief, in plain words. A fix an employee made to itself that would help everyone is drafted for you to send back, and nothing is sent without you.
 
 [The long version](docs/WHAT-SETS-THEM-APART.md).
 

package/docs/COST.md

@@ -49,6 +49,10 @@ Anthropic publishes no token or dollar quota per plan, so a plan cannot be mappe
 
 The only way to turn the table into dollars is an API key, and an API key loses the browser lane, which most of these routines need. Run them on a seat.
 
+## On Grok Bot
+
+Grok Bot is metered differently: a plan carries a weekly usage allowance, and the bots draw it down. As of August 21, 2026, bots come with Cursor Pro+ at $60 a month, SuperGrok Plus at $100, Cursor Ultra at $200, SuperGrok Heavy at $300, and Cursor Teams at $40 a seat, with a limited free trial. What the price does not say is how fast the allowance moves under a fleet: operators running several bots on patrol report reaching it early in the week. The kits are not always on, which is the point. One Employee is a handful of runs a day, each inside a window and a budget, and a skipped fire exits before it reads the contract. Start on the lowest tier that includes bots, run one Employee for a week, and read the meter before you add a second. Nothing on this page was measured on Grok Bot; the numbers above are its published prices, and the measurement will follow the first install that reports.
+
 ## Making cost a field, not a guess
 
 `scripts/runlog.mjs` accepts nine optional fields on a run record: `model`, `harness`, `turns`, `input_tokens`, `output_tokens`, `cache_write_tokens`, `cache_read_tokens`, `cost_usd`, and `cost_basis` (`api-list`, `subscription`, or `unknown`). They are counts and prices only, never required, and the refusal rules on the rest of the record are untouched. On the CLI, `claude -p --output-format json` prints `total_cost_usd` and the token counts on exit; the launcher in `run/` writes that JSON to `run/<id>.last.json`. A flag that attaches those numbers to the record the routine just wrote is not built yet, and until it is the fields get filled by the routine's own last step where a harness exposes them, or stay absent.

package/docs/FAQ.md

@@ -10,6 +10,8 @@
 
 **Which harness?** Built for Claude Code, OpenClaw, Hermes, OpenCode, Grok Bot, Codex, Antigravity, Pi, Cline, Qwen Code and DeepSeek. Claude Code is the one the GTM Engineer runs my own club launch on every weekday. OpenClaw, Hermes, Cline and Qwen Code have built in cron or scheduled tasks, Codex has scheduled runs, Antigravity has the `agy` job runner, DeepSeek schedules through a plugin, OpenCode and Pi use the operating system's scheduler, and Grok Bot runs from its own cloud computer. `docs/HARNESSES.md` has the invocation and the first run check for each.
 
+**Does it run on Grok Bot?** Yes, with one difference: the bot's computer is not yours. The bot installs the kit on its own cloud computer, you paste the kit's `AGENTS.md` into the bot's Instructions field, one recurring task per routine runs from `SCHEDULE.md`, and the morning brief is posted into the bot's own thread because you never open that computer's files. Every bot on your account shares that computer and every login on it, so scope by what you sign in to, never by which bot you talk to. The hosted section of `docs/HARNESSES.md` has the detail.
+
 **Can I run just one?** Yes. Each employee is a self contained folder. They share nothing but a scheduler. The GTM Engineer is the one to start with; the Chief of Staff is the one to add second, because it reads the run logs of every other employee on the machine and tells you which one quietly stopped.
 
 **What happens when my machine is asleep?** It depends on your scheduler: the Claude Desktop app and Windows Task Scheduler run one late catch up, launchd folds every missed fire into one, and cron skips it for good. Every routine has a window, so a late fire either does its work once or records a skip and exits. A closed laptop produces nothing, and the next morning's standup says so in plain words.
@@ -30,9 +32,11 @@
 
 **Can I run it for a client and charge for it?** Yes. The eight are MIT. Install them, adapt them, sell the work. Do not call your version Reinventing.AI or the Agent Ops Club; `TRADEMARKS.md` says what needs a rename.
 
-**Is any of my data sent anywhere?** Not by this repo. There is no telemetry in the kits, the installer, or the `hire` skill. What the agent reads during a run goes to your model provider the way any session on your harness does. Everything the employee writes stays in its folder on your machine, and the `.gitignore` inside each kit keeps it out of any repo you push.
+**Is any of my data sent anywhere?** Not by this repo. There is no telemetry in the kits, the installer, or the `hire` skill. Once a month each employee reads one public file, the `VERSION` of its own kit in the published package, to see whether a newer one exists; the request carries nothing about you or your install, and one line in that routine's `## Corrections` turns it off. What the agent reads during a run goes to your model provider the way any session on your harness does. Everything the employee writes stays in its folder on your machine, and the `.gitignore` inside each kit keeps it out of any repo you push.
+
+**How do updates work?** Your employee tells you. Once a month it checks the published version of its own kit, and when there is a newer one the next morning brief says so, with a few plain lines on what is new and the line to run. It never runs the upgrade itself. Employees update one at a time. Everything under `strategy/`, `state/`, your ledgers, your learned `recipes/*.json`, and the `## Corrections` at the foot of every file are yours and are never overwritten. Everything else is safe to replace. Each kit's `CHANGELOG.md` has the procedure under "Updating without losing your work", and `docs/UPGRADING.md` has the long version.
 
-**How do updates work?** Employees update one at a time. Everything under `strategy/`, `state/`, your ledgers, your learned `recipes/*.json`, and the `## Corrections` at the foot of every file are yours and are never overwritten. Everything else is safe to replace. Each kit's `CHANGELOG.md` has the procedure under "Updating without losing your work".
+**Can my fixes go back into the kits?** Yes, and the employee helps. When a routine repairs its own instructions it logs the change. Once a month the employee picks out the repairs that would be just as right on any business, takes your business out of them, and writes a draft to `improvements/contribution-draft-YYYY-MM.md`. The brief names it once. You read it, then paste it into an issue or delete it. No routine ever opens an issue or a pull request.
 
 **What is the club, and what is not in this repo?** The eight employees are complete and free for good; nothing in them is held back. The Agent Ops Club is where the guided walkthrough, the Masterclass, the premium software library with a resale license, the live sessions and, from October, premium employees live. A free club account gets you the session calendar, the walkthrough lesson with the launch replay, the preview lessons and employee updates. The README's Go further section has the link.
 

package/docs/GUARDRAILS.md

@@ -4,6 +4,8 @@
 
 **The second guardrail is on credentials, and it stays on.** No AI Employee creates an account, enters or generates a password, completes a captcha, accepts terms, or writes a credential into any file. It never needs your password to do its job, so there is nothing to release.
 
+**On a hosted harness the guardrails are still yours to keep, and bots are not a boundary.** On Grok Bot every bot on your account shares one cloud computer, one filesystem and every login on it. A release you write for one Employee is a file every bot can read, and a session you sync there is a session every bot can use. Scope by what you sign in to on that computer, never by which bot you talk to, and start read only on public pages before you sync anything.
+
 | Routine kind | Reads | Writes | Leaves for you | Holds, unless you release it |
 |---|---|---|---|---|
 | The standup, every weekday | Every ledger, run record and tick since yesterday | The board and the thirty line brief | The brief, first thing | Uses a browser |

package/docs/HARNESSES.md

@@ -16,7 +16,7 @@ Two rules hold on every harness. **Routines are scheduled jobs, not skills**: po
 | OpenClaw | Ready | Built in cron: `openclaw automations create "<cron>" "<message>" --name <id> --session isolated`, one per routine, with the timezone flag | The message is `Read <root>/routines/<id>/SKILL.md and follow it.` | Whether its browser control attaches to your signed in profile; run the probe in `CAPABILITIES.md` 1.2 | `mcp.servers` in its config, `openclaw mcp login <name>`; skills from ClawHub |
 | Hermes | Ready | Built in cron with delivery to any platform | Point each job at the routine file as its prompt | Whether it reads files and runs a shell command; then the browser question | `mcp_servers` in `~/.hermes/config.yaml`, or `hermes mcp install <name>` from its catalog |
 | OpenCode | Ready | None built in; use the operating system's | `opencode run "<prompt>"`, confirm against `opencode --help` | Add a browser automation server for the browser lane | `mcp.<name>` in `opencode.json`, then `opencode mcp auth <name>` |
-| Grok Bot | Ready | Its bots run routines on a schedule from their own cloud computer | One recurring task per routine, handed that routine's `SKILL.md` as the run prompt | Whether it can reach your signed in accounts at all; it runs elsewhere | Its built in connectors, or a custom connector by URL at grok.com/connectors |
+| Grok Bot | Ready | Its recurring tasks, one per routine, on a bot named after the Employee. Every bot on your account shares one cloud computer, and the kit lives there | The bot installs the kit on its own computer (`npx ai-employees hire <slug> --to ~/ai-employees/<slug>` in its terminal), you paste the kit's `AGENTS.md` into the bot's Instructions field, and each recurring task's prompt is `Read <root>/routines/<id>/SKILL.md and follow it.` with the fire time in the timezone `SCHEDULE.md` names | Whether your signed in sessions are on that computer. They are only if you signed in there or you run a cookie sync to it (Agent Cookie, from a Mac over Tailscale), and every bot then shares every login. Then that the first brief arrived in the bot's thread, which is `brief.deliver` | Its built in connectors, or a custom connector by URL at grok.com/connectors |
 | Codex | Confirmed | The app's automations: one cron automation per routine, named after the routine id, local execution, the kit folder as a working directory | The automation's own prompt, Shape B; `codex exec "<prompt>"` by hand where the CLI is signed in | The sandbox and the scheduled process: confirm it can write in the kit folder, reach the network, and reach the same connections the chat session could, because the first scheduled fire is the first real test of both | `[mcp_servers.<name>]` in `~/.codex/config.toml`, then `codex mcp login <name>`; skills in `.agents/skills` |
 | Antigravity | Ready | `agy` job runner pointed at the routine folder | `agy -p "<prompt>"` | Whether it drives your signed in browser profile or a clean one | `.agents/mcp_config.json` in the workspace or `~/.gemini/config/mcp_config.json`, with `serverUrl`, or its MCP Store |
 | Pi | Ready | None built in; use the operating system's | `pi -p "<prompt>"`, confirm against `pi --help` | Whether it reads the kit folder as the working directory; then the browser question | None. Pi runs no MCP servers by design, so only the command line routes in a kit's section 4b apply, wrapped as skills |
@@ -33,6 +33,18 @@ Every kit's `CAPABILITIES.md` section 4b names the connections that read its acc
 3. **Prove one routine by hand before registering the rest.** Run the standup, watch it write `brief-latest.md` and exactly one line into `runlog.jsonl`. Eight jobs registered on an invocation nobody ran is eight silent failures on the same morning.
 4. **A non zero exit should leave a record.** The Windows launcher does this through `runlog.mjs --failed-run`. On other harnesses, add the same `||` fallback to the command line.
 
+## Grok Bot, and the hosted shape it set
+
+Grok Bot is the one harness on this page whose computer is not yours, and the shape is worth writing down once because Codex cloud and Meta Muse share it. Everything here comes from operators' published accounts of the product in August 2026, and each kit's `CAPABILITIES.md` marks it `expected` until you write `confirmed` into `## Corrections`.
+
+- **One computer for every bot.** All the bots on an account share one persistent Linux machine with a terminal, file access and a real browser. Each bot has its own screen and runs one computer-use task at a time; several bots can drive the browser at once. So the kit lives on that computer, the bot installs it there itself, and the cloud sync rule does not apply.
+- **One bot per Employee, one task per routine.** Name the bot after the role, paste the kit's `AGENTS.md` into its Instructions field (it is the map that points at the files, and it is short enough to fit), and register one recurring task per routine with the Shape B prompt. Do not turn the routines into the bot's workflows: a workflow is invoked on demand, a routine runs in a window.
+- **Bots are not a security boundary.** Files, browser sessions and app logins are shared by every bot on the computer. A release you write for one Employee is a file every bot can read; a session you sync there is a session every bot can use. Scope by what you sign in to, never by which bot you talk to, and start read only on public pages before you sync anything.
+- **Staying signed in is a sync you run.** Nothing in a kit signs in, so your sessions reach the bot's browser only if you signed in there or you keep them there with a cookie sync such as Agent Cookie (Chrome cookies from a Mac to the bot over Tailscale, every fifteen minutes). The kit names it under `browser.session`, detects it, and installs nothing.
+- **The brief comes to your thread.** You never open that computer's files, so the standup resolves `brief.deliver` and posts `brief-latest.md` into the bot's own thread, which the Grok app carries to your phone. The file stays the record.
+- **Two more routes.** Claude Code can be logged in on the bot's computer, which turns the Grok Bot row into the Claude Code CLI row with Grok Bot as the scheduler. Peekaboo, installed by you on a Mac, lets the bot see and click native Mac apps over the same link. Both are yours to add.
+- **Watch the meter.** Plans carry a weekly usage allowance and fleet work moves it fast. Start on the lowest tier that includes bots, run one Employee for a week, and read the meter before you add a second.
+
 ## Ran a kit on one of these?
 
 Open an issue with the harness and version, the invocation you used, what the first run record said, and what you changed. It goes into the notes for that row, with your name on the change.

package/docs/HOW-EMPLOYEES-WORK.md

@@ -57,6 +57,7 @@ Every routine starts with the same five numbered items, in this order, before an
 - **The pause switch.** An empty file called `PAUSED` in the employee's folder stops every routine. Routine ids on lines inside it stop only those. Delete it and everything resumes; nothing was unregistered. No routine ever creates, writes, or deletes that file.
 - **Corrections.** Every file ends with a `## Corrections` section you write into and every routine reads at the top of every run. A dated line there outranks the file it sits in. This is how a kit gets good at your business specifically.
 - **The changelog of its own changes.** When a routine amends its own instructions it appends one line to `improvements/CHANGELOG.md` carrying the full text it replaced, so anything can be undone without the original download, and tomorrow's brief says what changed under `What changed about me`. It informs you. It does not ask you, because your harness already asks before anything writes to your disk, and that is the right place for that gate.
+- **The brief comes to you.** After the standup writes `brief-latest.md` it resolves `brief.deliver`: the dashboard on a machine you use, the employee's own thread on a hosted agent whose computer you never open, or your own inbox where a mail route exists. The delivered text is the file's text with nothing added, and a brief to your own thread or address is delivery, not a send. Absent every route the file is the brief.
 - **The one push.** It notifies you only when you are the thing blocking it: an expired login, a credential it needs, conversion tracking that died while ads are running, or a browser lock held by a run that died. Once each, never twice for the same problem, never outside your working hours. Everything else waits for the brief.
 
 ## The save test

package/docs/INSTALL.md

@@ -120,7 +120,7 @@ One line per routine, from `CAPABILITIES.md` section 9.3, with the full path to
 
 ### The other ten harnesses
 
-OpenClaw, Hermes, Cline and Qwen Code have a built in cron, Codex has scheduled runs, Antigravity has the `agy` job runner, DeepSeek schedules through a plugin, and Grok Bot runs recurring tasks from its own cloud computer: register one job per routine in that scheduler, with the kit folder as the working directory, the fire time from `SCHEDULE.md`, and the prompt `Read <root>/routines/<id>/SKILL.md and follow it.`. OpenCode and Pi have no scheduler of their own, so use the operating system's route above with their headless command in place of `claude -p`. `docs/HARNESSES.md` has the exact invocation and the first run check for each, and the same rule holds everywhere: run one routine by hand before you register the rest.
+OpenClaw, Hermes, Cline and Qwen Code have a built in cron, Codex has scheduled runs, Antigravity has the `agy` job runner, DeepSeek schedules through a plugin, and Grok Bot runs recurring tasks from its own cloud computer: register one job per routine in that scheduler, with the kit folder as the working directory, the fire time from `SCHEDULE.md`, and the prompt `Read <root>/routines/<id>/SKILL.md and follow it.`. OpenCode and Pi have no scheduler of their own, so use the operating system's route above with their headless command in place of `claude -p`. `docs/HARNESSES.md` has the exact invocation and the first run check for each, and the same rule holds everywhere: run one routine by hand before you register the rest. Grok Bot is the one whose computer is not yours: the bot installs the kit on its own cloud computer, you paste the kit's `AGENTS.md` into the bot's Instructions field, and the brief reaches you in the bot's thread. The hosted section of `docs/HARNESSES.md` has the rest, including what the shared computer means for your logins.
 
 ## What a first day looks like
 

package/docs/PREREQUISITES.md

@@ -53,7 +53,7 @@ Claude Code uses it for its shell tool and the Desktop app requires it for local
 
 Optional, and the section in each kit's README called "What you lose with no browser control" is honest about what it costs to skip. The requirement is the same on every harness: it has to drive a browser that carries your own logins, not a clean automated profile, because the routines share your browser's login state and never sign in to anything. On a login wall or a captcha they stop that phase and say so.
 
-On Claude Code that means Google Chrome or Microsoft Edge, the Claude in Chrome extension (1.0.36 or later), `claude --chrome` on the CLI or the Desktop app's own integration, a login based session rather than an API key, and the site permissions granted in the extension before the first scheduled run. On OpenCode and Codex it is a browser automation server you add. On Antigravity and DeepSeek browser control is part of the product, and the thing to settle is which profile it drives. On Grok Bot the browser runs on its own cloud computer, so whether it can reach your accounts at all is the first check. Each kit's `CAPABILITIES.md` section 1.2 has a probe that answers the question on any harness in a minute.
+On Claude Code that means Google Chrome or Microsoft Edge, the Claude in Chrome extension (1.0.36 or later), `claude --chrome` on the CLI or the Desktop app's own integration, a login based session rather than an API key, and the site permissions granted in the extension before the first scheduled run. On OpenCode and Codex it is a browser automation server you add. On Antigravity and DeepSeek browser control is part of the product, and the thing to settle is which profile it drives. On Grok Bot the browser runs on the bot's own cloud computer, so your sessions are there only if you signed in on that computer or you run a cookie sync to it (Agent Cookie syncs a Mac's Chrome cookies over Tailscale), and every bot on the account then shares every login: scope by what you sign in to, never by which bot you talk to. Each kit's `CAPABILITIES.md` section 1.2 has a probe that answers the question on any harness in a minute.
 
 ## 7. A scheduler
 
@@ -72,11 +72,11 @@ Otherwise the operating system's:
 
 ## 8. A machine that is awake at fire time
 
-These are scheduled routines on your machine, not a service somewhere else. Either the machine is awake at the times in `SCHEDULE.md`, or you move the fire times to after it normally wakes. On the Desktop app, turn on Keep computer awake. A closed lid still sleeps. Grok Bot is the one exception, because its schedule runs on its own cloud computer.
+These are scheduled routines on your machine, not a service somewhere else. Either the machine is awake at the times in `SCHEDULE.md`, or you move the fire times to after it normally wakes. On the Desktop app, turn on Keep computer awake. A closed lid still sleeps. Grok Bot is the one exception, because its schedule runs on its own cloud computer. The kit lives on that computer too, and the brief reaches you in the bot's own thread rather than in a file you open (`brief.deliver`, `CAPABILITIES.md` section 6).
 
 ## 9. A working folder outside cloud sync
 
-Not inside OneDrive, Dropbox, Google Drive or iCloud. The routines write state and a run log mid run, and a sync client corrupts exactly the file that tells tomorrow's run what already happened. `D:\AgentOps\gtm-engineer` or `~/ai-employees/gtm-engineer` is right. The installer refuses a synced path, and the install prompt moves the kit out of one if it finds itself there.
+Not inside OneDrive, Dropbox, Google Drive or iCloud. The routines write state and a run log mid run, and a sync client corrupts exactly the file that tells tomorrow's run what already happened. `D:\AgentOps\gtm-engineer` or `~/ai-employees/gtm-engineer` is right. The installer refuses a synced path, and the install prompt moves the kit out of one if it finds itself there. On Grok Bot the folder is on the bot's own cloud computer, which no sync client touches.
 
 ## 10. A usage budget
 

package/docs/STANDARD.md

@@ -2,7 +2,7 @@
 
 Build spec for every AI Employee in the club. Not shipped to members. The GTM Engineer is the reference implementation; every later Employee inherits everything here and adds only its own domain expertise.
 
-Standard version 1.3, 2026-09-11: LAW 4 names connected sources, the per capability routes a member connects in their own harness, read only and preferred over the browser lane. Version 1.2, 2026-09-05: LAW 2 became the two guardrails, the first of them released channel by channel by the member in `RELEASES.md`. Version 1.1, 2026-08-28. Laws 6 through 8 and the operator-session and browser-lane sections were earned in the first live week of the GTM Engineer running Mark's own launch; the release notes in each kit's CHANGELOG carry the short story.
+Standard version 1.4, 2026-09-23: LAW 7 gains a third delivery surface, `brief.deliver`, so the brief reaches the member on a harness whose computer they never open; section 4 gains the five questions a routine answers before it is scheduled. Version 1.3, 2026-09-11: LAW 4 names connected sources, the per capability routes a member connects in their own harness, read only and preferred over the browser lane. Version 1.2, 2026-09-05: LAW 2 became the two guardrails, the first of them released channel by channel by the member in `RELEASES.md`. Version 1.1, 2026-08-28. Laws 6 through 8 and the operator-session and browser-lane sections were earned in the first live week of the GTM Engineer running Mark's own launch; the release notes in each kit's CHANGELOG carry the short story.
 
 Derived from Mark's own production routines rather than invented: the push mechanics come from `night-shift-brief` and `morning-clicks-block`, the window and period guards from the same, the browser craft from roughly thirty live Chrome routines.
 
@@ -35,6 +35,7 @@ An Employee is judged on one question: **after ninety days of running unattended
 **LAW 7: The Employee brings the work to the member.** Work product that only exists as a file the member must go hunting for reads as no work at all. Two delivery surfaces, used wherever the role allows:
 - *The dashboard is a view over live state, never installed prose.* The build bakes the morning artifact, queue files, digests, and the run history straight from the working files; every routine that writes work product rebuilds the dashboard before writing its run record; a tab describing work renders from the board, not from text written at install, which rots the same week.
 - *The browser is a delivery surface.* Where the role touches the world through forms, drafts, or posts, the Employee fills the form and leaves the tab open, prepares the draft inside the member's own account in draft state, and stages the post ready to publish. The member's contribution shrinks to the one click a held guardrail reserves for them. Every browser-staged deliverable also lands in a durable queue file carrying the full text of every field, so a closed tab loses nothing. Anti-bot checks are never answered; they are left for the member with the submit.
+- *The brief is delivered, not filed.* Every standup resolves `brief.deliver` after it writes `brief-latest.md`: the dashboard on a machine the member uses, the Employee's own thread on a hosted harness whose computer the member never opens, the member's own address where a mail route exists. The delivered text is the file's text with nothing added. A brief to the member's own thread or address is delivery, not a send, and needs no release; absent every route the file is the brief and the run record says `brief: file only`. (v1.4, 2026-09-23, from the first hosted harness: a brief on a cloud computer nobody opens is no brief.)
 (Earned 2026-08-28, Mark: "They should bring it to me and bring it to my attention," and the same morning three directory submissions went live within minutes of forms being staged in his browser.)
 
 **LAW 8: A tick records consent; the routine performs the move.** When a member ticks a card whose definition of done implies a file change, the next routine to read that tick completes the mechanical part itself. A confirmed proof inventory whose lines never got moved is a day of thin drafts nobody wanted. Consent is the member's; labor is the Employee's.
@@ -151,6 +152,8 @@ scripts/             small deterministic helpers with a --selftest
 
 **Two routines never drive one browser.** A mutex with a dead-holder timeout, and a routine that never took the lock never deletes it.
 
+**Five questions before any routine exists**, and every shipped routine answers them in its `SCHEDULE.md` row, its brief lines and its push rules: **trigger** (a clock time, or an event such as new mail or a new row), **frequency** (how often the underlying thing actually changes, never how often it would be nice to look), **output** (where the result lands and who reads it), **silence** (what it does when there is nothing to report, which is nothing) and **stop** (the one condition that pages the member instead of waiting for the brief). A routine that cannot answer all five is not ready to schedule, and a routine whose honest answer to frequency is "rarely" gets a weekly row, not a patrol. (v1.4, 2026-09-23.)
+
 ---
 
 ## 5. Voice and copy

package/docs/UPGRADING.md

@@ -4,6 +4,14 @@ An installed employee is two things sharing one folder. The **kit** is ours: the
 
 An upgrade replaces the first and never touches the second. Everything on this page exists to make that guarantee real rather than hopeful.
 
+## Your employee tells you when there is one
+
+From 1.7.0 on, each employee checks once a month, on its first weekday routine, whether a newer version of its kit has been published. When there is one, the next morning brief carries a short `## About this kit` section: the two version numbers, up to five plain lines on what you get, and the two lines below. It shows in full once per version and as a one line reminder once a month after that.
+
+The check reads one public file and nothing else. **No routine ever runs the upgrade**, because a scheduled run that downloads a program and executes it unattended is the shape these kits refuse everywhere else. You run it, or you open a chat session in the employee's folder and tell your agent to run it for you. One line in that routine's `## Corrections` turns the check off.
+
+An employee installed before 1.7.0 does not have the check, so that upgrade is the last one you have to remember by yourself.
+
 ## The short version
 
 ```bash
@@ -69,6 +77,8 @@ npx ai-employees contribute gtm-engineer --to /path/to/your/employee --since 202
 
 That prints a field report ready to open as an issue. **Read it before you send it.** Those lines can name your own files, your customers and your numbers, and the command redacts nothing.
 
+From 1.7.0 on the employee also does a first pass for you. The same monthly routine reads that changelog, keeps only the repairs that would be just as right on a different business, takes your business out of them, and writes `improvements/contribution-draft-YYYY-MM.md`. The brief names the draft once. It is still yours to read before it goes anywhere, and **no routine ever opens an issue or a pull request**: you paste it into a new issue, or you delete the file.
+
 ## What an upgrade will not do for you
 
 It does not touch your scheduler. If a new version adds a routine, its row appears in `SCHEDULE.md.new` and registering it is yours to do. It also never changes a day, a window or a budget you have set, because those are the four controls the whole design hands to you.

package/docs/WHAT-SETS-THEM-APART.md

@@ -3,8 +3,11 @@
 - **They get better at your business every run.** When a page moves, a button changes or a step now needs a scroll, the routine fixes its own instructions in the run that hit it, keeps the text it replaced as the undo, and tells you in the next morning's brief under "What changed about me".
 - **They drive your browser and your PC the way you do.** Every browser routine works from a technique library written from real runs on my own machine, not from documentation: click what the page actually shows, read the page back to verify, leave a filled form open on the last step. Each site's flow is learned on your machine the first time a routine needs it and repaired every time after. Two routines never use the same signed in account at once, and on LinkedIn they read and never click.
 - **One push to your phone, only when you are the blocker.** A login expired, a credential is missing, your conversion tracking stopped while ads are live, or a run died holding the browser. Four cases and no fifth. One short line, never twice for the same thing, never outside your working hours, never on a first run. Everything else waits for the brief. [The one push](STANDARD.md#23-the-one-push).
+- **The brief comes to you.** After the standup writes it, the routine brings it to wherever you are: the dashboard on your own machine, the Employee's own thread on a hosted agent such as Grok Bot, or your own inbox where a mail route exists. A brief on a computer you never open is no brief, so on a hosted harness it lands in your thread and the Grok app carries it to your phone.
 - **They use the connections you already have.** Where your agent already has a connector for an account, the routine reads through it instead of the screen: Meta's own Ads MCP server for an ad account, the Gmail connector for drafts and replies, the Vercel and Supabase connectors for logs and advisors, Metricool for publishing. Each kit names its connections in one table, uses them read only, and works without any of them; nothing is installed for you.
 - **They run on the agent you already use.** Claude Code, OpenClaw, Hermes, OpenCode, Grok Bot, Codex, Antigravity, Pi, Cline, Qwen Code and DeepSeek, without a routine changing by one word. Routines describe what they need done, and one file per kit says how each agent does it.
+- **One routine, one job, one output.** Routines run solo and never supervise each other; the Chief of Staff reads their run logs afterwards and names what quietly stopped. Crews of agents that hand work to each other unsupervised have been measured multiplying their own errors many times over, and a wrong step here lands in your brief instead of in three other routines.
 - **You can direct any of them in chat.** Open a session in the employee's folder and it does anything you could do by hand, on your word: tick a card you confirmed, stage a form now, retune a strategy file, correct a stale brief. It leaves the same trail a routine would, and the scheduled runs treat that work as yours.
 - **You set how far they go.** Every employee drafts, fills and stages by default, and the last click is yours. Release a channel in `RELEASES.md` and the routine completes that action itself from then on. Your agent's own permission settings are the gate, and every file in the kit is plain text in your own folder, yours to change.
 - **Upgrades never overwrite your work.** `npx ai-employees upgrade` reports first, leaves any file you edited alone, and never reads your strategy or your ledgers. Every kit follows the published [Agent Employee Standard](STANDARD.md), and `npx ai-employees contribute` turns the fixes a kit made to itself into a report you can send upstream.
+- **They tell you when a newer kit is out.** Once a month each employee reads the published version of its own kit. When there is a newer one, the next morning brief says so once, with up to five plain lines on what you get and the one line that takes it. No routine ever runs the upgrade. The same monthly pass looks through the repairs the employee made to its own instructions, keeps the ones that would be just as right on any business, takes your business out of them, and leaves a draft in `improvements/` for you to read and send, or delete. Nothing is sent without you.

package/employees/ad-manager-employee/AGENTS.md

@@ -1,8 +1,12 @@
 # AGENTS.md
 
-**Ad Manager**, kit version 1.2.0. One of the eight AI Employees from [github.com/markfulton/ai-employees](https://github.com/markfulton/ai-employees).
+**Ad Manager**, one of the eight AI Employees from [github.com/markfulton/ai-employees](https://github.com/markfulton/ai-employees).
 
-This file follows the [AGENTS.md](https://agents.md) convention so that any harness can pick this kit up without being told how. It is a map, not the instructions. **The instructions are the files it points at, and they are authoritative over anything summarised here.**
+This file follows the [AGENTS.md](https://agents.md) convention so that any harness can pick this kit up without being told how. It is a map, not the instructions. **The instructions are the files it points at, and they are authoritative over anything summarised here.** The version this kit ships as is in `VERSION` at the root.
+
+## If your harness has an Instructions field instead of a folder
+
+On a hosted agent such as Grok Bot, the kit lives on the bot's own cloud computer and the bot reads an Instructions field before every task. Paste this whole file into that field, with the folder's absolute path on that computer in place of `«ADS_ROOT»`. It is the base layer (the two guardrails and the files that outrank everything else), the role layer (`ROLE.md`, which names the evidence standard) and the current focus (the strategy folder the routines keep current), and it is short enough to fit. Everything else stays in the files.
 
 ## If you have been asked to install this Employee