WORK SAMPLE ·Resolution Auditor·live Limitless markets

I pointed the resolution linter at Limitless's own live markets.

Ambiguity is the bug that causes resolution disputes. This tool fetches Limitless's real active markets through a Cloudflare Worker proxy and scores each one's resolution criteria against an 8-point rubric, then lets you lint your own draft. It runs live, on the company's actual book.

ⓘ Independent work sample by Edward Tay for the Limitless Content Specialist application. Not affiliated with or operated by Limitless. Market data is public and fetched live; the scoring is a heuristic checklist, not a verdict.
← The playbook
Fetching live markets from api.limitless.exchange…

The 8-point rubric

Ordered by how often each one, when missed, produces a resolution dispute. The live audit and the linter both run these exact checks.

1 · Named settlement source

One primary source specific enough to check. Relying only on "a consensus of credible reporting" is the same subjective standard UMA leaned on in Polymarket's disputed Zelenskyy "suit" market: it reads as a source but is a judgment call.

2 · Exact resolution time + timezone

A date, a clock time, and a timezone. "By end of year" and "on election night" are the classic ambiguities. Prefer UTC or a stated zone.

3 · Sharp YES / NO boundary

A trader must compute the outcome themselves. Both branches stated; inclusive vs exclusive at the threshold explicit ( vs >).

4 · Tie / void / no-event rule

What happens if the event is postponed, annulled, never occurs, or ends in an exact tie. Silence here is a dispute waiting to happen.

5 · No vague quantifiers

"Significant", "major", "soon", "well". Each is a subjective call the resolver gets argued with. Replace with a measurable threshold.

6 · Measurable threshold

For numeric markets: an explicit number and operator. above $100,000, not "a new high". Units and currency stated.

7 · Source-failure fallback

If the primary source is unavailable, revised, or delayed at resolution, the rule says what the resolver does next.

8 · Boundary precision

"By March 1" includes or excludes March 1? "Closing price" of which session? Pin the exact instant and whether endpoints are inclusive.

How the audit works

A Cloudflare Worker fetches Limitless's active markets from api.limitless.exchange (the API sends no CORS headers, so a proxy is required), strips the HTML from each resolution description, and returns them to this page. Each market is scored in your browser by the same deterministic 8-point checker the linter uses: named-source and consensus-reliance detection, date / time / timezone tokens, YES and NO branches, tie and void language, a vague-quantifier dictionary, numeric operators, and fallback phrasing. Nothing is a model call and nothing is a verdict on the market. It catches the structural gaps that cause most resolution disputes, so a human writer knows where to look first. If the live API is unreachable, the page falls back to a saved snapshot of real markets so it still runs.