consequential-actions
Separate Approve, Reject, and Request Changes
Specify approval outcomes by consequence, reason rule, resulting state, and next owner instead of relying on button order.
Updated 2026-08-01
Publication archive
Technology-neutral interface patterns, state maps, and acceptance checks for small operational tools.
consequential-actions
Specify approval outcomes by consequence, reason rule, resulting state, and next owner instead of relying on button order.
Updated 2026-08-01
consequential-actions
Make selected, visible, filtered, eligible, skipped, and failed records explicit before and after a bulk action.
Updated 2026-08-01
consequential-actions
Choose confirmation, review, delay, or undo from the actual consequence and recovery contract—not from a universal delete-dialog rule.
Updated 2026-08-01
consequential-actions
Review row scope, active filters, field scope, freshness, exclusions, delivery, and server authorization before creating an export.
Updated 2026-08-01
consequential-actions
Distinguish browser-memory edits, recoverable drafts, saving, durable success, and save failure before adding a leave warning.
Updated 2026-08-01