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
build(pages): register the new surfaces in routes, pages, structure and the feeds
nirholas12aa0d462a8d
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex f7fea442f..0464e995f 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -6,13 +6,20 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr## 2026-08-28+- **Brownout** (`/brownout`): Every response from this API says where its data came from and how fresh it is, and every declared fallback has been proven by breaking the upstream it protects against, inside the real request path. Read the receipts: which provider refused, which one caught the request, and how old the answer was.- **Companion** (`/companion`): A 3D companion that delivers your important messages in person. Connect your own Telegram bot, calendar, inbox, or phone, give each contact their own avatar and voice, and hear only what clears your bar.- **Docs · 3D Vision: let an agent see the model** (`/docs/3d-vision`): Every text-to-3D API answers with a link to a binary an AI agent cannot open, so the agent that made the model cannot check its own work. This surface renders any GLB from several angles and hands the frames back as images a vision model actually sees, over MCP, REST or the @three-ws/see SDK.- **Docs · Agent vitals: can it act?** (`/docs/agent-vitals`): Every liveness check was green while ten of twelve autonomous agents had not acted in weeks. Capability attestation models an agent's preconditions as a causal graph and returns the root blocker plus the command that fixes it, instead of a checklist of symptoms.+- **Docs · Companion** (`/docs/companion`): The personal companion: connect your own Telegram bot, calendar, inbox, or phone, give your contacts a face and a voice, and have a 3D character deliver what matters in person. Bridges, triage rules, the SDK, the CLI, the MCP server, and the desktop app.- **Docs · Feedback** (`/docs/feedback`): Telling the corner companion what broke: the proactive ask at the moment of failure, the route, build SHA, and console errors captured for you, the severity and clustering rules, the report API, and the boundary that keeps untrusted visitor text from ever reaching anything with write access.- **Docs · Terminal avatar** (`/docs/tty-avatar`): The @three-ws/tty-avatar package: any three.ws avatar or agent body rendered live in a terminal by a software rasterizer (truecolor half-blocks, braille, or plain ASCII), procedural moods, and Claude Code hooks that turn it into your coding agent's face.+- **Docs · The Oracle model, and how to run it yourself** (`/docs/oracle-model`): How the three.ws conviction model is fitted, what its three heads predict, why the outcome labels had to be made independent of the SOL price, how the promotion gate decides which model ships, and how to score launches locally with @three-ws/oracle-model.+- **Docs · Upstream resilience map** (`/docs/resilience`): Every third-party service this platform calls and what happens to a user when it goes down. Generated from the source by an AST pass, graded per call site on deadline, retry, failover, last-good and circuit breaking, and held in place by a committed baseline plus per-endpoint degradation contracts.+- **Glance** (`/glance`): Your three.ws agent on every home screen: a live card for the Windows 11 widgets board, a README, Slack, or any page.- **Herald** (`/herald`): Deliver a message in person: a 3D character walks onto your page and tells the user what happened. Open SDK, one line of code, an accessible fallback, and a CLI that announces when your build finishes.+- **Oracle Lab: the model, published** (`/oracle-lab`): The Oracle's conviction model in full: every bucket weight with the number of labeled launches behind it and what happened to them, the held-out reliability curve for each tier, the version history of every refit including the ones that were refused, and a live scorer that runs the real weights in your browser. Download it and reproduce any score offline.- **Portal** (`/portal`): Paste any web address and walk through it in 3D. Portal reads the page's real structure and builds a place from it: sections become buildings sized by what they say, links become doors you step into, images become billboards. Download the world as a GLB or embed it in your own site.+- **Progressive Avatars** (`/stream`): A3S packs a GLB into nested layers whose first 50 KB is already a complete, skinned, spec-valid avatar, then refines it in place over plain HTTP range requests. Live side-by-side against a classic GLB load.- **Publishing to the Solana dApp Store** (`/docs/seeker-publishing`): The release runbook for the three.ws Seeker app: Publisher Portal setup, the release keystore, building and verifying a signed APK, and submitting it for review.- **Terminal renderer** (`/tty`): curl three.ws/tty and a rigged 3D agent walks in your terminal. A software rasterizer streams ANSI frames over HTTP: no GPU, no WebGL, nothing to install. Also the @three-ws/tty CLI and library for rendering any GLB in a terminal.- **three.ws on iOS** (`/docs/ios-app`): What the App Store app adds on top of the website: the native share sheet, universal links, wallet deep links back to the page you left, real permission prompts, and an offline screen that recovers on its own.@@ -25,9 +32,11 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **Tell the agent in the corner what is broken**: The companion that walks your pages now listens. When a page actually fails, it turns and asks what you were doing, and the report it sends carries what you should never have to type: the page, the exact build it happened on, your screen size, and the errors the browser recorded at that moment. You can also open it any time from the control beside the avatar, and dictate instead of typing. Reports are grouped so that twenty people hitting one problem read as one problem, and every one of them is read by a person before anything changes. (`/docs/feedback`) `[feature, improvement]`- **The iOS app now exists in the repo, and the web half of it ships today**: three.ws is being packaged for the App Store as a native iOS app. The container and its Xcode project are in the repo, and the part that runs inside the website went live with this deploy: on iPhone the app will get a working share sheet, links that open the app instead of Safari, wallet sign-ins that return to the exact page you left, and a real offline screen. Nothing changes on the web. What is still outstanding is an Apple Developer organization account, app icons, and push notifications. (`/docs/ios-app`) `[feature, infra]`- **The Seeker app now runs full-screen, and its release process is written down**: The three.ws app on Solana Seeker verifies against the site and opens full-screen on its own home screen, with no browser address bar. Two bugs found while testing it on a real Android build are fixed: the app only recognised your Seed Vault wallet on the first page you opened, so signing in from the login page said no wallet was found, and the login page never loaded the wallet at all. A new guide documents exactly how a release reaches the Solana dApp Store, from the publisher account through building and submitting the app. (`/docs/seeker-publishing`) `[fix, docs]`+- **We now prove our fallbacks work, instead of hoping they do**: Adding a backup for an outside service is easy; knowing it made things better is not. A new audit reads the whole codebase and grades every call we make to an outside service on five protections, publishes the result as a public map, and fails the build if a new unprotected call is added or an existing one gets worse. On top of it, each endpoint now declares what it is allowed to tell you when a service it depends on is down, and a test proves it by actually breaking the service and checking the answer. That immediately caught a real bug: a token lookup was telling people a token did not exist when the price indexer was simply unreachable. Related fixes stop stale data reaching a payment retry, a token security verdict and an access check, where an out-of-date answer costs money or grants access. (`/docs/resilience`) `[feature, improvement, infra]`- **Your agent now tells you the important things in person**: Notifications no longer wait behind a badge. When something worth stopping for lands while you are on the site (a sale, money in, a 3D generation finishing, anything touching your account), your corner companion turns to you, plays a gesture, and says it out loud with a link straight to it. If the companion is switched off it is summoned for that one message and walks off again, without turning itself back on. It is a real delivery channel next to in-app, push, email and Telegram: toggle it per category in Settings, and there is a Turn off control in the bubble that silences it in that browser instantly. It only ever announces unread notifications under fifteen minutes old, says each one exactly once, caps itself at two per visit, and never speaks into a background tab. Nothing is spoken aloud unless you already turned on the companion's voice; otherwise it is text in the bubble, which screen readers announce too. (`/notifications`) `[feature]`- **Your agents can now tell you why they are not doing anything**: An audit found ten of twelve autonomous trading agents had not acted in weeks while every health check reported them perfectly fine: the container was up, the feed was streaming, every strategy was armed. Liveness measures the process, but acting needs a whole chain of preconditions the process knows nothing about. A new open-source package, @three-ws/agent-vitals, models those preconditions as a causal graph and answers the real question: can this agent act right now, and if not, what is the one thing to fix. It reports root causes instead of symptoms, so a stale deployment that killed a model chain that starved a decision queue reads as one item with one command, not three red rows to guess between. Run npm run agent:vitals for the fleet, or GET /api/agents/vitals. (`/docs/agent-vitals`) `[feature, sdk, infra]`- **Your avatar now runs in a terminal, and it can be your coding agent's face**: A new package, @three-ws/tty-avatar, draws any three.ws avatar or agent body live in a terminal window: one npx command, no browser, no GPU, 24 frames a second in colour. It has moods (thinking, working, happy, error, asleep) that work on any model without a rig, and one command wires it to Claude Code so the avatar thinks while the agent reads your prompt, nods while it edits files, shakes when a tool fails and bounces when it finishes, with a caption naming what it is doing. Every avatar and agent page now has the command in its Embed tab. (`/docs/tty-avatar`) `[feature, sdk]`+- **Your notifications now have a body: meet your companion**: Your phone buzzes forty times a day and two of those mattered. three.ws/companion is the other half of that problem. Connect what you already use, on your own keys: a Telegram bot you create, the private calendar link Google, Apple and Outlook all publish, your inbox over IMAP with an app password, or nothing at all but a token your phone, your Mac, your build script or an AI agent can post to. Everything that arrives is scored out of 100 against the things people actually want interrupting for (a saved contact asking you something, a one-time code, a meeting starting in ten minutes, a payment that failed) and the rest is kept quietly in a feed with the reason it stayed quiet. What clears your bar is delivered in person: a 3D character walks on, and if it is from someone you gave a face to, it arrives wearing their avatar and speaking in their voice. It reaches you on three.ws, as a push on your phone, and on your desktop, where a new companion app puts a character that walks across your screen and comes over to tell you. Quiet hours are absolute, the credentials are encrypted, and one button revokes every device. Developers get the whole thing as @three-ws/companion: a client, the same triage rules the server runs (so you can score your mail locally and never send the rest), a drop-in 3D stage for any page, a CLI, and an MCP server so an agent that finds something urgent can stand in front of you and say it. (`/companion`) `[feature, sdk, improvement]`## 2026-08-27diff --git a/STRUCTURE.md b/STRUCTURE.mdindex 3b9979d45..d359df365 100644--- a/STRUCTURE.md+++ b/STRUCTURE.md@@ -54,6 +54,7 @@ bottom.| Platform activity feed | [pages/feed.html](pages/feed.html) `→ /feed` + [pages/community.html](pages/community.html) `→ /community`, backend [api/users/me/feed.js](api/users/me/feed.js) | Live | Reverse-chronological creation events (avatars, agents, coins, models, worlds) plus follow activity, merged at read time from `forge_creations`, `dioramas`, and `user_follows` (no separate event log to drift out of sync). `?scope=following` (default; session-gated, anonymous gets 401) vs `?scope=all` (public; powers `/community` and first-visit feeds); `limit` 1..50, `before` ISO cursor. Items deep-link to creator portfolios. Distinct from the Money Pulse ticker `GET /api/feed` ([docs/money-feed.md](docs/money-feed.md)). Docs: [docs/social-layer.md](docs/social-layer.md) || Follow graph | [api/users/[username]/follow.js](api/users/%5Busername%5D/follow.js) + [api/users/[username]/follows.js](api/users/%5Busername%5D/follows.js), table `user_follows`, buttons on [pages/profile.html](pages/profile.html) | Live | `GET` returns `{following, followed_by, followers_count, following_count}`; `POST`/`DELETE` are idempotent (session + CSRF, self-follow 400) and return the same envelope so one round-trip updates the button and the counts. A genuinely new edge (`ON CONFLICT DO NOTHING`) publishes a `follow` user event to the notification bell exactly once. Feeds the activity feed's following scope, search ranking, and the `followers` leaderboard metric. Tests: [tests/api/users-follow.test.js](tests/api/users-follow.test.js). Docs: [docs/social-layer.md](docs/social-layer.md) || Notification bell & preferences | Event vocabulary [api/_lib/feed.js](api/_lib/feed.js) (`USER_EVENT_TYPES` → `publishUserEvent()` → `user_notifications`), endpoints [api/notifications/](api/notifications), preference matrix [api/_lib/notify-prefs.js](api/_lib/notify-prefs.js), bell client [src/notifications.js](src/notifications.js), avatar announcements [src/notification-herald.js](src/notification-herald.js), settings panel [src/dashboard-next/pages/settings.js](src/dashboard-next/pages/settings.js) | Live | In-app inbox covering remixes ([api/x402/remix-asset.js](api/x402/remix-asset.js)), DMs ([api/friends/messages.js](api/friends/messages.js)), coin bonding-curve graduations (pump cron in [api/cron/[name].js](api/cron/%5Bname%5D.js)), follows, sales, purchases, IRL, market, and account events. Preferences are a category × channel matrix (`in_app` always on; push/email/telegram/avatar are per-category opt-outs) edited from `/dashboard/settings`. **The `avatar` channel delivers in person:** for a fresh, unread notification in an opted-in category the corner companion walks on screen, gestures, and says the line with a link straight to it, summoning itself for that one message and retreating if it was off ([walk-sdk](walk-sdk) `control.announce`). Rules (15-minute freshness, once per browser, two per batch, visible tab only, device-level mute) live in [src/notification-herald.js](src/notification-herald.js). Docs: [docs/notifications.md](docs/notifications.md), [docs/social-layer.md](docs/social-layer.md). Tests: [tests/notification-herald.test.js](tests/notification-herald.test.js), [tests/notify-prefs.test.js](tests/notify-prefs.test.js) |+| Personal companion (`/companion`) | Page [pages/companion.html](pages/companion.html) `→ /companion` + [src/companion/](src/companion) (page, source cards, voice), API [api/companion/](api/companion) (settings, sources, contacts, events, `ingest`, `stream`, `poll`), engine [api/_lib/companion/](api/_lib/companion) (store, encrypted BYOK configs, triage, lanes for Telegram / iCal / IMAP), cron [api/cron/companion-poll.js](api/cron/companion-poll.js), migration [api/_lib/migrations/20260828140000_companion_harness.sql](api/_lib/migrations/20260828140000_companion_harness.sql) | Live | Turns a person's own inbox, chats, calendar and phone into deliveries a 3D character makes **in person**. BYOK per source (a Telegram bot the user made, a private iCal URL, IMAP with an app password) plus a universal bridge token anything can POST to. Every message is scored 0-100 by the shared deterministic rules ([@three-ws/companion/triage](packages/companion-sdk/src/triage-rules.js), the same module the CLI runs locally) and optionally refined by the user's own Anthropic key; above their threshold and outside quiet hours it is delivered through `companion_delivery` notifications, so the bell, Web Push, and the avatar channel all carry it. A contact's message is spoken by **that contact's avatar and voice** (`control.announce({ avatar })` in [walk-sdk](walk-sdk)). Live SSE at `/api/companion/stream` feeds the desktop app and any third-party body. Docs: [docs/companion.md](docs/companion.md). Tests: [tests/companion-triage.test.js](tests/companion-triage.test.js), [tests/companion-calendar.test.js](tests/companion-calendar.test.js), [packages/companion-sdk/tests/](packages/companion-sdk/tests) || Visitor feedback loop | Capture + panel [src/feedback-companion.js](src/feedback-companion.js) (mounted by [src/walk-companion.js](src/walk-companion.js)), intake [api/feedback/report.js](api/feedback/report.js), queue API [api/feedback/index.js](api/feedback/index.js), scoring [api/_lib/feedback/triage.js](api/_lib/feedback/triage.js), store [api/_lib/feedback/store.js](api/_lib/feedback/store.js), cron [api/cron/feedback-triage.js](api/cron/feedback-triage.js), review page [pages/feedback.html](pages/feedback.html) `→ /feedback` + [src/feedback-page.js](src/feedback-page.js) | Live | The return channel on the corner companion: the visitor tells the avatar what broke and the report carries the route, build SHA, viewport, and the last console errors and failed requests the browser captured, so a vague sentence lands as an actionable row. The companion offers proactively at the one moment worth asking (right after the page actually threw), once per route per session, never in a background tab. **Feedback is data, never an instruction:** the model that reads untrusted visitor text writes six scalars to that report's own row and has no path to the repo, a deploy, or any other write; the admin-only `/feedback` queue groups reports into one row per problem and a person decides. Docs: [docs/feedback.md](docs/feedback.md). Tests: [tests/feedback-triage.test.js](tests/feedback-triage.test.js) || Prepaid credits (`/credits`) | [pages/credits.html](pages/credits.html) `→ /credits` + [src/credits.js](src/credits.js), balance/ledger [api/credits/index.js](api/credits/index.js) `→ GET /api/credits`, deposit verifier [api/credits/deposit.js](api/credits/deposit.js) `→ POST /api/credits/deposit` over [api/_lib/credit-deposit.js](api/_lib/credit-deposit.js), ledger engine [api/_lib/credits.js](api/_lib/credits.js), schema [api/_lib/migrations/20260621200000_credits.sql](api/_lib/migrations/20260621200000_credits.sql) | Live | The prepaid balance every metered action on the platform debits. Top up by sending SOL or $THREE to the platform deposit wallet (connect + SIWS-link + sign in the page, or paste a signature you already sent); crediting is server-authoritative and idempotent on the signature, so a signature that is not signed by a wallet linked to the account credits nobody. The page renders the caller's $THREE holder tier from the same `holder` block [api/pricing.js](api/pricing.js) returns ([api/_lib/three-tier.js](api/_lib/three-tier.js)), which is the discount [api/_lib/credits.js](api/_lib/credits.js) already applies to every debit, and lists what credits buy straight from the pricing catalog ([api/_lib/pricing/catalog.js](api/_lib/pricing/catalog.js)). Ledger is keyset-paginated. Docs: [docs/payment-sessions.md](docs/payment-sessions.md). Tests: [tests/credits.test.js](tests/credits.test.js) || Skill bundles (seller builder + evidence pricing) | [pages/bundles.html](pages/bundles.html) `→ /bundles`, API [api/agents/[id]/bundles.js](api/agents/%5Bid%5D/bundles.js), arithmetic [api/_lib/bundle-pricing.js](api/_lib/bundle-pricing.js), checkout [api/marketplace/purchase-bundle.js](api/marketplace/purchase-bundle.js) | Live (seller side); no buyer-facing browser view yet | Sell several of one agent's skills as one purchase. The price is derived from the agent's own ledger rather than a rule of thumb: the public `?action=pricing` endpoint finds every buyer who already bought 2+ of the selected skills, suggests the median of what they really paid (`basis: median_basket`), and backtests any candidate price against those same baskets; with no such buyer yet it falls back to 20% off the sum of the parts and labels itself `discount_off_list` so a default is never read as a finding. Every amount is an atomic integer carried as a BigInt end to end, because a 9-decimal mint puts real sums past `Number.MAX_SAFE_INTEGER`. Checkout settles on-chain and writes one `skill_purchases` row per skill (`kind = 'bundle'`, amount 0) so one bundle sale is never counted as N skill sales. Docs: [docs/skill-bundles.md](docs/skill-bundles.md). Tests: [tests/bundle-pricing.test.js](tests/bundle-pricing.test.js), [tests/vercel-agents-subpath-routes.test.js](tests/vercel-agents-subpath-routes.test.js) |@@ -220,6 +221,7 @@ bottom.| Seeker / Saga dApp Store app | [solana-mobile/](solana-mobile): TWA wrapper [solana-mobile/twa/](solana-mobile/twa), Publisher Portal listing copy [solana-mobile/publish/](solana-mobile/publish), MWA wallet + Seeker detection [solana-mobile/src/](solana-mobile/src) | In-repo · signed APK + assetlinks live · awaiting owner's Publisher Portal submission | Everything needed to package three.ws as a Solana Mobile app and publish it to the on-chain dApp Store. Targets Seeker first; compatible with Saga Gen 1 and Gen 2. Docs: [solana-mobile/README.md](solana-mobile/README.md) || iOS App Store app | [ios/](ios): Capacitor shell + config [ios/capacitor.config.ts](ios/capacitor.config.ts), Xcode project [ios/native/App/](ios/native/App), web-side native bridge [ios/src/native-bridge.js](ios/src/native-bridge.js), offline shell [ios/shell/](ios/shell), listing copy [ios/publish/](ios/publish), app association handler in [api/wk.js](api/wk.js) | In-repo · project builds and the web half ships on every deploy · awaiting an Apple Developer organization account | three.ws as a native iOS app (`ws.three.app`). A Capacitor 8 shell whose WKWebView runs the live `https://three.ws`, so the app is never a version behind the site; what makes it an app is the native layer around it. `ios/src/native-bridge.js` ships with the SITE, not the .ipa (Capacitor injects its bridge into the remote page, so `window.Capacitor` exists on three.ws only inside the app): it supplies the `navigator.share` WKWebView does not have, routes off-site links to an in-app Safari sheet instead of stranding the app's only WebView, handles universal links and `threews://` wallet returns, holds the launch screen until the first real frame, and marks `html.ios-app`. The `three-ws-ios-native-bridge` plugin in [vite.config.js](vite.config.js) copies it into `dist/` content-hashed and injects it into every built page except the third-party embed entries (671 pages, `/viewer` and `/ar` included, which a `transformIndexHtml` could not reach because they are copied verbatim from `public/`). `GET /.well-known/apple-app-site-association` is served from the API rather than a static file because Apple demands an exact path, a JSON content type and no redirect; it answers `503 not_configured` until `APPLE_TEAM_ID` is set rather than publishing an association that would fail silently on device. Docs: [ios/README.md](ios/README.md), [docs/ios-app.md](docs/ios-app.md), App Review posture [ios/docs/REVIEW-RISK.md](ios/docs/REVIEW-RISK.md), submission [ios/docs/SUBMISSION.md](ios/docs/SUBMISSION.md). || Walk Avatar browser extension | [extensions/walk-avatar/](extensions/walk-avatar) — MV3 `manifest.json`, `background.js` | In-repo · Chrome Web Store release checklist staged ([RELEASE.md](extensions/walk-avatar/RELEASE.md)) | Walks your three.ws avatar across any site and reads pages aloud — a browsing companion built on the same rig as the [walk-sdk](walk-sdk). Ships its own store-required [PRIVACY.md](extensions/walk-avatar/PRIVACY.md), [PERMISSIONS.md](extensions/walk-avatar/PERMISSIONS.md), and [TERMS.md](extensions/walk-avatar/TERMS.md). |+| Desktop companion app | [apps/desktop/](apps/desktop) — Electron main [src/main.js](apps/desktop/src/main.js), preload [src/preload.cjs](apps/desktop/src/preload.cjs), stage [src/renderer/](apps/desktop/src/renderer) | In-repo · packaged with electron-builder (`npm run dist`), not yet published | A transparent, click-through, always-on-top character that strolls across the bottom of the desktop and walks over to deliver what cleared the user's bar. Subscribes to `/api/companion/stream` with the same bridge token the CLI stores, and drives the published [walk embed](pages/walk-embed.html) over its postMessage contract, so it carries no 3D code of its own. Not an npm workspace: it installs and builds on its own (see [apps/desktop/README.md](apps/desktop/README.md)). || DCC tool integrations (Blender, ComfyUI) | [integrations/](integrations) — [integrations/blender/](integrations/blender), [integrations/comfyui/](integrations/comfyui), shared Python client [integrations/_pyclient/](integrations/_pyclient) | In-repo | First-party plugins that drive the public Forge pipeline (`/api/forge`) from inside the tools artists already use, so a model is generated without leaving the DCC. Docs: [integrations/README.md](integrations/README.md) || Base58 difficulty model (the honest math) | [src/solana/vanity/base58-distribution.js](src/solana/vanity/base58-distribution.js), dispatch in [src/solana/vanity/validation.js](src/solana/vanity/validation.js); ported copies in [solana-agent-sdk/src/vanity/verify.ts](solana-agent-sdk/src/vanity/verify.ts) and [mcp-server/src/lib/base58-distribution.js](mcp-server/src/lib/base58-distribution.js), held in agreement by [tests/vanity-model-parity.test.js](tests/vanity-model-parity.test.js) | In-repo | The exact probability that a random Solana address matches a vanity pattern, and the single source of truth behind every quote, price, rarity tier, bounty payout and signed receipt. Base58 is a positional encoding of a 256-bit integer, so the *leading* character is not uniform: the 40 symbols `K`-`z` are 17.2x harder to lead with than `5`-`H`, a 58x spread the old flat 58ⁿ model erased. Models are versioned (`base58-exact/v2`, superseding `58^effectiveLength`) and receipts name theirs, so attestations issued before the correction still verify. Spec: [docs/PROTOCOL-vanity.md](docs/PROTOCOL-vanity.md#41-difficulty-model-versioning) || Vanity address grinder (Rust → WASM) | [crates/vanity-grinder/](crates/vanity-grinder) → compiled to [src/solana/vanity/wasm/](src/solana/vanity/wasm); consumed by [src/agent-vanity-grinder.js](src/agent-vanity-grinder.js), [src/agent-eth-vanity-card.js](src/agent-eth-vanity-card.js) | In-repo | The Rust source behind in-browser Solana/EVM vanity-address mining. Compiled to WebAssembly so grinding runs on the visitor's machine, never the server. Surfaced as the `vanity_grinder` MCP tool and the premium pre-ground inventory (`vanity_premium`). |@@ -322,6 +324,7 @@ packages/tutor-mcp/ → @three-ws/tutor-mcp (MCP server — itpackages/loom-mcp/ → @three-ws/loom-mcp (MCP server — Loom 3D-creation gallery: browse, fetch, submit)packages/spatial-mcp/ → @three-ws/spatial-mcp (Spatial MCP validator, builder + conformance fixture corpus)packages/agent-sniper/ → @three-ws/agent-sniper (engine + CLI + MCP server + x402 paid API — autonomous, self-custodial pump.fun sniper)+packages/companion-sdk/ → @three-ws/companion (personal companion: client + SSE stream, shared triage rules, page stage, CLI, MCP server)walk-sdk/ → @three-ws/walk (page walking companion + playground + avatar picker)tour-sdk/ → @three-ws/tour (guided site tour: 3D guide walks a live site, spotlights sections)assistant-sdk/ → @three-ws/assistant (embeddable 3D avatar assistant widget: loader + one-tag CDN build)@@ -363,6 +366,7 @@ is idempotent via `node scripts/publish-packages.mjs` (skips versions already onnpm).| Package | Location | Wraps | What it does |+| 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) ||---|---|---|---|| `@three-ws/forge` | [packages/forge/](packages/forge) | `api/forge*.js`, `api/mcp-3d.js` | Text/image/sketch → textured, rig-ready GLB; free TRELLIS lane + paid tiers + auto-rig || `@three-ws/names` | [packages/names/](packages/names) | `api/sns*.js`, `api/x402/pay-by-name.js` | ENS + SNS resolution, `*.threews.sol` minting, pay-by-name |diff --git a/data/changelog.json b/data/changelog.jsonindex ea1ea230f..42a9d0d88 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -1,6 +1,28 @@{"$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. `link` is optional and must be a live three.ws path.","entries": [+ {+ "date": "2026-08-28",+ "title": "We now prove our fallbacks work, instead of hoping they do",+ "summary": "Adding a backup for an outside service is easy; knowing it made things better is not. A new audit reads the whole codebase and grades every call we make to an outside service on five protections, publishes the result as a public map, and fails the build if a new unprotected call is added or an existing one gets worse. On top of it, each endpoint now declares what it is allowed to tell you when a service it depends on is down, and a test proves it by actually breaking the service and checking the answer. That immediately caught a real bug: a token lookup was telling people a token did not exist when the price indexer was simply unreachable. Related fixes stop stale data reaching a payment retry, a token security verdict and an access check, where an out-of-date answer costs money or grants access.",+ "tags": [+ "feature",+ "improvement",+ "infra"+ ],+ "link": "/docs/resilience"+ },+ {+ "date": "2026-08-28",+ "title": "Your notifications now have a body: meet your companion",+ "summary": "Your phone buzzes forty times a day and two of those mattered. three.ws/companion is the other half of that problem. Connect what you already use, on your own keys: a Telegram bot you create, the private calendar link Google, Apple and Outlook all publish, your inbox over IMAP with an app password, or nothing at all but a token your phone, your Mac, your build script or an AI agent can post to. Everything that arrives is scored out of 100 against the things people actually want interrupting for (a saved contact asking you something, a one-time code, a meeting starting in ten minutes, a payment that failed) and the rest is kept quietly in a feed with the reason it stayed quiet. What clears your bar is delivered in person: a 3D character walks on, and if it is from someone you gave a face to, it arrives wearing their avatar and speaking in their voice. It reaches you on three.ws, as a push on your phone, and on your desktop, where a new companion app puts a character that walks across your screen and comes over to tell you. Quiet hours are absolute, the credentials are encrypted, and one button revokes every device. Developers get the whole thing as @three-ws/companion: a client, the same triage rules the server runs (so you can score your mail locally and never send the rest), a drop-in 3D stage for any page, a CLI, and an MCP server so an agent that finds something urgent can stand in front of you and say it.",+ "tags": [+ "feature",+ "sdk",+ "improvement"+ ],+ "link": "/companion"+ },{"date": "2026-08-28","title": "AI agents can now see the 3D models they make",diff --git a/data/pages.json b/data/pages.jsonindex 529029fe4..fefdf04e8 100644--- a/data/pages.json+++ b/data/pages.json@@ -975,6 +975,14 @@"priority": 0.6,"changefreq": "monthly","added": "2026-08-28"+ },+ {+ "path": "/stream",+ "title": "Progressive Avatars",+ "description": "A3S packs a GLB into nested layers whose first 50 KB is already a complete, skinned, spec-valid avatar, then refines it in place over plain HTTP range requests. Live side-by-side against a classic GLB load.",+ "priority": 0.6,+ "changefreq": "monthly",+ "added": "2026-08-28"}]},@@ -4480,6 +4488,14 @@"priority": 0.6,"changefreq": "monthly"},+ {+ "path": "/docs/resilience",+ "title": "Docs · Upstream resilience map",+ "description": "Every third-party service this platform calls and what happens to a user when it goes down. Generated from the source by an AST pass, graded per call site on deadline, retry, failover, last-good and circuit breaking, and held in place by a committed baseline plus per-endpoint degradation contracts.",+ "priority": 0.6,+ "changefreq": "monthly",+ "added": "2026-08-28"+ },{"path": "/docs/shared-utilities","title": "Docs · Shared utilities",@@ -5193,6 +5209,14 @@"changefreq": "weekly","added": "2026-07-30"},+ {+ "path": "/brownout",+ "title": "Brownout",+ "description": "Every response from this API says where its data came from and how fresh it is, and every declared fallback has been proven by breaking the upstream it protects against, inside the real request path. Read the receipts: which provider refused, which one caught the request, and how old the answer was.",+ "priority": 0.6,+ "changefreq": "weekly",+ "added": "2026-08-28"+ },{"path": "/docs/tutorials/write-a-guard","title": "Docs · Write a repository guard",diff --git a/docs/start-here.md b/docs/start-here.mdindex 97a707012..f3b2380d5 100644--- a/docs/start-here.md+++ b/docs/start-here.md@@ -147,6 +147,7 @@ Curious what happens between the prompt and the model? [How the Forge works](./h- **Competing today?** → [Daily Match](./daily-match.md): live daily standings over real agent output (actions, trades, skill sales, launches), resetting 00:00 UTC- **Developer docs** → Read the [Introduction](./introduction.md) for the full technical picture- **Contributing code?** → [Shared utilities](./shared-utilities.md) — the modules to import instead of hand-rolling: sanitized Markdown, toasts, fuzzy search, retry/circuit-breaking, bounded caches and concurrency pools, and safe CSV export+- **Wondering what happens when a third-party service goes down?** → [Upstream resilience map](./resilience.md) — every external service this platform calls, what protects each call, and the degradation contract each endpoint is held to- **Your agent needs a face?** → [OKX.AI marketplace services](./okx-marketplace.md) — the Agent Identity Studio and the pay-per-call 3D services other agents buy from us; demo identities at [/agent-identities](/agent-identities)- **Buying 3D asset work per call?** → [The 3D Asset Pipeline](./3d-pipeline.md) — pay a few cents in USDC to rig, remesh, make game-ready, stylize, or background-remove an asset; one call, one finished URL, no account or API key- **Want your agent to have a body?** → [Embodiment](./embody.md) — one $1 USDC call turns a prompt or image into a rigged, animated, voiced 3D avatar plus a one-tag embed for any website; no account, no separate rigging stepdiff --git a/package.json b/package.jsonindex 42cba0e70..bb2a2fb60 100644--- a/package.json+++ b/package.json@@ -120,6 +120,7 @@"packages/tool-sdk","packages/spatial-mcp","packages/agent-runtime",+ "packages/render","packages/glb-diff","packages/tty-avatar"],@@ -190,6 +191,8 @@"audit:pages": "node scripts/audit-page-index.mjs --strict","audit:meetup": "node scripts/meetup-audit.mjs","audit:docs": "node scripts/audit-docs.mjs",+ "audit:upstreams": "node scripts/audit-upstreams.mjs",+ "audit:upstreams:map": "node scripts/audit-upstreams.mjs --map","docs:freshness": "node scripts/doc-freshness.mjs","check:docs-freshness": "node scripts/doc-freshness.mjs --check","tutorials:media": "node scripts/capture-tutorial-media.mjs",@@ -198,7 +201,7 @@"audit:route-shadowing": "node scripts/audit-route-shadowing.mjs","audit:handlers": "node scripts/audit-empty-handlers.mjs","audit:x402-catalog": "node scripts/audit-x402-catalog.mjs",- "gate": "npm run check:conflicts && npm run check:claude && npm run check:vendored && npm run check:fetch-timeouts && npm run check:tdz-bootstrap && npm run check:event && npm run check:cron-syntax && npm run check:studio-openapi && npm run test:gate && npm run test:gate-3d && npm run audit:mcp && npm run audit:mcp-golden && npm run audit:mcp-safety && npm run audit:mcp-catalog && npm run audit:routes && npm run audit:handlers && npm run audit:pages && npm run audit:links && npm run audit:docs && npm run check:tutorials && npm run audit:hidden-guard && npm run audit:inline-handlers && npm run audit:x402-catalog && npm run audit:tokens && npm run audit:guards && npm run audit:tour-atlas",+ "gate": "npm run check:conflicts && npm run check:claude && npm run check:vendored && npm run check:fetch-timeouts && npm run check:tdz-bootstrap && npm run check:event && npm run check:cron-syntax && npm run check:studio-openapi && npm run test:gate && npm run test:gate-3d && npm run audit:mcp && npm run audit:mcp-golden && npm run audit:mcp-safety && npm run audit:mcp-catalog && npm run audit:routes && npm run audit:handlers && npm run audit:pages && npm run audit:links && npm run audit:docs && npm run audit:upstreams && npm run check:tutorials && npm run audit:hidden-guard && npm run audit:inline-handlers && npm run audit:x402-catalog && npm run audit:tokens && npm run audit:guards && npm run audit:tour-atlas","test:gate-3d": "vitest run tests/glb-canonicalize.test.js tests/animation-retarget.test.js tests/animation-retarget-rest-pollution.test.js tests/viewer-framing.test.js","audit:mcp-golden": "node scripts/audit-mcp-golden.mjs","audit:mcp-safety": "node scripts/audit-mcp-safety.mjs",@@ -401,7 +404,8 @@"check:doc-media": "node scripts/check-doc-media.mjs","sync:studio-openapi": "node scripts/sync-studio-openapi.mjs","check:studio-openapi": "node scripts/sync-studio-openapi.mjs --check",- "token:volume": "node scripts/token-volume.mjs"+ "token:volume": "node scripts/token-volume.mjs",+ "companion:e2e": "node --env-file=.env.local --env-file=.env scripts/companion-e2e.mjs"},"dependencies": {"@0xsplits/splits-sdk": "^6.5.0",diff --git a/public/changelog.json b/public/changelog.jsonindex 0a331003c..8a2b58016 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,11 +1,21 @@{- "generated_at": "2026-08-28T03:32:47.846Z",+ "generated_at": "2026-08-28T03:37:23.829Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws","url": "https://three.ws"},"entries": [+ {+ "date": "2026-08-28",+ "type": "launch",+ "title": "Brownout",+ "summary": "Every response from this API says where its data came from and how fresh it is, and every declared fallback has been proven by breaking the upstream it protects against, inside the real request path. Read the receipts: which provider refused, which one caught the request, and how old the answer was.",+ "link": "/brownout",+ "tags": [+ "launch"+ ]+ },{"date": "2026-08-28","type": "launch",@@ -36,6 +46,16 @@"launch"]},+ {+ "date": "2026-08-28",+ "type": "launch",+ "title": "Docs · Companion",+ "summary": "The personal companion: connect your own Telegram bot, calendar, inbox, or phone, give your contacts a face and a voice, and have a 3D character deliver what matters in person. Bridges, triage rules, the SDK, the CLI, the MCP server, and the desktop app.",+ "link": "/docs/companion",+ "tags": [+ "launch"+ ]+ },{"date": "2026-08-28","type": "launch",@@ -56,6 +76,36 @@"launch"]},+ {+ "date": "2026-08-28",+ "type": "launch",+ "title": "Docs · The Oracle model, and how to run it yourself",+ "summary": "How the three.ws conviction model is fitted, what its three heads predict, why the outcome labels had to be made independent of the SOL price, how the promotion gate decides which model ships, and how to score launches locally with @three-ws/oracle-model.",+ "link": "/docs/oracle-model",+ "tags": [+ "launch"+ ]+ },+ {+ "date": "2026-08-28",+ "type": "launch",+ "title": "Docs · Upstream resilience map",+ "summary": "Every third-party service this platform calls and what happens to a user when it goes down. Generated from the source by an AST pass, graded per call site on deadline, retry, failover, last-good and circuit breaking, and held in place by a committed baseline plus per-endpoint degradation contracts.",+ "link": "/docs/resilience",+ "tags": [+ "launch"+ ]+ },+ {+ "date": "2026-08-28",+ "type": "launch",+ "title": "Glance",+ "summary": "Your three.ws agent on every home screen: a live card for the Windows 11 widgets board, a README, Slack, or any page.",+ "link": "/glance",+ "tags": [+ "launch"+ ]+ },{"date": "2026-08-28","type": "launch",@@ -66,6 +116,16 @@"launch"]},+ {+ "date": "2026-08-28",+ "type": "launch",+ "title": "Oracle Lab: the model, published",+ "summary": "The Oracle's conviction model in full: every bucket weight with the number of labeled launches behind it and what happened to them, the held-out reliability curve for each tier, the version history of every refit including the ones that were refused, and a live scorer that runs the real weights in your browser. Download it and reproduce any score offline.",+ "link": "/oracle-lab",+ "tags": [+ "launch"+ ]+ },{"date": "2026-08-28","type": "launch",@@ -76,6 +136,16 @@"launch"]},+ {+ "date": "2026-08-28",+ "type": "launch",+ "title": "Progressive Avatars",+ "summary": "A3S packs a GLB into nested layers whose first 50 KB is already a complete, skinned, spec-valid avatar, then refines it in place over plain HTTP range requests. Live side-by-side against a classic GLB load.",+ "link": "/stream",+ "tags": [+ "launch"+ ]+ },{"date": "2026-08-28","type": "launch",@@ -203,6 +273,18 @@"docs"]},+ {+ "date": "2026-08-28",+ "type": "update",+ "title": "We now prove our fallbacks work, instead of hoping they do",+ "summary": "Adding a backup for an outside service is easy; knowing it made things better is not. A new audit reads the whole codebase and grades every call we make to an outside service on five protections, publishes the result as a public map, and fails the build if a new unprotected call is added or an existing one gets worse. On top of it, each endpoint now declares what it is allowed to tell you when a service it depends on is down, and a test proves it by actually breaking the service and checking the answer. That immediately caught a real bug: a token lookup was telling people a token did not exist when the price indexer was simply unreachable. Related fixes stop stale data reaching a payment retry, a token security verdict and an access check, where an out-of-date answer costs money or grants access.",+ "link": "/docs/resilience",+ "tags": [+ "feature",+ "improvement",+ "infra"+ ]+ },{"date": "2026-08-28","type": "update",@@ -236,6 +318,18 @@"sdk"]},+ {+ "date": "2026-08-28",+ "type": "update",+ "title": "Your notifications now have a body: meet your companion",+ "summary": "Your phone buzzes forty times a day and two of those mattered. three.ws/companion is the other half of that problem. Connect what you already use, on your own keys: a Telegram bot you create, the private calendar link Google, Apple and Outlook all publish, your inbox over IMAP with an app password, or nothing at all but a token your phone, your Mac, your build script or an AI agent can post to. Everything that arrives is scored out of 100 against the things people actually want interrupting for (a saved contact asking you something, a one-time code, a meeting starting in ten minutes, a payment that failed) and the rest is kept quietly in a feed with the reason it stayed quiet. What clears your bar is delivered in person: a 3D character walks on, and if it is from someone you gave a face to, it arrives wearing their avatar and speaking in their voice. It reaches you on three.ws, as a push on your phone, and on your desktop, where a new companion app puts a character that walks across your screen and comes over to tell you. Quiet hours are absolute, the credentials are encrypted, and one button revokes every device. Developers get the whole thing as @three-ws/companion: a client, the same triage rules the server runs (so you can score your mail locally and never send the rest), a drop-in 3D stage for any page, a CLI, and an MCP server so an agent that finds something urgent can stand in front of you and say it.",+ "link": "/companion",+ "tags": [+ "feature",+ "sdk",+ "improvement"+ ]+ },{"date": "2026-08-27","type": "launch",diff --git a/public/changelog.xml b/public/changelog.xmlindex c44bcb21c..ce4169603 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -6,6 +6,14 @@<atom:link href="https://three.ws/changelog.xml" rel="self" type="application/rss+xml"/><description>What's new on three.ws: features, improvements, and releases, newest first.</description><language>en</language>+ <item>+ <title>Brownout</title>+ <link>https://three.ws/brownout</link>+ <guid isPermaLink="false">2026-08-28:Brownout</guid>+ <pubDate>Fri, 28 Aug 2026 12:00:00 GMT</pubDate>+ <category>launch</category>+ <description>Every response from this API says where its data came from and how fresh it is, and every declared fallback has been proven by breaking the upstream it protects against, inside the real request path. Read the receipts: which provider refused, which one caught the request, and how old the answer was.</description>+ </item><item><title>Companion</title><link>https://three.ws/companion</link>@@ -30,6 +38,14 @@<category>launch</category><description>Every liveness check was green while ten of twelve autonomous agents had not acted in weeks. Capability attestation models an agent's preconditions as a causal graph and returns the root blocker plus the command that fixes it, instead of a checklist of symptoms.</description></item>+ <item>+ <title>Docs · Companion</title>+ <link>https://three.ws/docs/companion</link>+ <guid isPermaLink="false">2026-08-28:Docs · Companion</guid>+ <pubDate>Fri, 28 Aug 2026 12:00:00 GMT</pubDate>+ <category>launch</category>+ <description>The personal companion: connect your own Telegram bot, calendar, inbox, or phone, give your contacts a face and a voice, and have a 3D character deliver what matters in person. Bridges, triage rules, the SDK, the CLI, the MCP server, and the desktop app.</description>+ </item><item><title>Docs · Feedback</title><link>https://three.ws/docs/feedback</link>@@ -46,6 +62,30 @@<category>launch</category><description>The @three-ws/tty-avatar package: any three.ws avatar or agent body rendered live in a terminal by a software rasterizer (truecolor half-blocks, braille, or plain ASCII), procedural moods, and Claude Code hooks that turn it into your coding agent's face.</description></item>+ <item>+ <title>Docs · The Oracle model, and how to run it yourself</title>+ <link>https://three.ws/docs/oracle-model</link>+ <guid isPermaLink="false">2026-08-28:Docs · The Oracle model, and how to run it yourself</guid>+ <pubDate>Fri, 28 Aug 2026 12:00:00 GMT</pubDate>+ <category>launch</category>+ <description>How the three.ws conviction model is fitted, what its three heads predict, why the outcome labels had to be made independent of the SOL price, how the promotion gate decides which model ships, and how to score launches locally with @three-ws/oracle-model.</description>+ </item>+ <item>+ <title>Docs · Upstream resilience map</title>+ <link>https://three.ws/docs/resilience</link>+ <guid isPermaLink="false">2026-08-28:Docs · Upstream resilience map</guid>+ <pubDate>Fri, 28 Aug 2026 12:00:00 GMT</pubDate>+ <category>launch</category>+ <description>Every third-party service this platform calls and what happens to a user when it goes down. Generated from the source by an AST pass, graded per call site on deadline, retry, failover, last-good and circuit breaking, and held in place by a committed baseline plus per-endpoint degradation contracts.</description>+ </item>+ <item>+ <title>Glance</title>+ <link>https://three.ws/glance</link>+ <guid isPermaLink="false">2026-08-28:Glance</guid>+ <pubDate>Fri, 28 Aug 2026 12:00:00 GMT</pubDate>+ <category>launch</category>+ <description>Your three.ws agent on every home screen: a live card for the Windows 11 widgets board, a README, Slack, or any page.</description>+ </item><item><title>Herald</title><link>https://three.ws/herald</link>@@ -54,6 +94,14 @@<category>launch</category><description>Deliver a message in person: a 3D character walks onto your page and tells the user what happened. Open SDK, one line of code, an accessible fallback, and a CLI that announces when your build finishes.</description></item>+ <item>+ <title>Oracle Lab: the model, published</title>+ <link>https://three.ws/oracle-lab</link>+ <guid isPermaLink="false">2026-08-28:Oracle Lab: the model, published</guid>+ <pubDate>Fri, 28 Aug 2026 12:00:00 GMT</pubDate>+ <category>launch</category>+ <description>The Oracle's conviction model in full: every bucket weight with the number of labeled launches behind it and what happened to them, the held-out reliability curve for each tier, the version history of every refit including the ones that were refused, and a live scorer that runs the real weights in your browser. Download it and reproduce any score offline.</description>+ </item><item><title>Portal</title><link>https://three.ws/portal</link>@@ -62,6 +110,14 @@<category>launch</category><description>Paste any web address and walk through it in 3D. Portal reads the page's real structure and builds a place from it: sections become buildings sized by what they say, links become doors you step into, images become billboards. Download the world as a GLB or embed it in your own site.</description></item>+ <item>+ <title>Progressive Avatars</title>+ <link>https://three.ws/stream</link>+ <guid isPermaLink="false">2026-08-28:Progressive Avatars</guid>+ <pubDate>Fri, 28 Aug 2026 12:00:00 GMT</pubDate>+ <category>launch</category>+ <description>A3S packs a GLB into nested layers whose first 50 KB is already a complete, skinned, spec-valid avatar, then refines it in place over plain HTTP range requests. Live side-by-side against a classic GLB load.</description>+ </item><item><title>Publishing to the Solana dApp Store</title><link>https://three.ws/docs/seeker-publishing</link>@@ -158,6 +214,14 @@<category>fix</category><description>The three.ws app on Solana Seeker verifies against the site and opens full-screen on its own home screen, with no browser address bar. Two bugs found while testing it on a real Android build are fixed: the app only recognised your Seed Vault wallet on the first page you opened, so signing in from the login page said no wallet was found, and the login page never loaded the wallet at all. A new guide documents exactly how a release reaches the Solana dApp Store, from the publisher account through building and submitting the app.</description></item>+ <item>+ <title>We now prove our fallbacks work, instead of hoping they do</title>+ <link>https://three.ws/docs/resilience</link>+ <guid isPermaLink="false">2026-08-28:We now prove our fallbacks work, instead of hoping they do</guid>+ <pubDate>Fri, 28 Aug 2026 12:00:00 GMT</pubDate>+ <category>feature</category>+ <description>Adding a backup for an outside service is easy; knowing it made things better is not. A new audit reads the whole codebase and grades every call we make to an outside service on five protections, publishes the result as a public map, and fails the build if a new unprotected call is added or an existing one gets worse. On top of it, each endpoint now declares what it is allowed to tell you when a service it depends on is down, and a test proves it by actually breaking the service and checking the answer. That immediately caught a real bug: a token lookup was telling people a token did not exist when the price indexer was simply unreachable. Related fixes stop stale data reaching a payment retry, a token security verdict and an access check, where an out-of-date answer costs money or grants access.</description>+ </item><item><title>Your agent now tells you the important things in person</title><link>https://three.ws/notifications</link>@@ -182,6 +246,14 @@<category>feature</category><description>A new package, @three-ws/tty-avatar, draws any three.ws avatar or agent body live in a terminal window: one npx command, no browser, no GPU, 24 frames a second in colour. It has moods (thinking, working, happy, error, asleep) that work on any model without a rig, and one command wires it to Claude Code so the avatar thinks while the agent reads your prompt, nods while it edits files, shakes when a tool fails and bounces when it finishes, with a caption naming what it is doing. Every avatar and agent page now has the command in its Embed tab.</description></item>+ <item>+ <title>Your notifications now have a body: meet your companion</title>+ <link>https://three.ws/companion</link>+ <guid isPermaLink="false">2026-08-28:Your notifications now have a body: meet your companion</guid>+ <pubDate>Fri, 28 Aug 2026 12:00:00 GMT</pubDate>+ <category>feature</category>+ <description>Your phone buzzes forty times a day and two of those mattered. three.ws/companion is the other half of that problem. Connect what you already use, on your own keys: a Telegram bot you create, the private calendar link Google, Apple and Outlook all publish, your inbox over IMAP with an app password, or nothing at all but a token your phone, your Mac, your build script or an AI agent can post to. Everything that arrives is scored out of 100 against the things people actually want interrupting for (a saved contact asking you something, a one-time code, a meeting starting in ten minutes, a payment that failed) and the rest is kept quietly in a feed with the reason it stayed quiet. What clears your bar is delivered in person: a 3D character walks on, and if it is from someone you gave a face to, it arrives wearing their avatar and speaking in their voice. It reaches you on three.ws, as a push on your phone, and on your desktop, where a new companion app puts a character that walks across your screen and comes over to tell you. Quiet hours are absolute, the credentials are encrypted, and one button revokes every device. Developers get the whole thing as @three-ws/companion: a client, the same triage rules the server runs (so you can score your mail locally and never send the rest), a drop-in 3D stage for any page, a CLI, and an MCP server so an agent that finds something urgent can stand in front of you and say it.</description>+ </item><item><title>three.ws for Seeker</title><link>https://three.ws/seeker</link>diff --git a/public/features.json b/public/features.jsonindex 810f47edf..c08702566 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-08-28T03:32:47.833Z",+ "generated_at": "2026-08-28T03:37:23.815Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",@@ -892,6 +892,16 @@"tags": [],"showcase": false},+ {+ "path": "/glance",+ "title": "Glance",+ "description": "Your three.ws agent on every home screen: a live card for the Windows 11 widgets board, a README, Slack, or any page.",+ "added": "2026-08-28",+ "auth": null,+ "indexable": true,+ "tags": [],+ "showcase": false+ },{"path": "/widgets","title": "Widgets Gallery",@@ -1181,6 +1191,16 @@"indexable": true,"tags": [],"showcase": false+ },+ {+ "path": "/stream",+ "title": "Progressive Avatars",+ "description": "A3S packs a GLB into nested layers whose first 50 KB is already a complete, skinned, spec-valid avatar, then refines it in place over plain HTTP range requests. Live side-by-side against a classic GLB load.",+ "added": "2026-08-28",+ "auth": null,+ "indexable": true,+ "tags": [],+ "showcase": false}]},@@ -1456,6 +1476,16 @@"tags": [],"showcase": false},+ {+ "path": "/oracle-lab",+ "title": "Oracle Lab: the model, published",+ "description": "The Oracle's conviction model in full: every bucket weight with the number of labeled launches behind it and what happened to them, the held-out reliability curve for each tier, the version history of every refit including the ones that were refused, and a live scorer that runs the real weights in your browser. Download it and reproduce any score offline.",+ "added": "2026-08-28",+ "auth": null,+ "indexable": true,+ "tags": [],+ "showcase": false+ },{"path": "/oracle/docs","title": "Oracle Docs: the conviction engine, end to end",@@ -4087,6 +4117,16 @@"tags": [],"showcase": false},+ {+ "path": "/docs/companion",+ "title": "Docs · Companion",+ "description": "The personal companion: connect your own Telegram bot, calendar, inbox, or phone, give your contacts a face and a voice, and have a 3D character deliver what matters in person. Bridges, triage rules, the SDK, the CLI, the MCP server, and the desktop app.",+ "added": "2026-08-28",+ "auth": null,+ "indexable": true,+ "tags": [],+ "showcase": false+ },{"path": "/docs/mcp","title": "Docs · MCP",@@ -5757,6 +5797,16 @@"tags": [],"showcase": false},+ {+ "path": "/docs/resilience",+ "title": "Docs · Upstream resilience map",+ "description": "Every third-party service this platform calls and what happens to a user when it goes down. Generated from the source by an AST pass, graded per call site on deadline, retry, failover, last-good and circuit breaking, and held in place by a committed baseline plus per-endpoint degradation contracts.",+ "added": "2026-08-28",+ "auth": null,+ "indexable": true,+ "tags": [],+ "showcase": false+ },{"path": "/docs/shared-utilities","title": "Docs · Shared utilities",@@ -5967,6 +6017,16 @@"tags": [],"showcase": false},+ {+ "path": "/docs/oracle-model",+ "title": "Docs · The Oracle model, and how to run it yourself",+ "description": "How the three.ws conviction model is fitted, what its three heads predict, why the outcome labels had to be made independent of the SOL price, how the promotion gate decides which model ships, and how to score launches locally with @three-ws/oracle-model.",+ "added": "2026-08-28",+ "auth": null,+ "indexable": true,+ "tags": [],+ "showcase": false+ },{"path": "/docs/x402-distribution","title": "Docs · x402 distribution",@@ -6687,6 +6747,16 @@"tags": [],"showcase": false},+ {+ "path": "/brownout",+ "title": "Brownout",+ "description": "Every response from this API says where its data came from and how fresh it is, and every declared fallback has been proven by breaking the upstream it protects against, inside the real request path. Read the receipts: which provider refused, which one caught the request, and how old the answer was.",+ "added": "2026-08-28",+ "auth": null,+ "indexable": true,+ "tags": [],+ "showcase": false+ },{"path": "/docs/tutorials/write-a-guard","title": "Docs · Write a repository guard",diff --git a/public/llms-full.txt b/public/llms-full.txtindex 5dddf5c20..10a312076 100644--- a/public/llms-full.txt+++ b/public/llms-full.txt@@ -546,6 +546,12 @@ URL: https://three.ws/artifactRenders Claude artifact bundles as standalone embeddable apps.+### Glance++URL: https://three.ws/glance++Your three.ws agent on every home screen: a live card for the Windows 11 widgets board, a README, Slack, or any page.+### Widgets GalleryURL: https://three.ws/widgets@@ -720,6 +726,12 @@ URL: https://three.ws/ttycurl three.ws/tty and a rigged 3D agent walks in your terminal. A software rasterizer streams ANSI frames over HTTP: no GPU, no WebGL, nothing to install. Also the @three-ws/tty CLI and library for rendering any GLB in a terminal.+### Progressive Avatars++URL: https://three.ws/stream++A3S packs a GLB into nested layers whose first 50 KB is already a complete, skinned, spec-valid avatar, then refines it in place over plain HTTP range requests. Live side-by-side against a classic GLB load.+## LabsExperimental features actively shipping. Expect fast iteration.@@ -884,6 +896,12 @@ URL: https://three.ws/oracleA fused AI conviction engine for every pump.fun launch: pedigree (who's buying), structure (bundle vs organic), narrative (what story is it riding), and momentum: fused into a single 0-100 conviction score with transparent pillar reasoning.+### Oracle Lab: the model, published++URL: https://three.ws/oracle-lab++The Oracle's conviction model in full: every bucket weight with the number of labeled launches behind it and what happened to them, the held-out reliability curve for each tier, the version history of every refit including the ones that were refused, and a live scorer that runs the real weights in your browser. Download it and reproduce any score offline.+### Oracle Docs: the conviction engine, end to endURL: https://three.ws/oracle/docs@@ -2481,6 +2499,12 @@ URL: https://three.ws/docs/web-componentReference for the <agent-3d> custom element.+### Docs · Companion++URL: https://three.ws/docs/companion++The personal companion: connect your own Telegram bot, calendar, inbox, or phone, give your contacts a face and a voice, and have a 3D character deliver what matters in person. Bridges, triage rules, the SDK, the CLI, the MCP server, and the desktop app.+### Docs · MCPURL: https://three.ws/docs/mcp@@ -3483,6 +3507,12 @@ URL: https://three.ws/docs/seed-qualityNobody asked for the assets the platform seeds into its own catalogue, so they have to earn their slot. The gate that decides whether a platform-generated model is published or discarded, and the metrics it scores.+### Docs · Upstream resilience map++URL: https://three.ws/docs/resilience++Every third-party service this platform calls and what happens to a user when it goes down. Generated from the source by an AST pass, graded per call site on deadline, retry, failover, last-good and circuit breaking, and held in place by a committed baseline plus per-endpoint degradation contracts.+### Docs · Shared utilitiesURL: https://three.ws/docs/shared-utilities@@ -3609,6 +3639,12 @@ URL: https://three.ws/docs/oracleThe complete story of Oracle: why it was built, how the scoring model works, the exact maths, the agent action loop, every platform feature that runs on it, and the paid integration other agents can call.+### Docs · The Oracle model, and how to run it yourself++URL: https://three.ws/docs/oracle-model++How the three.ws conviction model is fitted, what its three heads predict, why the outcome labels had to be made independent of the SOL price, how the promotion gate decides which model ships, and how to score launches locally with @three-ws/oracle-model.+### Docs · x402 distributionURL: https://three.ws/docs/x402-distribution@@ -4041,6 +4077,12 @@ URL: https://three.ws/guardsEvery mechanical guard that protects the three.ws codebase, and the stage each one runs in. This repository has no CI, so correctness is enforced by fast local checks wired into the prebuild, the gate, the deploy build, and the git pre-push hook. Filter by stage, search by command, and read the incident behind each one.+### Brownout++URL: https://three.ws/brownout++Every response from this API says where its data came from and how fresh it is, and every declared fallback has been proven by breaking the upstream it protects against, inside the real request path. Read the receipts: which provider refused, which one caught the request, and how old the answer was.+### Docs · Write a repository guardURL: https://three.ws/docs/tutorials/write-a-guarddiff --git a/public/llms.txt b/public/llms.txtindex f953c64f3..3d490f05c 100644--- a/public/llms.txt+++ b/public/llms.txt@@ -117,6 +117,7 @@ Create and customize an agent.- [glTF Validator](https://three.ws/validation): Khronos-spec validator for glTF/GLB files. Paste a URL or upload a model.- [Widget Studio](https://three.ws/studio): Pick an avatar, configure embed options, copy a one-line snippet for your site.- [Artifact Viewer](https://three.ws/artifact): Renders Claude artifact bundles as standalone embeddable apps.+- [Glance](https://three.ws/glance): Your three.ws agent on every home screen: a live card for the Windows 11 widgets board, a README, Slack, or any page.- [Widgets Gallery](https://three.ws/widgets): Pre-built chat, voice, and 3D-avatar widgets you can drop into any page.- [Hydrate](https://three.ws/hydrate): Take an existing on-chain agent (ERC-8004 / Solana) and attach a 3D body, voice, and skills.- [Integrations](https://three.ws/integrations): Drop-in 3D agents, chat widgets, walk companions, and live token embeds for any site. One script tag. Powered by three.ws.@@ -146,6 +147,7 @@ Create and customize an agent.- [Rig Doctor](https://three.ws/rig-doctor): Drop a .glb and find out in one second whether it will animate on three.ws. Names your skeleton convention, scores every limb group against the 52-joint canonical skeleton, repairs non-standard bone names in the browser, and previews the result. Nothing is uploaded.- [Skill Bundles](https://three.ws/bundles): Sell several of an agent's skills as one purchase, priced from your own sales instead of a rule of thumb. three.ws finds the buyers who already bought two or more of those skills separately and backtests any price against what they really paid, so you see what the bundle would have earned before you publish it.- [Terminal renderer](https://three.ws/tty): curl three.ws/tty and a rigged 3D agent walks in your terminal. A software rasterizer streams ANSI frames over HTTP: no GPU, no WebGL, nothing to install. Also the @three-ws/tty CLI and library for rendering any GLB in a terminal.+- [Progressive Avatars](https://three.ws/stream): A3S packs a GLB into nested layers whose first 50 KB is already a complete, skinned, spec-valid avatar, then refines it in place over plain HTTP range requests. Live side-by-side against a classic GLB load.## Labs@@ -182,6 +184,7 @@ On-chain features: pay-per-call, token launches, vanity wallets.- [Sperax on three.ws](https://three.ws/sperax): Free AI credits for three.ws users on chat.sperax.io: what the integration is and how to claim it.- [The AGI: narrow by design](https://three.ws/agi): The first AGI, narrow by design: a single autonomous agent that is genuinely superhuman at one thing, trading memecoins on pump.fun (Solana), and deliberately nothing else. Watch its embodied 3D body react to the market in real time, read every decision it makes with its stated confidence, and hold it to a chain-proven track record. Outside that one domain, it claims nothing.- [Oracle: AI Conviction Engine](https://three.ws/oracle): A fused AI conviction engine for every pump.fun launch: pedigree (who's buying), structure (bundle vs organic), narrative (what story is it riding), and momentum: fused into a single 0-100 conviction score with transparent pillar reasoning.+- [Oracle Lab: the model, published](https://three.ws/oracle-lab): The Oracle's conviction model in full: every bucket weight with the number of labeled launches behind it and what happened to them, the held-out reliability curve for each tier, the version history of every refit including the ones that were refused, and a live scorer that runs the real weights in your browser. Download it and reproduce any score offline.- [Oracle Docs: the conviction engine, end to end](https://three.ws/oracle/docs): The complete Oracle reference: the thesis behind fused pump.fun conviction, the four-pillar scoring model and its exact math, the data pipeline and worker loops, the calibration and backtest evidence, the agent action loop, the full API, the data model, limitations, and where it scales next. Written for everyone from first-time readers to researchers.- [Arm your agent: automate Oracle conviction](https://three.ws/oracle/arm): Configure your 3D agent to trade Oracle conviction automatically: set the minimum score, position size, daily and open-position caps, narrative filters and Telegram alerts, then arm it in simulate or live mode. Every action is graded against the outcome.- [Agent Activity: Oracle conviction in real time](https://three.ws/activity): The trading floor: every Oracle conviction action from every autonomous 3D agent on pump.fun, live. Filter by tier and mode, track outcomes, and copy the winners.@@ -449,6 +452,7 @@ Docs, tutorials, and reference.- [Docs · Embedding](https://three.ws/docs/embedding): Embed an agent via iframe, oEmbed, or the <agent-3d> web component.- [Docs · Assistant widget](https://three.ws/docs/assistant-widget): Add a 3D avatar assistant to any website: the one-tag script, the @three-ws/assistant npm package, and the assistant-widget MCP server for AI agents.- [Docs · <agent-3d>](https://three.ws/docs/web-component): Reference for the <agent-3d> custom element.+- [Docs · Companion](https://three.ws/docs/companion): The personal companion: connect your own Telegram bot, calendar, inbox, or phone, give your contacts a face and a voice, and have a 3D character deliver what matters in person. Bridges, triage rules, the SDK, the CLI, the MCP server, and the desktop app.- [Docs · MCP](https://three.ws/docs/mcp): Expose your agent as an MCP server for Claude, ChatGPT, and other clients.- [Docs · 3D Studio MCP (free)](https://three.ws/docs/mcp-studio): The free, no-auth MCP server behind the ChatGPT 3D Studio app: text and image to 3D, rigged avatars, conversational refinement, and living agent personas.- [Docs · AR in ChatGPT](https://three.ws/docs/chatgpt-ar): How a sentence typed into ChatGPT becomes a 3D model standing in your room: the free generation lane, the arUrl contract, the device-aware AR launcher, living avatars, and link unfurls.@@ -616,6 +620,7 @@ Docs, tutorials, and reference.- [Docs · The real-funds risk acknowledgment](https://three.ws/docs/risk-acknowledgment): Every feature that can move real money sits behind a one-time, versioned acknowledgment shown before a user's first real-funds action. What it says, how versioning works, and why it is not a dialog you can skip.- [Docs · Security](https://three.ws/docs/security): How three.ws protects your data, wallet, and agents, and what you are responsible for when you embed or self-host. The threat model, the boundaries enforced in code, and how to report an issue.- [Docs · The catalog quality gate](https://three.ws/docs/seed-quality): Nobody asked for the assets the platform seeds into its own catalogue, so they have to earn their slot. The gate that decides whether a platform-generated model is published or discarded, and the metrics it scores.+- [Docs · Upstream resilience map](https://three.ws/docs/resilience): Every third-party service this platform calls and what happens to a user when it goes down. Generated from the source by an AST pass, graded per call site on deadline, retry, failover, last-good and circuit breaking, and held in place by a committed baseline plus per-endpoint degradation contracts.- [Docs · Shared utilities](https://three.ws/docs/shared-utilities): Small dependency-backed modules that exist so the same problem is not solved twice. Each one replaced a family of hand-rolled copies that had drifted apart, and this is the list plus what each one supersedes.- [Docs · Sign language, avatars that sign](https://three.ws/docs/sign-language): three.ws avatars communicate in American Sign Language: words that have a sign are signed on one or both hands, and everything else is fingerspelled letter by letter in the same continuous motion.- [Docs · ERC-8004 smart contracts](https://three.ws/docs/smart-contracts): The three Solidity contracts behind the ERC-8004 identity registry: contract interfaces, deployed addresses, and how to read from and write to each registry from your own code.@@ -637,6 +642,7 @@ Docs, tutorials, and reference.- [Docs · Paid plans](https://three.ws/docs/plan-checkout): Upgrading to a paid tier is a single on-chain payment on Solana: no card and no billing processor. Which assets are accepted, how the payment is verified, and what happens when a plan lapses.- [Docs · Market Data API](https://three.ws/docs/market-data-api): The same live market data behind every three.ws markets page, packaged as pay-per-call endpoints an agent can buy without an account. Endpoint list, response shapes, and per-call pricing.- [Docs · Oracle, the conviction engine](https://three.ws/docs/oracle): The complete story of Oracle: why it was built, how the scoring model works, the exact maths, the agent action loop, every platform feature that runs on it, and the paid integration other agents can call.+- [Docs · The Oracle model, and how to run it yourself](https://three.ws/docs/oracle-model): How the three.ws conviction model is fitted, what its three heads predict, why the outcome labels had to be made independent of the SOL price, how the promotion gate decides which model ships, and how to score launches locally with @three-ws/oracle-model.- [Docs · x402 distribution](https://three.ws/docs/x402-distribution): three.ws sells dozens of pay-per-call services over x402. Building them is half the job; the other half is making sure every directory, crawler, and agent marketplace can find them. The distribution checklist.- [Docs · The closed-loop x402 ring economy](https://three.ws/docs/x402-ring-economy): A self-contained agent-to-agent payment loop where platform-controlled wallets pay the platform's own paid endpoints in real stablecoin, settled by the platform's own facilitator. No user funds are involved.- [Docs · The $THREE micro-buy loop](https://three.ws/docs/three-microbuy): Many tiny, real on-chain buys of $THREE per minute, each triggered by and paid through a settled pay-per-call payment. It exists to put continuous, verifiable buy pressure behind the platform's own token.@@ -709,6 +715,7 @@ Docs, tutorials, and reference.- [Tutorial · Ship an avatar manifest](https://three.ws/tutorials/ship-an-avatar-manifest): Turn a raw GLB into a signed-off, hash-anchored manifest: one document that names the avatar, records the exact bytes of its mesh, declares its skeleton, and fails your build if the model ever silently changes.- [Tutorial · Write a repository guard](https://three.ws/tutorials/write-a-guard): This repo has no CI, so a guard is the only thing between a mistake and production. Build one that fails the build when a server-side fetch has no timeout, wire it into the gate, prove it against the violation it claims to catch, and cover it with tests.- [Repository guards](https://three.ws/guards): Every mechanical guard that protects the three.ws codebase, and the stage each one runs in. This repository has no CI, so correctness is enforced by fast local checks wired into the prebuild, the gate, the deploy build, and the git pre-push hook. Filter by stage, search by command, and read the incident behind each one.+- [Brownout](https://three.ws/brownout): Every response from this API says where its data came from and how fresh it is, and every declared fallback has been proven by breaking the upstream it protects against, inside the real request path. Read the receipts: which provider refused, which one caught the request, and how old the answer was.- [Docs · Write a repository guard](https://three.ws/docs/tutorials/write-a-guard): Build a real guard end to end: write the checker, give it an npm script, register it in data/guards.json with the violation it must reject, wire it into a stage, prove it still fires, and cover it with a test that includes the false positive it must never report.- [Tutorial · Earn and spend in /play](https://three.ws/tutorials/earn-and-spend-in-play): Run the full economic loop in the open world: gather raw materials, sell them to a vendor, buy a better tool, bank the rest so death can't take it, and spin the wheel. Covers why the world has two currencies that never touch, and why the server decides every price.- [Docs: The showcase](https://three.ws/docs/showcase): The public directory of ERC-8004 agents that registered a real 3D avatar. Nothing is curated: an agent appears because the crawler verified its on-chain metadata resolves to a usable model. Covers the qualifying rules and the keyset-paginated API.diff --git a/public/sitemap/index.html b/public/sitemap/index.htmlindex 8ca25439f..a192f453c 100644--- a/public/sitemap/index.html+++ b/public/sitemap/index.html@@ -83,7 +83,7 @@<main class="sm-wrap"><div class="sm-hero"><h1>Sitemap</h1>- <p>All 848 pages on three.ws, grouped by purpose. Looking for the machine-readable versions?</p>+ <p>All 855 pages on three.ws, grouped by purpose. Looking for the machine-readable versions?</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>@@ -95,7 +95,7 @@</div><div class="sm-filter"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m21 21-4.3-4.3"/></svg>- <input id="sm-filter-input" type="search" placeholder="Filter 848 pages by name, path, or description…" aria-label="Filter pages" autocomplete="off" spellcheck="false" />+ <input id="sm-filter-input" type="search" placeholder="Filter 855 pages by name, path, or description…" aria-label="Filter pages" autocomplete="off" spellcheck="false" /><kbd aria-hidden="true">/</kbd></div><p class="sm-filter-count" id="sm-filter-count" role="status" aria-live="polite"></p>@@ -127,6 +127,14 @@<span class="sm-desc">Deliver a message in person: a 3D character walks onto your page and tells the user what happened. Open SDK, one line of code, an accessible fallback, and a CLI that announces when your build finishes.</span></a></li>+ <li>+ <a href="/glance">+ <span class="sm-new-date">Aug 28, 2026</span>+ <span class="sm-title">Glance</span>+ <span class="sm-path">/glance</span>+ <span class="sm-desc">Your three.ws agent on every home screen: a live card for the Windows 11 widgets board, a README, Slack, or any page.</span>+ </a>+ </li><li><a href="/tty"><span class="sm-new-date">Aug 28, 2026</span>@@ -136,43 +144,35 @@</a></li><li>- <a href="/docs/tty-avatar">+ <a href="/stream"><span class="sm-new-date">Aug 28, 2026</span>- <span class="sm-title">Docs · Terminal avatar</span>- <span class="sm-path">/docs/tty-avatar</span>- <span class="sm-desc">The @three-ws/tty-avatar package: any three.ws avatar or agent body rendered live in a terminal by a software rasterizer (truecolor half-blocks, braille, or plain ASCII), procedural moods, and Claude Code hooks that turn it into your coding agent's face.</span>+ <span class="sm-title">Progressive Avatars</span>+ <span class="sm-path">/stream</span>+ <span class="sm-desc">A3S packs a GLB into nested layers whose first 50 KB is already a complete, skinned, spec-valid avatar, then refines it in place over plain HTTP range requests. Live side-by-side against a classic GLB load.</span></a></li><li>- <a href="/docs/seeker-publishing">+ <a href="/oracle-lab"><span class="sm-new-date">Aug 28, 2026</span>- <span class="sm-title">Publishing to the Solana dApp Store</span>- <span class="sm-path">/docs/seeker-publishing</span>- <span class="sm-desc">The release runbook for the three.ws Seeker app: Publisher Portal setup, the release keystore, building and verifying a signed APK, and submitting it for review.</span>+ <span class="sm-title">Oracle Lab: the model, published</span>+ <span class="sm-path">/oracle-lab</span>+ <span class="sm-desc">The Oracle's conviction model in full: every bucket weight with the number of labeled launches behind it and what happened to them, the held-out reliability curve for each tier, the version history of every refit including the ones that were refused, and a live scorer that runs the real weights in your browser. Download it and reproduce any score offline.</span></a></li><li>- <a href="/docs/ios-app">- <span class="sm-new-date">Aug 28, 2026</span>- <span class="sm-title">three.ws on iOS</span>- <span class="sm-path">/docs/ios-app</span>- <span class="sm-desc">What the App Store app adds on top of the website: the native share sheet, universal links, wallet deep links back to the page you left, real permission prompts, and an offline screen that recovers on its own.</span>- </a>- </li>- <li>- <a href="/docs/feedback">+ <a href="/docs/tty-avatar"><span class="sm-new-date">Aug 28, 2026</span>- <span class="sm-title">Docs · Feedback</span>- <span class="sm-path">/docs/feedback</span>- <span class="sm-desc">Telling the corner companion what broke: the proactive ask at the moment of failure, the route, build SHA, and console errors captured for you, the severity and clustering rules, the report API, and the boundary that keeps untrusted visitor text from ever reaching anything with write access.</span>+ <span class="sm-title">Docs · Terminal avatar</span>+ <span class="sm-path">/docs/tty-avatar</span>+ <span class="sm-desc">The @three-ws/tty-avatar package: any three.ws avatar or agent body rendered live in a terminal by a software rasterizer (truecolor half-blocks, braille, or plain ASCII), procedural moods, and Claude Code hooks that turn it into your coding agent's face.</span></a></li><li>- <a href="/docs/3d-vision">+ <a href="/docs/seeker-publishing"><span class="sm-new-date">Aug 28, 2026</span>- <span class="sm-title">Docs · 3D Vision: let an agent see the model</span>- <span class="sm-path">/docs/3d-vision</span>- <span class="sm-desc">Every text-to-3D API answers with a link to a binary an AI agent cannot open, so the agent that made the model cannot check its own work. This surface renders any GLB from several angles and hands the frames back as images a vision model actually sees, over MCP, REST or the @three-ws/see SDK.</span>+ <span class="sm-title">Publishing to the Solana dApp Store</span>+ <span class="sm-path">/docs/seeker-publishing</span>+ <span class="sm-desc">The release runbook for the three.ws Seeker app: Publisher Portal setup, the release keystore, building and verifying a signed APK, and submitting it for review.</span></a></li></ul>@@ -586,7 +586,7 @@<section class="sm-section" id="build"><header>- <h2>Build<span class="sm-count" data-count>61</span></h2>+ <h2>Build<span class="sm-count" data-count>63</span></h2><p class="sm-section-desc">Create and customize an agent.</p></header><ul class="sm-list">@@ -814,6 +814,13 @@<span class="sm-desc">Renders Claude artifact bundles as standalone embeddable apps.</span></a></li>+ <li>+ <a href="/glance">+ <span class="sm-title">Glance</span>+ <span class="sm-path">/glance</span>+ <span class="sm-desc">Your three.ws agent on every home screen: a live card for the Windows 11 widgets board, a README, Slack, or any page.</span>+ </a>+ </li><li><a href="/widgets"><span class="sm-title">Widgets Gallery</span>@@ -1017,6 +1024,13 @@<span class="sm-desc">curl three.ws/tty and a rigged 3D agent walks in your terminal. A software rasterizer streams ANSI frames over HTTP: no GPU, no WebGL, nothing to install. Also the @three-ws/tty CLI and library for rendering any GLB in a terminal.</span></a></li>+ <li>+ <a href="/stream">+ <span class="sm-title">Progressive Avatars</span>+ <span class="sm-path">/stream</span>+ <span class="sm-desc">A3S packs a GLB into nested layers whose first 50 KB is already a complete, skinned, spec-valid avatar, then refines it in place over plain HTTP range requests. Live side-by-side against a classic GLB load.</span>+ </a>+ </li></ul></section>@@ -1185,7 +1199,7 @@<section class="sm-section" id="crypto"><header>- <h2>Crypto<span class="sm-count" data-count>136</span></h2>+ <h2>Crypto<span class="sm-count" data-count>137</span></h2><p class="sm-section-desc">On-chain features: pay-per-call, token launches, vanity wallets.</p></header><ul class="sm-list">@@ -1217,6 +1231,13 @@<span class="sm-desc">A fused AI conviction engine for every pump.fun launch: pedigree (who's buying), structure (bundle vs organic), narrative (what story is it riding), and momentum: fused into a single 0-100 conviction score with transparent pillar reasoning.</span></a></li>+ <li>+ <a href="/oracle-lab">+ <span class="sm-title">Oracle Lab: the model, published</span>+ <span class="sm-path">/oracle-lab</span>+ <span class="sm-desc">The Oracle's conviction model in full: every bucket weight with the number of labeled launches behind it and what happened to them, the held-out reliability curve for each tier, the version history of every refit including the ones that were refused, and a live scorer that runs the real weights in your browser. Download it and reproduce any score offline.</span>+ </a>+ </li><li><a href="/oracle/docs"><span class="sm-title">Oracle Docs: the conviction engine, end to end</span>@@ -2304,7 +2325,7 @@<section class="sm-section" id="learn"><header>- <h2>Learn<span class="sm-count" data-count>383</span></h2>+ <h2>Learn<span class="sm-count" data-count>387</span></h2><p class="sm-section-desc">Docs, tutorials, and reference.</p></header><ul class="sm-list">@@ -3071,6 +3092,13 @@<span class="sm-desc">Reference for the <agent-3d> custom element.</span></a></li>+ <li>+ <a href="/docs/companion">+ <span class="sm-title">Docs · Companion</span>+ <span class="sm-path">/docs/companion</span>+ <span class="sm-desc">The personal companion: connect your own Telegram bot, calendar, inbox, or phone, give your contacts a face and a voice, and have a 3D character deliver what matters in person. Bridges, triage rules, the SDK, the CLI, the MCP server, and the desktop app.</span>+ </a>+ </li><li><a href="/docs/mcp"><span class="sm-title">Docs · MCP</span>@@ -4240,6 +4268,13 @@<span class="sm-desc">Nobody asked for the assets the platform seeds into its own catalogue, so they have to earn their slot. The gate that decides whether a platform-generated model is published or discarded, and the metrics it scores.</span></a></li>+ <li>+ <a href="/docs/resilience">+ <span class="sm-title">Docs · Upstream resilience map</span>+ <span class="sm-path">/docs/resilience</span>+ <span class="sm-desc">Every third-party service this platform calls and what happens to a user when it goes down. Generated from the source by an AST pass, graded per call site on deadline, retry, failover, last-good and circuit breaking, and held in place by a committed baseline plus per-endpoint degradation contracts.</span>+ </a>+ </li><li><a href="/docs/shared-utilities"><span class="sm-title">Docs · Shared utilities</span>@@ -4387,6 +4422,13 @@<span class="sm-desc">The complete story of Oracle: why it was built, how the scoring model works, the exact maths, the agent action loop, every platform feature that runs on it, and the paid integration other agents can call.</span></a></li>+ <li>+ <a href="/docs/oracle-model">+ <span class="sm-title">Docs · The Oracle model, and how to run it yourself</span>+ <span class="sm-path">/docs/oracle-model</span>+ <span class="sm-desc">How the three.ws conviction model is fitted, what its three heads predict, why the outcome labels had to be made independent of the SOL price, how the promotion gate decides which model ships, and how to score launches locally with @three-ws/oracle-model.</span>+ </a>+ </li><li><a href="/docs/x402-distribution"><span class="sm-title">Docs · x402 distribution</span>@@ -4891,6 +4933,13 @@<span class="sm-desc">Every mechanical guard that protects the three.ws codebase, and the stage each one runs in. This repository has no CI, so correctness is enforced by fast local checks wired into the prebuild, the gate, the deploy build, and the git pre-push hook. Filter by stage, search by command, and read the incident behind each one.</span></a></li>+ <li>+ <a href="/brownout">+ <span class="sm-title">Brownout</span>+ <span class="sm-path">/brownout</span>+ <span class="sm-desc">Every response from this API says where its data came from and how fresh it is, and every declared fallback has been proven by breaking the upstream it protects against, inside the real request path. Read the receipts: which provider refused, which one caught the request, and how old the answer was.</span>+ </a>+ </li><li><a href="/docs/tutorials/write-a-guard"><span class="sm-title">Docs · Write a repository guard</span>diff --git a/vercel.json b/vercel.jsonindex ac73b93b8..8b04de0f3 100644--- a/vercel.json+++ b/vercel.json@@ -1340,6 +1340,14 @@"src": "/autopilot/?","dest": "/autopilot.html"},+ {+ "src": "/stream",+ "dest": "/stream.html"+ },+ {+ "src": "/stream/",+ "dest": "/stream.html"+ },{"src": "/avatar-sdk/?","dest": "/avatar-sdk.html"@@ -2671,6 +2679,18 @@"src": "/companion/","dest": "/companion.html"},+ {+ "src": "/knock",+ "dest": "/knock.html"+ },+ {+ "src": "/knock/",+ "dest": "/knock.html"+ },+ {+ "src": "/knock/([A-Za-z0-9._-]{1,40})",+ "dest": "/knock-door.html?to=$1"+ },{"src": "/herald","dest": "/herald.html"diff --git a/vite.config.js b/vite.config.jsindex eb1535441..b11187367 100644--- a/vite.config.js+++ b/vite.config.js@@ -535,6 +535,7 @@ const appConfig = {i18n: resolve(__dirname, 'src/i18n.js'),app: resolve(__dirname, 'pages/app.html'),proof: resolve(__dirname, 'pages/proof.html'),+ stream: resolve(__dirname, 'pages/stream.html'),preflight: resolve(__dirname, 'pages/preflight.html'),'app-next': resolve(__dirname, 'pages/app-next.html'),home: resolve(__dirname, 'pages/home.html'),@@ -635,8 +636,11 @@ const appConfig = {// replace it.'herald-page': resolve(__dirname, 'pages/herald.html'),companion: resolve(__dirname, 'pages/companion.html'),+ knock: resolve(__dirname, 'pages/knock.html'),+ 'knock-door': resolve(__dirname, 'pages/knock-door.html'),portal: resolve(__dirname, 'pages/portal.html'),feedback: resolve(__dirname, 'pages/feedback.html'),+ diff: resolve(__dirname, 'pages/diff.html'),'agent-edit': resolve(__dirname, 'pages/agent-edit.html'),'agent-mind': resolve(__dirname, 'pages/agent-mind.html'),'avatar-edit': resolve(__dirname, 'pages/avatar-edit.html'),@@ -729,6 +733,7 @@ const appConfig = {activity: resolve(__dirname, 'pages/activity.html'),tty: resolve(__dirname, 'pages/tty.html'),guards: resolve(__dirname, 'pages/guards.html'),+ brownout: resolve(__dirname, 'pages/brownout.html'),pipeline: resolve(__dirname, 'pages/pipeline.html'),'coin-intel': resolve(__dirname, 'pages/coin-intel.html'),'oracle-lab': resolve(__dirname, 'pages/oracle-lab.html'),@@ -1484,6 +1489,8 @@ const appConfig = {'/tour/atlas/': resolve(root, 'pages/tour-atlas.html'),'/guards': resolve(root, 'pages/guards.html'),'/guards/': resolve(root, 'pages/guards.html'),+ '/brownout': resolve(root, 'pages/brownout.html'),+ '/brownout/': resolve(root, 'pages/brownout.html'),'/pipeline': resolve(root, 'pages/pipeline.html'),'/pipeline/': resolve(root, 'pages/pipeline.html'),'/trending': resolve(root, 'pages/trending.html'),