Skip to content

Work Log - 2026-07-01

🎯 Focus for Today

  • Discover and name the agent framework we've been building implicitly
  • Refine the persona framework: opsgov as the director archetype, opslaw as the planned legal agent
  • Note the GitHub org/ownership decision as a parked director-level question
  • Acknowledge the akahu-opsdevnz module that's emerging from the opsfin work

✅ What Got Done

  • OpsMad framework named and described. "Operators Mad" — operator-first, mad about being left behind in DevOps naming. Complimentary to (not a fork of) the BMad Method. The acronym is independent: "Mad" is a statement of operator identity, not derived from BMad's "Build More Architect Dreams." (That said, the BMad observation — HALT gates, skills-as-step-files, Co-authored-by with the agent, conventional commits — is borrow-worthy; the next-steps doc captures what we'd take.)
  • Persona framework refined. The repo-to-persona map is now explicit:
  • public/opsdev.nz/ → opsdev (delivery) + opsfin (sub-agent, the financial one)
  • private/ledger.startmeup.nz/ → opsfin's home for the RAMP work
  • public/startmeup.nz/ → opsgov (future), opslaw (future)
  • outcome-engineering/ (private monorepo) → the integration point where all personas collaborate
  • opsgov clarified as the archetypical director pattern. smunz is one implementation of opsgov. The pattern is reusable; the implementation is specific to StartMeUp.NZ's context.
  • opslaw surfaced as a gap in the persona framework. Legal-affairs work — org structures, contracts, compliance — is currently folded into "smunz does it." Naming opslaw makes the gap visible. TBD where it lives and what's its scope.
  • GitHub presence / org structure opened as a parked director-level question at smunz/startmeup.nz #11. Current state: forks under github.com/john-opsdevnz (status quo). Options documented (status quo, startmeup-nz org, new dedicated org, hand to opsdev.nz collective, retire startmeup-nz). The decision is smunz/opsgov's, with opslaw input.
  • akahu-opsdevnz module acknowledged as emerging. The akahu/ package from today's opsfin work is the seed: the Akahu HTTP client, the CLI, the storage layout. When import_akahu.py and a reconcile-akahu skill land, that's a complete, publishable module. PyPI name candidate: akahu-opsdevnz under the opsdevnz org, matching the existing op-opsdevnz and worklog-opsdevnz.

🧠 Notes & Reflections

OpsMad is a pattern we were already doing, named explicitly for the first time. "Human + LLM + context = an agent; opsdev, opsfin, smunz, opslaw, opssec are instances." The persona framework has been the implicit structure all along. Naming it lets us talk about it, evolve it, and (eventually) document it for others.

OpsMad and BMad are complimentary, not competing. BMad's strengths: a published methodology, a community, working examples. OpsMad's strengths: tiered agent identities (Tier 0 sub-agent → Tier 1 heavy agent → Tier 2 scheduled), 1Password service-account isolation, Open Banking integration, public-monorepo deployment. The right answer is "borrow BMad's patterns, name ours." An ADR or working note lands when smunz has capacity.

opsgov is the pattern smunz is an instance of. Today's work confirmed: smunz/opsdev distinction maps to opsgov-the-archetype vs smunz-the-implementation. When opsgov is eventually created (a separate agent persona, not just a human role), it lives in public/startmeup.nz/. Until then, smunz does the opsgov work in the human+LLM form.

opslaw is a real gap, not a vanity. The persona framework's coverage is currently: opsdev (delivery), opsfin (financial), opssec (security, planned), opsgov (director, smunz implements). Legal affairs has no persona. Naming it makes the gap visible and gives us somewhere to route legal questions when they come up (they will, especially with the GitHub org structure decision).

The "mad operators not operating" critique still applies at the framework level. OpsMad is the methodology; the modules (op-opsdevnz, worklog-opsdevnz, soon akahu-opsdevnz) are the operations. The framework is implicit; making it explicit is a next-step. But not today — today's ops is building the Akahu client and the opsfin agent, not writing the framework book. Build the practice, document the theory later.

  • Parked: smunz/startmeup.nz #11 — GitHub presence / org structure (director-level decision)
  • Closed/parked: smunz/opsdev.nz #7 — BMad Method evaluation (pattern observation captured; adoption deferred)
  • Work item: smunz/internal/ledger.startmeup.nz #1 — Requirements Analysis on opsfin agent
  • Persona framework: outcome-engineering/docs/governance/personas/

⏳ Mañana

  • When capacity allows: opsgov spec (the director archetype; smunz is one instance)
  • opslaw planning (legal affairs — where does it live, what's its scope)
  • ADR or working note on OpsMad vs BMad (when there's time to evaluate BMad properly — Discord, deeper docs)
  • The opsfin Tier 1 setup (Linux user, SSH key, 1Password service account) — real engineering, not framework
  • akahu-opsdevnz PyPI publication once the importer + skill land

🔥 Token Burn

Logged in OpsDev's worklog... we used MiniMax M3 today.

As mentioned, we will in the future publish our agent usage summary from Opencode, they produce a nice graph and we are using their OpenCode Go plan.