Auto-cancel noise suppression.

The problem

When a posted load times out uncovered, the shipper auto-generates a cancellation-request email to the senior brokers. Routine, high volume, and it buries the rare email that matters: a carrier bailing on a load that was already committed. Preempting the routine ones by hand cost a median of 1h11 of attention per load.

How it works

• The platform already knows every posted load and its worst-case deadline clock. Auto-cancel releases loads past deadline in the TMS before the shipper's timeout fires, so the noisy email never gets generated.
• A cancel in this TMS is a one-way door: there is no un-cancel. So the invariant is re-checked with a live read immediately before the irreversible write. A timer alone can never fire it.
• The shipper does not auto-cancel overnight, so an overnight load is still coverable and gets deferred, not preempted. The business behavior is modeled, not steamrolled.
• The module splits three ways (pure decision, reads, the single irreversible write) so the decision logic is unit-tested without ever touching a live system that has no undo.
• When the TMS deprecated the status endpoint in September, the cancel failed loudly with the reason on screen, moved to the replacement endpoint the same day, and now reports every failure in words instead of a vanishing error.

// never cancel unless still an open quote with no carrier, re-read live immediately before the write

The result

Routine cancellation noise suppressed at the source. The important cancellations stand out again, and a median 1h11 of per-load manual attention went back to the desk.