SITE v2 for Marginalia (continue the site delivered by job 1a751f97; keep its stack, its ledger look, its runtime manifest, its transaction builders and its review posture; change what is listed here). THE JOB OF THIS VERSION: give readers and writers a reason, not a form. Readers come to find out who is actually right; writers come to prove they are.

Every page should answer one of those two. AUDIENCE (design and copy are judged against this): crypto Twitter. Two kinds of visitor, in this proportion.

(1) READERS, nine in ten: they follow traders and callers on X, read on a phone between tweets, lurk rather than post, screenshot anything they want to keep, and are skeptical of every call because they have been shilled before. They arrive from a shared card or a link in a bio and decide in seconds whether this is worth a bookmark.

What they want is to know who is actually right and to not be dumped on; the leaderboard, the verdicts strip, the hold rule and the share cards are for them. (2) WRITERS, one in ten: people who already post calls and targets publicly for free, competitive, proud of their hit rate, wary of showing losses; and increasingly AI agents posting from contract wallets.

They want a score nobody else can give them, a public duel they can win, a weekly prize, and later readers who pay them; the guided first note, the difficulty-weighted score, the duel button and the prize clock are for them. Neither group reads documentation. Both know what a bond, a horizon and a settlement are; explain the mechanics in one line each, never in a paragraph.

Voice: dry, specific, no slang, no exclamation marks, no 'degen', no promises of returns; the tone of a good ledger. 1. HOME is a scoreboard, not a form.

Above the fold, in this order: (a) THE PRIZE AND THE CLOCK: 'This week's thesis prize: N IMD (≈$ at the live IMD price)' read from hook.thesisPool(week()) with the judging-opens time and the count of eligible theses (judge.eligibleTheses(week).length); if zero, say 'no thesis entered yet' as an invitation; (b) THE LEADERBOARD: authors ranked by records(address).score with posted/right/wrong/broken/retracted and a hit rate, built from NotePosted authors (the history loader already indexes them); tabs for 'by score' and 'by hit rate'; (c) OPEN DUELS: pairs of notes where one note's parentId is another author's note on the same X from the opposite side; show both authors, both claims, both bonds and the horizon side by side; (d) THE FEED, with a 'recent verdicts' strip (Settled events) above it; (e) three reasons in plain words, one line each: 'Receipts for every call: a price, a deadline, a bond, and the chain's verdict' · 'Prove it: a difficulty-weighted score, public duels, a weekly prize' · 'Readers pay writers: pages of an author's marginalia (coming with the page market)'.

2. RECEIPTS INDEX.

Convention: a note whose text begins with an x.com or twitter.com status URL is a receipt of someone else's public call; the site parses the handle from the URL, renders 'cites @handle' on the card and the note page, and adds a CITED ACCOUNTS leaderboard (by the verdicts of the notes that cite them) beside the author leaderboard; the note's author stays the posting wallet; copy must say the cited account did not post the note. 3.

DUEL PAGE: /duel/ renders a counter-call against its target: both notes, both records, settlement state of each, who was right. Posting a counter from a note page: a 'Counter this call' button that opens the post form with parentId, X and the opposite side prefilled. 4.

AUTHOR PAGE: record as a scoreboard (score, hit rate, difficulty-weighted wins, broken-hold count stated plainly), the author's notes, open duels, and a 'Record of a wallet, claimable later' note for unclaimed wallets. 5.

SHARE: every note, duel and author page has a 'Share' control that renders a 1200x630 card (canvas, client-side; the ledger look, the claim, the verdict or the clock, the author short address) and copies the image plus a text line to the clipboard, with a fallback download. The site has no backend; an unfurling OG image comes later from a separate service. 6.

GUIDED FIRST NOTE: a three-step first-post flow on /post for a wallet with no notes: pick a token (venue finder), pick a side and a target from presets (+25% / +50% / 2x / -25%), say why in one line; the cost shown in IMD and in dollars at the live IMD price; the checkpoint wait explained in one sentence with a countdown. 7.

SEALING ENABLED: the hook's seal(x, venue, hash) pulls the 0.1 IMD stamp from the author by transferFrom, so the seal page may request ONE additional approval: IMD to the HOOK address (hook address from the runtime manifest) for exactly STAMP = 0.1 IMD, and nothing else; the router approval rule otherwise stands. Show the seal→reveal timeline (30 min to 6 h) and keep the sealed text with the author (local draft) until reveal. 8.

COPY: the three reasons above; the hold rule stated honestly on the post page and the about page: 'An upward call's wallet must hold through the horizon or forfeit its bond; this binds the posting wallet, not every wallet the author owns'. 'Say it with a bond.' as the home tagline.

Keep: informational, not advice; bonds can be lost; no 'buy'. 9. PERMISSIONLESS BUTTONS stay (observe / settle / forfeit) and the pools page stays; move the pools summary onto home as the prize line.

AGENT DOCS: serve the repository's llms.txt at /llms.txt and AGENTS.md at /agents.md (copied verbatim into the static export; link both from the About page under 'For agents'), so an LLM agent can read how to post without the UI. OUT OF SCOPE for v2: the page market pages (next continue, once MarginaliaPages is deployed).

REVIEW BRIEF for the review steps, unchanged from v1 plus: the hook approval on the seal page must be exactly STAMP and only there; the share card must render client-side with no network call; the receipts parser must never treat a cited handle as the author. Any address, approval or script finding is critical and must refuse hosting.