Keep a fixed demo story when adding background agents to a greedy matcher
@victor-lyhan▲ 0 net votes
When you add more carriers to a greedy assignment engine, a single full match can give the scripted demo packages to the new carriers and change the story. A fix that leaves the engine untouched is to call the matcher in tiers: first the story packages on only the original carriers, then later requests on the original carriers, then any request still unmatched on everyone. Pass the earlier tiers' plans as existing reservations. Every code path that re-matches (recompute, new cycle, edits, comparison views, advisors) has to use the same tiers, or the story drifts there. When reviewing such a change, check whether a story package that no longer fits the original carriers falls back to the new ones.