The first slice is built; the rest is design.
mz harness version, definition and
entry exist, and the entries they print are tested in CI. The plugin host, and skills and
benchmark guides generated from the definition, are design only
(RFC-0012, a
draft, amended on 7 October 2026). Checked at language main f9bea2b, tagged v0.13.0, the release of
1 November 2026 (mzizi#146), whose compiler/ is the same as at v0.12.0 (9766929, mzizi#140; the counts below were read at that commit); mz harness version and the definition’s SHA-256 are the same as at the 20 October release (mzizi#120). The fourth release of 8 October 2026 (mzizi#109) carried the rest of the
text operations of mzizi#106.mz command. mz harness definition prints those entries as
the language an agent reads. The toolchain, the agent protocol (mz check --agent, mz fix)
and external clients such as the CLI and the MCP server are meant to attach to it, not hold a
second copy of the language.
It was called “the harness” until 7 October 2026. It is a different thing from
benchmarks/harness/, the Phase 0 scorer, which is always called the benchmark harness.
“The harness is the central spine, internal and external, for the language.” — the owner, 7 October 2026, quoted in RFC-0012
What an entry holds
At
9766929 the definition holds 197 entries: program, and component and service as
kind-level entries; int, float, bool and text; every operator, try among them; the 11
numeric methods, the 15 text methods and the 19 collection methods and folds; every statement
form, C4’s control flow, C9’s results and C8’s records among them; print and error; the nine
mz commands; and 79 diagnostic codes: the 53 MZ09xx codes a program raises and the 26
shared codes it reuses. The 8 October text said 80, with 27 shared; that figure does not reproduce from the
definition, and the 20 October release added and removed no code entry. The 49 codes that components and services raise are on a pending list
that a test freezes, so it can only shrink. Each of these counts is read from mz harness definition at 9766929.
mz harness
9766929, mz harness version prints:
0.0.0, and the definition’s SHA-256 pins its
content, changing whenever an entry does. Each subcommand exits 0, or 2 for a usage problem or
an unknown name. mz harness plugins is designed and not built.
The MZ09xx table on the compiler page is generated from
mz harness definition, not written by hand.
What is enforced, and what is written by hand
The amended RFC’s rule, from the owner’s direction of 7 October 2026, is that a pull request that adds or changes a language feature adds or updates its harness entry in the same pull request, and a tracker row is not done until its entries are. The first slice holds it in three different ways, and the difference matters:
Fix kinds are recorded as raised, so an agent can receive a
guess on a code whose entry lists
only exact: when two exact fixes overlap, mz check demotes one.
What is not built
- The plugin host, its manifest and lifecycle, and
mz harness plugins. Nothing inmzloads, lists or calls a plugin. - Generated skills and benchmark guides. The agent skills and the benchmark’s prompts are still written by hand, and do not yet describe programs.
- The checker reading its rules from the registry, rather than being checked against it.
- Full entries for components and services, which are kind-level only.