MoxyWolf LLC
Resource pack

R5-03 · backs slide 29

R5-03 Ops model one-pager

Supports slide 29.

How MoxyWolf runs: two people, ten AI department agents, a Chief of Staff, and a named human on anything that ships.

Timeline

Date What happened Evidence
15 Oct 2025 Google Cloud’s AI Agents Live + Labs, Los Angeles. Work with a Google engineer I call “Sunshine” begins. Invitation emails; my account
3 Jan 2026 First app built together My account
20 Feb 2026 A CoWork plugin handed to Edify and Strike Graph My account
12 May 2026 Plugin marketplace goes public moxywolf-plugins first commit, 12 May 2026: “Initial MoxyWolf plugin marketplace”
31 May 2026 Release Owner’s Gate applied by rule to outbound Company norm
8 Jul 2026 Release Owner’s Gate published as SCF control AAT-33 (SCF 2026.2) SCF GitHub release notes, verified 17 Oct 2026
29 Aug 2026 Chief of Staff agent My account; see the note below
10 Sep 2026 SCAMPER becomes a command: /scamper in academic-pipeline 0.4.0 moxywolf-plugins commit, 10 Sep 2026
Sep 2026 QBatch switched off My account; vendor records
25 Sep 2026 Release Owner’s Gate forced on merges in the gstack plugins gstack-execution plugin
6 to 7 Oct 2026 Ten department agents: finance, operations, security, people, PMO, IT, strategy, customer experience, sales, marketing moxywolf-plugins: eight department plugins first committed 6 Oct, sales and marketing 7 Oct; Sprint 24 submission

What it runs

The seven-metric Monday scorecard (R5-02). The nightly sprint-block check. The commitment calendar. CRM sync health. The release gate on merges.

The governance

Agents propose and draft. A named human signs anything irreversible or new going outbound. Approved templates run only inside agreed limits. Autonomy is earned one task type at a time.

What it replaced

QBatch, at $35 an hour, because the agents now out-code the contractor. Before that, the Edify and KingdomKode agencies (R5-06).

What isn’t ours

The underlying tooling is open-source and vendor-published, from Anthropic and Google. Most of the plugin development started from repos both suggested. The department model, the governance and the compliance-domain skills are ours.

Not yet evidenced: the dates 15 Oct 2025, 3 Jan 2026 and 20 Feb 2026 rest on my account. The invitation emails and first-app records should be attached before submission.

Not yet evidenced: 29 Aug 2026 for the Chief of Staff. The chief-of-staff plugin’s first commit in moxywolf-plugins is 6 Oct 2026 (“chief-of-staff 0.1.0: CS-001 routes an ask to its departments”). If an earlier version ran elsewhere, that record needs attaching; otherwise slide 29 should say Oct.

Not yet evidenced: QBatch’s $35 hourly rate. It’s my figure; the invoices aren’t attached.

Not yet evidenced: “Sunshine” is a nickname. Her name, and whether she can be named, are still to confirm.

See it live

The plugin stack has a public field guide at go.moxywolf.com/plugins. It shows what to run for a given outcome, the human gate and the stop condition, and the full catalog.

As of 14 Oct 2026 (marketplace 1.136.0), the guide counts 378 entry points: 233 active skills, 133 commands and 12 agent files (ten department agents and two reading agents), across 50 catalog entries. The guide states what it hasn’t verified yet, live hook behaviour included. That’s the same rule as the deck: show your work.

Sources:

  • Sprint 24 micro-assessment v2, Oct 2026 (ten agents, the gate, graduated autonomy)
  • Capstone Facts Reconciled, 17 Oct 2026 (Release Owner’s Gate dates, SCAMPER commit)
  • SCF 2026.2 GitHub release notes (AAT-33)
  • MoxyWolfLLC/moxywolf-plugins git history, read 17 Oct 2026 (marketplace, department, Chief of Staff and /scamper dates)
  • My account of the Google collaboration and plugin history, Oct 2026