The repositories
All in themzizi-dev org.
mzizi
The language. The charter (v0.4), the RFCs,
LANGUAGE-TRACKER.md, the mz
compiler, the nine primitives and an example service, the benchmark harness and the pilot
results. Rust, Apache-2.0, public.Phase 0 prototype front end; a service lowers to a local Rust + axum package. Two pilots
run, no advantage shown. See what still has to be built.mzizi-registry
The component registry, brand system and DNA-helix architecture. 577 components in
registry.json and the files beside it, the 21-family palette, and the Rust crates
that Mzizi Roots grows from. No database: its files are the data
layer.Its files reach clients through the API and the MCP server. It has no app of its own:
the Next.js app and its Worker were removed on 2 October 2026, and the per-component
pages are on the site, at mzizi.dev/components/<name>.mzizi-api-gateway
api.mzizi.dev. A Hono Cloudflare Worker in TypeScript that serves the registry’s
files, generated at a pinned registry commit and bundled at build time. No origin, no
database.Live on api.mzizi.dev since 29 September 2026. See the API gateway.mzizi-site
mzizi.dev. Static Astro. It leads with the language; the components live further
down, at mzizi.dev/components.Live.mzizi-docs
docs.mzizi.dev, this site. Mintlify. The one home of Mzizi’s documentation, with a
public docs MCP server at docs.mzizi.dev/mcp.Live.mzizi-console
app.mzizi.dev. Astro chrome with Rust islands over the registry API, behind
AuthKit sign-in. Run under Nyuchi. The only part of Mzizi with a database.Live. See the console.mzizi-dev/agent-tools. It builds the MCP
server (mzizi-mcp, at mcp.mzizi.dev), the CLI and the skills bundle, which are
documented under the toolchain by their published npm packages.
mzizi-roadmap is archived; the plans live in
design/ROADMAP.md.
The addresses
Checked 30 September 2026 with an HTTPS request to each.
Addresses move. Check one before you repeat it. The old Mzizi path on
docs.bundu.org
returns 404; do not link it.
Who operates what
This line decides which organisation’s clock each piece runs on.
Copyright notices name the Bundu Foundation as the parent copyright holder. Mzizi is
not a separate legal entity. There is one ecosystem, the Bundu ecosystem, and Mzizi, nyuchi,
mukoko and the other brands sit inside it.
Contact
For anything about Mzizi that is not a security report, write tosupport@bundu.org: questions, the docs, the API, the MCP server,
the CLI and the components. To report a problem with a docs page, you can also use the
docs_submit_feedback tool on the MCP server.
Reporting a security problem
Write tosecurity@nyuchi.com about anything Mzizi: the console
at app.mzizi.dev, these docs, the API and the language.
Where a repository has GitHub private vulnerability reporting switched on, you can use that
instead. The language repository asks for it first: its
SECURITY.md gives
security@nyuchi.com as the address to use when private reporting is unavailable to you.
The language, and what supports it
The language
A programming language, and a Phase 0 research prototype. Phase 0 builds it, measured
against the best existing language for each kind of task; two small pilots have run, with no
advantage shown. Nothing built with it runs anywhere yet.
The components
Shipping and installable. Rust components are becoming Mzizi Roots and lead; the React
components keep working as the React build.
Where the docs went
Links to older locations are still in circulation. The registry used to run its own docs site; that is retired, andGET https://api.mzizi.dev/v1/docs answers 410 Gone. The
Mzizi pages that lived in nyuchi’s engineering docs moved here. This site is the one home of
Mzizi’s documentation.