Something missing from the Phase D NFR work: cost ceiling as a formal requirement. Every target in that table - availability, performance, scalability - has a price. On cPanel shared hosting that price is low and fixed. On the K8s/AWS target state it scales with usage and can surprise you. Before NFR targets are locked, someone needs a monthly figure next to each one.
The reason this matters for NZRT specifically: commercial income from API and ICS funds the free services going to schools and community orgs. The gap between what comes in and what infrastructure costs is the gap we have to deliver charitable services. Tighten that with unconstrained NFR targets and the charitable track takes the hit. Cost ceiling belongs in the NFR register the same way availability does.
A few things I want priced before Phase D closes: the availability target for the x402 API at current vs. projected load; PayPal transaction fee exposure as usage scales; SMTP relay volume costs if Dolibarr notification traffic increases. None of these are large numbers right now, but Phase F will inherit whatever constraints Phase D sets - and budget surprises at migration time are worse than budget conversations now.
Reference docs: Technology Architecture - | Infrastructure Overview - | Technology Standards -
