how about n agreeing oracles, chosen by the contracting parties ? or do you prefer m out of n? not a point of failure. but go ahead, build that secure source. more options, better.
Having this type of logic within a TX's opcodes just seems like the wrong place for it. How would a smart contracts be validated after the fact if an outcome is changed due to ruling?