The naive fix is a timestamp check. But timestamps lie — clock drift, late-arriving packets, firmware bugs. So I built a multi-signal arbitration engine that weighs event arrival time, signal strength, sequence continuity, and timestamp plausibility together before committing to a resolved state.

You POST your raw device payload to /v1/sign, then /v1/resolve. You get back a single authoritative state, a confidence score (0.50–1.0), a recommended_action enum (ACT / CONFIRM / LOG_ONLY), and a full arbitration trace showing exactly why it resolved the way it did.

The demo works right now with no signup — just grab the demo key from the landing page and fire a request. Happy to answer any questions about the arbitration logic.