首页 > AI前沿 > DataCupid: Stable Matching Repair for Training Data Acquisition with Delayed Feedback

DataCupid: Stable Matching Repair for Training Data Acquisition with Delayed Feedback

arXiv机器学习 2026-10-09 11:59 3 阅读 查看原文

Matching repair after utility changes can reuse valid observations, but new evaluations must respect matching capacity and may return out of order.

We study announced invalidations with bounded, possibly reward-dependent reporting delays and pending evaluations that do not occupy future matching capacity.

Residual load repair (RLR)

Residual load repair (RLR) combines sound outcome certificates with batched matching schedules for unequal sample deficits.

Its complete dyadic quota schedule admits a sharp issue-round bound with coefficient cb < 1.607 relative to the terminal residual endpoint load, together with separate delay and evidence-lifetime bounds.

RLR-P monitors complete issue-order prefixes without changing the sampling plan before acceptance.

Oracle Efficiency

With a deterministic pure oracle, a single-repair coupling from the same drained initial state guarantees no increase in certification time, issued observations, or time to a reusable checkpoint.

We also derive an information-load lower bound.

PrioritySearch on Fixed Priority-Star Markets

On fixed priority-star markets with unknown Bernoulli gaps, PrioritySearch attains the history-adjusted first-order constant for expected certification time as δ {\sim} 0, under hypothesis-independent linear history scaling and sublogarithmic reporting delays.

Simulation and Feedback

Paired simulations and measured-feedback replay quantify the trade-offs: in the replay, RLR-P has lower mean capped update-certification time than a monitored width-based baseline, at higher oracle CPU cost.