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(x): document the $THREE post-impact report and chart view, add its changelog entry and log the open verification
nirholas070e98ef79ef
diff --git a/STRUCTURE.md b/STRUCTURE.mdindex d6f3b1b1f..cdcc1c538 100644--- a/STRUCTURE.md+++ b/STRUCTURE.md@@ -72,6 +72,7 @@ packages, a generated standalone GitHub mirror). See| Anatomy (machines as interactive cutaways) | Page [pages/anatomy.html](pages/anatomy.html) + [src/anatomy/](src/anatomy) `→ /anatomy` and `→ /anatomy/:id` (spec contract [spec.js](src/anatomy/spec.js), streaming scanner [stream.js](src/anatomy/stream.js), shapes, effect shaders, [viewer.js](src/anatomy/viewer.js), embeddable UI `mountAnatomy` in [runtime.js](src/anatomy/runtime.js)), API [api/anatomy.js](api/anatomy.js) `→ /api/anatomy` over [api/_lib/anatomy/](api/_lib/anatomy) (writer ladder, spec guide, service, store), agent skill [.agents/skills/anatomy/](.agents/skills/anatomy) (reference.md generated by [scripts/build-anatomy-skill.mjs](scripts/build-anatomy-skill.mjs)) | Built and verified locally | One line becomes an isometric wireframe cutaway: a model writes a JSON spec that the page draws part by part while it streams, then saves to a permalink. Real part motion (spin, oscillate, slider-crank, pulse) with inherited hierarchies, WebGL flame/exhaust/plasma/water/smoke/steam/sparks/arc shaders, particle flows, a focus-framing tour, explode, section, x-ray and part inspection. Agents author specs directly with the skill and save them via `action: "publish"`. Docs: [docs/anatomy.md](docs/anatomy.md). Tests: [tests/anatomy.test.js](tests/anatomy.test.js), browser check [scripts/verify-anatomy-browser.mjs](scripts/verify-anatomy-browser.mjs) || Scene Composer (dress an avatar) | [pages/compose.html](pages/compose.html) `→ /compose` + [src/scene-compose.js](src/scene-compose.js) | Live | Forge props from text and parent them to a rigged avatar's skeleton bones, then Export GLB or save them back onto the avatar record as `appearance.attachments`. Bones are grouped into readable regions and stripped of rig prefixes; transform gizmos, 50-deep undo, grid snap, camera presets. Feeds off [api/forge.js](api/forge.js), [api/forge-gallery.js](api/forge-gallery.js) (own creations, falling back to the community showcase for a first-time visitor), [api/explore.js](api/explore.js) `?source=avatar&only3d=1` for the avatar picker, and `PATCH /api/avatars/:id` for Save outfit. Below 900px the scene panel becomes a drawer. Docs: [docs/compose.md](docs/compose.md) || Splat Viewer (photoreal Gaussian avatars) | [pages/splat.html](pages/splat.html) `→ /splat` + page module [src/splat-viewer.js](src/splat-viewer.js), renderer [src/splat-stage.js](src/splat-stage.js) | Live | Renders Gaussian-splat and radiance-field scenes in the browser, the photoreal output of capture engines like GaussianAvatars and HumanGaussian. Loads a `.ply`, `.spz`, `.splat`, `.ksplat` or `.sog` by URL, by upload, by drag-and-drop onto the stage, or from a `?src=` deep link, plus two procedurally generated samples; decoding is entirely client-side and nothing is uploaded. The format is sniffed from the bytes rather than the filename, and the URL loader rewrites GitHub `blob`/`raw`, Hugging Face `/blob/` and Dropbox links to their CORS-enabled raw form so a pasted human-facing link still fetches. [src/splat-stage.js](src/splat-stage.js) is shared with the Forge Studio Lab ([src/forge-studio/lab/mesh-to-splat.js](src/forge-studio/lab/mesh-to-splat.js)) and wraps [Spark](https://github.com/sparkjsdev/spark) (`@sparkjsdev/spark`, MIT), lazy-loaded on first render and torn down explicitly (the WebGL context is released by hand on every scene swap, which Spark's own dispose stops short of). Every state is designed: idle/drop, engine load, fetch, decode, sort, error, and a live HUD carrying the scene label, its real splat count, a recenter control and a download of the loaded buffer. Docs: [docs/splat.md](docs/splat.md) |+| X post reader and video tool | Shared reader [api/_lib/x-syndication.js](api/_lib/x-syndication.js), endpoints [api/x-video/extract.js](api/x-video/extract.js) + [api/x-video/download.js](api/x-video/download.js), page [pages/x-video.html](pages/x-video.html) `→ /x-video` + module [src/x-video.js](src/x-video.js) | Live | One keyless reader for public X posts: text, author, likes/replies/reposts/quotes/views/bookmarks, timestamps and every mp4 variant. Three rungs in order (X syndication, fxtwitter, guest-token GraphQL when `X_BEARER_TOKEN` is set); a rung that fails falls through, and only an all-rungs "gone" answer becomes `post unavailable` (404). It replaced oEmbed (text only) in `pumpfun_social_x_post_impact` ([api/pump-fun-mcp.js](api/pump-fun-mcp.js)) and [src/social/x-post-impact.js](src/social/x-post-impact.js). The free `/x-video` page extracts a post and offers one download per quality; the download proxy accepts only https `video.twimg.com` and `pbs.twimg.com`, refuses credentials and ports, and never follows redirects. Docs: [docs/x-video.md](docs/x-video.md) || Creator portfolio (human profile) | [pages/profile.html](pages/profile.html) `→ /u/:username` (self-view `/profile`), backend [api/users/[username].js](api/users/%5Busername%5D.js) + paginated [api/users/[username]/creations.js](api/users/%5Busername%5D/creations.js) `→ /api/users/:username/creations` | Live | Every three.ws user's public portfolio: avatars, agents, widgets, skills, plugins, coins, memories, items for sale, and (added 2026-07-12, extended 2026-07-23) a **Creations** tab merging forged 3D models + Scene Studio worlds + Material Studio restyles — real, live, spinning `<model-viewer>` cards, cursor-paginated for 100+ items. `/forge`, `/diorama`, and `/restyle` all stay anonymous by default (no login required); a signed-in creator's `user_id` is attached to `forge_creations`/`dioramas` rows at generation/save time (migration [api/_lib/migrations/20260712010000_creator_portfolio_user_ids.sql](api/_lib/migrations/20260712010000_creator_portfolio_user_ids.sql)) and to a new `material_restyles` row per AI restyle or colorway variant (migration [api/_lib/migrations/20260723140000_material_restyles.sql](api/_lib/migrations/20260723140000_material_restyles.sql), store [api/_lib/material-restyle-store.js](api/_lib/material-restyle-store.js)) so those creations surface here. The same opt-in attribution now links back from the diorama viewer HUD, the diorama gallery cards, and the forge result bar ("by @user") whenever a creation's creator is known. `/@:handle` ([pages/handle.html](pages/handle.html)) is a separate, narrower agent-embed page — not the human portfolio. || Model detail page (`/m/:id`) | [pages/model.html](pages/model.html) `→ /m/:id`, page module [src/model-page.js](src/model-page.js) + pure helpers [src/model-lib.js](src/model-lib.js) + [src/model.css](src/model.css), backend [api/forge-creation.js](api/forge-creation.js) (`?related=&view=` + voted state; `DELETE`, scoped to the owning `x-forge-client`, lets a creator erase a creation, its stored GLB, preview, and recorded source uploads included) and [api/forge-comments.js](api/forge-comments.js), store reads [api/_lib/forge-store.js](api/_lib/forge-store.js) (`getPublicCreation`/`listRelated`/`recordCreationView`), schema [api/_lib/migrations/20260805120000_model_page.sql](api/_lib/migrations/20260805120000_model_page.sql) | Live | Every finished forge model as a first-class page in the classic model-platform detail layout: interactive viewer hero with AR and fullscreen, title + creator card with a real follow button (follow graph), live triangle/vertex stats from `GET /api/3d/inspect` (nothing persisted, nothing invented), the full prompt as the description, honest attribute chips, anonymous likes shared with the Forge-Off vote rail (`forge_votes`, same `forge:cid` id), a real page-view counter (`forge_creations.view_count`), a signed-in comment thread (`forge_comments`, bell-notifies the creator via the `comment` event type), paid remix via the existing x402 rail, embed/share/download, and a same-category suggested-models rail. Linked from the Details button on `/creations` cards and the Forge showcase. Tests: [tests/model-lib.test.js](tests/model-lib.test.js) || Labs (hidden-gems hub) | [pages/labs.html](pages/labs.html) + [src/labs.js](src/labs.js) `→ /labs` | In-repo | Data-driven discovery hub: renders every `data/pages.json` entry flagged `showcase: true` as a live card (status check + iframe preview), filterable by category |@@ -401,7 +402,7 @@ packages, a generated standalone GitHub mirror). See| Shared utilities (import instead of hand-rolling) | Frontend [src/shared/markdown.js](src/shared/markdown.js) · [src/shared/toast.js](src/shared/toast.js) · [src/shared/fuzzy.js](src/shared/fuzzy.js) · `timeAgo`/`toEpochMs` in [src/shared/coin-format.js](src/shared/coin-format.js); backend [api/_lib/resilience.js](api/_lib/resilience.js) · [api/_lib/mem-cache.js](api/_lib/mem-cache.js) · [api/_lib/pool.js](api/_lib/pool.js) · [api/_lib/csv.js](api/_lib/csv.js); ops [scripts/check-cron-drift.mjs](scripts/check-cron-drift.mjs) | Live · doc [docs/shared-utilities.md](docs/shared-utilities.md) | Thin layers over vetted packages, each replacing a family of hand-rolled copies that had drifted. `markdown.js` = `marked` + `DOMPurify`, the single sanitized path for model/user text reaching `innerHTML` (the concierge SDK carries its own copy at [concierge-sdk/src/markdown.js](concierge-sdk/src/markdown.js) because it ships as an independent bundle). `toast.js` = one aria-live region with a real queue. `fuzzy.js` = `@leeoniya/ufuzzy` ranking + typo tolerance + match ranges for both command palettes. `resilience.js` = `cockatiel` circuit breakers **and** jittered retry (`withRetry`, `parseRetryAfter`, `isRetryableError`). `mem-cache.js` = `lru-cache` with true recency eviction and single-flight `cached()`. `pool.js` = `p-limit` bounded concurrency. `csv.js` = RFC 4180 quoting **plus** spreadsheet formula-injection neutralization. `check-cron-drift.mjs` = `cron-parser` validation of every cron declared in vercel.json against live Cloud Scheduler, sharing its job-id derivation with [scripts/create-gcp-scheduler.mjs](scripts/create-gcp-scheduler.mjs) so the two can never disagree. Tests: [tests/shared-markdown.test.js](tests/shared-markdown.test.js), [tests/fuzzy.test.js](tests/fuzzy.test.js), [tests/csv.test.js](tests/csv.test.js), [tests/resilience-shared.test.js](tests/resilience-shared.test.js) || Announcement factory (internal) | Calendar [scripts/announce-plan.mjs](scripts/announce-plan.mjs) `npm run announce:plan`, factory [scripts/announce-kit.mjs](scripts/announce-kit.mjs) `npm run announce:kit`, engine [api/_lib/announce/](api/_lib/announce), ranker [scripts/announce-rank.mjs](scripts/announce-rank.mjs), gate [scripts/check-announce.mjs](scripts/check-announce.mjs), packs [docs/announcements/](docs/announcements/README.md), deferrals [data/announce-deferred.json](data/announce-deferred.json) | Internal, owner-gated · doc [docs/announcement-factory.md](docs/announcement-factory.md) | Works the backlog of shipped surfaces nobody has posted about (322 of 429) into the X content queue, a batch at a time. The calendar is derived from the publisher's own cadence and rotation rules, so it can never promise a slot the scheduler would refuse, and a surface whose frame would carry live third-party market data is flagged for owner approval instead of being quietly packed. Each pack starts as an evidence brief (the rendered live page, the changelog, the docs, the README) whose every fact is already a check the verifier can run; the model chain drafts from that brief and nothing else, and the draft is held against the voice lint, the claims ledger, the evidence list and the account's own archive, then rewritten until it passes. A surface with no route (packages, workers, services) gets a title card typeset from its real README in the site's own fonts, because a post with no image measured 0.875x. Output is a pack plus a queue item at status `draft`: approval and publishing stay exactly where they were. Tests: [tests/announce-factory.test.js](tests/announce-factory.test.js) || X content pipeline (internal) | Queue [data/x-content/queue.json](data/x-content/queue.json), engine [api/_lib/x-content/](api/_lib/x-content), cron [api/cron/x-content.js](api/cron/x-content.js), CLI [scripts/x-content.mjs](scripts/x-content.mjs), media `public/x-media/` | Internal · docs [docs/x-content-pipeline.md](docs/x-content-pipeline.md), [docs/x-story-authoring.md](docs/x-story-authoring.md), [docs/x-reply-playbook.md](docs/x-reply-playbook.md) | The reviewed @trythreews publishing queue: posts and threads with native images, GIFs, and captioned video, blog or external pages imported as native posts or full X Articles (via the X Articles API), a copy lint against automated-feed tells, jittered cadence with lane rotation, and a database ledger that resumes a half-sent thread instead of reposting. A post's video is a proof reel ([reel.js](api/_lib/x-content/reel.js)): a filmed, passing end-to-end run of its own scenario against production, so a feature that does not work cannot be announced. The queue learns from its own measured results ([outcomes.js](api/_lib/x-content/outcomes.js)), releases filmed posts by policy with a veto window ([approval.js](api/_lib/x-content/approval.js)), and can ship an approved post without a deploy as a signed bundle ([overlay.js](api/_lib/x-content/overlay.js)). A daily partner spotlight ([partners.js](api/_lib/x-content/partners.js), CLI [scripts/x-partners.mjs](scripts/x-partners.mjs), registry [data/x-content/partners/](data/x-content/partners), docs [docs/x-partner-series.md](docs/x-partner-series.md)) owns the prime-time slot: one partner and one feature built on it each day, filmed live, drafted from registry facts only, plus a weekly partner deep-dive X Article built from every feature's run, and a scheduled Cloud Run Job runner ([deploy/x-partners/](deploy/x-partners), setup [scripts/create-x-partners-job.mjs](scripts/create-x-partners-job.mjs)). Previews only until `X_CONTENT_AUTO_PUBLISH=true`. Tests: [tests/x-content.test.js](tests/x-content.test.js), [x-content-reel](tests/x-content-reel.test.js), [x-content-approval](tests/x-content-approval.test.js), [x-content-outcomes](tests/x-content-outcomes.test.js), [x-content-overlay](tests/x-content-overlay.test.js), [x-content-partners](tests/x-content-partners.test.js) |-| X post archive + engagement analysis (internal) | Snapshots [data/x-archive/](data/x-archive), schema [api/_lib/migrations/20260814120000_x_account_archive.sql](api/_lib/migrations/20260814120000_x_account_archive.sql), normalization + analysis [scripts/x-archive-lib.mjs](scripts/x-archive-lib.mjs), commands [scripts/x-archive-import.mjs](scripts/x-archive-import.mjs) · [scripts/x-archive-refresh.mjs](scripts/x-archive-refresh.mjs) · [scripts/x-archive-analyze.mjs](scripts/x-archive-analyze.mjs), report [docs/x-archive/](docs/x-archive) | Internal · doc [docs/x-archive.md](docs/x-archive.md) | Every post our own X accounts published, kept as raw snapshot files and indexed into `x_account_posts` / `x_account_post_snapshots` so engagement is a measured time series rather than a memory. `npm run x:archive:analyze` regenerates a report ranking posts by engagement and by engagement *rate*, and scores every measurable signal (media, mentions, length, subject, hour) as lift against the corpus median. Two scraper defects are handled rather than inherited: a profile scrape returns reposts of other accounts with `isRetweet: false` (authorship is read from the permalink instead), and X renders like counts lazily so real posts arrive at "0 likes" (those are archived, named, and excluded from the medians until `npm run x:archive:refresh` replaces them with exact X API counters). Distinct from `x_posts`, which is what platform users publish through [api/x/post.js](api/x/post.js). Tests: [tests/x-archive.test.js](tests/x-archive.test.js) |+| X post archive + engagement analysis (internal) | Snapshots [data/x-archive/](data/x-archive), schema [api/_lib/migrations/20260814120000_x_account_archive.sql](api/_lib/migrations/20260814120000_x_account_archive.sql), normalization + analysis [scripts/x-archive-lib.mjs](scripts/x-archive-lib.mjs), commands [scripts/x-archive-import.mjs](scripts/x-archive-import.mjs) · [scripts/x-archive-refresh.mjs](scripts/x-archive-refresh.mjs) · [scripts/x-archive-analyze.mjs](scripts/x-archive-analyze.mjs), report [docs/x-archive/](docs/x-archive) | Internal · doc [docs/x-archive.md](docs/x-archive.md) | Every post our own X accounts published, kept as raw snapshot files and indexed into `x_account_posts` / `x_account_post_snapshots` so engagement is a measured time series rather than a memory. `npm run x:archive:analyze` regenerates a report ranking posts by engagement and by engagement *rate*, and scores every measurable signal (media, mentions, length, subject, hour) as lift against the corpus median. Two scraper defects are handled rather than inherited: a profile scrape returns reposts of other accounts with `isRetweet: false` (authorship is read from the permalink instead), and X renders like counts lazily so real posts arrive at "0 likes" (those are archived, named, and excluded from the medians until `npm run x:archive:refresh` replaces them with exact X API counters). Distinct from `x_posts`, which is what platform users publish through [api/x/post.js](api/x/post.js). `npm run x:archive:price` ([scripts/x-archive-price-impact.mjs](scripts/x-archive-price-impact.mjs), logic in [api/_lib/x-content/price-impact.js](api/_lib/x-content/price-impact.js)) joins every post to the $THREE/SOL price at post time and its +1h/+4h/+24h returns against an any-time baseline, writes [public/data/trythreews-post-impact.json](public/data/trythreews-post-impact.json) for the Posts view on the $THREE oracle chart ([public/oracle-coin.js](public/oracle-coin.js)), and stamps the content pipeline's outcome rows with a +24h price return ([api/_lib/x-content/outcomes.js](api/_lib/x-content/outcomes.js)). Tests: [tests/x-archive.test.js](tests/x-archive.test.js) || X mention-reply bot + operator console | Reader [api/_lib/x-mentions.js](api/_lib/x-mentions.js), real-time webhook [api/x/webhook.js](api/x/webhook.js) `→ /api/x/webhook` (Account Activity API, CRC + HMAC signature verified, gated by `X_WEBHOOK_ENABLED`), pure intent parser [api/_lib/x-mention-intents.js](api/_lib/x-mention-intents.js), ledger [api/_lib/x-mention-store.js](api/_lib/x-mention-store.js) (`x_mention_events`), per-agent decisions endpoint [api/x/mention-decisions.js](api/x/mention-decisions.js) `→ /api/x/mention-decisions`, operator controls [api/_lib/x-mention-admin.js](api/_lib/x-mention-admin.js) (kill switch, blocklist, live-send), console API [api/x/ops/[action].js](api/x/ops/%5Baction%5D.js) `→ /api/x/ops/*`, console page [pages/x-ops.html](pages/x-ops.html) + [src/x-ops.js](src/x-ops.js) + [src/x-ops.css](src/x-ops.css) `→ /x/ops` (admin-only, noindex), health [api/_lib/x-mention-health.js](api/_lib/x-mention-health.js) feeding `/api/healthz`, public status [api/x/mention-bot/status.js](api/x/mention-bot/status.js) `→ /api/x/mention-bot/status` (shown on [/grok](pages/grok.html)) | Console: Live (admin-only) · Webhook: receives and records (not yet live-replying) · doc [docs/x-mention-bot.md](docs/x-mention-bot.md) (internal) | Every `@`-mention of a company or agent X account, delivered by polling or by the Account Activity webhook, is parsed into one of seven intents (never treated as an instruction to spend, transfer, launch or post on its own) and recorded once per tweet id before any reply is composed; a reply can be captured dry-run (recorded, never sent) or live. `/x/ops` is the admin review surface over that ledger: filter by account, intent, decision and dry-run status, read the full mention and would-be-reply text, pause or resume the bot (`app_settings` kill switch, also honored via `X_MENTION_BOT_PAUSED`), blocklist or unblock an author, and, for one dry-run `reply` row, send that exact already-composed reply live (company account via OAuth 1.0a, agent account via its own OAuth2 connection) behind an explicit "this posts publicly" confirmation. The enforcement side (a poll cron honoring the kill switch and blocklist, composing and sending replies automatically) is a separate piece of work tracked in the x-grok campaign; this console and webhook only ever write the switches and ledger rows they are responsible for. Tests: [tests/x-ops-authorization.test.js](tests/x-ops-authorization.test.js), [tests/api/x-webhook.test.js](tests/api/x-webhook.test.js), [tests/x-mention-health.test.js](tests/x-mention-health.test.js) || Interactive 3D history timeline | [pages/timeline.html](pages/timeline.html) `→ /timeline`, [src/timeline.js](src/timeline.js), data [data/timeline.json](data/timeline.json) | Live | three.ws's public history (launches, partnerships, listings, press, product ships) as an explorable 3D scene: 60+ milestones as glowing markers along a curved path, 360° free-orbit or a marker-to-marker Walk mode with a guide beacon (reuses the shared `AnimationManager` + default rig from [src/walk.js](src/walk.js)'s pattern), a synced bottom scrubber, category filters, and a detail panel linking to the original source where one exists (IBM Community, NVIDIA Developer Forums, Yahoo Finance, Phemex, CoinGecko, HackerNoon). Real accessible HTML-list fallback for no-WebGL or fetch-failure. || Upstream resilience toolkit | [scripts/resilience/](scripts/resilience) + [scripts/audit-upstreams.mjs](scripts/audit-upstreams.mjs) `→ npm run audit:upstreams`, baseline [data/upstream-baseline.json](data/upstream-baseline.json), generated map [docs/resilience.md](docs/resilience.md) | Live | Answers the question a fallback alone cannot: when a third-party service is down, what is each endpoint ALLOWED to say? An AST pass grades every outbound call site on five protections (deadline, retry, failover, last-good, breaker) and ratchets against a committed baseline, so a new unbounded call fails the build while the existing tail is paid down at its own pace. On top of it, endpoints declare a degradation contract (`may-serve-stale`, `must-refuse`, `must-not-serve-stale`) that [tests/upstream-degradation.test.js](tests/upstream-degradation.test.js) proves by replacing fetch with a dead upstream and judging the real response. Built after four fallbacks that each passed review turned out to serve remembered data on paths where staleness costs money or grants access. Complements [scripts/check-fetch-timeouts.mjs](scripts/check-fetch-timeouts.mjs), which enforces the deadline floor. Docs: [scripts/resilience/README.md](scripts/resilience/README.md) |diff --git a/_context/integrate-PROGRESS.md b/_context/integrate-PROGRESS.mdindex 12ccecb08..1a106c872 100644--- a/_context/integrate-PROGRESS.md+++ b/_context/integrate-PROGRESS.md@@ -14,3 +14,10 @@- Not verified, so prompts/finish/532 stays: (1) `curl /api/kol/tracker` and (2) the cron writing `oracle_narrative` rows both need the server and a database; this checkout has no `DATABASE_URL` and `node_modules` could not boot `server/index.mjs`. Owner of the remainder: whoever has the DB env, run `node server/index.mjs` with `--env-file`, hit `/api/kol/tracker`, then the cron.- `npm run build:pages` currently fails on another agent's changelog entry ("See whether our X posts move $THREE") which uses `tag` instead of `tags`.- Incident: my `npm ci` raced about 35 concurrent npm processes and left the shared `node_modules` incomplete (vitest, lru-cache missing). Run `npm ci` once when no other agent is installing.++## 2026-10-23: integrate 37, $THREE post impact on the chart (not fully closed)++- Built: `api/_lib/x-content/price-impact.js` (no-lookahead pricing, no interpolation, 3600s stale cap), `scripts/x-archive-price-impact.mjs` (`npm run x:archive:price`), `beforeTimestamp` paging in `api/_lib/market/ohlcv.js`, the Posts view in `public/oracle-coin.js` and `.css` ($THREE mint only), the `priceReturn24h` lift in `api/_lib/x-content/outcomes.js` and `runner.js`, tests in `tests/x-archive.test.js` and `tests/x-content-outcomes.test.js`. The code landed in sweep commits 0ad88fb38, 22a5a1f49, 2b7bb3921; docs and changelog are in the commit that touches this entry.+- Measured (live GeckoTerminal, 197 own posts, all priced): median +1h 1.59% (baseline -0.12%), +4h 1.61% (-0.68%), +24h -1.38% (-2.41%).+- Verified: Posts view with 197 bubbles at 390, 768 and 1280 px; 32 price tests passing in an isolated vitest install.+- Not verified: `npm test` and the full `tests/x-content-outcomes.test.js` in this checkout (shared `node_modules` is incomplete, see the integrate 33 entry), so prompts/finish/536 stays. Owner of the remainder: whoever runs `npm ci` once, then `npm test` and `npm run build:pages`.diff --git a/data/changelog.json b/data/changelog.jsonindex 4c24eb93a..ec1be7154 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -1,6 +1,15 @@{"$comment": "Curated changelog entries for three.ws, the editorial layer of the public changelog. New PAGE launches are tracked automatically via the `added` field in data/pages.json; this file is for everything else holders care about: improvements, fixes, SDK releases, trading/payments capabilities, security work. scripts/build-page-index.mjs merges both sources into CHANGELOG.md, public/changelog.json, and public/changelog.xml. Newest first. Allowed tags: feature, improvement, fix, sdk, infra, docs, security, desktop (desktop entries become the desktop app's release notes). `link` is optional and must be a live three.ws path.","entries": [+ {+ "date": "2026-10-23",+ "title": "See whether our X posts move $THREE: a Posts view on the coin chart",+ "summary": "The $THREE chart has a new Posts tab that plots every @trythreews post at the price it went out at, sized by engagement and coloured by the +4h return, each bubble linking to the post. Across 197 posts the median +1h and +4h return after a post was +1.6%, against -0.1% and -0.7% at arbitrary moments; the +24h median was -1.4% against -2.4%. The content pipeline now also records the +24h price return after each post and lets it nudge ranking, lightly, once enough posts carry one.",+ "tags": [+ "feature"+ ],+ "link": "/oracle/coin/FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump"+ },{"date": "2026-10-23","title": "KOL tracker shows follower counts without an X API key, and the Oracle reads KOL timelines",diff --git a/data/x-archive/README.md b/data/x-archive/README.mdindex a5029ff10..236353bee 100644--- a/data/x-archive/README.md+++ b/data/x-archive/README.md@@ -26,6 +26,27 @@ npm run x:archive:refresh # pull exact metrics from the X API into a new snapnpm run x:archive:analyze # rebuild docs/x-archive/<handle>-engagement.md```+A price command joins the archive to the coin:++```bash+npm run x:archive:price # $THREE price at each post and its +1h/+4h/+24h returns+```++It pages the $THREE/SOL pool's 15-minute candles from GeckoTerminal, prices each+own post (no reposts, no replies) at the close of the last bar that had finished+when it went out, and measures the return at each horizon. A return with no+price behind it (the post predates the pool, or nothing traded for over an hour+around either end) is `null`, never interpolated. Each horizon also carries the+same return measured at arbitrary moments (the baseline), because a coin that+drifts down every day makes every post look bad. The result is+`public/data/trythreews-post-impact.json`, which the **Posts** view on the+$THREE chart at `/oracle/coin/FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump`+reads: bubbles sized by engagement, coloured by the +4h return, each linking to+the post. The content pipeline stamps its own outcome rows the same way, so+`learnLifts` reports a `priceLifts` section (the +24h return after posts with+each attribute, shrunk by sample size) and `learnedScore` adds at most 4 ranking+points for it once 20 matured posts carry a measured return.+A fourth command pulls the long-form side of the account:```bash