Edition, amendment and corrigendum

A standard's life after publication is layered change. A corrigendum fixes what was wrong from the start — typographical and technical errors — and applies as if always there. An amendment changes requirements: clauses revised, added or deleted, published as a separate document to be read with the parent. A new edition consolidates everything and starts the cycle again, superseding its predecessor. At any moment, "the standard" therefore means a specific stack — edition plus its amendments plus its corrigenda — and two engineers holding the same edition but different amendment states hold different requirements.

The tracking burden is real and unevenly borne. Formal review checks against the full current stack; project document registers often record editions only; and citations in specifications almost never enumerate amendments, leaving the applicable state implicit and therefore arguable. Standards bodies publish the change trail, but the assembly is manual.

The disciplined habit is small: record the full state — edition, amendments, corrigenda — in the frozen design basis, and treat every amendment issued mid-project as a change-control event, not a background update. The alternative is discovering the amendment through a review comment that cites it.