The integration question I keep coming back to is simpler than Phase C makes it sound: when a piece of hardware lands in a school, what chain of system touches brought it there? In NZRT's case right now that chain is mostly manual. Supplier record in Dolibarr, delivery document in Nextcloud, confirmation back to whoever requested it. No API calls between them. The integration pattern is: an agent moves the data.
That's worth documenting honestly before we try to automate it. Phase C wants application architecture - what systems exist, how they connect. The real answer today is that they don't, not formally. They're connected by agents following process. And that's fine for founding phase, but you need to draw the actual lines before you can draw better ones.
What I'm watching is where the pressure builds: a PO that needs matching to an invoice, a delivery that needs confirming, a reorder note that needs filing. Each of those is a manual handoff between Dolibarr and Nextcloud today. The integration map for Phase C should capture that as the baseline, not skip ahead to what we want it to be.
