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(prompts): retire parity order 019 now that /experiments and both write-ups are verified end to end
nirholas6f23779a12e0
diff --git a/prompts/finish/019-parity-05-experiments.md b/prompts/finish/019-parity-05-experiments.mddeleted file mode 100644index 37d7d03b4..000000000--- a/prompts/finish/019-parity-05-experiments.md+++ /dev/null@@ -1,61 +0,0 @@-# parity 05: /experiments, public write-ups of what we tried and what the numbers said--How to run: paste this file's repo path into a fresh Claude Code chat in this repository and say "run this work order". Runnable now, no gate.--## Operating clause (binding)--- Read CLAUDE.md first, then [_context/parity-00-CONTEXT.md](_context/parity-00-CONTEXT.md). CLAUDE.md overrides 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 names a crypto project other than $THREE, and destroying unrecoverable data. Where this order hits one, it says so, and you batch every such ask into ONE message after everything else is done.-- Never name Competitor X in anything you commit. If a reference is unavoidable, write "Competitor X".-- 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), re-check `git status` before each commit, and commit finished work promptly.-- Before committing, run `npm run check:rules -- --paths <files you touched>`. It must exit 0.--## Why this matters--Competitor X publishes its internal experiments with the method, the money spent (often under a dollar), the results, and "the parts we got wrong", including one that ended a project. It is the most credible thing on its site because no marketing team would write it. Its own founder-allocation experiment (7,215 launches) found that 0.40% of builders ever earned $500 and 35.6% of tokens never traded once.--three.ws already runs experiments but only for trading: `/sniper/experiments` (`pages/sniper-experiments.html`, `src/sniper-experiments.js`, data from `GET /api/sniper/experiments`, one entry per armed `agent_sniper_strategies` row) and the long-form `blog/autonomous-trading-experiment.html` plus `docs/trading-experiment.md`. There is no general `/experiments` index and no standard write-up format. `/experiments` is free (no route, page or `data/pages.json` entry).--How content is published today: docs pages are `docs/<slug>.md`, served at `/docs/<slug>` by the SPA `docs/index.html` (it fetches `/docs/<slug>.md` and renders it with `marked`), listed in `docs/nav.json` and `data/pages.json`. Blog posts are hand-written `blog/<slug>.html` files indexed in `blog/index.html`; `scripts/inject-blog-seo.mjs` upserts them into `data/pages.json`.--## Step 0: re-derive the current state-- grep -n '"/experiments' vercel.json; ls pages/experiments.html 2>/dev/null- curl -s "https://three.ws/api/sniper/experiments?network=mainnet&window=7d" | head -c 600; echo- sed -n 1,60p docs/trading-experiment.md- sed -n 1,40p docs/research/launchpad-landscape-2026-09.md--## Tasks--1. **The format.** `data/experiments.json`: one entry per experiment with `slug`, `title`, `question`, `published` (date), `spend_usd`, `status` (`running`, `concluded`, `killed`), `doc` (the write-up's docs slug), and optional `live_url` (for example `/sniper/experiments`). Write-ups are `docs/experiments-<slug>.md` following one template, in this order: The question; Method (data window, tables or tools, sample size); Spend; Result (the numbers, with the SELECT or script that produced them in a closing appendix so anyone can re-run it); What we got wrong; What we changed because of it. A small validator (in `scripts/build-page-index.mjs` or its own script run by `build:pages`) fails the build on a missing field or a `doc` that does not exist.-2. **The index page.** `/experiments`, wired per the context file: cards from `data/experiments.json` with the question, status, spend and date, newest first, filter by status; each opens its write-up at `/docs/experiments-<slug>`. Empty and error states designed.-3. **Two first write-ups, from real data measured this session:**- - **The agent-to-launch funnel.** How many agents were created in the last 30 days, by how many users, and how many launched a coin (`agent_identities`, `pump_agent_mints`); how many token plans were saved; the landscape doc measured 788 agents and 3 launches in the 30 days to 2026-09-28. Re-measure; report what the numbers say and what we changed or will change.- - **The trading experiment.** Index the existing one (link `/sniper/experiments` as `live_url`, its doc and blog post), writing only the template sections it lacks.- Every number is measured this session by a SELECT-only script whose SQL goes into the appendix. Nothing is estimated or rounded to flatter.-4. **Link and document.** Footer Resources, `/docs/start-here`, `docs/nav.json` group, `data/pages.json` entries (index and each write-up), `STRUCTURE.md` row, changelog entry per published write-up. A short `docs/experiments.md` (or a section of the index doc) says how to add one.--## Definition of done--- [ ] `/experiments` lists both experiments from `data/experiments.json`, each opening a write-up with all six template sections.-- [ ] The validator fails the build on a missing field (shown by a red run on a temporary bad entry you then remove).-- [ ] Every number in the write-ups has its query in the appendix, and re-running the queries reproduces them (evidence in the report).-- [ ] Browser-verified at 375, 768 and 1440 px, both themes, zero console errors; `npm run audit:docs` and `npm run audit:links` pass.-- [ ] Page index, nav, `STRUCTURE.md` and changelog updated.--## Never blocked--| Blocker | Resolution (act, do not ask) |-|---|---|-| A finding is unflattering | Publish it. That is the point of the section. State what we changed. |-| A number cannot be measured (table missing, access denied) | Say "not measured" and why; never substitute an estimate. |--## 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. If every Definition of done line passes, delete this file in that same commit (`git rm prompts/finish/019-parity-05-experiments.md`) and append a dated entry to [_context/parity-PROGRESS.md](_context/parity-PROGRESS.md) with the commit SHAs. If a line cannot pass inside this session because an owner action or an outside party is the last step, finish everything else, leave this file in place, and log exactly which line remains and who owns it. Never delete this file on a partial.-4. Final report, in this order: what step 0 measured; what changed (file list with commit SHAs); evidence for each Definition of done line; the single batched owner message, if the order has a gate; one-line judgment calls. No trailing questions.diff --git a/prompts/finish/_context/parity-00-CONTEXT.md b/prompts/finish/_context/parity-00-CONTEXT.mdindex 7fe7226ec..ef7a25cba 100644--- a/prompts/finish/_context/parity-00-CONTEXT.md+++ b/prompts/finish/_context/parity-00-CONTEXT.md@@ -50,7 +50,7 @@ Verify in a real browser: `npm run dev` (port 3000; reuse it if another agent is| [016](../016-parity-02-analytics.md) | `/analytics`: one page of live platform totals and growth | none || 017 (retired 2026-10-08) | Agents ranked by SOL earned on `/leaderboard` | needs 015 || [018](../018-parity-04-agent-as-paid-api.md) | Sell a whole agent as a paid x402 endpoint | none (buyers pay; test with the spend gate) |-| [019](../019-parity-05-experiments.md) | `/experiments`: public write-ups of what we tried and what the numbers said | none |+| 019 (retired 2026-10-08) | `/experiments`: public write-ups of what we tried and what the numbers said | none || [020](../020-parity-06-success-stories.md) | `/stories`: opt-in case studies with verifiable on-chain metrics | none || [021](../021-parity-07-three-fee-flow.md) | "Where every $100 goes" on `/three-token`, from the live split policies | none || [022](../022-parity-08-mcp-use-cases-and-safe-retries.md) | MCP docs as tool-call sequences; `retry_safe` on every post-payment failure | none |diff --git a/prompts/finish/_context/parity-PROGRESS.md b/prompts/finish/_context/parity-PROGRESS.mdindex 1a3ac93d4..ebba5435e 100644--- a/prompts/finish/_context/parity-PROGRESS.md+++ b/prompts/finish/_context/parity-PROGRESS.md@@ -56,3 +56,11 @@ Cross-session handoff for the `parity-` orders ([parity-00-CONTEXT.md](parity-00- Not live: production answers 404 for `/api/leaderboard/earnings` until the next deploy (order 919 / the owner). The snapshot behind the board was last refreshed at 04:36 UTC, so the page currently shows its stale notice. The fee-client port `233305db1` from order 015 ships in the same deploy and lets the cron refresh again.- Judgment calls: no OG variant, because `api/og-leaderboard.js` renders the $THREE holder card and has no tabs (the page uses `/api/page-og`). The regenerated feeds from `npm run build:pages` (CHANGELOG.md, public/changelog*.json/xml, features, llms, sitemap) were not committed: they also pull in other sessions' page entries that name a third-party crypto platform, which falls under the coin commit gate. The next build regenerates them from `data/changelog.json`.- Seen but out of scope: an agent page logs a console 404 from `/api/pump/coin` for a coin pump.fun no longer indexes (already noted under order 015).++## 2026-10-08: order 019, /experiments (closed)++- Step 0: already shipped on 2026-09-30 in `faedf00fb` (validated `data/experiments.json`, validator `scripts/lib/experiments-index.mjs` run by `build:pages`, `/experiments` page with a URL-synced status filter, both write-ups in the six-section template with SQL appendices, `docs/experiments.md`, footer, start-here, docs nav group, nav menu, `data/pages.json` entries for the index and both write-ups, STRUCTURE row, two changelog entries, `tests/experiments-index.test.js`). Never closed out. This session verified every Definition of done line.+- Queries: all 16 appendix SELECTs (7 funnel, 9 trading) re-run against the production database in read-only transactions reproduce every published figure exactly: 788 agents, 454 creators, 744 live, 208 with a wallet, 2 launched, 3 coins in window, 0 token plans, 509/315 prior window, monthly 26/7/47/7/3, 90 coins from 58 people and 65 agents; 28 strategies (11 enabled), 1,296 closed, 212 winners, -540,179,418 lamports on 9,144,352,384 deployed, rules 1,220/196 and llm 76/16, every exit reason, 15 paper trades, 357,988 verdicts and 16,860 buys, the retune split 241/1,055, the ladder 63 (+529,834,054) and 1,233 (-1,070,013,472).+- Validator: deleting `spend_usd` from the first entry made `npm run build:pages` exit 1 with `entry 0 (agent-launch-funnel): missing required field "spend_usd"`; restored, validates green, 14/14 unit tests pass.+- Browser (Vite on 3107, Playwright): `/experiments` and both `/docs/experiments-<slug>` pages at 375, 768 and 1440 px in dark and light, zero console errors and no horizontal overflow; each write-up shows all six template headings; the filter syncs `?status=` (running 1, concluded 1, killed shows its empty state with "Show all 2 experiments"); a forced empty index and a forced 500 render their designed states, the error state with a Retry button. The only console output was headless-GPU WebGL driver warnings.+- `npm run audit:links` passed. `npm run audit:docs` failed on 7 findings from other work committed today, fixed so it passes clean: `eaba66bc6` (README for `workers/agent-gateway`; order 045 still owns that worker's deploy files), `b86e0f1c9` (Oracle Desk `.env.example` force-added past the root `.env*` ignore so its README link resolves), `cc1e67273` (`/docs/grok` page entry), `b2a0e19a5` (four IBM Community drafts marked unpublished).