--- name: mzizi-design description: "Use this skill for the Mzizi design system and brand: generating well-branded interfaces (production or prototype), design tokens, and ecosystem-level work. Contains the canonical 21-family palette (seven African Minerals, seven Heritage tones, the Experimental Seven) with generated stylesheets (tokens/palette.css, tokens-update.css), the radius scale, Noto Sans/Serif and JetBrains Mono type, pill buttons, the Bundu floor (17px body, 14px captions, 49px hit region, 14px inset, 7px gaps, 1.5 leading) and the density layer, 7:1/4.5:1/3:1 contrast, status and surface tokens, the Dashboard and Discover Standards' brand overlays (colour and mark only), the verified brand constellation (each brand's mineral, voice, meaning, URL), the five Ubuntu pillars and principles, what is and isn't an ecosystem app, and the wordmarks. Also covers Apple's Human Interface Guidelines as the baseline and where Mzizi is the authority: touch targets, spacing, type scale, colour, pill geometry, materials, density and the shell." --- # Mzizi design — the system and the ecosystem This skill replaces three 0.7.0 skills: `nyuchi-design` (UI and tokens, now "The design system" below), the Ubuntu and ownership half of `ecosystem-app-setup` (now "What belongs in the ecosystem"), and the tokens of `mukoko-design`, which moved here. mukoko's brand files (the Swarm mark, the app icon, favicons, the lockup and backgrounds) are in the `mukoko-design` skill, restored in 0.15.0. ## Files this skill ships All generated from `palette.canonical.json` at the package root by `scripts/generate-tokens.mjs`, and gated against it. Never hand-edit them; never retype a hex. | File | Contents | | ---------------------- | ---------------------------------------------------------------------------------------------------- | | `tokens/palette.css` | all 21 families, light + dark, as CSS custom properties | | `tokens/palette.json` | all 21 families, machine-readable | | `tokens/minerals.css` | the seven minerals only | | `tokens/minerals.json` | the seven minerals only, machine-readable | | `tokens-update.css` | all 21 families (light, dark, `.dark`, `prefers-color-scheme`) plus the radius scale, as one drop-in | ## The ecosystem **Mzizi** is the parent identity at the ecosystem level — the Mzizi programming language, its toolchain, the design language, the component registry and the open doctrine every brand builds on. Everything revenue-generating (the Mzizi console, fundi, paid plans, billing) is Nyuchi's. Three pillars: **mukoko** (consumer super app), **nyuchi** (infrastructure & enterprise), and **shamwari ai** (the intelligence pillar), with the **sister brands** as specialist verticals — one identity, one design system, one open data commons. Doctrine **v4.1.0**. **The repo is the source of truth, and there is no database.** Colour comes from `palette.canonical.json` at the root of this package — 21 families, vendored from `mzizi-dev/mzizi-registry → lib/tokens/palette.source.ts` and gated against it. The ecosystem constellation and the Ubuntu pillars and principles come from `mzizi-registry → content/doctrine/`, served at (`.ecosystem`, `.philosophy`) and by the MCP as `mzizi_get_tokens` (`family: "ecosystem"`) and `mzizi_get_doctrine`. Two notes: principles were renamed in v4.x, so use the set below and not older Shona-named lists; and the registry still names its ecosystem-layer entry `bundu` (URL **bundu.org**). That is registry data, and it changes in mzizi-registry, not here. The **five** pillars and **five** principles below are a count of Ubuntu doctrine, not of the palette, and they are correct — `/v1/brand` `.philosophy.ubuntuPillars` serves exactly these five. Do not "fix" them to seven to match the colour families. ### The ecosystem-level identity - **Mineral:** `copper` — `#BF5A36` light / `#FF8A65` dark (`--color-copper`) · connection, foundation, stewardship - **Registry entry:** `bundu` in `/v1/brand` `.ecosystem` (meaning _wilderness_, Shona) · **URL:** - **Voice:** visionary, grounded, inclusive - **Role:** the ecosystem — the layer that holds the whole, the commons, governance, philosophy - **Wordmark:** `Mzizi`, capitalised, Noto Serif 600. (The other wordmarks stay lowercase.) - **No standalone ecosystem-level logo mark is registered in the registry yet** — that's an open identity item. Until one exists, ecosystem-level materials use the wordmark in copper, optionally with Mukoko's Swarm mark (the `mukoko-design` skill) when the subject is the product family. Don't invent an ecosystem mark ad hoc. - **Copper is the ecosystem layer, not Mzizi's own surfaces.** mzizi.dev, docs.mzizi.dev, the registry and the language are the `mzizi` row of the constellation below: theme them in **hematite** (owner decision, 2026-09-30). Keep copper for material where the ecosystem as a whole speaks: governance, the commons, the manifesto register. ### The brand constellation (verified, v4.1.0) Every brand owns a mineral and a voice. Theme each brand's surfaces and copy in **its own** mineral and register — never default everything to tanzanite. | Brand | Role | Mineral | Meaning | Voice | | ------------ | ------------------------------------------- | ---------- | ---------- | -------------------------------------- | | **bundu** | The ecosystem | copper | Wilderness | visionary, grounded, inclusive | | **nyuchi** | Infrastructure & enterprise | gold | Bee | technical, reliable, industrious | | **mukoko** | Africa's super app | tanzanite | Beehive | welcoming, structured, protective | | **shamwari** | Sovereign AI companion | sodalite | Friend | helpful, warm, intelligent | | **Mzizi** | The root: language, registry, design system | hematite ¹ | Root | precise, honest, grounded | | events | Events & gatherings (Mukoko Events) | malachite | Gathering | celebratory, communal, vibrant | | bushtrade | Marketplace | gold | Bush trade | practical, trustworthy, local | | lingo | Language learning | cobalt | Language | encouraging, cultural, playful | | campfire | Platform messaging anchor | malachite | Campfire | direct, warm, always present | | bytes | Short-form creator video | tanzanite | Bytes | energetic, creative, youthful | | novels | Publishing platform | malachite | Novels | literary, thoughtful, immersive | | places | Geographic knowledge graph | gold | Places | authoritative, helpful, discoverable | | transport | Public transit & booking | gold | Transport | efficient, reliable, practical | | planner | Productivity hub | cobalt | Planner | organised, clear, supportive | | wallet | Payments & tokens | gold | Wallet | trustworthy, precise, secure | | pulse | Feed & Mukoko Home | tanzanite | Pulse | personal, adaptive, ambient | | health | Wellness & telemedicine | malachite | Health | caring, accurate, private | | circles | Community messaging | terracotta | Circles | inclusive, moderated, community-driven | | kweli | Trust and verification | malachite | Truth | honest, rigorous, reassuring | | learning | Education (Nyuchi Learning) | gold | Learning | patient, practical, encouraging | | news | News and journalism | cobalt | News | clear, credible, balanced | | weather | Weather and alerts | cobalt | Weather | calm, precise, timely | The `bundu` row is the ecosystem layer as `/v1/brand` serves it today; the table mirrors the registry, so it changes when mzizi-registry renames the entry. The last four rows joined canon on 2026-10-04 (owner decisions, mzizi-registry #409): kweli is malachite (it used to borrow Mukoko's tanzanite), news and weather are cobalt, and **learning is gold** because every Nyuchi brand is gold. The education industry category follows it: education is gold, not cobalt. The `events` row is **Mukoko Events**, at `events.mukoko.com` (owner decision, 2026-10-04). The _nhimbe_ brand is retired. `nhimbe` survives only as a deprecated alias of `events`: canon still resolves it, and `brand-nhimbe.css` re-exports `brand-events.css`, so nothing that names it breaks. New work names `events` and writes "Mukoko Events" in copy. The mineral is unchanged: malachite. ¹ **Mzizi's brand colour is hematite, and hematite is a Heritage tone, not one of the seven minerals** (owner decision, 2026-09-30). `/v1/brand` serves it in `.ecosystem` as `{"name": "mzizi", "meaning": "Root", "language": "Swahili", "mineral": "hematite"}` and lists hematite under `.heritage`, not `.minerals`: the field is called `mineral`, but it names a palette family, usually a mineral. Mzizi owns and operates the language, the registry, the design system, the docs and the API; `/v1/brand` gives its role as "Language, registry and design system", and its voice as "Precise, honest, grounded". A Mzizi surface takes its primary from hematite, as the shipped stylesheets do: `@bundu/ui`'s `brand-mzizi.css` (which mzizi.dev uses) sets `--primary` to `var(--color-hematite)`, and the registry's `mzizi-tokens-globals.css` defaults `--primary` to `var(--heritage-hematite-aa)`. Not gold (nyuchi's), not tanzanite (mukoko's), not copper (the ecosystem layer's). Take the values from `palette.canonical.json` (`hematite`, Heritage). The narrative spine: **nyuchi is the bee, mukoko is the hive, Mzizi is the root everything grows from.** Use this when explaining the ecosystem — it is the one-sentence architecture. ### Ubuntu as identity (live doctrine) Mzizi carries the philosophy. _Ndiri nekuti tiri_ — I am because we are. **Five Pillars** (spheres of belonging): **family** (the household and kin, the primary web of belonging) → **community** (neighbours, peers, chosen kin) → **society** (the broader human web — strangers, institutions, the polity) → **environment** (the natural world that holds all relationships; Ubuntu is ecological before it is social) → **spirituality** (the vertical dimension — meaning, purpose, ancestry, the sacred). **Five Principles** (operating rules): **survival** (collective endurance — no one survives alone) · **solidarity** (firm, persevering commitment to the common good) · **compassion** (active care shown through helping, sharing, welcoming) · **respect** (unprejudiced consideration of another's privileges, beliefs, norms — includes elder-respect) · **dignity** (inherent worth by virtue of existence, irrespective of status or background). In ecosystem materials, philosophy is **structural, not decorative**: name a pillar/principle only when the feature or message genuinely embodies it. ### Rules for ecosystem-level work - **Wordmarks:** `Mzizi` is capitalised. Every other wordmark is lowercase: `nyuchi`, `mukoko`, `shamwari`, `bundu` and every sister brand. - **Copper accents** signal "this is the ecosystem speaking" (parent-level pages, governance, commons, manifesto-register material). - **Cross-brand layouts:** lead with the brand that owns the message; bring in the constellation table's minerals when showing the family together (each brand in its own mineral). - **Voice shifts with the speaker.** An ecosystem-level page is visionary/grounded/inclusive; the same content on mukoko.com becomes welcoming/structured/protective. Don't copy-paste tone across brands. - Cultural specificity is non-negotiable: Shona vocabulary and Zimbabwean grounding are structural. - All UI tokens (radius, type, spacing, surfaces, status colours) are under "The design system" below. Mukoko's logo and assets are in the `mukoko-design` skill. - **Every brand owns a mineral, but the palette is not only minerals.** A cross-brand piece has 21 families to draw on — seven minerals, seven Heritage tones, the Experimental Seven. Use the minerals to say _who is speaking_ (and hematite when Mzizi is); use Heritage for atmosphere and surface, and the Experimental Seven for categorical sets that would otherwise stretch a mineral past its meaning. ## The design system > **Doctrine v4.1.0. The canonical palette ships with this package.** > `palette.canonical.json` at the root of `@nyuchi/mzizi-skills` states all **21 colour > families** — seven African Minerals, seven Heritage tones, the Experimental Seven — and > every token file in this bundle is generated from it and gated against it. Read it, or the > stylesheets generated from it (`tokens-update.css` and `tokens/palette.css` here). Do not retype hex values out of this prose into a project. > > Canon upstream is `mzizi-dev/mzizi-registry → lib/tokens/palette.source.ts`, served publicly > at and by the MCP as `mzizi_get_tokens`. There is no > database: the registry's files are the data layer. > > **Colour is derived and gated. Everything else on this page is hand-maintained** — > typography, spacing, radius, sizes, motion, shadow, z-index and the semantic set. The > radius scale and control sizes were checked against `mzizi-registry` `main` for 0.8.0; > confirm the rest with `mzizi_get_tokens` (`typography`, `spacing`, `radii`, `semantic`, > `componentSpecs`) if precision matters. **The published design system.** The brand book, the tokens as data, the marks and static previews of the components (Badge, Button, Card, Checkbox, Input, StatusBadge, Switch, Tabs and more) are published as the Design System artifact at . Its source of truth is the `design-system/` folder in `mzizi-dev/mzizi-registry` (arriving with mzizi-registry#418), which the artifact is built from file for file. To change the design system, change that folder, never the artifact page: the artifact is republished from registry `main` after a merge that touches it. ### Rules that are non-negotiable - **Wordmarks** — `Mzizi` is capitalised. `mukoko`, `nyuchi`, `bundu`, `shamwari`, `bushtrade` are lowercase, always. (Product names such as Mukoko Events are written as names, not wordmarks.) - **The palette is 21 families: seven Minerals + seven Heritage + the Experimental Seven.** Any interface that uses only the minerals is using a third of the system. Do not describe it as "the seven-colour palette". - **Seven African Minerals** (geological, the core palette). The custom properties are `--color-`, `--color--container`, `--color--on-container` — those are the names the design system defines. (`--container-` / `--on-container-` appeared in earlier revisions of this skill and are defined nowhere upstream; `tokens-update.css` now ships them as aliases so existing work keeps rendering, but do not reach for them in new code.) - `cobalt` — primary blue, links, CTAs · digital future, trust - `tanzanite` — **mukoko's brand mineral**, social features · premium, connection - `malachite` — success states, positive actions · growth - `gold` — achievements, rewards, highlights · honey, warmth - `terracotta` — community features · earth, grounding - `sodalite` — **AI / Shamwari surfaces, deep-reasoning states** · intelligence, depth _(added v4.1.0)_ - `copper` — **Bundu ecosystem identity, the commons** · connection, stewardship _(added v4.1.0)_ - **Seven Heritage tones** (atmospheric anchors — mini-app surfaces, backgrounds, moods; no family or role, with one exception: `hematite` is Mzizi's brand colour): `indigo` (dusk, the dyer's craft) · `savanna` (sun-dried grass, the dry season) · `baobab` (the tree of life, bark, shelter) · `sunset` (day's end, the gathering hour) · `river` (flow, the journey) · `hematite` (the neutral anchor, the substrate) · `kalahari` (the light anchor, openness). Reach for them via `--color-` (aliasing `--heritage-`); values are in `palette.canonical.json`. _(Two earlier framings are withdrawn: the ten-colour one from before the palette settled, and the two-anchor one that survived into v0.5.1 of this bundle. **There are seven.** A skill that named two produced two-tone output in projects that had never seen each other.)_ - **The Experimental Seven** — a computed heptagon (hues offset 17°, prime saturations, foregrounds solved to P7), each tone carrying a `heptagonIndex` 0–6 that fixes its place on the wheel: `ember` · `acacia` · `fern` · `lagoon` · `storm` · `dusk` · `protea`. Four tiers each: `--exp-`, `--exp--container`, `--exp--on`, `--exp--ui`. Use them for generated/wheel-derived surfaces and categorical sets where the minerals would have to be stretched past their meanings. - **Each brand owns a mineral** (the ecosystem map, verified v4.1.0 and served at `/v1/brand` as `.ecosystem`): bundu→**copper**, nyuchi→**gold**, mukoko→**tanzanite**, shamwari→**sodalite**, Mzizi→**hematite** (a Heritage tone, not a mineral: the one brand whose colour comes from the Heritage set), events (Mukoko Events)/campfire/novels/health/kweli→malachite, lingo/planner/news/weather→cobalt, bushtrade/places/transport/wallet/learning→gold (learning, and with it the education category, is gold because every Nyuchi brand is), bytes/pulse→tanzanite, circles→terracotta. Theme a surface in its brand's colour — never default everything to tanzanite, and never give a Mzizi surface gold, tanzanite or copper as its primary. - **Buttons are ALWAYS pill** (`rounded-full` → `--radius-full`, 9999px). Inputs match buttons visually. The exception is the Mzizi Dashboard Standard (below): its app Button and controls use the small radius, as their contracts state. - **The Bundu floor: hard minimums on every device** (owner rulings 2026-11-01 and 2026-11-02, mzizi-registry#597; registry 4.23.0, `@bundu/ui` 0.8.0). Bundu sets the standard for outdoor reading and for people who find technology hard, so the minimums are as high as they can be. **Body text is 17px on every device**, desktop included (Apple's iOS default). **Captions, metadata and secondary text are 14px** (2 x 7), and nothing readable is smaller: `text-xs` and `text-sm` both paint 14px, badges and chart labels are 14px, and an arbitrary `text-[10px]` is wrong. **Every interactive control keeps a 49px hit region (7 x 7) on every pointer**, above Apple's 44 pt (Buttons: "a hit region of at least 44x44 pt"). On touch, controls are drawn at 49px: `h-control`, `h-control-sm`, `size-control-icon` and `h-field` are 49px, `h-control-lg` 56px (`--target-floor`, `min-h-touch-min`). At desktop density (fine pointer, hover, 64rem and up) a control may be DRAWN 28 to 40px (`--control-floor` is 28px) but keeps its 49px hit region through a transparent `::after` the token layer's `hit-area` rule gives every `button`, `summary`, button-like role and `.hit-area` element; `--target-floor` is never lowered. A native input, select or textarea cannot carry a pseudo-element, so `h-field` stays 49px drawn on desktop, and a standalone link that is a target is drawn at 49px or takes `hit-area`. Use the **size roles**, never `h-12`, `h-14`, `size-12`, `size-14` or `min-h-[44px]`. Only display and heading sizes step down as screens grow; body and secondary text never do (h1 is 34px on a phone, Apple Large Title). Density is visual size only: **never use screen size to guess network quality**. Spacing between targets has its own floor (next bullet): a 7px gap, and the spacing tokens do not change with density. The radii are unchanged: 4, 7, 12, 14, 17 and a pill. `` is the compatibility alias: it restores the sizes from before 2026-11-01 (48px floor, 56px default, 16px body, 12px captions), steps out of the Bundu floor, and is planned for removal in the next major; set it only for an app that has not migrated, and remove it once it has. The numbers live in one place, `BUNDU_FLOOR` in the registry's `lib/tokens/roles.source.ts`, and are what `button.tsx`, `button.astro`, the Roots `button.rs` and `/v1/brand` `.componentSpecs` (`minTouchTarget: 49`) state; the language's `primitives/button.mz` still says 56 until that file is updated in its own repository. Dashboards and Discover: the Dashboard and Discover Standards' components read the same size roles; each contract's `density` states the rows, and about 40 rows that predate the floor (links and controls on literal `h-11`/`h-12` classes) are pinned in the registry's `HIT_AREA_GAPS` until they move, so do not copy their heights. **The Bundu Order** (registry `brand-guidelines`, "The Bundu Order") is where these numbers come from: the unit is 7px, the floors are 17 (a prime), 14 (2 x 7) and 49 (7 x 7), P7 and P17 are prime steps of the surface ladder, and the owner says it draws on biblical mathematical patterns and prime numbers. Cite it as the owner's provenance, not as an engineering reason. - **The spacing floor: minimum padding, gaps and leading that nothing can go under** (owner, 2026-11-04, mzizi-registry#617). The Bundu floor sets spacing as well as sizes, on the same 7px unit. The five minimums: **inset 14px** (`--inset-floor`, 2 x 7: padding between text and its container edge); **control gap 7px** (`--gap-floor`: between adjacent interactive controls, measured visible edge to visible edge; hit regions may touch, never overlap, and the `hit-area` overlay of a control drawn small at desktop density may reach into the neighbouring space as before); **label gap 7px** (a label and its field); **item gap 7px** (sibling items in a list, grid or toolbar); and **body leading 1.5** (`--leading-floor`: line height, WCAG 1.4.12). They sit beside 17px body, 14px captions, the 49px hit region (`--target-floor`), 7:1 body contrast and the 28px visible control. The numbers live in one place, `BUNDU_FLOOR.spacing` in the registry's `lib/tokens/roles.source.ts` (`insetPx` 14, `controlGapPx` 7, `labelGapPx` 7, `itemGapPx` 7, `leadingBody` 1.5), and `/v1/brand`, `mzizi_get_tokens` and `mzizi_get_doctrine` serve them. **How it is enforced:** a base-layer rule in the token layer gives every element the floor even when you add no padding or gap, so an unstyled container is already at the floor; the token test fails any component spec that sets padding or a gap below it; each component contract asserts its spacing minimums (TypeScript and Rust agree); a rendered geometry guard checks neighbouring controls, text inset and the WCAG 1.4.12 stress (line height 1.5, paragraph spacing 2x, letter spacing 0.12em, word spacing 0.16em) for clipping; and `mzizi check` (`@nyuchi/mzizi-cli`) fails a project's CSS or TSX that goes under it. **Nothing may go under a floor:** no brand pack, no density layer, no app, no one-off. Density changes visual size only; the spacing floor holds at every density. `` is the one opt-out, the same alias that restores the pre-floor sizes (it steps out of the spacing floor too, and is planned for removal in the next major). **What to do:** build with the components and the tokens (`--inset-floor`, `--gap-floor`, `--leading-floor`), which already sit at or above the floor, and run `mzizi check` before you push. Never write `p-0`, `px-0`, `gap-0`, a negative margin, `leading-none`, `leading-tight` or an arbitrary `p-[4px]` on a text container or a row of controls. The floor is rolling out across the registry, `@bundu/ui`, `@nyuchi/mzizi-cli` and the MCP (mzizi-registry#617): `mzizi check` needs `@nyuchi/mzizi-cli` 0.8.0 or later, and a registry or `@bundu/ui` older than the spacing floor has none of the custom properties, so check what you installed before relying on them. Where a value below the floor is deliberate (a decorative, non-text box; a hit region that overlaps by design is still never allowed), put an exception comment on the same or the previous line: `mzizi-spacing-exempt: `, with a reason. An exception without a reason fails. - **`text-base` can collide with `--color-base`.** The token layer registers `--text-base` (17px, the font-size step) and the palette also has a surface colour named `base` (`--color-base`), and Tailwind 4 reads both namespaces for a `text-base` class, so an app that has both may not get the 17px step. This is a known open point (registry decision pending, a follow-up to mzizi-registry#597), not something to work around by renaming a token. Until it is decided: write body copy as `text-body` (17px) or leave it unclassed, use `text-xs` and `text-sm` (both 14px) for secondary text, which work, and never use `text-[Npx]` under 14. - **Radius scale** (px), every step from a 7px unit: `xs` 4 (unit − 3) · `sm` 7 · `md` 12 · `lg` 14 (**DEFAULT** cards/panels) · `xl` 17 · `2xl` 17 · `full` 9999 (pills). That is `mzizi-registry/styles/globals.css`, the Rust `mzizi-tokens` `Radius`, and `/v1/brand` `.radii` ("ecosystem numbers: 4, 7, 12, 14, 17"; `xs` joined in mzizi-registry#544). Legend swatches, kbd keys and inline tags use `xs`, checkboxes `sm`, inputs and small cards `md`, cards and panels `lg`, modals, sheets, dialogs and tabs `xl`. Reference via `--radius-`. `2xl` is 17px, never 24. (Until 0.8.0 this skill listed `none` 0 and `2xl` 24, which were never upstream values.) - **H1–H3 are Noto Serif. H4+ and body are Noto Sans. Code is JetBrains Mono.** - **Rings over shadows.** Cards get `ring-1` of `--border`, not a drop shadow. - **No gradients, no glassmorphism** except sticky chrome (`backdrop-blur`) and the Discover Standard's hero wash (DiscoverHero's `gradient-showcase`, which mixes `--primary` into the background, as its contract declares). - **Emoji only as mini-app identifiers**, never as chrome or body decoration. - **Status has its own names: `--status-success` / `--status-warning` / `--status-error` / `--status-info` / `--status-neutral`.** Use those names and do not hardcode a hex. Upstream they alias `--success` / `--warning` / `--destructive` / `--info` / `--neutral`, so there is one decision per status — which means the resolved values are mineral-derived in the shipped theme (success reads as malachite, info as cobalt), not the standalone #22C55E/#F59E0B/#EF4444/#3B82F6 set an earlier revision of this skill listed. Those hexes are the per-component `var(--token, #hex)` fallback for an app that has not defined the properties; they are not the theme. Severity scale (`--severity-low/moderate/high/severe/extreme/cold`) and connection (`--connection-online/syncing/cached/offline`) follow the same logic. Verification is the only place minerals carry status meaning; it has its own rule, next. - **Verification is two things, not one ladder: assurance levels and attestations** (mzizi-registry#577; the source is `gateway/lib/assurance.py` in `nyuchi/nyuchi-api`, the one access decision every surface derives from — read that, never re-derive it). Read the roles, never a hex; each has `-container`, `-on-container` and `-text`, and passes APCA in both themes. - **Assurance levels** are ordered (`>=` is meaningful): how strongly an identity is proven. 0 `none` "Unverified" → `--assurance-none` (the neutral grey, `--status-neutral`) · 1 `otp` "Contact Verified" → `--assurance-otp` (cobalt) · 2 `documented` "Documents Checked" → `--assurance-documented` (sodalite) · 3 `government` "Government Verified" → `--assurance-government` (gold) · 4 `licensed` "Licensed Professional" → `--assurance-licensed` (tanzanite). - **A level can expire.** A `government` check holds for five years and a `licensed` one for a year (`LEVEL_VALIDITY_YEARS` in assurance.py, nyuchi-api#375). When the term runs out the level is withdrawn, so show the level a person holds now and never cache it as permanent. - **Attestations** are unordered and held beside the level: who vouches for the subject. `community` "Community Vouched" → `--attestation-community` (terracotta) · `business` "Registered Business" → `--attestation-business` (malachite) · `domain` "Domain Verified" → `--attestation-domain` (copper). Show each as its own chip next to the level (`app/tier-status` and `ui/mzizi-verified-badge` do this, from registry v4.17.0; `ui/mzizi-trust-meter` shows the level and renders no attestation chips). - **Provenance: where an attestation came from, and when it was checked** (mzizi-registry#593, on registry `staging`, released with the next registry version: `ui/mzizi-verified-badge` 1.2.0 and `app/tier-status` 1.2.0). A stored attestation record may carry `source` (a short id such as `"osm"`), `sourceRef` (the source's own reference, kept and never shown) and `checkedAt` (an ISO date or date-time). The chip label stays the canonical one ("Community Vouched"), and an optional second line reads "via · checked ", for example "via OpenStreetMap · checked 14 Mar 2026". Source names come from `ATTESTATION_SOURCES` in `mzizi-trust-tier-data` (`osm` → "OpenStreetMap"), and the line is built by `attestationProvenance`. Two rules: **never invent a check date.** With no `checkedAt`, or one that does not parse or names a day that does not exist, the line is "via OpenStreetMap" with no date. And **never a per-source label**: a source changes the second line only, never the chip's name, its colour or the closed set of three attestations (an OpenStreetMap verification is a `community` attestation, never a level). The date is formatted in UTC from the locale (`en-GB` by default) so the day never shifts. The chip's `aria-label` stays the canonical name and the line is its `aria-description` (badge) or is read with the name (tier status, the date as `