artifact-formalizerlisted

# Artifact formalizer (specification register) ## Purpose A reader of an essay-register artifact performs two passes: one to locate the requirement, one to decide whether a given sentence carried one. This skill removes the second pass. It has two modes. | Mode | When | Instrument | Owns | | :--- | :--- | :--- | :--- | | **A — Authoring** | before and during writing | `references/authoring-contract.md` | the defect is not written | | **B — Audit** | on an existing document | `scripts/scan_register.py` + a reading pass | what Mode A missed | Mode A prevents the defect; Mode B measures what Mode A missed. **Why in that order.** Defective prose measured 5.1% of one corpus's words (731 of 14,288), while removing it required reading and editing all 14,288. Register also varied by authoring model on the same repository, so an unwritten standard is not a standard. [`references/measurement-baseline.md`](references/measurement-baseline.md) §5 carries both figures. ## Scope boundary — what this is NOT This is not a jargon or terminology tool. Domain terms are precise and stay verbatim: `singleflight`, `RTM`, `дедлайн`, `throttle`. Translating engineering vocabulary into business language for customer-facing documents is a different problem with a different audience, and this skill does not attempt it. ## 1. Red Flags (Anti-Rationalization) A definition list, not a table: the reality column is prose, and `documentation-standards` §5.1 prescribes converting such a column rather