Serial Component Occupancy Replay Replay serial component occupancy across declared assembly slots.
Replay serial component occupancy across declared assembly slots. Supply a source revision, baseline and cutoff sequences, exact assembly-slot tuples, known serial IDs, placements immediately after the baseline and uniquely sequenced install or remove events. Sequences are nonnegative safe integers. The cutoff must be at or after the baseline, and every event must be strictly after the baseline and at or before the cutoff. Events at the cutoff are applied; events outside this window reject the input rather than being silently ignored. Events run in ascending sequence order regardless of input order. At every step, a slot contains at most one serial and a serial occupies at most one slot globally. An install requires an empty declared slot and an unassigned known serial. A remove must name the exact serial currently in that slot. Assembly-slot identities use collision-safe tuples, so delimiters in labels cannot merge different slots. The report returns half-open closed occupancy intervals [start,end), open occupancy intervals with a null end, all final declared slots including empty slots, chronologically replayed events and unassigned known serials. A baseline interval starts at the observation baseline, not an inferred original install time. A null end means no end was observed as of the cutoff and makes no guarantee about later occupancy. Initial intervals retain supplied placement order, followed by installs in sequence order. Duplicate serial IDs, slot tuples, initial placements, event IDs or event sequences, unknown references, impossible chains and invalid replay boundaries reject the entire request during preflight, including a late invalid event. No state survives between calls. Up to 128 slots, 128 known serials, 128 initial placements and 256 events 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. This supplied-record replay does not install, remove or authorize anything and does not prove serial identity, physical placement, provenance or genealogy; it is distinct from static serial genealogy and hardware assignment closeout. 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.