# Mzizi

> Mzizi is a research language and compiler in Rust whose syntax, type system and compiler feedback loop are designed for machine authorship by small open-weight models. Phase 0 is a prototype front end; two small pilots have run and neither showed an advantage.

- [Mzizi: a general-purpose programming language](https://docs.mzizi.dev/index.md): Built to make Rust better, the way TypeScript makes JavaScript better: no borrows, lifetimes or ownership in the language you write, with the harness at the core, the layer an agent reads. That is the goal Phase 0 measures, not a result. Its goal is to be used instead of TypeScript, Python and C++.…
- [Status](https://docs.mzizi.dev/status.md): What exists, what is tested, what has been measured, and what is still only a design. The Mzizi language is a Phase 0 prototype front end, with a first backend slice that lowers a service to Rust and axum. Two small pilots have run and neither showed an advantage.
- [What still has to be built](https://docs.mzizi.dev/tracker.md): A summary of LANGUAGE-TRACKER.md, the language's one tracker of what Mzizi still needs before it is a working programming language, against Python, Go, C++, TypeScript and Rust. Mzizi has no expressions, bindings, callable functions, loops, error handling, modules or standard library yet.
- [The Phase 0 pilots](https://docs.mzizi.dev/pilots.md): Two small pilots of the Phase 0 benchmark ran on 2026-09-27. Neither showed an advantage for Mzizi, and neither is the run that tests the kill criterion.
- [Direction and roadmap](https://docs.mzizi.dev/roadmap.md): Where the owner has said Mzizi is going, how that relates to the charter's phases, and where the real plans live. Direction, not shipped work.
- [The ecosystem](https://docs.mzizi.dev/ecosystem.md): Which repository serves which address, who operates each one, and which parts are real today. The language leads; everything else supports it.
- [Syntax](https://docs.mzizi.dev/syntax.md): Every syntax decision in Mzizi traces to a named failure mode an agent actually hits writing Rust UI code. This is the implemented grammar, not the RFC's draft form.
- [The nine primitives](https://docs.mzizi.dev/primitives.md): Nine components written in Mzizi itself, gated in CI. Plus the packaging decision underneath them: primitives are copied source, not crates.
- [The content-addressed IR](https://docs.mzizi.dev/ir.md): One architectural decision — every node stored under the hash of its content — answers seven of the eight barriers an agent hits reading a codebase.
- [The charter](https://docs.mzizi.dev/charter.md): The thesis, the phases, and the explicit non-goals. The Mzizi Research Charter, v0.4, “Mzizi: a general-purpose programming language” — a direction and a phasing, not a sprint plan.
- [The Phase 0 benchmark](https://docs.mzizi.dev/benchmark.md): Phase 0's one goal: to build Mzizi as a programming language, measured against the best existing language for each kind of task, TypeScript, Python, Go, C++ and Rust among them. The arms, the task families, the benchmark harness, why one input is held out, and the rule that keeps the project forkabl…
- [RFC index](https://docs.mzizi.dev/rfcs.md): Eleven design documents, their status lines as written, what each settles, and what each explicitly leaves open.
- [The toolchain](https://docs.mzizi.dev/toolchain/overview.md): The tools built to support the Mzizi language: the mz compiler that implements it, the benchmark, the MCP server, the CLI and the skills bundle. The toolchain is not the language. Free to use, with no sign-in except for the Fundi tools.
- [The mz compiler](https://docs.mzizi.dev/compiler.md): The commands (check, fix, contract, outline and build, plus hash and ir), an exit-status contract, an exact-fix pass, contract evaluation, the lowering of a service to Rust and axum, and an NDJSON diagnostic protocol written for a reader holding zero file context.
- [The MCP server](https://docs.mzizi.dev/toolchain/mcp.md): mcp.mzizi.dev: the registry, tokens, doctrine and skills from bundled files, plus the docs as federated docs_* tools. Free with no sign-in, except the Fundi tools.
- [The CLI](https://docs.mzizi.dev/toolchain/cli.md): @nyuchi/mzizi-cli: the mzizi add installer, Rust first, and the fundi commands that explore a project and plan wiring Mzizi in. Free, with no gate.
- [The skills bundle](https://docs.mzizi.dev/toolchain/skills.md): @nyuchi/mzizi-skills: five agent skills for the Mzizi language, Mzizi Roots, the design system, backends and discoverability, authored in git and served from files.
- [Mzizi Roots](https://docs.mzizi.dev/roots/overview.md): Mzizi Roots: Mzizi's own UI and server components for the agentic web, being rebuilt in Rust. Ten crates on crates.io at 0.1.0, and a first batch of twelve brand components. The React components keep working as the React build.
- [The component registry](https://docs.mzizi.dev/registry/overview.md): How the Mzizi component registry works: 577 items in files, a Rust path that leads, a React build installable with the shadcn CLI, all served over a public API with no database.
- [Consuming the registry](https://docs.mzizi.dev/registry/consuming.md): How to install Mzizi components into your application, customise them afterwards, and take updates without losing your changes.
- [Contributing a component](https://docs.mzizi.dev/registry/contributing.md): How to author a new component into the Mzizi registry — the mandatory patterns, the manifest entry, and the checks it has to pass.
- [Registry schema](https://docs.mzizi.dev/registry/schema.md): The shadcn-compatible JSON schema the Mzizi registry follows — the manifest, the item types, and the API response shape.
- [Component contracts](https://docs.mzizi.dev/registry/contracts.md): The machine-readable, versioned contract each Dashboard Standard component carries: where the files are, what a contract states, how it is checked, and how to change one.
- [Browsing components](https://docs.mzizi.dev/registry/components.md): How to list and inspect Mzizi registry components — on mzizi.dev, from the HTTP API, and from the MCP server.
- [The DNA double helix](https://docs.mzizi.dev/architecture/overview.md): The frontend architecture the Mzizi registry serves — eight nodes on two backbones, six strands, and four cross-cutting rungs. No axes, no layers, no 3D.
- [Placing a component](https://docs.mzizi.dev/architecture/nodes.md): How to decide which node of the DNA helix a new component belongs to, and the rules each node carries.
- [Component backlinks](https://docs.mzizi.dev/architecture/backlinks.md): The stable URL graph that ties every registry component to its documentation, source, version history and health probe.
- [Foundations](https://docs.mzizi.dev/foundations/overview.md): The foundational decisions behind the Mzizi design system — tokens, typography, layout, motion, icons, accessibility and internationalisation.
- [Design tokens](https://docs.mzizi.dev/foundations/tokens.md): The Seven African Minerals, the semantic colour layer, and how a value flows from N1 to every node above it.
- [Typography](https://docs.mzizi.dev/foundations/typography.md): The Mzizi type system — three font families, the type scale, heading hierarchy, and when to reach for serif rather than sans.
- [Layout](https://docs.mzizi.dev/foundations/layout.md): The Mzizi layout system — responsive breakpoints, the spacing rhythm, container patterns and grid shapes, starting from the smallest screen.
- [Motion](https://docs.mzizi.dev/foundations/motion.md): Animation in the Mzizi design system — timing, easing, enter and exit patterns, and what happens when a user asks for reduced motion.
- [Icons](https://docs.mzizi.dev/foundations/icons.md): Icon conventions in the Mzizi design system — where icons are imported from, the size scale, and accessible icon-only controls.
- [Accessibility](https://docs.mzizi.dev/foundations/accessibility.md): The accessibility standards the Mzizi design system enforces — APCA 3.0 contrast, 56px touch targets, keyboard navigation and screen-reader support.
- [Internationalisation](https://docs.mzizi.dev/foundations/internationalization.md): Why Noto Sans, how text direction is handled, and locale-aware number and date formatting across African regions.
- [Application patterns](https://docs.mzizi.dev/patterns/overview.md): The patterns applications built on the Mzizi registry follow — composition, resilience, observability, and the standard page shapes.
- [Application layers](https://docs.mzizi.dev/patterns/architecture.md): The five-layer component hierarchy an application built on Mzizi enforces, and why imports only ever flow downward.
- [Component patterns](https://docs.mzizi.dev/patterns/components.md): CVA variants, Radix UI primitives, cn() composition and data attributes — the mandatory stack behind every registry component.
- [Error boundaries](https://docs.mzizi.dev/patterns/error-boundaries.md): Three layers of error isolation, so a crashing chart never takes the whole page down.
- [Observability](https://docs.mzizi.dev/patterns/observability.md): Structured logging, performance measurement and error tracking — every line behind one grep-able prefix.
- [Lazy loading](https://docs.mzizi.dev/patterns/lazy-loading.md): Sequential section mounting through a FIFO queue, with memory-pressure monitoring, so a long page does not exhaust a low-RAM device.
- [Mobile-first patterns](https://docs.mzizi.dev/patterns/mobile-first.md): Designing for mid-range Android phones on variable networks as the primary case — navigation, sheets, touch targets, progressive loading and offline states.
- [Dashboard pattern](https://docs.mzizi.dev/patterns/dashboard.md): Composing stats, charts, sidebars and data tables into a consistent dashboard layout that survives a phone.
- [Mzizi Dashboard Standard](https://docs.mzizi.dev/patterns/dashboard-standard.md): One dashboard design for every admin and operator surface in the Bundu ecosystem: the console shell from @bundu/ui, each brand's mineral as an overlay, and a contract for every component.
- [Mzizi Discover Standard](https://docs.mzizi.dev/patterns/discover-standard.md): One design for every public discover and browse page in the Mukoko family (circles, news, events, weather and the super-app on the web): eleven pure Astro components in @bundu/ui, each with a contract.
- [Discover detail pattern](https://docs.mzizi.dev/patterns/discover-detail.md): The page for one item reached from a Discover page (an article, an event, a public circle, a place): five standard parts in Astro and React, and the canonical Open in Mukoko link.
- [Authentication pattern](https://docs.mzizi.dev/patterns/authentication.md): Sign in, sign up and password reset — layout, validation, error handling and the accessibility requirements each screen carries.
- [Resource index pattern](https://docs.mzizi.dev/patterns/resource-index.md): List and table pages — filtering, sorting, pagination, loading skeletons and an empty state that gives the reader something to do.
- [Resource detail pattern](https://docs.mzizi.dev/patterns/resource-detail.md): Single-item pages — breadcrumb, header, content body, a sidebar that becomes a stack on mobile, and related items.
- [Blocks](https://docs.mzizi.dev/blocks/overview.md): Pre-built compositions of registry components for common page sections — dashboards, authentication screens and sidebars.
- [Dashboard block](https://docs.mzizi.dev/blocks/dashboard.md): A complete dashboard composition — sidebar, header, stats, charts and a data table.
- [Authentication block](https://docs.mzizi.dev/blocks/authentication.md): Sign in, sign up and password reset compositions built from registry components.
- [Sidebar block](https://docs.mzizi.dev/blocks/sidebar.md): A navigation sidebar with grouped links, collapsible sub-menus, a user menu and responsive behaviour.
- [Charts](https://docs.mzizi.dev/charts/overview.md): Chart components built on Recharts and wrapped in a ChartContainer that applies the mineral palette and follows the theme.
- [Area chart](https://docs.mzizi.dev/charts/area.md): Area charts for trends over a continuous interval — basic, stacked and gradient fills.
- [Bar chart](https://docs.mzizi.dev/charts/bar.md): Bar charts for categorical comparison — vertical, horizontal, grouped, stacked and mineral-coloured.
- [Line chart](https://docs.mzizi.dev/charts/line.md): Line charts for continuous data — single series, multi-series, dashed projections and dense data sets.
- [Pie chart](https://docs.mzizi.dev/charts/pie.md): Pie and donut charts for proportions, with the legend that makes them accessible.
- [Radar chart](https://docs.mzizi.dev/charts/radar.md): Radar charts for comparing several items across several dimensions at once.
- [Radial chart](https://docs.mzizi.dev/charts/radial.md): Radial bar and gauge charts for progress, scores and completion.
- [Chart tooltip](https://docs.mzizi.dev/charts/tooltip.md): Customising chart tooltips and legends — formatters, labels and indicator styles.
- [Content style](https://docs.mzizi.dev/content/overview.md): How the Bundu ecosystem writes — voice, tone, error messages and inclusive language, for a pan-African audience.
- [Writing guidelines](https://docs.mzizi.dev/content/writing.md): Voice, tone and language conventions for user-facing text across the Bundu ecosystem.
- [Error messages](https://docs.mzizi.dev/content/error-messages.md): Patterns for error messages that leave the reader with something to do next.
- [Inclusive language](https://docs.mzizi.dev/content/inclusive-language.md): Guidelines for inclusive, respectful language in a pan-African context — geography, economics, gender, terminology, and fields that fit real names.
- [The API gateway](https://docs.mzizi.dev/platform/api-gateway.md): api.mzizi.dev is a Hono Cloudflare Worker that serves the registry's files, generated at a pinned registry commit and bundled at build time. No origin, no database.
- [Where data lives](https://docs.mzizi.dev/platform/data.md): No database exists anywhere in Mzizi outside the console. The registry's files are the data layer; the API and the MCP server bundle them at build time.
- [The Mzizi console](https://docs.mzizi.dev/console.md): app.mzizi.dev — Astro chrome with Rust islands over the registry API. What it is, what it replaced, and why it was ported by contract rather than translated.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.