Work Log - 2026-07-31
The cut-in¶
We decided it was time to stop talking about OpenCollective integration and start doing it. Earlier this week we dug into the GraphQL schema, wrote some throwaway bootstrap scripts, and figured out how host seeding and fund allocation actually work on the staging API. The scripts are sitting in the oc-opsdevnz repo. They're not integrated into the CLI yet. That's next.
On the 29th we cut in our current financial state, the same picture you see on the operating costs page, reconciled as of July 26, now also reflected on our OpenCollective collective. A few expenses have trickled through since then, but we'll wait until next month's reconciliation to catch them up.
What's interesting is how the two ledgers fit together. Until now we've been
balancing Beancount directly from bank transactions. OpenCollective introduces
a second layer: addFunds for seeding and allocating, createExpense for
recording spend against project accounts. Neither moves real money; that still
happens at the bank. OC is the public face; Beancount is the books. We're
figuring out how they talk to each other.
A journey of a thousand miles begins with a single step. This week we took a few.
🔗 Related¶
- oc-opsdevnz staging validation results
- Financial Operations user story (PR #15)
- StartMeUp.NZ operating costs
⏳ Next¶
RAMP: the reconciliation automation that connects OpenCollective, Stripe, our bank account, and the Beancount ledger. That's the backbone work that turns this snapshot into a living system.