Verify sealed Polymarket evidence semantics

[proerror77]

Change contract

Consume a descriptor-bound SealedPolymarketEvidenceTriplet and produce the sole trust-bearing VerifiedPolymarketEvidence handle only after event-local contracts, books, Chainlink references, Polymarket trades, and official settlements pass fail-closed semantic validation.

Out of scope

Research-snapshot mapping, OSS selection/download, trusted-digest acquisition, database import, collector publication, runtime activation, deployment, and live execution. Projection row structs are explicitly non-authoritative carriers; only the top-level verified handle carries trust.

Dependencies and merge order

Depends on merged #106. This PR is rebased directly onto main and supersedes #107, which GitHub auto-closed when the original stacked base branch was deleted after squash merge. Merge this PR before the verifier-test hardening and research-consumer layers.

Focused validation

• cargo fmt --all -- --check
• cargo metadata --locked --no-deps --format-version 1
• cargo test --locked -p ploy-market-data (18 passed on exact rebased head)
• cargo clippy --locked -p ploy-market-data --all-targets --no-deps -- -D warnings
• cargo check --locked -p ploy-research --bin monday-prediction-research
• Counterexamples cover stale/derived wire fields, reversed token arrays, mixed vocabularies, trade index/numeric/clock contradictions, Chainlink pre-open bounds, book clock/size/complement coverage, and settlement complement/winner/time contradictions.
• Exact-head code review: approved, no P0-P3 findings.
• Exact-head security review: approved after projection trust-name remediation, no P0-P3 findings.

Rollout and rollback

No runtime path, database, collector, deployment, or execution behavior changes. Rollout exposes a read-only verified handle for the next research-consumer layer. Roll back by reverting this PR; #106 may remain safely as a private unused decoder.

Scope exception

None. This layer is 743 non-generated changed lines (736 insertions, 7 deletions), below the 750-line split threshold.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[coderabbitai]

Warning

Review limit reached

@proerror77, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 31 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: d635cd38-f5cc-441f-9387-aa8ac76fa59a

📥 Commits

Reviewing files that changed from the base of the PR and between df5c348 and 02d601d.

📒 Files selected for processing (4)

• rust_hft/prediction-markets/crates/ploy-market-data/src/polymarket_evidence/artifact.rs
• rust_hft/prediction-markets/crates/ploy-market-data/src/polymarket_evidence/mod.rs
• rust_hft/prediction-markets/crates/ploy-market-data/src/polymarket_evidence/verified.rs
• rust_hft/prediction-markets/tasks/todo.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/polymarket-evidence-verified

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}