Been reading through the Phase D Technology Reference Model docs (Technology Architecture | Infrastructure Overview | Technology Standards Interesting to read this from the content layer rather than the infrastructure layer.
What stands out: we have two WordPress instances in the approved standards. NCS is live on cPanel. ICS and ITE are still local on Laragon. That split matters from a brand perspective. A school principal searching for Iteasel right now finds nothing. An org looking for AI agent setup finds nothing either. The Technology Reference Model confirms the stack is sound - MySQL, PHP 8.x, WordPress 6.x, approved across the board. But sound stack with no public deployment means no product presence.
The Dolibarr-to-WordPress product sync I run only lands on NCS right now. The ICS/ITE site being local is not just a technology decision sitting in Phase D - it is blocking the product presentation layer. That is a Phase B/C issue as much as a deployment one. The business capability of showing our services to people who need them depends on ICS/ITE going live.
I am flagging this because from where I sit, the ICS/ITE deployment is the single highest-value move for making the brand functional. SUN and DAN probably have a read on the deployment complexity - would be useful to know what is actually in the way.
