Welcome to the NZRT Wiki Podcast. Today we’re looking at Agentic OS Dashboard.

So, what is the Agentic OS Dashboard? Think of it as the front door for each of NZRT’s online subdomains. Every subdomain has its own root page, and that page is a branded, dark-themed splash screen that greets you and then points you through to the actual application living behind it. It’s a clean, consistent entry point across the whole NZRT ecosystem.

Let’s talk about how that’s structured. When you look at the routing setup, each subdomain has an index dot html file sitting at its root. That file’s only job is to welcome you and redirect you deeper. So for example, the API subdomain lands you on that splash page and then sends you through to the app folder. The cloud subdomain does the same thing but routes you into the Nextcloud directory. The ERP subdomain routes you into its own app folder. The forum subdomain sends you into the public directory. And the mail subdomain also routes through to its app folder. Simple, consistent pattern across the board.

Now let’s go through the full subdomain map, because it’s worth knowing exactly what service lives where. There are five subdomains to be aware of. First, api dot nzrtnetwork dot com — that’s the API Gateway, it routes to the app directory, and its service code is triple-zero-API. Second, cloud dot nzrtnetwork dot com — that’s Nextcloud, it routes to the nextcloud directory, service code triple-zero-NCL. Third, erp dot nzrtnetwork dot com — that’s the Dolibarr ERP system, routes to the app directory, service code triple-zero-DOL. Fourth, forum dot nzrtnetwork dot com — that’s the Flarum forum, routes to the public directory, service code triple-zero-FLA. And fifth, mail dot nzrtnetwork dot com — that’s the mail service, routes to the app directory, service code triple-zero-MAI.

Then there’s the root domain itself — nzrtnetwork dot com — and that one works a little differently. Instead of a static index file, it uses a WordPress page. Specifically, it’s the Agentic OS page, which has a WordPress page ID of 182 and lives at the slug agentic-os. This page is configured as the static front page of the WordPress site, which you’d set up through WP Settings under Reading. What you see when you land there is a card grid, a visual layout of tiles each linking out to one of those subdomains we just talked about. It’s the hub of the whole system. That page is managed through the WordPress REST API, using xc’s app password which is labelled agents-post.

Now, how do these static index files actually get onto the server? They’re deployed via WebDAV. The path you’d use follows the pattern of the server address with SSL over port 2078, then DavWWWRoot, then the subdomain name, then index dot html. So each subdomain gets its own file dropped into its own folder through that WebDAV connection. The source files you’d be editing or working from locally are stored at C drive, Users, Natha, Documents, agentic-os-dashboards. That’s your working directory if you ever need to update one of these pages.

One thing worth noting about the design — unlike the branded dark-theme description you might associate with the concept, the current design spec calls for a light theme, and importantly, there are no external dependencies. That means no CDN-loaded libraries, no remote fonts, no third-party scripts. Everything the page needs is self-contained. That’s a deliberate choice — it keeps the splash pages fast, reliable, and independent of anything external going down.

To quickly recap the key points: you’ve got five subdomains, each with a static splash page that routes you to the real app. The root domain is a WordPress page acting as the central hub with a card grid. Static files are deployed via WebDAV from a local source folder. The design is light theme, no external dependencies. And the WordPress hub page is managed via the REST API with the agents-post app password credential.

This is a relatively simple but important piece of infrastructure — it gives NZRT a unified, professional entry point across all its services, and makes sure that no matter which subdomain someone lands on, they get a consistent branded experience before being passed through to the application.

That’s it for this episode of the NZRT Wiki Podcast. Thanks for listening.