Publish an independently verified immutable ready-event catalog

[proerror77]

Parent

#314

What to build

Publish an append-only catalog of qualified Polymarket events. The producer qualification bytes from #318 are an untrusted carrier. Only an independent verifier that reopens and rehashes authenticated objects may append an authoritative ready, partial, or rejected catalog receipt. Catalog queries return event-local capabilities and authenticated object identities without rereading mutable sibling paths or treating producer self-report as a trust anchor.

The continuously-ready product contract is BTC x 300 seconds only. SOL or any other symbol/horizon is rejected until a separate verified contract exists.

Acceptance criteria

• Evidence identity is market_id plus independently verified content digest. Each verification revision is a separate immutable receipt keyed by its full receipt digest, including producer-qualification-byte digest and verifier identities; no path or receipt may be overwritten.
• A ready receipt binds the independent verifier source/binary, configuration and policy digests, authenticated OSS identity for data/manifest/_SUCCESS, verified content and manifest digests, exact BTC/300-second event window, Up and Down token identities, sequence/completion proof, reference and settlement coverage, availability clocks, and supported research tasks.
• Ready cohort queries return exact receipt digests, filter by supported task, and use deterministic ordering; they never infer a mutable latest receipt.
• Partial means independently authenticated but incomplete evidence. Missing/nonexistent objects, corrupt bytes, impossible settlement timing, unsupported product, contradictory sequence or identity, or producer/evidence mismatch are rejected rather than accepted as producer-declared partial.
• Partial and rejected receipts remain queryable with typed reasons but are excluded from ready cohort selection.
• Promotion re-verifies bound bytes and external trust anchors rather than trusting producer carrier strings, local sidecars, status fields, or mutable object keys.
• Event-local queries isolate complete events from incomplete siblings; a sibling cannot fill, reject, or alter another market.
• Counterexamples reject a wrong trust anchor, token swap, symbol/window mismatch, SOL/unsupported horizon, mutable object identity, missing independent verification, settlement completion before event close, sequence mismatch, and a producer-ready record whose bytes fail verification.

Blocked by

#336, then #337

Out of scope

Snapshot materialization, cohort/partition construction, Mission admission, evaluator or MCTS behavior, database services, mutable latest pointers, and production deployment.

[proerror77]

Completed by merged PR #348 (fe48eab78a683ceece835863a91a58890cc6d967): independently verified append-only ready-event catalog, focused package validation, and all required CI gates passed. Closing the stale issue so downstream #320/#326 dependencies reflect the merged contract.