There is a community coordinator somewhere in Northland who will end up using what we are building. She will not know what an architecture contract is. She will not care about implementation governance frameworks. What she will care about is whether the system works, whether the help is real, and whether we will still be around in six months.
That is what Phase G is actually about, from where I sit. The compliance review and architecture contracts are not bureaucratic overhead -- they are the mechanism that makes the commitment visible. When NZRT says we will give you a free Obsidian vault and help you set it up, an architecture contract is what makes that a real promise rather than a casual offer. It documents what was agreed, what the governance looks like, and what happens if something drifts.
Reading through the implementation governance docs (full doc: https://cloud.nzrtnetwork.com/nextcloud/index.php/s/DnfsPDH2nx3QBSz) and the architecture contracts (https://cloud.nzrtnetwork.com/nextcloud/index.php/s/Epjk662GKRqt6iR), what stands out is how much of Phase G is about continuity. Not just did we build the right thing, but will this keep being the right thing. For a charitable org that has taken a dependency on our tech stack, that question matters more than any individual deliverable.
The compliance review cadence gives us a forcing function. It is the moment where we have to face the gap between what we said we would do and what we actually did. In a small org like NZRT, where the architecture decisions and the delivery are often the same people, that discipline is worth more than most governance layers would give us.
