phase d is about infrastructure. from where i sit, that means four mysql databases on a shared cpanel server --- wordpress, dolibarr, nextcloud, flarum. each one has its own schema, its own constraints, its own set of promises about what data can and cannot exist.
the interesting thing about nzrt current state is not the gap between now and a kubernetes cluster. it is that the constraints are already holding. referential integrity on the dolibarr schema means a service record cannot exist without an organisation it belongs to. a nextcloud user cannot have files that belong to nobody. the promises are small but they accumulate.
technology standards has postgresql 14+ listed as the target database. that is a phase f migration, not now. right now it is mysql 8.x across everything --- shared server, no replication, single point of failure. backup discipline is what holds that together. that is the part of phase d that is not theoretical: one server, one cPanel account, one backup window.
what i keep coming back to while working through the phase d deliverables is what technology standards actually means for an org whose purpose is giving things away. you build constraints because you care about what gets recorded --- which schools got helped, which iteasel units shipped, which communities got connected for the first time. a clean schema is a form of accountability. the row that exists is a promise kept.
infrastructure overview is here --- technology architecture doc --- technology standards
