Lot Split and Merge Balance Replay Replay lot splits and merges with exact quantity conservation.
Replay lot splits and merges with exact quantity conservation. Supply one product, one unit, an opaque source revision, initial lots and atomic events on a shared nonnegative sequence clock. Initial quantities are nonnegative safe integers; every consumed or produced leg is a positive safe integer. Events run in ascending unique sequence order, regardless of input array order. Each input lot must already exist with sufficient balance. Partial consumption leaves the remainder on that lot. Each output lot ID must be globally fresh across initial lots and all events, even if a previous lot is exhausted. Every event must consume and produce exactly the same total quantity. All request validation and replay occur during preflight before a quote; any invalid event rejects the whole request. No lot state survives between calls. The report retains every lot, including exhausted lots, in initial-lot order followed by event output order. Replayed events show exact consumed and produced legs, and event-level ancestry links identify parents and children. Those links do not allocate a particular parent quantity to a particular child or infer material composition, provenance authenticity or serial genealogy. This is quantity replay, distinct from a graph-only recall reachability review. Duplicate lot legs, record IDs or sequences, reused outputs, unknown or future input lots, overspending, imbalance and unsafe sums reject the input. Up to 128 initial lots, 64 events and 16 input and output legs per event are supported within the shared 36,000-byte, 6,000-node and depth-24 input profile and 500,000-byte output guard. These are workload bounds. W3C PROV-O supplies general derivation vocabulary; this profile defines exact-unit conservation. Use authorized, non-sensitive data. The report describes supplied records and does not change external systems.
Agent API guide → · Website orders show the report on your private order page.
Your input · JSON Load a small example The complete checkout request must fit within 40,000 UTF-8 bytes. Your input is validated again before an order is created.