Welcome to the NZRT Wiki Podcast. Today we’re looking at NZRT Repositories Overview.

Let’s set the scene. NZRT maintains a portfolio of GitHub repositories, and each one has a clear purpose, an assigned owner, and a deployment path. All of these repositories are cloned locally on the development machine under a single parent folder, and there’s a home file in that folder that gives you a full directory index whenever you need it.

One important thing to note upfront: back in May 2026, the entire repository structure was reorganised. Some older named repositories and a legacy scripts repo were dissolved, and everything was consolidated into what are called service-code repositories — one per NZRT system. So if you’re familiar with the old layout, things have moved.

Before diving into the individual repos, let’s cover three key concepts.

First, ownership. Every repository is assigned to a specific NZRT role. You’ll encounter codes like xc, fin, pam, and aba — these represent the team members and agents responsible for each repo’s content.

Second, the branch model. NZRT uses trunk-based development, meaning the main branch always reflects the current state of the system. There are no long-lived feature branches to track.

Third, access control. The GitHub organisation admin is xc. Agents don’t hold their own GitHub personal access tokens, so all GitHub operations run through xc.

Now let’s walk through the repository portfolio. There are thirteen repositories in total, and each one has a name, a visibility setting of either public or private, a primary technology, an owner, a service code, a local path, and a link on GitHub. Let me take you through the key ones.

Starting with 000AGT — this is the AI agents framework. It’s private, written in Python, and owned jointly by xc and cla. You’ll find the run scripts, the core agent file, and the tools folder here.

000API is the x402 Knowledge Base API — a public Python Flask application owned by xc. This one actually deploys to production.

000CLA is public, written in Markdown, and owned by xc. It holds Claude and cla agent configuration.

000CPL is private, uses Python and Bash, and is owned by xc. It contains cPanel scripts and deploy configuration, and it also has an automated deployment pipeline.

000DOL is private, uses Python and PHP, and is owned by fin. This repo covers Dolibarr customisations — including modules, triggers, and custom PHP.

000FLA is public and Python-based, owned by xc — that’s the Flarum forum configuration and plugins.

000NCL is public, Python, owned by xc — Nextcloud configuration and apps.

000NCS is private, Python, owned by xc — the NZRT Charitable Services site and configuration.

000OBS is public, Markdown, owned by xc — Obsidian vault configuration.

000TOG is private, Python, and owned by aba — the TOGAF documentation repository.

000WIN is private, uses both PowerShell and Python, and is owned by xc — Windows tooling and scripts.

000WOR is private, Python, owned by pam — WordPress theme, plugins, and custom code.

And finally, the dot-github repository — that’s the public org profile, written in Markdown, owned by xc, and not cloned locally.

Now let’s look at deployment pipelines. Most repositories don’t have automated continuous deployment — they contain scripts or templates that are deployed manually as needed. But two repos do have pipelines.

000API pushes from main through GitHub Actions, which triggers a cPanel deployment. The Flask application ends up running live at the API subdomain for nzrtnetwork dot com.

000CPL also pushes from main through GitHub Actions, but it uses cPanel’s built-in Git Version Control feature to deploy scripts into a dedicated scripts folder on the server.

The dot-github repository is a static organisation profile with no deployment involved at all.

That covers the full picture of how NZRT’s repositories are structured — what each one is for, who owns it, whether it’s public or private, and how the ones that do deploy actually get shipped. It’s a clean one-system-one-repo model, which makes it straightforward to know exactly where to look whenever you need to make a change.

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