Skip to main content
Every component in the registry has a set of canonical URLs. The table below says which answer today, checked against button on 30 September 2026. Several of the portal’s old per-component pages did not survive the move of mzizi.dev to the site, and the health and chaos probes depended on console data that the registry no longer holds.

​
URL structure

The API’s own liveness probe is api.mzizi.dev/v1/health. For why the two API routes answer 503, see the API gateway.

​
Status semantics, as designed

The health and chaos probes are not served on 30 September 2026. This is what they are specified to answer. For /api/health/{name}:
  • 200 — the component exists.
  • 404 — no component by that name.
For /api/chaos/{name}:
  • GET 200 — returns the supported-fault manifest for the component: render error, slow render, missing data, network timeout.
  • POST 405 — by design. Chaos injection is in-process; install the N8 chaos library into your own application rather than pointing faults at a shared service.

​
DOM integration

Every rendered component carries a data-portal attribute pointing at its portal page:
That single attribute is what makes several things possible at once:
  • DevTools inspection clicks through to the component’s documentation.
  • Error tracking enriches a stack trace with a documentation link.
  • N8 chaos testing looks up the supported-fault manifest by stable URL.
  • The N9 fundi rung resolves a rendered component back to its canonical documentation.
The attribute is emitted by the component itself, so it stays correct without anyone maintaining a mapping table.