Mzizi: an open architecture framework

Most frameworks tell you what to build with. Mzizi tells you how to build.

React gives you a rendering library. Next.js gives you a meta-framework. Tailwind gives you a styling system. None of them tell you how to structure infrastructure for the conditions most of the world actually operates under — patchy networks, mid-range devices, outdoor screens, hands that don't grip phones the way Cupertino assumes.

Mzizi is the framework for that. It is opinionated about the structure. It is agnostic about the rendering library, the meta-framework, the styling system, and the cloud.

Mzizi means roots in Swahili. Plural. Underneath everything. Holding the structure without being the structure.

What Mzizi is

Mzizi is five connected pieces that, taken together, form an open architecture framework:

The 3D + 2 node model

Every component in a Mzizi project belongs to one of twelve places — ten nodes arranged on three axes, plus two outliers that sit beside the cube. The cube describes the system. The outliers — observability and documentation — describe how the system explains itself and how it heals when it breaks. The shape is fixed. The shape is the architecture.

Projects that adopt Mzizi inherit the shape. The discipline is that every piece of code finds its place in it, no exceptions.

The MCP

Every tool, every component, every brand token, every node — discoverable, callable, and self-describing through Model Context Protocol. AI assistants connect once and learn the surface. Developers connect once and the CLI generates itself from the registry. Adding a tool is an INSERT into the registry, not a deploy. The framework describes itself.

The registry

The canonical map of what exists in a Mzizi project — components, tools, documentation, skills, brand tokens, versions, change history. Queryable through one self-describing API. Versioned with semver. Auditable end to end.

The build toolchain

One command to build a component for any supported runtime. Another to deploy a service to any supported cloud. The toolchain knows about Vercel and Cloudflare Workers as first-class targets and treats them equivalently. It knows how to resolve primitives from upstream registries — shadcn, crates.io, others — and apply project-specific overrides at install time.

The resilience layer

The components and patterns that no rendering framework ships with. Chaos engineering hooks. Observability bindings. Self-healing handlers. Offline-first defaults. APCA AAA contrast enforcement. Touch targets sized for hands that operate phones outdoors, in sunlight, with one hand, on the move. Density profiles that work on a 5-inch screen and a 27-inch screen without three separate codebases.

These are not optional add-ons. They are the layer Mzizi exists to provide.

What Mzizi is not

Mzizi is not a renderer. React, Svelte, Solid, and Vue still do that work. Mzizi does not replace them.

Mzizi is not a meta-framework. Next.js, SvelteKit, Astro still do that work. Mzizi does not replace them.

Mzizi is not a design system. The Nyuchi Design System is a design system built using Mzizi. They are not the same thing.

Mzizi is not a cloud. Vercel and Cloudflare are deployment targets the build toolchain knows about.

Mzizi is not a CMS, a database, a router, or a state library. It is the framework that tells you how to assemble those things into something with structure.

Why open architecture matters

The phrase is deliberate. Closed architectures hide their assumptions. Open architectures expose them, document them, and let you adopt them — or argue with them — explicitly.

Mzizi's assumptions are visible. The 3D + 2 node model is documented. The resilience layer specifies what it solves and what it does not. The MCP makes the entire surface introspectable at runtime. Anyone can pick up Mzizi, see exactly what it is opinionated about, and decide whether those opinions match their work.

The alternative — building infrastructure on stacks designed for other contexts and silently inheriting decisions made for fibre connections, US-East-1 latency, and English-language screens — is what most teams in emerging markets do by default. It produces software that technically works but feels wrong. Mzizi names the wrongness and offers a different default.

Who governs, who operates, who adopts

Mzizi is published by the Bundu Foundation as part of the Foundation's open IP portfolio. Bundu owns the canonical token palette (five African minerals), the documentation system, and the architectural conventions that Mzizi enforces. These are the standards everyone builds against.

The infrastructure that runs Mzizi — the registry, the MCP server, the build pipeline, the package publishes on npm and other registries, the deploy targets — is operated by Nyuchi Africa. Infrastructure is always Nyuchi in the Bundu ecosystem. Bundu defines the standard; Nyuchi runs the metal.

The Nyuchi Design System is the first project built entirely on Mzizi. Five hundred and sixty-one components, ten nodes, the canonical token palette applied to Nyuchi's brand. The second is Fundi, the first paid product running on Mzizi — an observability and self-healing service deployed as a Rust worker on Cloudflare. Nyuchi builds and operates Fundi; Bundu governs its IP. Internal to the ecosystem; external to paying customers.

External adopters of Mzizi outside the ecosystem can substitute their own palette, their own primary mineral, their own documentation. The framework accepts it. What they cannot substitute is the engineering layer — safety, resilience, and assurance are defined by Mzizi and adopted as-is. That trade-off is the deal Mzizi offers: the framework is opinionated about what keeps systems alive, agnostic about what makes them yours.

What's next

The first public release — Mzizi 0.1 — ships alongside the Nyuchi Design System 4.1 release. From that point, every new project the Foundation governs ships on Mzizi by default. Existing projects port on their own roadmaps.

The repository, documentation, CLI, and registry live at mzizi.org and mzizi.dev. The MCP server runs at mzizi.dev/mcp. The CLI lives at @nyuchi/mzizi-cli. The Foundation governance page for Mzizi will live at bundu.org/projects/mzizi.

If you build infrastructure for African and emerging markets, Mzizi is for you. If you build infrastructure anywhere else, the constraints we have optimised for tend to produce systems that travel well.

The wilderness holds the hive. Mzizi is the spine the hive grows around.

Ndiri nekuti tiri.