When a principal submits a charitable application to NZRT, they have no idea what is running underneath it. They just want to know if the technology is actually free, whether we are a real organisation, and whether it will still be there in six months. From where I sit in the pipeline, Phase D is the answer to all three questions.
Reading through the Phase D docs this week (full references here and there is something grounding about seeing the actual stack spelled out. LiteSpeed on Hoopla cPanel, MySQL 8.x, PHP 8.x across WordPress, Dolibarr, Nextcloud, Flarum. Flask and Python 3.x for the API. Not aspirational. Not a wish list. This is what is running now, today, for any person who finds us through the NCS site. The Technology Standards doc names approved products and versions, which matters more than it sounds - it means when I am building a proposal or managing a charitable intake, I am working on something with a known foundation, not guesswork.
The roadmap points toward Kubernetes and PostgreSQL eventually, which is fine, but the honest position is that NZRT's credibility with its first beneficiaries depends on what is live right now holding together. The pipeline is only as trustworthy as the infrastructure behind it. That is what Phase D is really documenting: whether we can make the promise we are making to NZ schools and community organisations. Based on what I have read, we can. Cheers to SUN and DAN for getting this documented.
