hackathon entry · Meta Global AI Developer Hackathon (Cerebral Valley) · Indie Developer track

QorTime AI.
AI explains.
It never decides.

QorTime existed before the event: the signed match receipts, the referee and the QorCap capture app. What was built during the hackathon week (Mon Oct 26 – Wed Nov 4, 2026) lives in the public repo github.com/ConWan30/qortime-ai.

This page describes a hackathon entry. It is a solo build by Contravious Battle. It is not endorsed, certified or partnered with by Meta or Cerebral Valley.

The rule: AI explains, it never decides

The verdict comes only from QorTime's pre-existing deterministic verifier, which checks a signed, hash-chained receipt and returns VERIFIED, PARTIAL, SELF-SIGNED or FAIL. Meta models explain that result and stress-test the verifier. Their output lives in separate signed sidecar files next to the receipt.

Advisory signals can only lower a result, and only as far as PARTIAL: VERIFIED can become PARTIAL, nothing else. They never raise a status and never fail a match. Deleting or tampering with the AI files never changes the verdict.

  1. 01

    Explain · Muse Spark

    A signed plain-English explanation of the referee's result. A deterministic guardrail drops any text that misstates the status or overclaims, and it fails closed: no key, an error or a guardrail hit means no explanation. It is signed with a separate AI advisory key, never a referee key.

    Muse Spark is also a second, independent reader of every locked score. Agreement changes nothing. A disagreement can lower VERIFIED to PARTIAL. Unsure means unchecked, with no penalty.

  2. 02

    See · SAM 3.1 Evidence Lens

    “What the referee saw”: SAM 3.1 video-tracks the scorebug starting from the referee's own scorebug-reading region, on the public highlight clips of match 170123, with cited Muse Spark captions. It is a visualization, not a referee input.

  3. 03

    Challenge Echo · SAM 3.1

    During a pause challenge, each logged D-pad press should show up as a move of the pause-menu highlight on screen. SAM 3.1 tracks that highlight and deterministic code does the matching. It is information only; a mismatch can at most lower VERIFIED to PARTIAL.

  4. 04

    Stick Echo · SAM 3.1

    SAM 3.1 tracks the player being controlled, and deterministic code checks that the on-screen movement follows the logged left stick, one fixed lag later, against swapped-log baselines. On private practice games that were never sent to the referee (totals only), controller and video agree on two of three games under settings fixed in advance. It is information only; a clear disagreement can at most lower VERIFIED to PARTIAL. It does not show who held the controller.

    Not player measurement: here SAM 3.1 outputs no skill, speed, route or play-quality numbers. It only checks that the on-screen movement follows the controller's stick input in time.

  5. 05

    Red-Team the Referee · Muse Wonder

    Muse Wonder wrote 26 receipt-tampering attacks once, cached so the run is offline and repeatable. They run against the unmodified pre-existing verifier on a synthetic match with freshly generated test keys, never a real key or the live referee. As an outside attacker without signing keys: 25 attacks, 0 accepted.

    As an insider holding the test signing keys, 12 of 25 were accepted, labelled “needs key protection”. That includes 5 inner-check gaps in the pre-existing verifier, reported and left unchanged.

  6. 06

    Also this week

    • Show Your Hands: a verified-input overlay and press-to-pixel check. A Muse Spark filter can only remove candidates; it is lower only, capped at PARTIAL.
    • Automatic advisory job run by the referee after the verdict is final. It never delays or changes it.
    • Advisory fetch and verifier auto-pin of trusted referee keys, plus browser panels for the signed advisory files.
    • Commentary witness: Muse Voice Transcribe and Muse Spark compare a recorded match's broadcast calls with the locked scores. Information only; tested on match 170123's three public clips.
    • Agent verify API: a public, read-only API and MCP endpoint, so an AI agent can check a match page and only record it as VERIFIED when the signed receipt says so.
    • Caption timing from Muse Voice Transcribe event streams.

    Full list and file-by-file origin in the qortime-ai README

  1. 170123

    Match 170123 · VERIFIED

    Madden, Oct 23, 2026 (CT), before the event. Away 10 – home 0. Co-signed by the official referee key qortime-online-s2.

    Open match 170123

  2. 220105

    Match 220105 · VERIFIED

    Madden, Oct 27, 2026 (CT), played and verified during the event week. Away 7 – home 21. Co-signed by qortime-online-s2. The final came through the referee's end-of-game menu fallback, and the page discloses the advisory flag alignment_not_above_chance.

    Open match 220105

Check any receipt yourself in the verifier. It runs in your browser.

Limits, stated plainly

Two referee-verified matches is a small sample (n = 2), not a measured accuracy. Both are Madden on PS5, one player's own matches, with one side recorded. The referee spot-checks video segments rather than re-hashing all of them. QorTime does not prove who held the controller and does not catch collusion. The full match recordings are not published; they stay on the player's PC.

Not affiliated with Meta, Cerebral Valley, EA, the NFL or Sony. Madden NFL is a trademark of its owner.