How would decentralized fleet assignment handle a network partition?
Instruction: Fictional simulator: agents A and B both believe they own pickup P after a network partition. The dispatcher has a durable assignment generation number; only its current generation is valid. Specify the assignment protocol, reconciliation and metrics. This concerns fleet scheduling, not steering control.
Updated
Worked answer
Use the dispatcher-authorized assignment ID and generation as the source of truth. Local bids or swarm scores propose assignments; they do not independently authorize two agents to fulfill P. Before committing a pickup workflow, verify the current assignment through the defined authorization path. If the partition prevents that verification, retain an explicit pending/unconfirmed state and use the simulator's approved service fallback rather than promise both agents own the job.
After reconnecting, reconcile P against the durable generation, cancel stale scheduling work, notify the affected service workflow and record delay/duplicate-attempt evidence. A generation check must be enforced at the operation boundary; merely attaching a number to a message does not prevent a stale agent from acting. The exercise requires an enforcement mechanism consistent with the physical pickup workflow.
Measure assignment conflicts, unserved demand, waiting time and recovery duration under injected partitions. Compare with the centralized baseline; local heuristics may improve ordinary allocation while worsening recovery. Never let scheduling optimization override the independent validated driving controller.