feat: add company operations planning workflow

[EthanThatOneKid]

Summary

• add a load-on-demand company-operations planning skill for Zo Computer
• make Zo the supervised research, planning, coding, deployment, documentation, drafting, and review workflow
• establish GitHub as the work tracker and wazootech/memory as the durable knowledge wiki
• keep external account operations, quota bypasses, and side effects out of the default workflow

Workflow

The skill provides /company start, /company plan, /company build, /company brand, /company launch, and /company scale. It includes read-only scheduled-review guidance and approval gates for deployments, public changes, billing, ads, account connections, and outbound communications.

The current Computer runtime has no direct cross-repository memory tool, so the skill prepares reviewable memory handoffs instead of claiming that repository-bound GitHub tools wrote to wazootech/memory.

Verification

• pnpm typecheck passed
• pnpm test passed: 52 tests
• git diff --check passed
• focused company-operations skill smoke check passed
• pnpm build compiled successfully, then stopped during page-data collection because TRUSTED_DEPLOYMENT_HOSTS is not configured in this environment
• pnpm build:eve is blocked by the host's Node.js 22.23.1; Eve requires Node.js 24+

No deployment or merge was performed.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
computer	Ready	Preview	Sep 23, 2026 5:33pm UTC

[wazoocomputer]

I hit an error while handling your request (Model provider API error: Invalid schema for function 'cleanup_run_history': schema must be a JSON Schema of 'type: "object"', got 'type: null'.).

Please try again, rephrase, or reach out if it keeps failing.

Error id: d9833f33-7d45-4fcc-9178-bdfa5fb11e49

[wazoocomputer]

This session could not recover from an error (Model provider API error: Invalid schema for function 'cleanup_run_history': schema must be a JSON Schema of 'type: "object"', got 'type: null'.).

Start a new comment to continue.

Error id: d9833f33-7d45-4fcc-9178-bdfa5fb11e49

[EthanThatOneKid]

I found no blocking correctness issues. CI passes, the skill is scoped to the attached repository, and the memory handoff/side-effect boundaries are clearly stated.

One non-blocking concern: the root routing instruction says to load company-operations whenever the user asks for “building.” That word covers nearly every ordinary implementation request, so it may over-trigger company-planning guidance on normal bug fixes and coding tasks. I would narrow it to /company, company validation/planning/branding/launch/growth, or explicitly “building a company or product.”

[EthanThatOneKid]

Change request — still a draft, and it needs a rebase plus a regenerated computer.af

Reviewing this because it was in the queue, not because it is up for merge: it is a draft, and its own description says no deployment or merge was performed. Nothing here is a rejection of the content — the skill is careful and its gates read the way this repository's instructions already talk (GitHub as tracker, wazootech/memory as the durable wiki, deployment/public/billing/account actions held behind approval, no quota or rate-limit bypass). The refusal to claim that repository-bound GitHub tools wrote to wazootech/memory, and the decision to prepare reviewable handoffs instead, is the right instinct.

Three things before it can leave draft:

1. Mark it ready when you want it reviewed as such. A draft is not in the merge queue by design, so it cannot be triaged alongside the others.

2. Rebase, and regenerate the agent file. It merges clean against main right now. But it edits agent/instructions.ts, and wazootech/computer#75 adds a CI gate (pnpm run check:agent-file) that regenerates computer.af from the source and fails on any diff. Once #75 lands, this branch — like every other PR that touches agent/instructions.ts or adds a tool — will fail CI until it re-exports and commits agents/@wazootech/computer/computer.af. Same applies to #70, #67 already having landed, and to anything else in flight.

3. Decide on the always-on line. This PR adds a line to the root instructions telling the agent to load company-operations for validation/planning/branding/launch/growth/review requests. That line is in the system prompt for every session, including ones with nothing to do with company operations, and computer.af's system block is already ~10 KB. The existing convention in this repo is a short pointer per skill (triaging-issues, github-linear-bridging, writing-quality), so this is consistent — but it is the sixth such pointer, and the front door is broad (/company start|plan|build|brand|launch|scale). Worth asking whether the trigger should be narrower, or whether the skill should be discovered the way the others are without an added instruction line.

