Slot Relocation Move Plan Plan ordered asset moves between declared single-occupancy slots.
Plan ordered asset moves between declared single-occupancy slots. Supply sourceRevision, slots with unique IDs, initialPlacements and exactly one desiredPlacements assignment for every initially placed asset. Slot and asset identities are opaque, case-sensitive ASCII labels of 1 to 48 letters, digits, underscores, periods, colons, pipes or hyphens. Every slot reference must be declared; each asset and occupied or desired slot is unique. Set the required nullable bufferSlotId field to null for no designated buffer, or name a declared slot that is initially empty and is never desired. The policy repeatedly moves the first asset in initial placement order whose desired slot is empty. When only closed cycles remain, it moves the first remaining asset to the designated buffer, then resumes desired moves. Fixed placements need no move; a swap needs three moves and a three-asset cycle needs four. If any closed cycle needs a buffer and none is designated, the whole request returns blocked with its cycles, zero orderedMoves and identical initial and final inventories, including any acyclic work that otherwise could proceed. Other unused empty slots are not temporary buffers under this policy. A blocked result describes this restricted move policy, not physical impossibility. Inventory retains declared slot order, unchangedAssets contains assets with no proposed move, and blocked cycle traversal follows initial placement order. Up to 128 declared slots and 128 assets are supported within the shared 36,000-byte, 6,000-node, depth-24 input profile and 500,000-byte output guard. These are workload bounds. Duplicate or unknown identities and an occupied or desired buffer reject the whole request during preflight. This deterministic supplied-record plan does not move anything, authorize work, model travel, weight, access or handling constraints, prove physical feasibility, or promise global optimality. 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.