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-grok): write the mention-bot runbook and bring docs, STRUCTURE and the changelog up to what shipped
nirholas2cfa5363c5ee
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 52e08f81c..22a493451 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -7,7 +7,9 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr## 2026-10-11- **An agent set to Grok now answers as Grok everywhere, with a badge when it can't**: Profile chat, the agent editor's copilot, scheduled strategy runs, and the gateway all now read an agent's chosen brain through the same resolver, so picking Grok for an agent actually means Grok on every surface, not just the one where it was set. A Grok pick first tries the agent owner's own saved xAI key, then the platform's, before falling back to the free default chain. When Grok genuinely can't answer (no key reachable anywhere), profile chat now shows a small badge naming which model answered instead, so it's never a silent swap. `[improvement]`+- **Choose which @-mentions your agent answers, right from its editor**: An agent's Social tab now has an "Answer mentions" section: turn it on, keep it in dry run while you watch what it would say, cap it at a daily reply count, and pick exactly which kinds of mentions it may act on. A new decisions list on the same page shows the agent's own recent calls, what it decided and why, so the owner never has to ask an admin to check a console on their behalf. (`/agents`) `[feature]`- **Sentiment Scout's X reads gained a second, independent path through xAI**: The Sentiment Scout reads X for posts quoting a coin's exact contract address, as evidence a holder can open and check. When our own X search credentials are unavailable or rate limited, it now fails over to xAI's x_search tool, a second route to the same posts, metered by its own daily cap so an outage on one path never silently costs more than planned on the other. No change for anyone reading the Scout: the evidence looks the same either way. (`/docs/sentiment-scout`) `[improvement, infra]`+- **Share a finished Forge creation on X and it plays inline**: A link to a finished Forge creation now carries an X player card instead of a flat image: the post expands into the real 3D model, posed with its own poster frame and ready to orbit, through the same safe embed runtime the agent-profile embeds use (no audio or video element, HTTPS assets only). A creation that is still generating keeps the plain image card until it finishes, so a link never promises a model that isn't ready yet. (`/forge`) `[feature]`- **The @-mention reply bot now reports its own status, and /grok shows it live**: A new public endpoint, /api/x/mention-bot/status, answers whether the @-mention reply bot is live, in dry run, or paused, how many handles it has replied on, how many replies it sent in the last 24 hours, and its median reply time. No mention text or author identity is included. The /grok page now shows this as a live section, and /api/healthz carries the same signal as a platform subsystem, so an operator sees a wedged reply queue or a rising error rate within the hour it starts, instead of the bot quietly going silent with no signature anywhere. (`/grok`) `[feature, improvement]`## 2026-10-10diff --git a/STRUCTURE.md b/STRUCTURE.mdindex 9e4375c40..f93f33a03 100644--- a/STRUCTURE.md+++ b/STRUCTURE.md@@ -330,7 +330,7 @@ bottom.| 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)). 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 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 mention-reply bot + operator console | Reader [api/_lib/x-mentions.js](api/_lib/x-mentions.js), 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) | Console: Live (admin-only) | Every `@`-mention of a company or agent X account 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 (the poll cron honoring the kill switch and blocklist before replying) is a separate piece of work; this console only ever writes the switches and ledger rows it is responsible for. Tests: [tests/x-ops-authorization.test.js](tests/x-ops-authorization.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/data/changelog.json b/data/changelog.jsonindex 98f3b01e5..e284299c2 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -1,6 +1,20 @@{"$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-11",+ "title": "Share a finished Forge creation on X and it plays inline",+ "summary": "A link to a finished Forge creation now carries an X player card instead of a flat image: the post expands into the real 3D model, posed with its own poster frame and ready to orbit, through the same safe embed runtime the agent-profile embeds use (no audio or video element, HTTPS assets only). A creation that is still generating keeps the plain image card until it finishes, so a link never promises a model that isn't ready yet.",+ "tags": ["feature"],+ "link": "/forge"+ },+ {+ "date": "2026-10-11",+ "title": "Choose which @-mentions your agent answers, right from its editor",+ "summary": "An agent's Social tab now has an \"Answer mentions\" section: turn it on, keep it in dry run while you watch what it would say, cap it at a daily reply count, and pick exactly which kinds of mentions it may act on. A new decisions list on the same page shows the agent's own recent calls, what it decided and why, so the owner never has to ask an admin to check a console on their behalf.",+ "tags": ["feature"],+ "link": "/agents"+ },{"date": "2026-10-11","title": "The @-mention reply bot now reports its own status, and /grok shows it live",diff --git a/docs/x-mention-bot.md b/docs/x-mention-bot.mdnew file mode 100644index 000000000..7adb2ce93--- /dev/null+++ b/docs/x-mention-bot.md@@ -0,0 +1,236 @@+# The X @-mention reply bot++Internal operator runbook. Not a product surface: nothing here is linked from+the public site until the bot goes live (owner order 928). It documents the+pieces that answer an `@`-mention of `@trythreews` or one of our agents'+connected X accounts: how a mention becomes a decision, where that decision is+reviewed, and what is and is not wired yet.++For the sibling capability that lets an X account *sign in* to three.ws+(rather than be read as a mention), see the "Account linking" section below.+For the launch-by-mention intent (`launch <NAME> $<TICKER>`), see+`prompts/finish/925-parity-15-mention-to-launch.md`: it plugs its reply into+the same parser and the same ledger this doc covers, and this file is the one+place it should extend rather than write a second mention doc.++## Design rules++These come from `prompts/finish/_context/x-grok-00-CONTEXT.md` and apply to+every piece below, not just the ones that enforce them automatically yet+(see "What is not wired yet"):++1. **Mention text is untrusted.** A tweet, a bio, a quoted post, or image alt+ text is data, never an instruction. No path from it reaches a spend, a+ transfer, a launch, or a post to anyone other than the author who tagged+ us, in the same conversation.+2. **No spend through this path.** The bot can read, generate, and reply. It+ can never move funds, pay x402, or launch a coin itself; a launch intent+ only ever builds a `/launch` link the author reviews and signs themselves.+3. **Dry run by default.** Every write path is gated by an env flag+ (`X_MENTION_BOT_LIVE`) and, per agent, by that agent's own policy. With it+ unset, the pipeline reads, decides, and records what it would have+ replied, and posts nothing.+4. **Reply only when addressed**, one reply per mention, never to our own+ replies.+5. **`$THREE` is the only coin this bot promotes or recommends.**++## The ledger: `x_mention_events`++Every mention is recorded exactly once, before anything else happens. Table+`x_mention_events` (migration+[`api/_lib/migrations/20261008170000_x_mention_events.sql`](../api/_lib/migrations/20261008170000_x_mention_events.sql)),+keyed by `tweet_id` so two readers that both see the same mention race on one+`INSERT ... ON CONFLICT DO NOTHING` and exactly one wins the right to handle+it. Columns: which account was mentioned (`account_kind` company/agent,+`account_ref`), the author, the raw mention text, the intent the parser gave+it, the `decision` (`reply | skip | rate_limited | unsafe | budget | error |+pending | paused`, null while undecided), the reply text/media/link it sent+or would send, whether it was a `dry_run`, and timestamps. Reader/writer:+[`api/_lib/x-mention-store.js`](../api/_lib/x-mention-store.js)+(`recordMention`, `updateDecision`, `recentDecisions`, `adminListMentions`,+`adminCountMentions`, `countConversationReplies`). Polling cursors live in+`app_settings` under `x_mentions_cursor:<kind>:<ref>`, not in this table.++## Turning a mention into an intent++[`api/_lib/x-mention-intents.js`](../api/_lib/x-mention-intents.js) is a pure+module (no network, no DB, no clock): `parseMentionIntent` reads a normalized+mention and our account, and returns one of seven intents, deterministically:++| Intent | What it is |+|---|---|+| `make` | A 3D-model request from a text description. |+| `image3d` | Turn an attached, quoted, or replied-to image into a 3D model. |+| `avatar` | Turn the author into a rigged avatar (including "3D my pfp"). |+| `help` | Commands/usage, or any mention the parser cannot read safely. |+| `launch` | `launch <NAME> $<TICKER> [description]` grammar (925's intent). |+| `chat` | Anything else addressed to us, answered without a tool call. |+| `ignore` | Not addressed to us (only inherited through a reply chain, etc). |++Safety is enforced inside the parser, before any model ever sees the text:+phrasing that asks for funds to move, a signed transaction, or a secret+(private key, seed phrase, API key) is forced to `help` rather than reaching+`chat` or any generator, and the same happens for instruction-override+phrasing ("ignore previous instructions", "you are now..."). Untrusted text+is also normalized first (`normalizeText`: NFKC fold, invisible/bidi+character stripping, length cap) so lookalike characters and zero-width+tricks cannot dodge the rules above. `addressing()` classifies how a post+reached us (`direct`, `inherited` through a reply chain, or `absent`), and+only `direct` ever produces a reply. Tested in+[`tests/x-mention-intents.test.js`](../tests/x-mention-intents.test.js),+including hostile fixtures.++## Reading mentions: the two inputs++Two independent readers feed the same ledger, so either one can be the+trigger without the other existing:++- **Polling.** [`api/_lib/x-mentions.js`](../api/_lib/x-mentions.js) calls+ `GET /2/users/:id/mentions` since a cursor, for the company account (app+ OAuth 1.0a) or an agent's own connected account (its OAuth2 user token).+ Typed failures (`XTierUnavailable`, `XRateLimited`, `XAuthFailed`,+ `XMentionsError`) let a caller act without parsing strings. A scheduled+ cron that calls this on a loop, decides each mention, and sends the reply+ is not built on this branch yet; see "What is not wired yet."+- **The Account Activity webhook.** `GET /api/x/webhook` answers X's+ Challenge-Response Check; `POST /api/x/webhook` verifies the+ `x-twitter-webhooks-signature` header (HMAC-SHA256 over the raw body with+ the app's OAuth 1.0a consumer secret, constant-time compared), normalizes+ the delivery with+ [`api/_lib/x-webhook-events.js`](../api/_lib/x-webhook-events.js)+ (`normalizeActivityEvent`, producing the same shape the poller does), and+ records it through `recordMention`, leaving `decision = null` for the+ decision step to pick up. It is disabled by default+ (`X_WEBHOOK_ENABLED`) and, when enabled without company X credentials+ configured, acks `{ok:true,disabled:true}` without touching the database.+ `scripts/x-webhook-register.mjs` registers, lists, or deletes the+ subscription (`--dry-run`, `--list`, `--delete`, `--url`). X's Account+ Activity API needs an Enterprise or Pay-Per-Use tier, capped at 3+ subscriptions: owner order 926's gap, named in the handler's own top+ comment. Tests:+ [`tests/api/x-webhook.test.js`](../tests/api/x-webhook.test.js).++## Account linking: mapping an X author to a three.ws account++[`api/_lib/x-identity.js`](../api/_lib/x-identity.js) exports+`findUserByXId(authorId)`, the one shared answer to "is this X user one of+ours": it checks `social_connections` (an owner's own account, connected to+post) and falls back to `agent_x_connections` (a single agent's connected+account), both scoped to `disconnected_at is null`. The mention-reply flow,+the creation-claim flow, and order 925's launch flow all share this lookup+rather than each resolving identity their own way.++An X account can also **sign in** to three.ws, not just be read as a mention+author: `api/auth/x/[action].js`'s `login` action reuses the existing OAuth2+client (scopes `tweet.read users.read offline.access`, read-only) and signs+in through three branches: already linked (`findUserByIdentity`), already+connected for posting (`findUserByXId`, links and signs in), or a new+passwordless account on the same `@wallet.local` placeholder pattern+`api/auth/siws/[action].js` already uses for wallet sign-in (X's OAuth2+profile never reliably carries a verified email, so there is no+email-matching step like Google's). `public/login.html` shows the button+once `api/config.js`'s `xLoginEnabled` is true, which needs+`X_OAUTH_CLIENT_ID`/`X_OAUTH_CLIENT_SECRET` configured; neither exists on any+deployment of this repository yet. Tests:+[`tests/x-identity.test.js`](../tests/x-identity.test.js),+[`tests/user-identities-provider-constraint.test.js`](../tests/user-identities-provider-constraint.test.js).++## Per-agent mention settings++An agent owner controls whether their agent answers mentions of its own+connected X account from the Social tab of+[`pages/agent-edit.html`](../pages/agent-edit.html): enable/dry-run toggles, a+daily reply cap (0 to 50), and which intents it may act on, over+`GET`/`PUT /api/x/agents` ([`api/x/agents.js`](../api/x/agents.js)). Four+columns on `agent_x_policies`+(migration+[`20261011220000_agent_mention_policy.sql`](../api/_lib/migrations/20261011220000_agent_mention_policy.sql)):+`mention_replies_enabled`, `mention_replies_dry_run`,+`mention_replies_daily_cap`, `mention_replies_allowed_intents`, validated by+[`api/_lib/x-agent-policy.js`](../api/_lib/x-agent-policy.js) (an unknown+intent id or an out-of-range cap is a `validation_error`). The panel also+shows the agent's own recent decisions+(`GET /api/x/mention-decisions`,+[`api/x/mention-decisions.js`](../api/x/mention-decisions.js), owner-only,+limit 1 to 20) with the decision badge, author, reason, would-be reply text,+and media thumbnail. Tests:+[`tests/x-mention-decisions-endpoint.test.js`](../tests/x-mention-decisions-endpoint.test.js),+[`tests/agent-mention-policy-migration.test.js`](../tests/agent-mention-policy-migration.test.js).++## The operator console: `/x/ops`++Admin-only, `noindex`, not in the public sitemap: [`pages/x-ops.html`](../pages/x-ops.html)++ [`src/x-ops.js`](../src/x-ops.js), backed by+[`api/x/ops/[action].js`](../api/x/ops/%5Baction%5D.js) and+[`api/_lib/x-mention-admin.js`](../api/_lib/x-mention-admin.js). It is the+review surface over the ledger above, not a second decision engine:++| Action | What it does |+|---|---|+| `list` / `status` | Filter the ledger by account, intent, decision, dry-run status; read the kill switch and blocklist. |+| `pause` / `resume` | Flip `app_settings` key `x_mention_bot_paused` (also honored via env `X_MENTION_BOT_PAUSED`). Pausing never needs a redeploy. |+| `block` / `unblock` | Edit the `app_settings`-backed JSON blocklist (key `x_mention_blocklist`) of author ids. |+| `send` | For exactly one dry-run `reply` row with no `reply_tweet_id` yet: resolve the posting target (company OAuth 1.0a or the agent's own OAuth2 connection), upload media if present, post, and flip the row to `dry_run: false` with the real tweet id. Gated by CSRF and, in the UI, a native confirmation naming the account, tweet id, and reply text before the request fires. |++Every mutating action is admin-authenticated and CSRF-checked before it runs.+Tests: [`tests/x-ops-authorization.test.js`](../tests/x-ops-authorization.test.js)+(43 cases: anonymous 401, non-admin 403, CSRF enforced per action, success+shapes).++## Health and public status++Two surfaces, same signals, different audiences:++- **Operator:** `gatherMentionBotHealth()` in+ [`api/_lib/x-mention-health.js`](../api/_lib/x-mention-health.js) feeds+ `api/healthz.js`'s `subsystems` array (key `x_mention_bot`). Derived+ entirely from `x_mention_events` plus the pause/live switches (no+ dependency on a poll cron or budget module existing): `ok` / `degraded` /+ `paused` / `unknown`. `degraded` at more than 10 minutes of oldest-undecided+ lag, or more than 20% hourly error rate at a minimum 5-decision sample (so+ one early error never flaps it); `paused` always wins over lag or errors,+ since mentions are still recorded while paused, just never decided or+ sent.+- **Public:** `GET /api/x/mention-bot/status`+ ([`api/x/mention-bot/status.js`](../api/x/mention-bot/status.js)), rate+ limited and cached 60s, returns `status`, `mode`, `handlesServed`,+ `repliesLast24h`, `medianReplySeconds`, `checkedAt`. Explicitly no mention+ text, author identity, or budget data. Shown live on+ [`/grok`](https://three.ws/grok) as a four-stat section. Tests:+ [`tests/x-mention-health.test.js`](../tests/x-mention-health.test.js).++## What is not wired yet++Documented plainly rather than papered over, since this file is the single+source of truth for everything in this subsystem:++- **No poll cron runs the pipeline end to end on this branch.** The pieces+ above (reader, parser, ledger, webhook) record mentions and leave+ `decision = null`, or let an admin manually compose and send a reply+ through `/x/ops`. A scheduled cron that calls `x-mentions.js` on a loop,+ runs the parser, decides, and replies automatically does not exist here+ yet (tracked as x-grok order 060, blocked on reconciling this branch+ against the version of this subsystem built independently on `main`; see+ `prompts/finish/_context/x-grok-PROGRESS.md`, 2026-10-11 entries).+- **No standalone safety-guard module** (kill switch + blocklist + rate caps+ enforced automatically before a reply is composed) runs on this branch.+ The kill switch and blocklist exist and are enforced manually by the+ `/x/ops` console; an automatic per-mention guard that calls them before+ composing a reply is part of the same cron gap above.+- **No budget/degrade-ladder module** throttles reply generation by cost+ tier as X API usage approaches a cap. `DECISIONS` already reserves a+ `budget` value for this.+- **No automatic reply composition.** Nothing on this branch turns a `make`+ / `image3d` / `avatar` intent into a generated 3D model and a composed+ reply; that is also owned by the cron gap above.+- **Creation claiming** (moving what the bot made into the author's library+ once they link X) has no `/x/claim` page or `forge_creations.x_author_id`+ column on this branch yet.++None of these gaps block what is documented above: the ledger, the parser,+the webhook, the per-agent settings, the ops console, and the health/status+endpoints are all real, tested, and independently useful (an admin can+already review real mentions and send a real, manually-reviewed reply+through `/x/ops` today). Going fully live, i.e. setting+`X_MENTION_BOT_LIVE=1` and whatever automatic pipeline eventually drains the+ledger, stays owner order 928.diff --git a/prompts/README.md b/prompts/README.mdindex 5fc866c7d..8a130f9ce 100644--- a/prompts/README.md+++ b/prompts/README.md@@ -88,7 +88,7 @@ directory, never this table. For the order to run them in, see [RUN-ORDER.md](RU| `simulation-ready-` | The physics-grade asset campaign: turning generated 3D into assets a rigid-body simulator can consume unedited (metric scale, watertightness, mass and inertia, a collision proxy), signed into the provenance credential and filterable by a buying agent. Its context file carries the frontier bet, the scored candidate table it beat, and the measured kernel evidence (20 live assets graded; 2 of 20 usable as-is, 0 of 10 from our own lanes). Retired 2026-09-03: the architect pass ran and all 8 of its build tasks shipped, so both files are gone and the surface is documented in [docs/sim-readiness.md](../docs/sim-readiness.md) and its `STRUCTURE.md` row. || `store-submissions-` | Listing three.ws MCP tools across the Claude and OpenAI marketplaces and the MCP registries. All 21 numbered orders shipped; [the closeout](finish/store-submissions-01-submission-closeout.md) owns the remaining code gaps and the human submission steps. || `swarm-100-` | The "100% production ready, roadmap complete" goal decomposed into fully independent, single-task orders (per-route browser audits, per-batch api/cron/docs audits, per-worker and per-SDK audits, repo-wide sweeps, and one order per README-roadmap slice). Any file runs standalone in a fresh chat and depends on no index (154 left on 2026-09-03: 150 route audits and 4 repo-wide sweeps; the roadmap slice retired). |-| `x-grok-` | three.ws inside Grok Bot and on X: Grok Bot (xAI's computer-use agent, @bot on X) as a client of our MCP servers (compatibility probe, cloud-agent rate limits, OAuth and scoped keys, agent-first results, a Grok surface, `/grok`, docs, CLI, recipes, an xAI end-to-end proof), xAI as a provider (model catalog, X search rung, Grok brains), and an @-mention bot for @trythreews and agent accounts (gateway worker rebuild, reader, parser, schema, adapter, cron, reply brain, make-it-3D, image-to-3D, avatar, safety, bot-to-bot with @grok and @bot, budget, claim, linking, agent mode, ops console, webhook, health, player card). 023 to 066 runnable, 926 to 931 owner-gated. Shared facts: [finish/_context/x-grok-00-CONTEXT.md](finish/_context/x-grok-00-CONTEXT.md). |+| `x-grok-` | three.ws inside Grok Bot and on X: Grok Bot (xAI's computer-use agent, @bot on X) as a client of our MCP servers (compatibility probe, cloud-agent rate limits, OAuth and scoped keys, agent-first results, a Grok surface, `/grok`, docs, CLI, recipes, an xAI end-to-end proof), xAI as a provider (model catalog, X search rung, Grok brains), and an @-mention bot for @trythreews and agent accounts. As measured 2026-10-11: lane A/B and the mention bot's reader, parser, ledger, webhook, ops console, per-agent settings, identity mapping, health/status and player card have all shipped on `evolve`, documented in [docs/x-mention-bot.md](../docs/x-mention-bot.md); the automated poll cron, reply brain, safety-guard enforcement, budget ladder and claim flow exist only on `main` and need the branch reconciliation tracked in `production-100-OWNER-ACTIONS.md` row 34 before they land here. Open order files: `023`/`024` (built, waiting on a deploy), `039` (built, one owner-gated DoD line), `060` (blocked on the row-34 reconciliation), `061` (built, waiting on a migration apply, owner row 35). 926 to 931 remain owner-gated. Shared facts: [finish/_context/x-grok-00-CONTEXT.md](finish/_context/x-grok-00-CONTEXT.md). |Fully completed campaigns leave the queue once every order is verified shipped (x402-catalog andx402-overhaul were retired 2026-07-28; agent-briefs, whose world-online program shipped throughdiff --git a/prompts/RUN-ORDER.md b/prompts/RUN-ORDER.mdindex 8042662ef..ff1915df2 100644--- a/prompts/RUN-ORDER.md+++ b/prompts/RUN-ORDER.md@@ -10,7 +10,7 @@ so you can open one, run it, and open the next without consulting anything. Ever|---|---|---|| `001` to `014` | Runnable right now, no gate. Highest value first. Start at `001`. | 14 || `015` to `022` | The `parity-` campaign, added 2026-09-30. Runnable, no gate except where an order names one step. Run 015 before 017 (017 ranks 015's data); 919 ships them. | 8 |-| `023` to `066` | The `x-grok-` campaign, added 2026-10-08: Grok Bot as an MCP client, xAI as a provider, and the X mention bot (dry run). Runnable; lane C ships nothing live. Run 023 first, 045 before 049, 046 to 049 before 050. | 44 |+| `023` to `066` | The `x-grok-` campaign, added 2026-10-08: Grok Bot as an MCP client, xAI as a provider, and the X mention bot (dry run). Most of lane C has shipped; its automated reply path still needs the `evolve`/`main` reconciliation in `production-100-OWNER-ACTIONS.md` row 34. Run 023 first, 045 before 049, 046 to 049 before 050. | 6 || `100` to `248` | The route-audit swarm, ordered by measured defect class. Parallel-safe. | 149 || `300` to `313` | The unbuilt Home campaign, in numeric order (04 gates 05 and 06, 11 gates 20). | 14 || `400` to `499` | Written by the evolve scout lane ([docs/ops/evolve.md](../docs/ops/evolve.md)), each from a dated measurement. Runnable, no gate. | varies |diff --git a/public/changelog-recent.json b/public/changelog-recent.jsonindex 7dbdb2f53..bf64ddc4a 100644--- a/public/changelog-recent.json+++ b/public/changelog-recent.json@@ -1,11 +1,11 @@{- "generated_at": "2026-10-11T08:10:44.766Z",+ "generated_at": "2026-10-11T08:54:58.088Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws","url": "https://three.ws"},- "total": 3854,+ "total": 3856,"complete": false,"full_feed": "/changelog.json","entries": [@@ -19,6 +19,16 @@"improvement"]},+ {+ "date": "2026-10-11",+ "type": "update",+ "title": "Choose which @-mentions your agent answers, right from its editor",+ "summary": "An agent's Social tab now has an \"Answer mentions\" section: turn it on, keep it in dry run while you watch what it would say, cap it at a daily reply count, and pick exactly which kinds of mentions it may act on. A new decisions list on the same page shows the agent's own recent calls, what it decided and why, so the owner never has to ask an admin to check a console on their behalf.",+ "link": "/agents",+ "tags": [+ "feature"+ ]+ },{"date": "2026-10-11","type": "update",@@ -30,6 +40,16 @@"infra"]},+ {+ "date": "2026-10-11",+ "type": "update",+ "title": "Share a finished Forge creation on X and it plays inline",+ "summary": "A link to a finished Forge creation now carries an X player card instead of a flat image: the post expands into the real 3D model, posed with its own poster frame and ready to orbit, through the same safe embed runtime the agent-profile embeds use (no audio or video element, HTTPS assets only). A creation that is still generating keeps the plain image card until it finishes, so a link never promises a model that isn't ready yet.",+ "link": "/forge",+ "tags": [+ "feature"+ ]+ },{"date": "2026-10-11","type": "update",@@ -1538,28 +1558,6 @@"fix","infra"]- },- {- "date": "2026-09-18",- "type": "update",- "title": "Standard Anthropic SDK clients can now use a three.ws agent's AI budget",- "summary": "The AI proxy behind every embedded three.ws agent now answers at the address an Anthropic SDK or command-line tool builds for itself. Point a client at /api/llm/anthropic/agents/<your agent id> with one of your API keys and it runs on that agent's model, limits, and monthly budget. The proxy also stopped turning such clients away over their defaults: a system prompt sent as a list of text blocks is accepted, and an output limit above 16,000 tokens is lowered to 16,000 instead of rejected.",- "link": "/docs/api-reference",- "tags": [- "feature",- "sdk"- ]- },- {- "date": "2026-09-18",- "type": "update",- "title": "Text avatars now wear what you describe",- "summary": "Typing a description on /genesis (or sending a prompt to the avatar API) used to produce the same template body with a face pasted onto it, so an explorer in a teal flight jacket came back in someone else's clothes. Text avatars are now built from your words head to toe: the prompt is painted as a full-body character, sculpted into a textured 3D model on our own GPU, and given a skeleton so it animates immediately. Selfies still use the face pipeline, which is what a likeness needs. The free 3D generator behind the forge_avatar tool also stopped failing when the community GPU spaces were out of quota: it now moves the job onto our own worker instead of giving up.",- "link": "/genesis",- "tags": [- "fix",- "improvement"- ]}]}diff --git a/public/changelog.json b/public/changelog.jsonindex ad76fbea4..21c8c45cb 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,5 +1,5 @@{- "generated_at": "2026-10-11T08:10:44.739Z",+ "generated_at": "2026-10-11T08:54:58.064Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws",@@ -16,6 +16,16 @@"improvement"]},+ {+ "date": "2026-10-11",+ "type": "update",+ "title": "Choose which @-mentions your agent answers, right from its editor",+ "summary": "An agent's Social tab now has an \"Answer mentions\" section: turn it on, keep it in dry run while you watch what it would say, cap it at a daily reply count, and pick exactly which kinds of mentions it may act on. A new decisions list on the same page shows the agent's own recent calls, what it decided and why, so the owner never has to ask an admin to check a console on their behalf.",+ "link": "/agents",+ "tags": [+ "feature"+ ]+ },{"date": "2026-10-11","type": "update",@@ -27,6 +37,16 @@"infra"]},+ {+ "date": "2026-10-11",+ "type": "update",+ "title": "Share a finished Forge creation on X and it plays inline",+ "summary": "A link to a finished Forge creation now carries an X player card instead of a flat image: the post expands into the real 3D model, posed with its own poster frame and ready to orbit, through the same safe embed runtime the agent-profile embeds use (no audio or video element, HTTPS assets only). A creation that is still generating keeps the plain image card until it finishes, so a link never promises a model that isn't ready yet.",+ "link": "/forge",+ "tags": [+ "feature"+ ]+ },{"date": "2026-10-11","type": "update",diff --git a/public/changelog.xml b/public/changelog.xmlindex ca7c56af4..a636c6813 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -14,6 +14,14 @@<category>improvement</category><description>Profile chat, the agent editor's copilot, scheduled strategy runs, and the gateway all now read an agent's chosen brain through the same resolver, so picking Grok for an agent actually means Grok on every surface, not just the one where it was set. A Grok pick first tries the agent owner's own saved xAI key, then the platform's, before falling back to the free default chain. When Grok genuinely can't answer (no key reachable anywhere), profile chat now shows a small badge naming which model answered instead, so it's never a silent swap.</description></item>+ <item>+ <title>Choose which @-mentions your agent answers, right from its editor</title>+ <link>https://three.ws/agents</link>+ <guid isPermaLink="false">2026-10-11:Choose which @-mentions your agent answers, right from its editor</guid>+ <pubDate>Sun, 11 Oct 2026 12:00:00 GMT</pubDate>+ <category>feature</category>+ <description>An agent's Social tab now has an "Answer mentions" section: turn it on, keep it in dry run while you watch what it would say, cap it at a daily reply count, and pick exactly which kinds of mentions it may act on. A new decisions list on the same page shows the agent's own recent calls, what it decided and why, so the owner never has to ask an admin to check a console on their behalf.</description>+ </item><item><title>Sentiment Scout's X reads gained a second, independent path through xAI</title><link>https://three.ws/docs/sentiment-scout</link>@@ -22,6 +30,14 @@<category>improvement</category><description>The Sentiment Scout reads X for posts quoting a coin's exact contract address, as evidence a holder can open and check. When our own X search credentials are unavailable or rate limited, it now fails over to xAI's x_search tool, a second route to the same posts, metered by its own daily cap so an outage on one path never silently costs more than planned on the other. No change for anyone reading the Scout: the evidence looks the same either way.</description></item>+ <item>+ <title>Share a finished Forge creation on X and it plays inline</title>+ <link>https://three.ws/forge</link>+ <guid isPermaLink="false">2026-10-11:Share a finished Forge creation on X and it plays inline</guid>+ <pubDate>Sun, 11 Oct 2026 12:00:00 GMT</pubDate>+ <category>feature</category>+ <description>A link to a finished Forge creation now carries an X player card instead of a flat image: the post expands into the real 3D model, posed with its own poster frame and ready to orbit, through the same safe embed runtime the agent-profile embeds use (no audio or video element, HTTPS assets only). A creation that is still generating keeps the plain image card until it finishes, so a link never promises a model that isn't ready yet.</description>+ </item><item><title>The @-mention reply bot now reports its own status, and /grok shows it live</title><link>https://three.ws/grok</link>diff --git a/public/features.json b/public/features.jsonindex fa7ee3418..144d44718 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-10-11T00:07:40.247Z",+ "generated_at": "2026-10-11T08:54:58.053Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",diff --git a/public/sitemap/index.html b/public/sitemap/index.htmlindex 420822555..21cb0d1c4 100644--- a/public/sitemap/index.html+++ b/public/sitemap/index.html@@ -3,16 +3,16 @@<head><meta charset="utf-8" /><meta name="viewport" content="width=device-width,initial-scale=1" />-<title>Sitemap · three.ws</title>-<meta name="description" content="Human-readable index of every page on three.ws." />+<title data-i18n="sitemap_index.meta_title">Sitemap · three.ws</title>+<meta name="description" content="Human-readable index of every page on three.ws." data-i18n-attr="content:sitemap_index.meta_description"/><meta name="robots" content="index, follow, max-image-preview:large, max-snippet:-1" /><link rel="canonical" href="https://three.ws/sitemap" /><meta property="og:type" content="website" /><meta property="og:site_name" content="three.ws" /><meta property="og:locale" content="en_US" /><meta property="og:url" content="https://three.ws/sitemap" />-<meta property="og:title" content="Sitemap · three.ws" />-<meta property="og:description" content="Human-readable index of every page on three.ws." />+<meta property="og:title" content="Sitemap · three.ws" data-i18n-attr="content:sitemap_index.meta_og_title"/>+<meta property="og:description" content="Human-readable index of every page on three.ws." data-i18n-attr="content:sitemap_index.meta_og_description"/><meta property="og:image" content="https://three.ws/api/page-og?s=main&t=Sitemap&d=Human-readable+index+of+every+page+on+three.ws.&p=%2Fsitemap" /><meta property="og:image:width" content="1200" /><meta property="og:image:height" content="630" />@@ -20,8 +20,8 @@<meta property="og:image:alt" content="Sitemap - three.ws" /><meta name="twitter:card" content="summary_large_image" /><meta name="twitter:site" content="@trythreews" />-<meta name="twitter:title" content="Sitemap · three.ws" />-<meta name="twitter:description" content="Human-readable index of every page on three.ws." />+<meta name="twitter:title" content="Sitemap · three.ws" data-i18n-attr="content:sitemap_index.meta_twitter_title"/>+<meta name="twitter:description" content="Human-readable index of every page on three.ws." data-i18n-attr="content:sitemap_index.meta_twitter_description"/><meta name="twitter:image" content="https://three.ws/api/page-og?s=main&t=Sitemap&d=Human-readable+index+of+every+page+on+three.ws.&p=%2Fsitemap" /><script type="application/ld+json">{"@context":"https://schema.org","@graph":[{"@type":"WebPage","name":"Sitemap","description":"Human-readable index of every page on three.ws.","url":"https://three.ws/sitemap","isPartOf":{"@type":"WebSite","name":"three.ws","url":"https://three.ws"},"primaryImageOfPage":"https://three.ws/api/page-og?s=main&t=Sitemap&d=Human-readable+index+of+every+page+on+three.ws.&p=%2Fsitemap"}]}</script><link rel="alternate" type="application/xml" title="XML sitemap" href="/sitemap.xml" />@@ -95,15 +95,15 @@<header><div id="nav-container"></div></header><main class="sm-wrap"><div class="sm-hero">- <h1>Sitemap</h1>+ <h1 data-i18n="sitemap_index.sitemap">Sitemap</h1><p><span>982</span> <span data-i18n="sitemap_index.pages_grouped">pages on three.ws, grouped by purpose. Looking for the machine-readable versions?</span></p><div class="sm-formats">- <a href="/sitemap.xml"><code>sitemap.xml</code> · for search engines</a>- <a href="/llms.txt"><code>llms.txt</code> · for AI agents</a>- <a href="/llms-full.txt"><code>llms-full.txt</code> · long form</a>- <a href="/api/features.json"><code>features.json</code> · machine manifest</a>- <a href="/changelog"><code>changelog</code> · what's new</a>- <a href="/openapi.json"><code>openapi.json</code> · HTTP API</a>+ <a href="/sitemap.xml" data-i18n-html="sitemap_index.for_search_engines"><code>sitemap.xml</code> · for search engines</a>+ <a href="/llms.txt" data-i18n-html="sitemap_index.for_ai_agents"><code>llms.txt</code> · for AI agents</a>+ <a href="/llms-full.txt" data-i18n-html="sitemap_index.long_form"><code>llms-full.txt</code> · long form</a>+ <a href="/api/features.json" data-i18n-html="sitemap_index.machine_manifest"><code>features.json</code> · machine manifest</a>+ <a href="/changelog" data-i18n-html="sitemap_index.what_s_new"><code>changelog</code> · what's new</a>+ <a href="/openapi.json" data-i18n-html="sitemap_index.http_api"><code>openapi.json</code> · HTTP API</a></div></div><div class="sm-filter">@@ -113,8 +113,8 @@</div><p class="sm-filter-count" role="status" aria-live="polite"><span id="sm-filter-count"></span><span id="sm-filter-hint" aria-hidden="true"></span></p><section class="sm-new" id="sm-new" aria-labelledby="sm-new-title">- <h2 id="sm-new-title">Newest<a class="sm-new-more" href="/changelog">full changelog →</a></h2>- <p class="sm-section-desc">The 9 most recently launched pages, straight to the live surface.</p>+ <h2 id="sm-new-title" data-i18n-html="sitemap_index.newestfull_changelog">Newest<a class="sm-new-more" href="/changelog">full changelog →</a></h2>+ <p class="sm-section-desc" data-i18n="sitemap_index.the_9_most_recently_launched_pages_straight">The 9 most recently launched pages, straight to the live surface.</p><ul class="sm-list"><li><a href="/docs/tutorials/grok-bot-recipes">@@ -191,22 +191,22 @@</ul></section><nav class="sm-toc" aria-label="Sections">- <a href="#main">Main</a>- <a href="#build">Build</a>- <a href="#labs">Labs</a>- <a href="#crypto">Crypto</a>- <a href="#agent-tools">Agent Tools</a>- <a href="#account">Account</a>- <a href="#learn">Learn</a>- <a href="#blog">Blog</a>- <a href="#legal">Legal</a>- <a href="#machine">Machine-readable</a>- <a href="#news">News</a>+ <a href="#main" data-i18n="sitemap_index.main">Main</a>+ <a href="#build" data-i18n="sitemap_index.build">Build</a>+ <a href="#labs" data-i18n="sitemap_index.labs">Labs</a>+ <a href="#crypto" data-i18n="sitemap_index.crypto">Crypto</a>+ <a href="#agent-tools" data-i18n="sitemap_index.agent_tools">Agent Tools</a>+ <a href="#account" data-i18n="sitemap_index.account">Account</a>+ <a href="#learn" data-i18n="sitemap_index.learn">Learn</a>+ <a href="#blog" data-i18n="sitemap_index.blog">Blog</a>+ <a href="#legal" data-i18n="sitemap_index.legal">Legal</a>+ <a href="#machine" data-i18n="sitemap_index.machine_readable">Machine-readable</a>+ <a href="#news" data-i18n="sitemap_index.news">News</a></nav><section class="sm-section" id="main"><header><h2><span data-i18n="sitemap_index.section_main">Main</span><span class="sm-count" data-count>62</span></h2>- <p class="sm-section-desc">Entry points into the product.</p>+ <p class="sm-section-desc" data-i18n="sitemap_index.entry_points_into_the_product">Entry points into the product.</p></header><ul class="sm-list"><li>@@ -649,7 +649,7 @@<section class="sm-section" id="build"><header><h2><span data-i18n="sitemap_index.section_build">Build</span><span class="sm-count" data-count>80</span></h2>- <p class="sm-section-desc">Create and customize an agent.</p>+ <p class="sm-section-desc" data-i18n="sitemap_index.create_and_customize_an_agent">Create and customize an agent.</p></header><ul class="sm-list"><li>@@ -1218,7 +1218,7 @@<section class="sm-section" id="labs"><header><h2><span data-i18n="sitemap_index.section_labs">Labs</span><span class="sm-count" data-count>25</span></h2>- <p class="sm-section-desc">Experimental features actively shipping. Expect fast iteration.</p>+ <p class="sm-section-desc" data-i18n="sitemap_index.experimental_features_actively_shipping_expe">Experimental features actively shipping. Expect fast iteration.</p></header><ul class="sm-list"><li>@@ -1402,7 +1402,7 @@<section class="sm-section" id="crypto"><header><h2><span data-i18n="sitemap_index.section_crypto">Crypto</span><span class="sm-count" data-count>156</span></h2>- <p class="sm-section-desc">On-chain features: pay-per-call, token launches, vanity wallets.</p>+ <p class="sm-section-desc" data-i18n="sitemap_index.on_chain_features_pay_per_call_token">On-chain features: pay-per-call, token launches, vanity wallets.</p></header><ul class="sm-list"><li>@@ -2503,7 +2503,7 @@<section class="sm-section" id="agent-tools"><header><h2><span data-i18n="sitemap_index.section_agent-tools">Agent Tools</span><span class="sm-count" data-count>10</span></h2>- <p class="sm-section-desc">Manage, talk to, and deploy individual agents.</p>+ <p class="sm-section-desc" data-i18n="sitemap_index.manage_talk_to_and_deploy_individual_agents">Manage, talk to, and deploy individual agents.</p></header><ul class="sm-list"><li>@@ -2582,7 +2582,7 @@<section class="sm-section" id="account"><header><h2><span data-i18n="sitemap_index.section_account">Account</span><span class="sm-count" data-count>14</span></h2>- <p class="sm-section-desc">Sign-in, dashboard, billing.</p>+ <p class="sm-section-desc" data-i18n="sitemap_index.sign_in_dashboard_billing">Sign-in, dashboard, billing.</p></header><ul class="sm-list"><li>@@ -2689,7 +2689,7 @@<section class="sm-section" id="learn"><header><h2><span data-i18n="sitemap_index.section_learn">Learn</span><span class="sm-count" data-count>457</span></h2>- <p class="sm-section-desc">Docs, tutorials, and reference.</p>+ <p class="sm-section-desc" data-i18n="sitemap_index.docs_tutorials_and_reference">Docs, tutorials, and reference.</p></header><ul class="sm-list"><li>@@ -5897,7 +5897,7 @@<section class="sm-section" id="blog"><header><h2><span data-i18n="sitemap_index.section_blog">Blog</span><span class="sm-count" data-count>39</span></h2>- <p class="sm-section-desc">Long-form announcements, launches, and writing from three.ws.</p>+ <p class="sm-section-desc" data-i18n="sitemap_index.long_form_announcements_launches_and_writing">Long-form announcements, launches, and writing from three.ws.</p></header><ul class="sm-list"><li>@@ -6251,7 +6251,7 @@<section class="sm-section" id="machine"><header><h2><span data-i18n="sitemap_index.section_machine">Machine-readable</span><span class="sm-count" data-count>18</span></h2>- <p class="sm-section-desc">Indexes and well-known files for crawlers and AI agents.</p>+ <p class="sm-section-desc" data-i18n="sitemap_index.indexes_and_well_known_files_for_crawlers">Indexes and well-known files for crawlers and AI agents.</p></header><ul class="sm-list"><li>@@ -6386,7 +6386,7 @@<section class="sm-section" id="news"><header><h2><span data-i18n="sitemap_index.section_news">News</span><span class="sm-count" data-count>112</span></h2>- <p class="sm-section-desc">Product launches, integrations, and announcements from three.ws.</p>+ <p class="sm-section-desc" data-i18n="sitemap_index.product_launches_integrations_and_announceme">Product launches, integrations, and announcements from three.ws.</p></header><ul class="sm-list"><li>@@ -7177,10 +7177,10 @@</section><div class="sm-empty" id="sm-empty" hidden><p><span data-i18n="sitemap_index.no_pages_match">No pages match</span> “<span id="sm-empty-q"></span>”.</p>- <p class="sm-empty-hint">Try a shorter word, or search everything: global search covers agents, coins, and skills too.</p>+ <p class="sm-empty-hint" data-i18n="sitemap_index.try_a_shorter_word_or_search_everything">Try a shorter word, or search everything: global search covers agents, coins, and skills too.</p><div class="sm-empty-actions">- <button type="button" id="sm-empty-clear">Clear filter</button>- <a id="sm-empty-search" href="/search">Search all of three.ws</a>+ <button type="button" id="sm-empty-clear" data-i18n="sitemap_index.clear_filter">Clear filter</button>+ <a id="sm-empty-search" href="/search" data-i18n="sitemap_index.search_all_of_three_ws">Search all of three.ws</a></div></div></main>diff --git a/scripts/audit-docs.mjs b/scripts/audit-docs.mjsindex 379a19844..f97c9368c 100644--- a/scripts/audit-docs.mjs+++ b/scripts/audit-docs.mjs@@ -394,6 +394,7 @@ const UNPUBLISHED_DOCS = new Map([['trading-experiment', 'owner-gated: names a crypto project other than $THREE'],['trading-hub', 'in-flight: landed mid-session, register with its /trading page'],['x402-solana-july-roundup-response', 'internal: ready-to-paste X reply draft; posting is owner-gated'],+ ['x-mention-bot', 'internal: operator runbook for the @-mention reply bot; public once the bot goes live (order 928)'],['x-content-pipeline', 'internal: owner-gated @trythreews publishing queue runbook'],['x-story-authoring', 'internal: how a post for the @trythreews queue is written and filmed, like x-content-pipeline'],['x-story-author-brief', 'internal: the brief handed to a story author, like x-story-authoring'],