Skip to content

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.

docs(changelog): record the partner spotlight scheduler and new partner records in the changelog and structure map

nirholase8aaaba5b0f3
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 670b4d0cb..8ab72b6a2 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -30,7 +30,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Trenches Pulse** (`/docs/trenches`): How the Trenches Pulse surface is wired: the vendored Pulse service, the allowlisted /api/trenches proxy, the /trenches page, local run steps and the Cloud Run deploy notes.
- **Web Desktop** (`/docs/desktop`): How the three.ws web desktop works: the CTRL Mica theme, taskbar and Start menu, snappable windows that frame real pages, deep links, saved layout, the classic view and how to add an app.
- **3D viewers no longer flood the browser console, and /trenches stops hammering an offline feed**: Every page with a 3D model viewer moved to model-viewer 4.4.0, the first release that both decodes our compressed avatars and drops the debug lines 4.3 printed for every model on the page. The trenches dashboard now checks the feed once and backs off while it is offline instead of sending five requests every 15 seconds, and desktop app windows no longer trigger a fullscreen-attribute warning. (`/marketplace`) `[fix]`
-- **A daily partner spotlight on X: one partner, one feature built on it, filmed live every day**: @trythreews now features one partner from the partners page every day, with a thread on something three.ws built on that partner's technology. Each spotlight is filmed working against production that morning, so the reel is proof rather than a promo, and it rotates between a card, a GIF, the reel and generated art for its head. Every sentence comes from a partner registry with evidence behind it, the program name is stated exactly as the partner grants it, and nobody is tagged. The spotlight owns the prime-time slot, and three days are kept in stock so a bad run never leaves the slot empty. (`/partners`) `[feature, docs]`
+- **A daily partner spotlight on X: one partner, one feature built on it, filmed live every day**: @trythreews now features one partner from the partners page every day, with a thread on something three.ws built on that partner's technology. Each spotlight is filmed working against production that morning, so the reel is proof rather than a promo, and it rotates between a card, a GIF, the reel and generated art for its head. Every sentence comes from a partner registry with evidence behind it, the program name is stated exactly as the partner grants it, and nobody is tagged. The spotlight owns the prime-time slot, and three days are kept in stock so a bad run never leaves the slot empty. Once a week the series also publishes a partner deep-dive as an X Article: every feature built on that partner, filmed that day, with the runs, the evidence behind each sentence, the real requests and responses, and inline frames from the reels. (`/partners`) `[feature, docs]`
- **A page for every three.ws app: Android, Solana Seeker, iPhone, desktop and the web desktop**: The new Apps hub lists every way to run three.ws, each with its own page: the web desktop, the Android app (APK download), Solana Seeker (live on the dApp Store, Seed Vault sign-in and Genesis Token verification), iPhone and iPad (what runs today and what the native build adds once Apple enrollment clears), and the Windows and Linux desktop app, whose download button reads the live release feed and picks the right file for your system. (`/apps`) `[feature]`
- **A registry of every place three.ws is listed**: The listings registry tracks 121 surfaces across MCP directories, x402 directories, aggregators, cloud marketplaces, awesome-list pull requests and press, with a command that re-fetches every live entry so a dropped listing shows up. (`/docs/listings-registry`) `[docs]`
- **API keys can no longer arm spenders or move payout addresses without the wallet scope**: Sixteen routes that accept an API key could arm something that spends or redirect where money lands, for any key at all. They now require the wallet:write scope: the treasury autopilot, the auto-launcher, the market maker, live Oracle watches, the pump buyback and distribute policy, signal subscriptions, recurring agent charges, team tasks that hire paid agents, agent orders and spending mandates, an agent's wallet address, a skill listing's proceeds split, animation payout addresses, a Launchpad page's payout wallet or pricing, and opening or re-terming a vault. Pausing, cancelling and closing stay open to any key, and editing an agent no longer lets a narrow key raise its spend limits or change its payment fallbacks. (`/docs/mcp`) `[security, fix]`
diff --git a/STRUCTURE.md b/STRUCTURE.md
index 47751de8a..514e4435c 100644
--- a/STRUCTURE.md
+++ b/STRUCTURE.md
@@ -381,7 +381,7 @@ bottom.
| Internationalization (i18n) | Runtime [src/i18n.js](src/i18n.js) `→ /i18n.js`; catalogs [public/locales/](public/locales) (`en` + 84 locales, `manifest.json`, `localized-pages.json`); pipeline [scripts/i18n-annotate.mjs](scripts/i18n-annotate.mjs) · [i18n-extract.mjs](scripts/i18n-extract.mjs) · [i18n-translate.mjs](scripts/i18n-translate.mjs) (Vertex Gemini, glossary-locked) · [i18n-backfill.mjs](scripts/i18n-backfill.mjs) (re-translates copy that was baked to English during a backend outage); hreflang in [api/sitemap/[type].js](api/sitemap/%5Btype%5D.js) | Live (85 languages) | LobeHub-model client-side copy swap. `npm run i18n:annotate` auto-injects `data-i18n*` into static HTML (byte-surgical), `i18n:extract` builds `en.json`, `i18n:translate` fans it out to every locale via Vertex with brand/protocol terms masked. `i18n:backfill` finds keys whose value is still byte-identical to English (the silent failure mode: a baked fallback is present, so every later run skips it) and re-translates them. Runtime auto-detects locale, mounts a floating `<lang-switcher>`, and injects hreflang. Doc: [docs/i18n.md](docs/i18n.md). Tests: [tests/i18n.test.js](tests/i18n.test.js), [tests/i18n-annotate.test.js](tests/i18n-annotate.test.js), [tests/i18n-backfill.test.js](tests/i18n-backfill.test.js). |
| 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) | 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. 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 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) | 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) |
| 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/data/changelog.json b/data/changelog.json
index bcdd8f3a7..3cbcab319 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -5,7 +5,7 @@
"date": "2026-10-11",
"title": "A daily partner spotlight on X: one partner, one feature built on it, filmed live every day",
"link": "/partners",
- "summary": "@trythreews now features one partner from the partners page every day, with a thread on something three.ws built on that partner's technology. Each spotlight is filmed working against production that morning, so the reel is proof rather than a promo, and it rotates between a card, a GIF, the reel and generated art for its head. Every sentence comes from a partner registry with evidence behind it, the program name is stated exactly as the partner grants it, and nobody is tagged. The spotlight owns the prime-time slot, and three days are kept in stock so a bad run never leaves the slot empty.",
+ "summary": "@trythreews now features one partner from the partners page every day, with a thread on something three.ws built on that partner's technology. Each spotlight is filmed working against production that morning, so the reel is proof rather than a promo, and it rotates between a card, a GIF, the reel and generated art for its head. Every sentence comes from a partner registry with evidence behind it, the program name is stated exactly as the partner grants it, and nobody is tagged. The spotlight owns the prime-time slot, and three days are kept in stock so a bad run never leaves the slot empty. Once a week the series also publishes a partner deep-dive as an X Article: every feature built on that partner, filmed that day, with the runs, the evidence behind each sentence, the real requests and responses, and inline frames from the reels.",
"tags": [
"feature",
"docs"
diff --git a/public/changelog-recent.json b/public/changelog-recent.json
index 578edd562..ef07b6b48 100644
--- a/public/changelog-recent.json
+++ b/public/changelog-recent.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-10-11T20:20:26.258Z",
+ "generated_at": "2026-10-11T20:28:39.141Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -223,7 +223,7 @@
"date": "2026-10-11",
"type": "update",
"title": "A daily partner spotlight on X: one partner, one feature built on it, filmed live every day",
- "summary": "@trythreews now features one partner from the partners page every day, with a thread on something three.ws built on that partner's technology. Each spotlight is filmed working against production that morning, so the reel is proof rather than a promo, and it rotates between a card, a GIF, the reel and generated art for its head. Every sentence comes from a partner registry with evidence behind it, the program name is stated exactly as the partner grants it, and nobody is tagged. The spotlight owns the prime-time slot, and three days are kept in stock so a bad run never leaves the slot empty.",
+ "summary": "@trythreews now features one partner from the partners page every day, with a thread on something three.ws built on that partner's technology. Each spotlight is filmed working against production that morning, so the reel is proof rather than a promo, and it rotates between a card, a GIF, the reel and generated art for its head. Every sentence comes from a partner registry with evidence behind it, the program name is stated exactly as the partner grants it, and nobody is tagged. The spotlight owns the prime-time slot, and three days are kept in stock so a bad run never leaves the slot empty. Once a week the series also publishes a partner deep-dive as an X Article: every feature built on that partner, filmed that day, with the runs, the evidence behind each sentence, the real requests and responses, and inline frames from the reels.",
"link": "/partners",
"tags": [
"feature",
diff --git a/public/changelog.json b/public/changelog.json
index d053099bf..237441e6f 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-10-11T20:20:26.236Z",
+ "generated_at": "2026-10-11T20:28:39.120Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -220,7 +220,7 @@
"date": "2026-10-11",
"type": "update",
"title": "A daily partner spotlight on X: one partner, one feature built on it, filmed live every day",
- "summary": "@trythreews now features one partner from the partners page every day, with a thread on something three.ws built on that partner's technology. Each spotlight is filmed working against production that morning, so the reel is proof rather than a promo, and it rotates between a card, a GIF, the reel and generated art for its head. Every sentence comes from a partner registry with evidence behind it, the program name is stated exactly as the partner grants it, and nobody is tagged. The spotlight owns the prime-time slot, and three days are kept in stock so a bad run never leaves the slot empty.",
+ "summary": "@trythreews now features one partner from the partners page every day, with a thread on something three.ws built on that partner's technology. Each spotlight is filmed working against production that morning, so the reel is proof rather than a promo, and it rotates between a card, a GIF, the reel and generated art for its head. Every sentence comes from a partner registry with evidence behind it, the program name is stated exactly as the partner grants it, and nobody is tagged. The spotlight owns the prime-time slot, and three days are kept in stock so a bad run never leaves the slot empty. Once a week the series also publishes a partner deep-dive as an X Article: every feature built on that partner, filmed that day, with the runs, the evidence behind each sentence, the real requests and responses, and inline frames from the reels.",
"link": "/partners",
"tags": [
"feature",
diff --git a/public/changelog.xml b/public/changelog.xml
index 975908fd0..1a93052a1 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -180,7 +180,7 @@
<guid isPermaLink="false">2026-10-11:A daily partner spotlight on X: one partner, one feature built on it, filmed live every day</guid>
<pubDate>Sun, 11 Oct 2026 12:00:00 GMT</pubDate>
<category>feature</category>
- <description>@trythreews now features one partner from the partners page every day, with a thread on something three.ws built on that partner's technology. Each spotlight is filmed working against production that morning, so the reel is proof rather than a promo, and it rotates between a card, a GIF, the reel and generated art for its head. Every sentence comes from a partner registry with evidence behind it, the program name is stated exactly as the partner grants it, and nobody is tagged. The spotlight owns the prime-time slot, and three days are kept in stock so a bad run never leaves the slot empty.</description>
+ <description>@trythreews now features one partner from the partners page every day, with a thread on something three.ws built on that partner's technology. Each spotlight is filmed working against production that morning, so the reel is proof rather than a promo, and it rotates between a card, a GIF, the reel and generated art for its head. Every sentence comes from a partner registry with evidence behind it, the program name is stated exactly as the partner grants it, and nobody is tagged. The spotlight owns the prime-time slot, and three days are kept in stock so a bad run never leaves the slot empty. Once a week the series also publishes a partner deep-dive as an X Article: every feature built on that partner, filmed that day, with the runs, the evidence behind each sentence, the real requests and responses, and inline frames from the reels.</description>
</item>
<item>
<title>A page for every three.ws app: Android, Solana Seeker, iPhone, desktop and the web desktop</title>
diff --git a/public/features.json b/public/features.json
index 113c3e9ae..23964e560 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-10-11T20:20:26.221Z",
+ "generated_at": "2026-10-11T20:28:39.106Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",