# Mzizi

> Mzizi is a Bundu Foundation research project: a Rust framework 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, and nothing has yet been measured against the charter's kill criteria.

- [A language designed to be written by machines that are not very good at writing](https://docs.mzizi.dev/index.md): Mzizi is a Bundu Foundation research project: a Rust framework whose syntax, type system and compiler feedback loop are built for small open-weight models. Phase 0 is a prototype front end, and the thesis is still unmeasured.
- [Status](https://docs.mzizi.dev/status.md): What exists, what is tested, what is measured, and what is still only a design document. Mzizi-lang is a Phase 0 prototype front end and has not been measured against its own kill criteria.
- [The ecosystem](https://docs.mzizi.dev/ecosystem.md): Which repository serves which domain, who owns each one, and which of those addresses actually resolve today.
- [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 mz compiler](https://docs.mzizi.dev/compiler.md): Four commands, an exit-status contract, and an NDJSON diagnostic protocol written for a reader holding zero file context.
- [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 five phases, and the explicit non-goals. Bundu Foundation Research Charter v0.1 — a direction and a phasing, not a sprint plan.
- [The Phase 0 benchmark](https://docs.mzizi.dev/benchmark.md): The measurement the whole thesis rests on: what it measures, why one input to it is held out, and the dependency rule that keeps the public project forkable. It has not run.
- [RFC index](https://docs.mzizi.dev/rfcs.md): Four design documents, their status lines as written, what each settles, and what each explicitly leaves open.
- [The component registry](https://docs.mzizi.dev/registry/overview.md): How the Mzizi component registry works — a shadcn-compatible registry serving 575 items over a public API, backed by files in a repository.
- [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.
- [Browsing components](https://docs.mzizi.dev/registry/components.md): How to list and inspect Mzizi registry components — from the portal, from the HTTP API, and from the MCP server.
- [The MCP server](https://docs.mzizi.dev/registry/mcp.md): The one Mzizi MCP endpoint — eleven consolidated tools over the registry, the brand system and the architecture model, behind a free signup gate.
- [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.
- [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.
- [Agent tooling](https://docs.mzizi.dev/tooling.md): The published Mzizi agent tooling — the MCP server, the fundi CLI and SDK, and the skills bundle — and what fundi means in each of the two places it appears.
- [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.