ChangeLock freezes the requested material change, requires independent approval, revokes old authority, applies one field, and requests a new ReleaseLock evaluation.
Capability map
Carrier, driver, tractor, trailer, origin, destination, facilities, windows, risk, policy, seal information, and critical instructions cannot be casually replaced.
Requester and approver separation, active scope, strong authentication, versions, and deadlines are rechecked inside the command.
The current backend enforces a numeric approval threshold; carrier-security plus customer-security approval domains are not yet guaranteed.
Current decisions and unused credentials are revoked before the approved value changes.
Applying a change never creates new authority. A later persisted evaluation must consider the updated shipment state.
See it in context
Use fictional shipment data to explore a valid arrival, a blocked mismatch, a protected change, and a replay attempt.