artifact-formalizer

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 §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 than widening it.

• "I'll write it, then run the formalizer." That is the expensive order. §Purpose gives the measured cost. Mode A first.
• "The scan is clean, so the text is clean." Every zero is reported next to what the detector actually saw. Read DIAGNOSTICS: a corpus whose longest sentence equals the limit was written for the gate.
• "I'll add a pattern for this new phrasing." First ask whether a test in the authoring contract already forbade it. If it did, the lexicon gains a faster detector and nothing else changes. If it did not, the contract is amended (§6).
• "«Шов», «нога», «мост» — это термины проекта." A term appears in ARCHITECTURE.md, a public API, or a cited standard. Run --terms docs/ARCHITECTURE.md and let the scanner apply that test.
• "I formalized the section that was quoted at me." The pass that produced this skill's own worked example did exactly that. It left seventeen occurrences of one metaphor in the same task set. Coverage is per section: --sections.
• "The whole document reads badly — I'll rewrite it." Conforming sentences stay verbatim. Over-rewriting introduces errors that were not there.
• "I'll shorten it by trimming the requirement." Register changes, substance does not. Numbers, identifiers, obligations and scope limits survive verbatim.
• "This word is fine — I'll widen the threshold." A failing scan is fixed in the prose. Thresholds move only when a measurement moves them.
• "It flagged a false positive, so the rule is wrong." The scanner is advisory by design. Judge the finding; info exists because the author decides.