Skip to content

Work Log - 2026-06-10

🎯 Focus for Today

  • Standardise oc-opsdevnz module against practice-template-opsdevnz
  • Backport governance files to template repo
  • Draft collective onboarding criteria for SMUNZ
  • Prep for using oc-opsdevnz to set up OpsDev.nz as an OpenCollective collective

✅ What Got Done

  • oc-opsdevnz standardised — docs scaffold (specs, design, stories, coverage), Zensical config, AGENTS.md, CI/CD workflows (test.yml with Python matrix, publish.yml for Trusted Publishing, sast.yml with bandit + pip-audit), dependabot.yml. PR merged: tests passing, clean Zensical build.
  • Template repo backported — practice-template-opsdevnz now has full LICENSE (Apache 2.0), CODE_OF_CONDUCT, CODEOWNERS, CONTRIBUTING, RELEASING, AGENTS.md, zensical.toml, docs/ scaffold, sast.yml, pytest-cov. Mounted as submodule in outcome-engineering monorepo.
  • Collective onboarding criteria drafted — six criteria (strategic fit + operational readiness) in docs/governance/collectives/. MR merged.
  • Module template structure updated in modules/README.md to include all standard files.
  • MCP discovery — found modelcontextprotocol/python-sdk and an existing OpenCollective MCP server. Noted in docs/discovery/agents/.
  • Coverage baseline — oc-opsdevnz at 73% (13 tests, 420 statements). Report at docs/specs/coverage.md.
  • Fedora dev env — installed 1password-cli on opsdev-sandbox-fedora-dev0 for OC_SECRET_REF token resolution.

🧠 Notes & Reflections

The template is converging. oc-opsdevnz and practice-template-opsdevnz now agree on structure: AGENTS.md, zensical.toml, docs/, CI/CD workflows, governance files. The next module created from the template will come out with the full skeleton.

The open source licensing criterion for collective onboarding needed nuance: infra code is Apache 2.0, product code is the collective's choice. JJobs taught us that IP clarity matters more than license choice.

Someone already built an OpenCollective MCP server. It wraps the same GraphQL API we use. Could be a reference for an MCP layer on top of oc-opsdevnz, or a replacement if it covers our needs. Worth evaluating before we build too much.

⏳ Mañana

  • Authenticate op CLI and set OC_SECRET_REF
  • Test oc-opsdevnz whoami against staging OpenCollective
  • Create OpsDev.nz collective on staging via: oc-opsdevnz collectives --staging --file ../startmeup.nz/opencollective/staging-collectives.yaml
  • Review and update prod OC config in public/startmeup.nz/opencollective/ (prod-host.yaml, prod-projects.yaml — needs prod collective config)
  • Begin process of moving from staging to production OC setup
  • Commit and push template repo changes to GitHub

🔥 Token Burn

Deep Seek V4 Pro

175k tokens

$0.78 spent