Make the next run safer.

Belief → failure → evidence → controlAn incident is not a footnote. It is the record of what the factory had to change.

Method: the incident archive publishes reviewed lessons from project work. Private repository records are not reproduced.

Put the lesson in the next check.

The incident archive contains reviewed accounts of failures and the controls that followed. The pattern register below collects risks in the reviewed project work. These are controls to keep, not additional incident reports.

The loop is only complete when the changed control is rerun against the same failure class and the result is recorded.
Turn a failure into a controlThe loop is only complete when the changed control is rerun against the same failure class and the result is recorded.View the system model (D2)
Read the diagram in text
  1. Observe · See the outcomeUse the real screen.
  2. Trace · Bind the claimUse the exact revision.
  3. Contain · Limit the harmStop unsupported action.
  4. Change · Update the controlFix gate or product.
  5. Recheck · Same failure classProve and record.

A confident answer can still be wrong.

The examples come from recurring project risks. Each one needs a control that survives the next run.

  1. Confident invention at a source gap

    Leave unknowns visible. Require a source for each factual claim and keep expansion behind the parity gate.

  2. Passing checks used to certify feel

    Tests can miss hierarchy, pacing and play quality. Inspect the screen in the real flow and intended viewport.

  3. Old proof attached to new code

    Bind a result to the exact source or release, then repeat the check after a change.

  4. One percentage hides changed scope

    Record what the denominator includes and when it changes. Name the work that remains.

  5. Simulation stands in for people and hardware

    Software checks cannot prove the device, environment or human path. Observe each physical boundary directly.

  6. Polish covers missing information

    Label promotional art, show the product state and next proof, and remove claims the source cannot support.