Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
docs(arena): document that a tournament result outranks an idle entrant
nirholas7eacd5a0180b
diff --git a/docs/trading-arenas.md b/docs/trading-arenas.mdindex 05ff51412..d7f7de1a0 100644--- a/docs/trading-arenas.md+++ b/docs/trading-arenas.md@@ -18,6 +18,8 @@ PvP trading tournaments. Anyone signed in can **create** one: pick the scoring mWhile a tournament runs, standings stream live over SSE every few seconds. Anti-gaming rules are enforced in the scoring, not the honor system: prize eligibility requires a minimum number of closed trades and unique coins, a churn ceiling, and — for prize brackets — trades with real on-chain signatures. Expand any standing row to see the entrant's trade-proof pills, each linking to the transaction on Solscan.+**A result beats no result.** An entrant that closed nothing inside the window ranks below every entrant that traded, whatever the scoring metric says. Without that rule, realized-PnL scoring hands a clean `0` to an agent that never traded and ranks it above every agent that took a real loss, so the podium fills with no-shows and the prize splits (which only ever pay *eligible* ranks) go unallocated. Idle entrants still appear on the full board, honestly labeled with their zero; they just sit under the agents who competed. The crown, the podium and the prize ladder go further and only ever name an entrant that has actually traded, so a tournament nobody has traded in reads as "awaiting the first ranked trade" rather than crowning a zero.+When it ends, the creator **closes** the tournament — which freezes the final ranking and **attests the podium on-chain** (a signed SPL-Memo transaction, `threews.tournament.v1`, linked from the page) — and then **settles** it, which pays each winner their $THREE cut as a real SPL transfer. Settlement is idempotent, and if the prize wallet isn't configured on a deployment the UI says **BLOCKED** with the reason rather than pretending it paid.**The Daily Arena runs itself.** You do not have to wait for someone to host a bracket: the house keeper (`/api/cron/arena-tick`, every 10 minutes, see [api/_lib/arena-house.js](../api/_lib/arena-house.js)) keeps today's Daily Arena live and tomorrow's queued, and enters every agent with a real trading mandate (an armed sniper strategy, or a real on-chain position opened recently) so the board is populated by agents that are actually trading. Auto-entry publishes nothing new: every agent it enters is already ranked by name, wallet and realized PnL on the public [leaderboard](https://three.ws/leaderboard), and an owner can withdraw an entry through the normal endpoint at any time. The Daily is ranked on realized PnL, the number a spectator can check row-by-row on Solscan.diff --git a/prompts/swarm-100/route-arena.md b/prompts/swarm-100/route-arena.mddeleted file mode 100644index 2c53cf39a..000000000--- a/prompts/swarm-100/route-arena.md+++ /dev/null@@ -1,119 +0,0 @@-# Route audit: /arena (The Arena: live PvP trading tournaments)--How to run: paste this file's repo path into a fresh Claude Code chat in this-repository and say "run this work order". This file is fully self-contained:-it depends on no other prompt file anywhere. If neighboring files in-prompts/swarm-100/ are gone, that work is done; if present, ignore them.-Every claim below rots; step 0 re-measures, and what you measure wins.--## Operating clause (binding)--- Read CLAUDE.md first. Its rules override everything, including this file.-- Finish 100% in this session. Never end the turn with a question, an option- list, or an unexecuted plan. A judgment call goes in one line of the final- report; it never becomes a question that halts work.-- The only permitted stops are the CLAUDE.md stop-and-ask gates: spending real- funds or any irreversible on-chain write, git push or a production deploy,- committing content that references a crypto project other than $THREE, and- destroying unrecoverable data.-- No mocks, no fake data, no placeholder stubs, no unfinished-work markers, no- commented-out code. Real APIs and real integrations only.-- The em-dash and en-dash characters are banned in everything you write.-- Concurrent agents share this worktree: stage explicit paths only (never a- bare add-everything), and commit finished work promptly.-- Before committing, run: npm run check:rules -- --paths <files you touched>.- It must exit 0.--## Step 0: re-derive the current state--1. This route's declared entry (path, description, added date):-- node -e "const p=require('./data/pages.json');for(const s of p.sections)for(const g of s.pages)if(g.path==='/arena')console.log(JSON.stringify(g,null,2))"--2. Find the serving implementation: grep "/arena" in vercel.json (the live- route table server/index.mjs boots from), then list matching files in- pages/ and src/. STRUCTURE.md maps every surface to its directory if the- grep is ambiguous.-3. Production right now:-- curl -so /dev/null -w '%{http_code}\n' https://three.ws/arena--4. Start (or reuse) the local dev server: npm run dev (vite, port 3000).--## Task: audit this one route end to end, then fix everything found--Route: /arena ("The Arena: live PvP trading tournaments", section "crypto").-Declared purpose: Time-boxed PvP tournaments where AI agents compete on real, verified pump.fun P&L. Live rankings, on-chain attested standings, and $THREE prizes for the winners.--Drive the page in a real headless browser. Playwright is already a dev-dependency; keep your probe script in the session scratchpad, never in the-repo.--1. Load http://localhost:3000/arena. Record the HTTP status, every console- error and warning, and every failed network request.-2. Exercise it like a first-time user: click the primary actions, run the- primary flow if one exists, follow the page's internal links. Every button- must do something real; every link must resolve. If the page renders data,- prove in the network log that it came from a live endpoint, not a baked-in- fallback array.-3. States: verify populated, empty, loading, and error states are designed and- reachable. Block the page's primary fetch in Playwright and confirm an- actionable error state appears, not a blank void or a raw exception.-4. Responsive: render at 320, 768, and 1440 px. No horizontal page scroll, no- overlapping or clipped controls.-5. Accessibility basics: one h1; interactive elements are real buttons or- links with visible focus states; images carry alt text; form fields have- labels.-6. Head: a specific title tag and meta description that match the declared- purpose above.-7. Fix every defect at its root in the page's real source files and re-run the- probe until clean. Defects in shared modules are in scope when this route- exercises them.--## Definition of done--- [ ] Local load of /arena: HTTP 200, zero console errors, zero unhandled- failed requests (a third-party outage must land in a designed fallback,- not a broken page).-- [ ] No dead interactive element on the page: no stub href="#", no button- without a handler, no link to a missing path.-- [ ] Empty, loading, error, and populated states verified.-- [ ] 320 / 768 / 1440 px renders verified clean.-- [ ] Title and meta description present and specific.-- [ ] npm test passes; npm run check:rules -- --paths <touched files> exits 0.-- [ ] Production status from step 0 recorded in the report; if production- needs a deploy to pick up a fix, the report says so (deploys stay- owner-gated).--## Never blocked--| Blocker | Resolution (act, do not ask) |-|---|---|-| Missing env var or credential | Check .env and .env.local, then the Cloud Run service env, then Secret Manager (the CLAUDE.md self-unblock playbook has the exact commands). If it truly exists nowhere, wire the code fully behind the env var, prove the wiring with a dry run, and name the single missing var in the report. |-| gcloud not on PATH | Run: export PATH="$HOME/google-cloud-sdk/bin:$PATH" |-| Dev server port 3000 busy | Another agent may be serving this repo; probe it and reuse if so. Otherwise start your own on a free port: npx vite --port 3101 |-| Playwright browser missing | npx playwright install chromium |-| A surface needs a signed-in user | Register a fresh account through the real /register flow against the real API and use it. Never mock the session. |-| A defect sits in code you did not touch | Fix it if it blocks a Definition of done line (root cause it, never mask it). Otherwise note it in the report and continue. |-| An unrelated test is red | Same rule. Never pipe npm test through tail; it masks exit codes. |--## Close out (required)--1. Verify every Definition of done line with the actual command output in- front of you. Never claim a line you did not verify.-2. Commit with explicit paths and a subject that describes the diff (house- style: type(scope): what changed and why a reader cares).-3. Delete this prompt file in that same commit:-- git rm prompts/swarm-100/route-arena.md-- The shrinking directory is this campaign's only progress ledger; there is- no progress log to update.-4. Final report: what step 0 measured, what changed (file list), evidence per- Definition of done line, and any one-line judgment calls. No trailing- questions, no unexecuted plans.--If a line genuinely cannot pass inside this session (an external party must-respond, or an owner-gated action is the final step), finish everything else,-leave this file in place, and state exactly which line remains and who owns-it. Never delete this file on a partial.