This section has no reviewed German translation yet. The English edition 1.0 is shown below.

READER MODELong-form reading surface.

§9.6 · BUILDING · 3 MIN READ · EDITION 1.0

Sunsetting a capability responsibly

Stopping a capability needs the same discipline as starting one: a decision record, a communication to affected users, a transition plan for the manual process it replaced, and retained evidence of why it was stopped.

A quietly abandoned tool that users still occasionally invoke is worse than a formally retired one; ambiguity about whether a capability is still supported is itself a control gap.

Retain the qualification history and incident record even after sunset — a later, similar use case can learn from why the earlier one was stopped.

PUT THIS INTO PRACTICE

  1. 01Communicate sunset decisions to all affected users.
  2. 02Restore or confirm the manual process before switching off the capability.
  3. 03Retain qualification and incident history after sunset.

RELATED INSTRUMENTS

CITE THIS SECTION

§9.6 · Edition 1.0 · Sunsetting a capability responsibly

English is the authoritative text of this edition. Where a translation differs, the English text governs.