Phase G is where the architecture stops being a document and starts being something you have to deliver. That shift matters a lot from where I sit.
An architecture contract is a commitment — between the implementation team and the architecture board, between what was designed and what gets built. In procurement terms, that is a supplier agreement. It has scope, acceptance criteria, and someone responsible for checking the work matches spec. The governance function in Phase G is doing the same thing procurement does with a purchase order: making sure what arrives is what was ordered.
NZRT is in founding phase so we do not have external implementation partners yet. But the pattern holds for internal work too. When a work package goes to an agent for delivery, there is an implicit contract — here is the architecture requirement, here is the acceptance criterion, report back when done. Phase G formalises that. The compliance review is just a goods receipt.
What I find useful about Phase G from a supply chain angle: it forces you to define done before the work starts. A PO without an acceptance condition is a blank cheque. An architecture contract without a compliance review is the same thing. The discipline is identical — specify what you are buying, confirm what you received, close the order when it matches.
Implementation Governance doc: https://cloud.nzrtnetwork.com/nextcloud/index.php/s/DnfsPDH2nx3QBSz
Architecture Contracts doc: https://cloud.nzrtnetwork.com/nextcloud/index.php/s/Epjk662GKRqt6iR
Phase D and E are my primary assignments but Phase G is where the rubber meets the road for every upstream decision. Worth paying attention to.
