Apply the fixed selection rule below. This is a record-serialization adapter, not a new evaluation of answer quality. It is not a separate selector specified by SPO's published Algorithm 1. Deterministic application without a model call is the study default. If used as a model prompt, its call and any failure count toward the adaptation budget and its output must be checked against the rule. Use only the pair IDs and four comparison records. Do not request or inspect task answers, assessor material, external scores, comparator rationales, candidate prompts, histories, or memory. Do not change the rule or break a tie using an opinion about quality. The vote counts below are internally generated pairwise decisions, not independent assessor scores. A valid record has one distinct round number from 1 through 4, a_id and b_id equal to the two distinct supplied pair IDs in either order, and choice exactly A or B. Map A to a_id and B to b_id. A null choice is invalid. Missing, duplicate, extra, malformed, or incorrectly mapped records make the entire comparison incomplete. Do not repair them or synthesize a vote. If exactly four valid records cover rounds 1, 2, 3, and 4, count votes for each pair. Accept the candidate only if its votes strictly exceed the incumbent's. A 2-2 tie keeps the incumbent. If the comparison is incomplete, keep the incumbent regardless of any valid votes; set both vote totals to null rather than presenting partial counts as a completed decision. Return one JSON object, no Markdown or additional text, with exactly these keys: { "incumbent_id": , "candidate_id": , "comparison_complete": , "incumbent_votes": , "candidate_votes": , "accept_candidate": , "selected_id": , "reason": <"candidate_majority", "incumbent_majority", "tie_keep_incumbent", or "incomplete_keep_incumbent"> } Replace every angle-bracket specification with a JSON value. If complete, vote totals must sum to four. No additional memory, confidence, explanation, or quality score is permitted in the output. INCUMBENT_PAIR_ID_JSON {{INCUMBENT_ID_JSON}} CANDIDATE_PAIR_ID_JSON {{CANDIDATE_ID_JSON}} COMPARISON_RECORDS_JSON {{COMPARISON_RECORDS_JSON}}