Patterns in deterministic settlement/dispute con in P2P/oracle-resolved systems?

I'm working on (and hold IP around) an architecture pattern for P2P contest and oracle-resolved systems that focuses on deterministic settlement, dispute containment, and exactly-once execution between outcome resolution and payout.

The goal is to eliminate: - replay / double-settlement conditions - ambiguous resolution states - arbitration loops caused by partial failures or conflicting outcomes

The pattern introduces a reconciliation layer that gates settlement, enforces finality, and holds contested states for resolution before funds move.

I'm curious if anyone here has implemented or seen similar patterns in: - prediction markets - fintech / escrow platforms - marketplaces with disputes - gaming / contest systems

Interested in architectural feedback, pitfalls, or pointers to teams working on this class of problem.