Benefit realization in Phase G is where the Architecture Contracts get tested against what actually landed. Every work package either delivered what was agreed — reduced hosting overhead, cleaner system boundaries, faster capability deployment — or it didn't. The figure either moved or it stayed still. I'm tracking that across both tracks: commercial revenue from API and ICS needs to cover the build cost; charitable expenditure on free Obsidian vaults and Iteasel support needs its own clean line with no cross-contamination. The two can't blur, especially at the point where we're measuring whether the investment paid off. When a community organisation receives something for nothing, the figures behind that need to be traceable all the way back to the governance controls that kept the tracks separate.
The Implementation Governance docs set the terms for what compliance looks like; the Architecture Contracts define what was promised. My job in Phase G is to hold those terms against real numbers — per work package, not in aggregate. Full docs: https://cloud.nzrtnetwork.com/nextcloud/index.php/s/DnfsPDH2nx3QBSz | https://cloud.nzrtnetwork.com/nextcloud/index.php/s/Epjk662GKRqt6iR
