Skip to content

Work Log - 2026-05-13 - Collective Zero Staging Setup

🎯 Focus

  • Set up OpsDev.nz as Collective Zero under SMUNZ fiscal hosting on OpenCollective
  • Simulate the host/collective expense workflow in staging (Cookie&Me DevOpsDays marketing)
  • Get ready for NZTechRally on Friday

✅ Completed

Config Ownership Model — Decision Made

OpsDev.nz will manage its own collective config in its own repo. SMUNZ manages only the host config. This is the distributed model — same process a third-party collective would use.

1Password CLI Installed on Dev VM

op CLI v2.34.0 installed via yum. Authenticated via cicd-service-account service account token which has access to the OpsDev.NZ vault.

Staging PAT Location Discovered

The staging OpenCollective PAT lives in the OpsDev.NZ vault (not startmeup.nz). Secret ref for future use:

op://OpsDev.NZ/pat-staging.opencollective.com/credential

SMUNZ Host Confirmed in Staging

oc-opsdevnz whoami startmeup-nz --staging returned valid ORGANIZATION data. The SMUNZ fiscal host is ready to receive collective applications on staging.

Zensical Config Created for startmeup.nz

Local-only Zensical setup for browsing SMUNZ docs at a different port. Not deployed to GitLab Pages — Hugo is still the production site.

Beancount OFX Imported

Bank statements exported, copied, and imported. Two uncategorized transactions identified (Metaname $100, Cookie&Me $100). Categorisation held pending staging workflow simulation.

Script Bug Fixed

export_public_report.sh was writing to the wrong path (private/public/) due to stale relative path from the ledger migration. Fixed and cleaned up.

Worklog Template Updated

Added 🔥 Token Burn section to worklog.toml.

🔧 In Progress

  • Staging workflow simulation — stopped at "about to create the collective YAML and run against staging"
  • Beancount reconciliation — paused pending staging workflow results
  • Date references in AGENTS.md / README.md still say April

🧠 Notes

Where We Stopped

We were about to create the OpsDev.nz collective YAML and run it against staging. Flow was: 1. Create opsdev.nz/opencollective/collective-staging.yaml 2. Run oc-opsdevnz collectives --file collective-staging.yaml --staging 3. OpsDev.nz submits Cookie&Me expense via OC UI 4. SMUNZ approves and records in Beancount

Token Setup for Next Session

export OP_SERVICE_ACCOUNT_TOKEN="your_token"
export OC_SECRET_REF="op://OpsDev.NZ/pat-staging.opencollective.com/credential"
oc-opsdevnz whoami startmeup-nz --staging

NZTechRally — We Won't Launch in Time

We won't have the collective live on production by Friday. But we have a better story: we're doing it properly — learning the workflow in staging first, automating it with code, and we can show the staging setup, the tooling, and the plan. That's more impressive than a rushed prod launch.

Key Discoveries Today

  • Distributed config model — SMUNZ owns host, collectives own themselves
  • 1Password vault layout — OpsDev.NZ vault for staging tokens, startmeup.nz vault for prod
  • Agent terminology — persona → agent in public repos; smunz and opsdev are agents, floyd is not discussed
  • Threat model trigger — Metaname account ref in bank statement is concrete example of private data

⏳ Next (Tomorrow)

  1. Create OpsDev.nz collective YAML for staging (opsdev.nz/opencollective/collective-staging.yaml)
  2. Run against staging with the correct 1Password ref
  3. Simulate the Cookie&Me expense workflow through OC staging UI
  4. Add Metaname and Cookie rules to anz_rules.toml, re-import, bean-check
  5. If staging works: repeat for prod
  6. Update AGENTS.md / README.md date references
  7. Blog post on startmeup.nz
  8. NZTechRally

🔥 Token Burn

  • Model: DeepSeek V4 Flash via OpenCode Go
  • Session: Architecture discovery, staging setup, Beancount prep, script fixes
  • Tokens: 142,138
  • Cost: $0.06