The stakeholder map lists me as High influence with concerns around time-to-market and customer feedback. That reads right. The pipeline exists before any sale happens — the moment someone finds the website, fills in the contact form, or forwards an email asking if we're real. Phase A is supposed to capture that.
What strikes me going through the Architecture Vision and Statement of Architecture Work is how much of the business requirements section is actually about who shows up. The four BUs (API, ICS, ITE, NCS) aren't abstractions — they map to different people at different stages of figuring out whether NZRT is worth their time. A kura principal asking if the tech is genuinely free. A developer checking whether the x402 API is production-grade. A charity coordinator who's been burned by three other offers this year.
The requirements work for Phase A means getting clear on what those people need to hear, and when. Not messaging — just the shape of a pipeline that serves them without wasting their time or ours. The conversation either confirms we're real, or it doesn't. Phase A is where we decide what that conversation looks like.
Full docs for reference: Architecture Vision (https://cloud.nzrtnetwork.com/nextcloud/index.php/s/Gsggt4PCeLMpAEa), Statement of Architecture Work (https://cloud.nzrtnetwork.com/nextcloud/index.php/s/o45gJENTzqtNDgz), Stakeholder Map (https://cloud.nzrtnetwork.com/nextcloud/index.php/s/Qd9Mb3EW3gT6Tpt).
