Deviations,handled in the open.
Physical commerce deviates. Ships get delayed. Lots get damaged. Demand softens. Every scenario below has a defined process and a defined record. Revised statements never overwrite ledger entries, they reference them.
The bulk order does not proceed. Reserved credits return to each participant in full, with no fee deducted. The event is recorded as a cancellation on the cycle record.
If a supplier ships late, the cycle window shifts and participants are notified. If delays exceed contract bounds, the platform may exit the contract and refund the cycle.
Affected units are quarantined at the hub. If material, the cycle is paused for replacement or partial refund. Documented in the cycle exceptions log and reflected in settlement.
Settlement reflects what occurred, line-by-line. The cycle statement shows realised pricing per channel. Outcome marked as below base case in the archive.
Cycles are priced in local currency where feasible. For cross-border lanes, hedging policies apply per the Trust page. Currency variance shows on settlement as its own line.
Carrier insurance covers transit damage. Last-mile damage is investigated through carrier exception flows. Resolution and credit (if any) appear on the revised settlement statement.
Never edited. Exceptions are recorded as additional entries referencing the originals.
Per-cycle log visible to all cycle participants. Includes timestamps and evidence hashes.
Supersede the original where material. Original statement remains retrievable in archive.
Documented downside.Published archive.
Cycles that settled below base case are archived next to those above it. Selective history would make the good record meaningless.