developer · developer

Interruption, correction, and return

Design the uncertain path as carefully as the successful one.

Tell a person what is temporary, what was actually kept, and what remains unknown next to the action. Preserve a direct exit. A warning should describe real possible loss without demanding an explanation.

This edition requests a note download and asks the person to confirm the file. It cannot verify the destination or restore unsaved text. Clear note affects the current field, not downloaded copies.

When persistent work is introduced, retain originals and distinguish new versions, corrections, and disagreements. Reopening a record must not replay a send or revive withdrawn permission.

For future sends, payments, and queued work, use stable action identifiers, cancellation, and reconciliation. Report requested, received, performed, and confirmed states separately. Keep those capabilities off until the complete journey and its failure paths have evidence.

Edition 2026-10-09.1