Naming and placement are right: company-operations matches the existing lowercase-hyphen convention in agent/skills/, and it sits beside triaging-issues, github-linear-bridging, and writing-quality.

[wazoocomputer]

I hit an error while handling your request (Model provider API error: Authentication Fails, Your api key: ****53a6 is invalid).

Please try again, rephrase, or reach out if it keeps failing.

Error id: 68457453-277d-4c8b-acd5-39c7b85cd393

[wazoocomputer]

This session could not recover from an error (Model provider API error: Authentication Fails, Your api key: ****53a6 is invalid).

Start a new comment to continue.

Error id: 68457453-277d-4c8b-acd5-39c7b85cd393

[EthanThatOneKid]

Addressed in cd82d95.

Both places that named the trigger now drop bare "building":

• agent/instructions.ts — the routing line reads: load company-operations when the user invokes /company or asks for company validation, planning, branding, launch, growth, recurring operating reviews, or building a company or product.
• agent/skills/company-operations/SKILL.md — the frontmatter description carries the same narrowed list, which matters because Eve routes on the description, so the over-trigger would have persisted there even with the routing line fixed.

/company build is unaffected: the explicit subcommand still reaches the build step, and only the implicit "user said building" path is gone.

Verification: pnpm run build:eve (Node 24), pnpm run typecheck, pnpm test (165 pass), pnpm run check:agent-file, and pnpm run check:data-agent-file all pass, and computer.af is regenerated from the updated source.

One thing worth recording from doing this: the instructions block is a JS template literal, so a backtick in that prose has to be escaped. Writing `/company` unescaped closed the literal and the build failed with company is not defined — legible only because CI and the local build both compile it. Worth knowing before the next edit to that block.

[EthanThatOneKid]

Narrowed in cd82d95, and both open review items are now resolved.

The over-trigger. "building" appeared in two places that both feed routing: the root routing line in agent/instructions.ts and the skill's own description frontmatter, which is what Eve routes on. Both now read "when the user invokes /company or asks for company validation, planning, branding, launch, growth, recurring operating reviews, or building a company or product" — your suggested phrasing. Ordinary bug fixes and coding tasks no longer match the word, and /company build still reaches the build path through the explicit doorway.

The metadata block. Removed in cdf8f08; the packaged skill keeps only the required name and description frontmatter and matches its directory name. Thread resolved.

Verification on cd82d95: pnpm run build:eve, pnpm run typecheck, pnpm test (165 passing), and both agent-file checks pass; computer.af is regenerated from the updated source, and this branch's verify workflow ran green on the previous head.

One thing worth flagging: my first pass at this edit broke the build. I put `/company` in the instructions with raw backticks, which closed the template literal and made the following prose parse as JavaScript — eve build failed with "company is not defined". Escaped, rebuilt, clean now. Worth knowing that the instructions file is a template literal, so any backtick in that copy has to be escaped.

[EthanThatOneKid]

Both review items are addressed in cd82d95, pushed to feat/polsia-planning.

"Not necessary." (skill metadata block) — removed in cdf8f08 and confirmed against the current file: the frontmatter is name + description only, no compatibility or metadata keys, and the directory name matches name. pnpm run check:agent-file reports skills: 4 and the file up to date. Thread resolved.

"building" over-triggers (routing line) — narrowed in cd82d95, in both places the trigger was stated, since Eve routes on the skill's description and the routing line is what the model reads:

• agent/instructions.ts: now Load the \company-operations` skill when the user invokes `/company` or asks for company validation, planning, branding, launch, growth, recurring operating reviews, or building a company or product.`
• agent/skills/company-operations/SKILL.md description: same narrowing.

Bare "building" is gone from both, so an ordinary bug fix or coding request no longer matches. The explicit doorway (/company, and /company build) still loads it, and "building a company or product" keeps the intent-level trigger.

agents/@wazootech/computer/computer.af is regenerated from the updated source, as verify requires. Locally: typecheck clean, 165/165 tests pass, build:eve succeeds, and both check:agent-file and check:data-agent-file report up to date. verify passes on cd82d95.

