Yonder

A prediction market platform

A mobile-first web product where a person bets YES or NO on real-world events using stablecoins. Outcomes resolve against reality, not against opinion. The bet this project makes is better clarity and onboarding than the existing markets, for people who follow the news and are not traders.

What you are holding is a finished design deliverable and its documentation. There is no application code, no server, no database and no build step, and that is deliberate: every screen below is a static file you can open. The panel on the left is the twelve stages that produced it, in order.

The product Event Feed The painted product, from its entry screen. Clickable end to end: feed, event, sign in, funding, your bets. Open this first. The handoff One page instead of an explanation What this package is and is not, which theme is primary, how it behaves, how to add to it, and who decides now. Open this second. The system Why it is like this The design system in five minutes, the traps it has already paid for, and the vitrine that shows every component on its own page.

No build, no server, no install

Clone the repository and open any file straight from disk, or read it published at the same addresses. Every painted screen links exactly one stylesheet and every page you can reach is a file that already exists.

If you are taking this over

Four documents answer what no rendered page can

A screen shows a state and cannot tell you what reaches it, what it is made of, or what it promises a reader who cannot use it the ordinary way. Start at the handoff page, which leads to all four.

Document	The question it answers
behaviour.md	What the product does: five flows step by step, every terminal and its recovery, the states each surface has, what each field enforces. Every row cites the source that already said it
map.md	Screen to zone to component to token to copy, taken from the code. Then the same data inverted, which is what it is for: if I change this token, what moves
a11y.md	Every accessibility ruling the system carries, each with the instrument that checks it and a status of two values, confirmed or debt
onboarding-gaps.md	What a reader with no context could not work out, and what they worked out wrongly. The second list is the expensive one

Everything else

The index is the README

README.md is the route to every folder and every source document, with the one status table. Three rules decide the rest of them, and they are in CLAUDE.md with the measurement that produced each one.

If you want	Open
the product, painted and clickable	ui-visual/event-feed.html
every component on its own page	ui-kit/overview.html
what the product is, as a product	PRODUCT.md
what was decided and why, dated	docs/decisions.md
what is still open	docs/backlog.md
where a file lives	STRUCTURE.md

This page is the front door and nothing else: it holds no fact of its own, so there is nothing here to go stale. The stage list on the left is rendered from assets/_roadmap.js, which is the one registry of it.