# `vocabulary` — the destination language of harness emissions
The descriptor adapter emits ordinary Rust expressions that reach the harness through public constructors, readers, closed-choice arms, stamp clauses, and operation roads.
This home owns those destination spellings so each renderer states which harness concept it needs instead of carrying an independent string copy of the address.
## Authority in and value out
[`HarnessName`] names a semantic segment of a rendered harness path or call.
[`HarnessWord`] names a clause key or target-supplied seat in stamped material.
The rendering operations turn those informed spellings into generated tokens rooted at the harness binding declared by the consuming target.
The vocabulary is demand-driven rather than an introspection registry.
A renderer asks for the destination it needs, while the harness remains the authority that declares what the destination means and whether a construction is lawful.
## Composition
Trial, benchmark, and mutation projections consume this shared destination language while retaining their own declaration grammars and render operations.
The support home owns the carrier, schema gate, and invocation matcher that transport those projections across the consumption boundary.
The harness descriptor, benchmark, and Muterprater homes own the public values and operations the generated expressions reach.
[`path`] preserves the complete caller-declared harness binding before appending destination segments.
A consumer therefore reaches the same vocabulary through a direct dependency, a renamed dependency, or a facade path without this home learning a crate spelling.
## Evidence ceiling
Centralized destination spellings prevent renderer-local drift, but they cannot prove that the harness still publishes every destination.
That agreement is established only when generated cargo is expanded and type-checked against the harness, alongside the independent schema-pin and public-operation observations.
This home does not own harness policy, a benchmark backend, the carrier gate grammar, or Rust's own operations.