One unrelated note on the red Vercel check: it is not this change. The Next.js build compiles successfully; the deployment then fails in the eve build step with 402 payment_required — Hobby plan usage limit exceeded for Snapshots Storage, resetting 2026-10-01. Preview deploys for this repo are walled off until then; the check is non-required, and the deploy-zo-service production path on main is unaffected.

[wazoocomputer]

I hit an error while handling your request (Model provider API error: Authentication Fails, Your api key: ****53a6 is invalid).

Please try again, rephrase, or reach out if it keeps failing.

Error id: 484e06b9-0245-44b5-83da-f5607ae5dc79

[wazoocomputer]

This session could not recover from an error (Model provider API error: Authentication Fails, Your api key: ****53a6 is invalid).

Start a new comment to continue.

Error id: 484e06b9-0245-44b5-83da-f5607ae5dc79

[EthanThatOneKid]

The non-blocking concern from the review is addressed in cd82d95.

Trigger narrowed. The routing line in agent/instructions.ts and the skill's description frontmatter both listed bare "building", which covers nearly every ordinary implementation request and would have loaded company-planning guidance on normal bug fixes and coding tasks. Both now name /company plus "building a company or product", which keeps the explicit doorway and drops the over-broad word. /company build still routes through the /company trigger.

agents/@wazootech/computer/computer.af was regenerated from the updated source.

Verification (local, cd82d95): pnpm run typecheck clean, pnpm test 165/165 pass, pnpm run build:eve succeeds, pnpm run check:agent-file and pnpm run check:data-agent-file both report up to date. verify is green on the pushed commit.

The Vercel check failure is a plan limit, not this diff. The Next.js build compiles successfully; the deploy dies afterwards, in eve build, while prewarming its Vercel sandbox template:

Failed to prewarm Vercel sandbox template "eve-sbx-tpl-vercel-488112768c1df409-...":
Status code 402 is not ok: Hobby plan usage limit exceeded for Snapshots Storage.
Limit will be reset on 2026-10-01T00:00:00.000Z.

Every deployment on this project now fails at that step, preview or production, until the snapshots-storage limit resets on 2026-10-01 or unused snapshots are deleted / the account moves to Pro. c0d65ea deployed green yesterday at 17:21Z, so the limit was reached in the last day. It does not touch the code in this PR, and it is reported as a non-required check, so the PR stays MERGEABLE.

Filed as #80.

[wazoocomputer]

I hit an error while handling your request (Model provider API error: Authentication Fails, Your api key: ****53a6 is invalid).

Please try again, rephrase, or reach out if it keeps failing.

Error id: 698b10f8-711b-4d70-a9ec-9237dd507a04

[wazoocomputer]

This session could not recover from an error (Model provider API error: Authentication Fails, Your api key: ****53a6 is invalid).

Start a new comment to continue.

Error id: 698b10f8-711b-4d70-a9ec-9237dd507a04

[EthanThatOneKid]

Closing as obsolete under the simplification decision (Computer's brain moves onto the Zo host; the eve factory, its Vercel Blob memory, and the .af projection are being retired).

Two concrete reasons this cannot land: it modifies agents/@wazootech/computer/computer.af, which #93 deleted, and it is CONFLICTING with main for that reason. The company-operations skill and its playbook notes depend on read_factory_brain and the Blob-backed factory, which is the layer being removed.

The skill content is not lost — it stays readable in this closed PR's diff if we want to port the playbook into Computer's new persona records later.

[wazoocomputer]

This pull request (PR #59) is closed as obsolete. It introduces a company-operations planning skill.

The core reason for closing is that the changes are incompatible with the ongoing simplification of Computer's architecture, specifically the retirement of the Eve factory, its Vercel Blob memory, and the .af projection. This PR modifies agents//computer.af, which has since been deleted. The company-operations skill relies on read_factory_brain and the Blob-backed factory, both of which are being removed.

The content of the skill is not lost and remains accessible in the diff of this closed PR, should we choose to port it to Computer's new persona records in the future.