Rendered from docs/obligations/0088-correcting-an-identifier-is-mechanical-and-it-is-not-local.md in the Headwater corpus. Every document on this half of the site is typed by the taxonomy the descriptor names: corpus.json.

Correcting an identifier is mechanical and it is not local

Context

Spec 12 lists four mechanical fixes, and one of them is to correct the format of an identifier. Two of the three ways an identifier fails its pattern do have one derivable outcome. A wrong namespace has the declared namespace, and a short sequence has the declared width.

Neither fix is confined to the document that holds the finding. An identifier is the one value that other documents keep copies of, because Q4 rules that a relation target is an identifier. This corpus names HW-SPEC-taxonomy-model from three other documents, so a patch that rewrote it would leave three dangling edges behind. The zero-padding case is worse, because allocation is reconcile-first and the padded value may already belong to another document.

Obligation

Either spec 12 qualifies its own example, or check --fix gains a class of fix that spans documents and reports every file it would touch.

Discharge

So identifier.pattern.not_met offers no fix, and the rule that spec 12 states is per finding while this repair is corpus-wide. The record on fixable is the same flag read two ways, and this is a third question about it.