Skip to content

Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.

docs(atlas): register the alpha-drip surfaces and regenerate the page, changelog and llms feeds

nirholas0aa76f6819ca
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 2baf0ad6e..5a2a3e37a 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -16,6 +16,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Docs · The browser voice loop** (`/docs/home-voice`): How hands-free works for a connected home: a wake word matched by a model running in your own tab, an interruption that stops the agent mid-sentence, a pause that does not truncate your command, and a spoken confirmation narrow enough that a background yes can never unlock a front door. Includes the measured latency of every leg and how to mount the loop on your own surface.
- **Docs · The live 3D home** (`/docs/home-scene`): How the connected house becomes a room you can stand in: the room graph the bridge builds from Home Assistant's registries, how a real light dimming dims the model, what the scene does while the house is unreachable, and the fallback that keeps every control usable without WebGL.
- **Docs · three.ws Drive** (`/docs/carplay`): How a three.ws agent rides in the car: the CarPlay entitlement categories measured, why Apple's voice-based conversational category is the one that fits and why it grants no drawing surface, the open-source in-car projects worth adopting and the copyleft ones that are not, and how the /drive surface, the native CarPlay scene, and an open head unit share one implementation.
+- **Docs: Alpha-drip** (`/docs/alpha-drip`): Alpha-drip lets a copy-trading leader price the latency of their own signal: $THREE holders in higher tiers see the copy intent first, everyone else after a delay the leader sets. It delays the reveal, never the record.
- **Hands-free voice for your home** (`/voice/home`): Talk to your house without finding a phone: a wake word matched on your own device, real barge-in mid-sentence, and a spoken confirmation that a background yes can never satisfy.
- **Home plan** (`/smart-home/plan`): What your plan covers for connected homes: homes, household seats, live screens, voice minutes and agent turns, each with what you have used and when it resets. Pause and resume which homes are live without disconnecting any of them. Locking up, closing a garage and arming an alarm are never limited.
- **Join a home** (`/smart-home/join`): Accept an invitation to somebody's connected home. The link says which home it is, exactly what your role would let you do there and what it would never let you do, before you sign in. It works once and it expires.
@@ -26,6 +27,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **A stranger cannot make your agent open your front door**: The home lane now has a written threat model and eleven security checks that run with every build, and the standard they hold is a lock, not a database row. The big fix: the address you give for your house is now resolved and pinned on our side before anything dials it, so a web address that secretly points back into our own network is refused instead of connected to, and it is re-checked every time your house reconnects rather than trusted from the day you added it. A device or integration in your house cannot talk your agent into anything either: we wrote an unlock instruction into a real room name, a real device name and a real scene name, ran a real agent against that house, and the front door stayed locked. Your privacy page is now rate limited like everything else, so nobody can hammer the export or the delete. (`/smart-home`) `[security, improvement]`
- **Agent avatars on the Pay page load instead of 404ing**: Every agent card on the x402 Pay page asked for its owner's avatar picture at a URL that has never existed on this site, so the picture always 404'd and the card fell back to a plain letter tile. The page now uses the real thumbnail the rest of three.ws uses, so an agent with a public avatar shows its face on the card, and an agent whose avatar is private still gets the letter tile without a wasted failed request. (`/pay`) `[fix]`
- **Any assistant can now run your house, and it still will not open your door**: There is a new way to connect your home that needs no three.ws account and no remote web address at all: install @three-ws/home-mcp in Claude, Cursor, or anything else that speaks Model Context Protocol, give it your Home Assistant address and a token, and it reads your rooms, runs the scenes you already built, and calls services. Because it runs on your own machine, your ordinary home network address works and nothing about your house leaves the building. The safety rule is the same one the rest of the platform uses, applied honestly to this setup: locking up, closing the garage and arming the alarm run straight away and never ask. Unlocking, opening a door and disarming are refused outright, every time, because saying yes to opening a building takes a person and this kind of connection has no person in it to ask. If you genuinely want one specific door handled without asking, you name that exact door yourself when you start it, by hand, and nothing your assistant can do will widen that to any other door. We proved it against a real Home Assistant rather than a stand-in: the front door was told to unlock seven different ways, including with a fake confirmation smuggled into the request, and it stayed locked every time. Alongside it there is now a full walkthrough from nothing to a working agent in a real house, covering what to do when it says your home is unreachable, and what a guest in your household can and cannot do. (`/smart-home`) `[feature, sdk, docs]`
+- **Avatar posters and clips survive a CDN outage instead of coming back blank**: Some of the images we render of an avatar on the server are drawn by a headless browser that loads three.js from a public CDN: the images the render endpoint and the MCP render tools return, rendered clips, and the preview cards for models our fast in-process renderer cannot decode on its own. When that one CDN was slow or unreachable, the page's module load simply hung, the render timed out, and the image came back empty with nothing to explain why. A failover had been written for exactly this and was never connected to the renderers. It is connected now: before each render we check that the CDN is answering and switch to a second one if it is not, remembering the answer for ten minutes so a burst of renders pays for a single check. The three renderers also share one pinned version of three.js instead of keeping three copies that could drift apart, and a test now fails the build if a renderer ever goes back to hardcoding a single CDN. `[fix, infra]`
- **Coin Radar tells you when it is your filter, not the market, that is empty**: Search the radar for a ticker it has not seen and the board used to say "Radar is clear, waiting for the next launch", which blamed a quiet market for a filter you set and gave you no way back. Most of Radar's filters run on the server, so an over-tight one came back looking exactly like a quiet window. Now the board reads your filters instead of the response: it says no coins match, lists every filter you have on as a chip you can click to drop just that one, and keeps a reset-everything button next to it. The 24-hour pulse strip across the top also got an honest state of its own. It is a separate request from the live feed, and when it failed it used to shimmer as if still loading forever; now it says the aggregate did not load, offers a retry, and leaves the feed below running. On a 320px phone every card was losing about 19 pixels off its right edge to a layout overflow that the mobile scroll guard was quietly clipping; cards now fit the screen they are on. (`/radar`) `[fix, improvement]`
- **Connect a home that only exists on your own network**: Most Home Assistant installs sit on a home network with nothing exposed to the internet, so until now three.ws had no way to reach them. Now the house connects to us instead. Install one integration through HACS, paste a ten-minute pairing code, and your agent can see your rooms and run your scenes with nothing listening on your network, no port forwarded, and no firewall rule changed. The part worth saying plainly: three.ws never receives a Home Assistant token for a home connected this way. The integration signs in to Home Assistant on your own machine with a credential it makes for itself and never sends anywhere, so there is nothing stored here that would open your house. What we can do through that connection is a fixed list, enforced twice, once by us and once by the integration on your machine: reads, your room layout, and device controls. It can never run code on the machine Home Assistant lives on, restart or reconfigure your instance, or reach anything else on your network. Unlocking, opening and disarming still stop and ask a person first, every time, exactly as they do for a home connected by address. Disconnecting works from either end and takes effect immediately. There is an honest threat model in the docs, including what a compromise of three.ws would mean for a connected house; read it before you decide. (`/docs/home-relay`) `[feature, security]`
- **Connect your house to your agent, and see every way it can go wrong**: The /smart-home page now takes you from "I have a Home Assistant somewhere" to a connected house, and it is honest at every step. An address that only exists on your home network is refused the moment you type it, with the two real ways round it, instead of spinning for fifteen seconds. A rejected token says so and puts the cursor back in the token box. A house that stops answering keeps its rooms on screen, marked stale with how long ago it last replied, rather than blanking out. Your access token is sent once, encrypted at rest, and never comes back to the page: it is not in your browser storage, not in a URL, and not in any response. Disconnecting says plainly that the stored token is erased and reminds you to delete it in Home Assistant too. (`/smart-home`) `[feature]`
@@ -51,6 +53,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **three.ws Drive on Android Auto, and your agent can reach your house from the car**: The car surface now has an Android Auto app to go with the CarPlay one. Open three.ws on your car screen and you get four big controls, and your agent listens straight away. The car screen is Android's own layout, which is the rule for every app that runs while you drive, so the conversation runs on your phone and comes out of the car speakers. There is a notification while it is running, on purpose: your agent should never be listening invisibly, and one tap stops it. The bigger part is what it can now do. If you have connected your home to three.ws, your agent already reaches it, so "turn the porch light on" works while you are driving home. Anything that opens or unlocks something is different and stays different: your agent will not touch a lock, a garage door or an alarm on its own, and it will not even ask you to approve one while the car is moving. It tells you it is waiting and offers it for the moment you park. On the car screen, where you cannot see what you would be approving, it asks you to do it on your phone instead. (`/drive`) `[feature, improvement]`
- **three.ws Drive: your agent, in the car**: There is a new page at /drive built for a car screen instead of a desk. Your agent is on it full size, you hold one big button and talk, and it answers out loud in its own voice with its face moving. It shows you one line of what it said rather than a wall of chat, because you are driving. It starts dark, because a bright panel at night is glare, and it will switch to a day palette on one press or one sentence. The keyboard stays out of the way while you are moving: if your browser can tell how fast you are going, text entry locks itself the moment you pull away and comes back when you have properly stopped. A few things you say never leave the car at all, so "repeat that", "stop talking", "louder" and "night mode" happen instantly, while "stop at the next charger" still goes to your agent like any other question. It works today on a head unit browser, on a phone in a cradle, and on Android Automotive. The Apple CarPlay version is built and waiting on Apple's approval for voice assistants in the car. One thing this fixed for everyone: an avatar used to answer in silence if you were not signed in, and now it always has a voice. (`/drive`) `[feature, improvement]`
- **Tour Atlas counts its own stops honestly, and says why a stop has no picture**: The atlas advertised 185 stops in its page title, its search prompt, its social cards and its listing everywhere on the site. It has had 263 for a while, and nothing was checking, so the number quietly went stale. It now says 263, and the atlas guard fails the build if that number ever stops matching the manifest again. Eighteen stops carry no screenshot because they are live 3D or live-market pages that never stop painting long enough to be photographed; their cards used to claim the page 'did not respond', which was untrue of all of them, and now they say what actually happened and invite you to open the page live. Opening one of those stops used to show an empty black frame above the write-up, and now shows the same explanation. If the atlas itself cannot load you get a plain sentence about what went wrong and a Try again button, instead of a raw browser error or an instruction to run a developer command. And a /tour/atlas#stop-name link now opens that stop even when you are already on the page or have a filter narrowing the grid. (`/tour/atlas`) `[fix, improvement]`
+- **Traders can now price the latency of their own calls**: Copy trading has a new option for the trader being copied: alpha-drip. A trader can set how long each $THREE holder tier waits before their copy intent is revealed, so holding more $THREE means seeing their calls sooner. It is off unless a trader turns it on, and the rules are strict on purpose: a higher tier can never wait longer than a lower one, no delay can exceed fifteen minutes, and the delay only affects when a copier is SHOWN the trade. The trade itself is still recorded the instant it happens and still appears in the trader's public track record, so nothing is ever hidden. Copiers see exactly which seat their balance buys before they subscribe, and a held intent shows a live countdown that unlocks in place. Traders can also ask for a suggested ladder tuned to how fast their own edge actually decays, measured from their real closed trades, and get warned when the slowest tier would be waiting longer than that edge lasts. (`/docs/alpha-drip`) `[feature]`
- **We tried making your agent a Matter device, measured it, and decided against it for now**: Matter is the standard that lets smart-home gear from different brands work together, and the plan had always been to make a three.ws agent show up as a Matter device so that any smart-home controller could see it, drop it in a room, and use it in an automation. We built it and pointed it at a real Home Assistant to find out whether the idea holds up. It does, technically: the agent paired in under a second over an ordinary network with no Bluetooth and no special radio, Home Assistant listed it as a proper device with a name, a model and a serial number, put it in the living room, and messages went both ways in well under a second. It also held the line that matters most: an automation that asked the agent to unlock a front door was refused and the door stayed locked, because an automation is not a person saying yes, and only a real confirmation from a person opened it. We are still not shipping it, and the honest reason is that it would be a narrower version of something you can already have. The three.ws Home Assistant integration already puts your agent inside your house with the whole conversation available to it, where Matter would offer a switch and a sensor. On top of that, appearing in the big-name smart-home apps needs a certified manufacturer identity we do not hold. The full write-up, every measurement, and the exact conditions that would change our answer are now in the smart-home documentation, so nobody has to guess or start over. (`/docs/smart-home`) `[docs]`
- **Your Home Assistant voice assistant can have a face now**: If you already run Home Assistant with a voice pipeline, it hears you, understands you, turns on the lights and answers, and the whole visual side of that is an LED ring. You can now point that same pipeline at a three.ws agent and get a face on any screen in the house: it reacts while you speak, the transcript fills in as your own speech recognition produces it, and it lip-syncs the answer to the audio your own text-to-speech generated. Home Assistant keeps every part of the pipeline, running on your own hardware exactly as it does today. Setup is a pairing code, one Docker command, and adding it in Home Assistant as a Wyoming Protocol integration. Nothing needs to be exposed to the internet: Home Assistant connects out to the satellite on your own network, the satellite connects out to us, and there is no port to forward. The rule the whole thing is built around is that closing the page never stops your voice assistant working, so the run finishes, the lights still change, and the only thing you lose is the face. (`/smart-home/satellite`) `[feature]`
- **Your home is a household now, and a house sitter still cannot open your front door**: A house has more than one person in it, and until now the only way to let a partner, a house sitter or a colleague use a connected home was to hand over your password. Every home has a household. On its card under “Who can reach this home” you can invite somebody by email and choose exactly what they get. There are five roles and each one says plainly what it can and cannot do at the moment you pick it. Someone who lives there can control everything and approve unlocking a door. A guest can turn the lights on and can never approve unlocking anything, ever, no matter what your agent asks them: that refusal is enforced on our servers and there is no version of the app that could offer them the button. A guest or a viewer can also be given just the kitchen, or just three specific devices, and the rooms you did not give them are removed from what they receive rather than hidden on screen, so their app never learns those rooms exist. Invitations work once, expire after a week, and can be withdrawn before anyone uses them. Removing somebody takes back every standing allowance they ever approved in the same instant, so a door can never keep opening on the say-so of a person who has left. And every action in your home log is attributed to the person who took it, so “who did what” has a real answer. (`/smart-home`) `[feature, security]`
diff --git a/STRUCTURE.md b/STRUCTURE.md
index 13b4b11ee..daee4bf46 100644
--- a/STRUCTURE.md
+++ b/STRUCTURE.md
@@ -260,6 +260,7 @@ bottom.
| AgentCore payments MCP | [packages/agentcore-payments-mcp/](packages/agentcore-payments-mcp) | Published as `@three-ws/agentcore-payments-mcp` (v0.1.2) | MCP server for platform-managed agent payment sessions |
| VS Code x402 extension | [packages/vscode-x402/](packages/vscode-x402) | In-repo (v0.2.0, not yet published to npm) | VS Code extension for the x402 bazaar |
| Meta-Allocator (the ETF of degens) | [pages/meta-allocator.html](pages/meta-allocator.html) + [src/meta-allocator.js](src/meta-allocator.js) `→ /meta-allocator`, brain [api/_lib/meta-allocator.js](api/_lib/meta-allocator.js), endpoint [api/meta-allocator.js](api/meta-allocator.js) | Live (non-custodial planning) | Spreads a budget across the top verified pump.fun leader agents, ranked by risk-adjusted on-chain track record (win rate, realized ROI, peak-to-trough max drawdown from `agent_sniper_positions`) and diversified across derived correlation groups, then returns a rebalance rule. Free-first `llmComplete` shaping with a deterministic same-shape fallback so it never fails. Returns a plan (weights + suggested sizes), never a transaction; users act one leader at a time via [/vaults](pages/vaults.html). Doc: [docs/meta-allocator.md](docs/meta-allocator.md). |
+| Alpha-drip (a leader prices their signal latency) | Ladder rules [api/\_lib/alpha-drip.js](api/_lib/alpha-drip.js), fanout half [api/\_lib/copy-drip-runtime.js](api/_lib/copy-drip-runtime.js), measured edge half-life [api/\_lib/alpha-drip-stats.js](api/_lib/alpha-drip-stats.js), endpoint [api/copy/alpha-drip.js](api/copy/alpha-drip.js) `-> /api/copy/alpha-drip`, leader editor [src/alpha-drip-panel.js](src/alpha-drip-panel.js) mounted on [/dashboard/copy](src/dashboard-next/pages/copy.js), copier seat on the trader page [src/copy-panel.js](src/copy-panel.js), schema [api/\_lib/migrations/20260903235500\_copy\_alpha\_drip.sql](api/_lib/migrations/20260903235500_copy_alpha_drip.sql) | Live (off unless a leader turns it on) | The $THREE sink on the copy rail: a leader sets how long each holder tier waits before a copy intent is revealed to them, so the thing being sold is latency rather than only a share of the profit. Two rules are structural and enforced server-side: a higher tier can never wait longer than a lower one, and **a drip delays the reveal, never the record** (the intent row is written in full at fanout time and the public track record is untouched, so there are no hidden trades). The copier is shown the seat their balance buys BEFORE they subscribe, not after; a locked intent renders as a countdown that unlocks in place, and `POST /api/copy/executions` refuses an unreleased one in the same statement that changes its status, so the guard cannot be raced. Tier size caps are applied after the copy engine has sized and gated the order, never before, so the copier's own caps still bind first. The edge half-life the fairness warning judges a ladder against is measured from the leader's own profitable closes, and is null rather than guessed below five of them. Release runs inside [api/cron/copy-fanout.js](api/cron/copy-fanout.js) rather than a second cron, so the release cadence is the fanout cadence. Doc: [docs/alpha-drip.md](docs/alpha-drip.md). Tests: [tests/alpha-drip.test.js](tests/alpha-drip.test.js) |
| Ghost-copy (paper-copy a leader) | [pages/ghost-copy.html](pages/ghost-copy.html) + [src/ghost-copy.js](src/ghost-copy.js) `→ /ghost-copy`, simulator [api/_lib/ghost-copy.js](api/_lib/ghost-copy.js), endpoint [api/pump/ghost-copy.js](api/pump/ghost-copy.js), tests [tests/ghost-copy.test.js](tests/ghost-copy.test.js) | Live (paper only, zero custody) | The bridge between the leaderboard and actually copying someone. Pick a verified trader agent, a budget and a window, and it replays that agent's real closed on-chain round-trips (`agent_sniper_positions`) against a wallet that does not exist, sizing every order through `planCopyOrder`, the SAME function the live [copy-fanout cron](api/cron/copy-fanout.js) uses, so the result is what the copy engine would actually have generated rather than a marketing figure. Deliberately unflattering: P&L per trade is derived from exact chain lamports (never the stored pct column), losing round-trips all count, the ghost wallet has a real cash constraint so capital locked in an open copy blocks the next one, every skip carries a machine reason plus a human sentence, and the leader's still-open positions are marked at THEIR last on-chain quote and reported as unrealized outside the realized headline. Needs no account, no wallet, no signature and no funded signer, so it ships ahead of any custody decision; state lives in the query string so a result is deep-linkable and shareable. Converts into [/vaults](pages/vaults.html) for real money. Doc: [docs/ghost-copy.md](docs/ghost-copy.md). |
| Clip Director (content engine) | [pages/clip-director.html](pages/clip-director.html) + [src/clip-director-page.js](src/clip-director-page.js) `→ /clip-director`, brain [api/_lib/clip-director.js](api/_lib/clip-director.js), endpoint [api/clip-director.js](api/clip-director.js) | Live | Turns one real closed trade (`agent_sniper_positions`) into the optimal shareable card per surface (X / Telegram / Feed): honest hook, the real number, an avatar gesture mapped to a real animation clip, CTA, and alt text, plus an on-chain proof link. Losses get an honest card too. Free-first `llmComplete` with a deterministic same-shape fallback. Doc: [docs/clip-director.md](docs/clip-director.md). |
| Atlas (site-wide Cmd+K search + route map) | Palette [public/atlas.js](public/atlas.js) `-> /atlas.js`, ranking [public/atlas/score.js](public/atlas/score.js), map page [pages/atlas.html](pages/atlas.html) + [src/atlas-page.js](src/atlas-page.js) `-> /atlas`, index [scripts/build-atlas-index.mjs](scripts/build-atlas-index.mjs) `-> public/atlas-index.json`, task catalog [data/atlas-intents.json](data/atlas-intents.json), coverage [scripts/inject-atlas.mjs](scripts/inject-atlas.mjs) | Live | **Discovery layer for 650+ routes.** Cmd+K (or `/`) opens a search over every page in `data/pages.json` plus a curated set of TASKS that answer with ordered steps rather than one link, because "which page starts the get-paid flow" is a harder question than "where is /x402/studio". Zero-dependency single file so it runs identically on 250+ standalone HTML entry points; the index is fetched on first open, not page load. Every task step target is resolved against the real route table at build time, so an onboarding path cannot dead-end on a 404. Injected by a Vite `three-ws-atlas` plugin plus a post-build `dist/` walk (same belt-and-suspenders as [scripts/inject-tour-boot.mjs](scripts/inject-tour-boot.mjs), for the same plugin-ordering reason). Embeds and the nav/footer fragments are excluded. Doc: [docs/atlas.md](docs/atlas.md). Tests: [tests/atlas.test.js](tests/atlas.test.js). |
diff --git a/data/changelog.json b/data/changelog.json
index 6581a9f58..afd162cce 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -26169,6 +26169,24 @@
"infra"
],
"link": "/docs/autonomous-x402"
+ },
+ {
+ "date": "2026-09-03",
+ "title": "Avatar posters and clips survive a CDN outage instead of coming back blank",
+ "summary": "Some of the images we render of an avatar on the server are drawn by a headless browser that loads three.js from a public CDN: the images the render endpoint and the MCP render tools return, rendered clips, and the preview cards for models our fast in-process renderer cannot decode on its own. When that one CDN was slow or unreachable, the page's module load simply hung, the render timed out, and the image came back empty with nothing to explain why. A failover had been written for exactly this and was never connected to the renderers. It is connected now: before each render we check that the CDN is answering and switch to a second one if it is not, remembering the answer for ten minutes so a burst of renders pays for a single check. The three renderers also share one pinned version of three.js instead of keeping three copies that could drift apart, and a test now fails the build if a renderer ever goes back to hardcoding a single CDN.",
+ "tags": [
+ "fix",
+ "infra"
+ ]
+ },
+ {
+ "date": "2026-09-03",
+ "title": "Traders can now price the latency of their own calls",
+ "summary": "Copy trading has a new option for the trader being copied: alpha-drip. A trader can set how long each $THREE holder tier waits before their copy intent is revealed, so holding more $THREE means seeing their calls sooner. It is off unless a trader turns it on, and the rules are strict on purpose: a higher tier can never wait longer than a lower one, no delay can exceed fifteen minutes, and the delay only affects when a copier is SHOWN the trade. The trade itself is still recorded the instant it happens and still appears in the trader's public track record, so nothing is ever hidden. Copiers see exactly which seat their balance buys before they subscribe, and a held intent shows a live countdown that unlocks in place. Traders can also ask for a suggested ladder tuned to how fast their own edge actually decays, measured from their real closed trades, and get warned when the slowest tier would be waiting longer than that edge lasts.",
+ "link": "/docs/alpha-drip",
+ "tags": [
+ "feature"
+ ]
}
]
}
diff --git a/data/pages.json b/data/pages.json
index 152f79622..9cd036e65 100644
--- a/data/pages.json
+++ b/data/pages.json
@@ -4323,6 +4323,14 @@
"priority": 0.7,
"changefreq": "monthly"
},
+ {
+ "path": "/docs/alpha-drip",
+ "title": "Docs: Alpha-drip",
+ "description": "Alpha-drip lets a copy-trading leader price the latency of their own signal: $THREE holders in higher tiers see the copy intent first, everyone else after a delay the leader sets. It delays the reveal, never the record.",
+ "added": "2026-09-03",
+ "priority": 0.7,
+ "changefreq": "monthly"
+ },
{
"path": "/docs/copy-trading",
"title": "Docs: Copy Trading",
diff --git a/public/changelog.json b/public/changelog.json
index c9a96b859..6f715fc03 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-09-03T07:27:18.798Z",
+ "generated_at": "2026-09-03T07:32:51.766Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -106,6 +106,16 @@
"launch"
]
},
+ {
+ "date": "2026-09-03",
+ "type": "launch",
+ "title": "Docs: Alpha-drip",
+ "summary": "Alpha-drip lets a copy-trading leader price the latency of their own signal: $THREE holders in higher tiers see the copy intent first, everyone else after a delay the leader sets. It delays the reveal, never the record.",
+ "link": "/docs/alpha-drip",
+ "tags": [
+ "launch"
+ ]
+ },
{
"date": "2026-09-03",
"type": "launch",
@@ -209,6 +219,17 @@
"docs"
]
},
+ {
+ "date": "2026-09-03",
+ "type": "update",
+ "title": "Avatar posters and clips survive a CDN outage instead of coming back blank",
+ "summary": "Some of the images we render of an avatar on the server are drawn by a headless browser that loads three.js from a public CDN: the images the render endpoint and the MCP render tools return, rendered clips, and the preview cards for models our fast in-process renderer cannot decode on its own. When that one CDN was slow or unreachable, the page's module load simply hung, the render timed out, and the image came back empty with nothing to explain why. A failover had been written for exactly this and was never connected to the renderers. It is connected now: before each render we check that the CDN is answering and switch to a second one if it is not, remembering the answer for ten minutes so a burst of renders pays for a single check. The three renderers also share one pinned version of three.js instead of keeping three copies that could drift apart, and a test now fails the build if a renderer ever goes back to hardcoding a single CDN.",
+ "link": null,
+ "tags": [
+ "fix",
+ "infra"
+ ]
+ },
{
"date": "2026-09-03",
"type": "update",
@@ -482,6 +503,16 @@
"improvement"
]
},
+ {
+ "date": "2026-09-03",
+ "type": "update",
+ "title": "Traders can now price the latency of their own calls",
+ "summary": "Copy trading has a new option for the trader being copied: alpha-drip. A trader can set how long each $THREE holder tier waits before their copy intent is revealed, so holding more $THREE means seeing their calls sooner. It is off unless a trader turns it on, and the rules are strict on purpose: a higher tier can never wait longer than a lower one, no delay can exceed fifteen minutes, and the delay only affects when a copier is SHOWN the trade. The trade itself is still recorded the instant it happens and still appears in the trader's public track record, so nothing is ever hidden. Copiers see exactly which seat their balance buys before they subscribe, and a held intent shows a live countdown that unlocks in place. Traders can also ask for a suggested ladder tuned to how fast their own edge actually decays, measured from their real closed trades, and get warned when the slowest tier would be waiting longer than that edge lasts.",
+ "link": "/docs/alpha-drip",
+ "tags": [
+ "feature"
+ ]
+ },
{
"date": "2026-09-03",
"type": "update",
diff --git a/public/changelog.xml b/public/changelog.xml
index 8edc61441..42c0af407 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -86,6 +86,14 @@
<category>launch</category>
<description>How a three.ws agent rides in the car: the CarPlay entitlement categories measured, why Apple's voice-based conversational category is the one that fits and why it grants no drawing surface, the open-source in-car projects worth adopting and the copyleft ones that are not, and how the /drive surface, the native CarPlay scene, and an open head unit share one implementation.</description>
</item>
+ <item>
+ <title>Docs: Alpha-drip</title>
+ <link>https://three.ws/docs/alpha-drip</link>
+ <guid isPermaLink="false">2026-09-03:Docs: Alpha-drip</guid>
+ <pubDate>Thu, 03 Sep 2026 12:00:00 GMT</pubDate>
+ <category>launch</category>
+ <description>Alpha-drip lets a copy-trading leader price the latency of their own signal: $THREE holders in higher tiers see the copy intent first, everyone else after a delay the leader sets. It delays the reveal, never the record.</description>
+ </item>
<item>
<title>Hands-free voice for your home</title>
<link>https://three.ws/voice/home</link>
@@ -166,6 +174,14 @@
<category>feature</category>
<description>There is a new way to connect your home that needs no three.ws account and no remote web address at all: install @three-ws/home-mcp in Claude, Cursor, or anything else that speaks Model Context Protocol, give it your Home Assistant address and a token, and it reads your rooms, runs the scenes you already built, and calls services. Because it runs on your own machine, your ordinary home network address works and nothing about your house leaves the building. The safety rule is the same one the rest of the platform uses, applied honestly to this setup: locking up, closing the garage and arming the alarm run straight away and never ask. Unlocking, opening a door and disarming are refused outright, every time, because saying yes to opening a building takes a person and this kind of connection has no person in it to ask. If you genuinely want one specific door handled without asking, you name that exact door yourself when you start it, by hand, and nothing your assistant can do will widen that to any other door. We proved it against a real Home Assistant rather than a stand-in: the front door was told to unlock seven different ways, including with a fake confirmation smuggled into the request, and it stayed locked every time. Alongside it there is now a full walkthrough from nothing to a working agent in a real house, covering what to do when it says your home is unreachable, and what a guest in your household can and cannot do.</description>
</item>
+ <item>
+ <title>Avatar posters and clips survive a CDN outage instead of coming back blank</title>
+ <link>https://three.ws/changelog</link>
+ <guid isPermaLink="false">2026-09-03:Avatar posters and clips survive a CDN outage instead of coming back blank</guid>
+ <pubDate>Thu, 03 Sep 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>Some of the images we render of an avatar on the server are drawn by a headless browser that loads three.js from a public CDN: the images the render endpoint and the MCP render tools return, rendered clips, and the preview cards for models our fast in-process renderer cannot decode on its own. When that one CDN was slow or unreachable, the page's module load simply hung, the render timed out, and the image came back empty with nothing to explain why. A failover had been written for exactly this and was never connected to the renderers. It is connected now: before each render we check that the CDN is answering and switch to a second one if it is not, remembering the answer for ten minutes so a burst of renders pays for a single check. The three renderers also share one pinned version of three.js instead of keeping three copies that could drift apart, and a test now fails the build if a renderer ever goes back to hardcoding a single CDN.</description>
+ </item>
<item>
<title>Coin Radar tells you when it is your filter, not the market, that is empty</title>
<link>https://three.ws/radar</link>
@@ -366,6 +382,14 @@
<category>fix</category>
<description>The atlas advertised 185 stops in its page title, its search prompt, its social cards and its listing everywhere on the site. It has had 263 for a while, and nothing was checking, so the number quietly went stale. It now says 263, and the atlas guard fails the build if that number ever stops matching the manifest again. Eighteen stops carry no screenshot because they are live 3D or live-market pages that never stop painting long enough to be photographed; their cards used to claim the page 'did not respond', which was untrue of all of them, and now they say what actually happened and invite you to open the page live. Opening one of those stops used to show an empty black frame above the write-up, and now shows the same explanation. If the atlas itself cannot load you get a plain sentence about what went wrong and a Try again button, instead of a raw browser error or an instruction to run a developer command. And a /tour/atlas#stop-name link now opens that stop even when you are already on the page or have a filter narrowing the grid.</description>
</item>
+ <item>
+ <title>Traders can now price the latency of their own calls</title>
+ <link>https://three.ws/docs/alpha-drip</link>
+ <guid isPermaLink="false">2026-09-03:Traders can now price the latency of their own calls</guid>
+ <pubDate>Thu, 03 Sep 2026 12:00:00 GMT</pubDate>
+ <category>feature</category>
+ <description>Copy trading has a new option for the trader being copied: alpha-drip. A trader can set how long each $THREE holder tier waits before their copy intent is revealed, so holding more $THREE means seeing their calls sooner. It is off unless a trader turns it on, and the rules are strict on purpose: a higher tier can never wait longer than a lower one, no delay can exceed fifteen minutes, and the delay only affects when a copier is SHOWN the trade. The trade itself is still recorded the instant it happens and still appears in the trader's public track record, so nothing is ever hidden. Copiers see exactly which seat their balance buys before they subscribe, and a held intent shows a live countdown that unlocks in place. Traders can also ask for a suggested ladder tuned to how fast their own edge actually decays, measured from their real closed trades, and get warned when the slowest tier would be waiting longer than that edge lasts.</description>
+ </item>
<item>
<title>We tried making your agent a Matter device, measured it, and decided against it for now</title>
<link>https://three.ws/docs/smart-home</link>
diff --git a/public/features.json b/public/features.json
index d449d1e34..1f77caf4a 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-09-03T07:27:18.729Z",
+ "generated_at": "2026-09-03T07:32:51.716Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",
@@ -5518,6 +5518,16 @@
"tags": [],
"showcase": false
},
+ {
+ "path": "/docs/alpha-drip",
+ "title": "Docs: Alpha-drip",
+ "description": "Alpha-drip lets a copy-trading leader price the latency of their own signal: $THREE holders in higher tiers see the copy intent first, everyone else after a delay the leader sets. It delays the reveal, never the record.",
+ "added": "2026-09-03",
+ "auth": null,
+ "indexable": true,
+ "tags": [],
+ "showcase": false
+ },
{
"path": "/docs/copy-trading",
"title": "Docs: Copy Trading",
diff --git a/public/llms-full.txt b/public/llms-full.txt
index 9368e4eea..3c0b66683 100644
--- a/public/llms-full.txt
+++ b/public/llms-full.txt
@@ -3340,6 +3340,12 @@ URL: https://three.ws/docs/user-wallet
Every user account can own one custodial wallet: the master wallet, the financial hub for the person rather than the bot. Provision it, read balances, send SOL or any SPL token, fund an agent, and read its on-chain history, with the spend safeguards on each route.
+### Docs: Alpha-drip
+
+URL: https://three.ws/docs/alpha-drip
+
+Alpha-drip lets a copy-trading leader price the latency of their own signal: $THREE holders in higher tiers see the copy intent first, everyone else after a delay the leader sets. It delays the reveal, never the record.
+
### Docs: Copy Trading
URL: https://three.ws/docs/copy-trading
diff --git a/public/llms.txt b/public/llms.txt
index 24c92a630..d67f19d67 100644
--- a/public/llms.txt
+++ b/public/llms.txt
@@ -593,6 +593,7 @@ Docs, tutorials, and reference.
- [Docs: Agent wallet control API](https://three.ws/docs/agent-wallet-api): Every three.ws agent owns one custodial Solana wallet. Seven owner-only HTTP surfaces hang off it, and this is their developer reference: exact routes, exact request and response JSON, exact error codes, and a working curl call for each.
- [Docs: USDC agent vaults](https://three.ws/docs/vaults): A vault lets strangers put real USDC behind one trading agent, on terms the agent's owner publishes up front. The deep reference: every route and who may call it, the share and fee math, the guards in front of a trade, and the public audit ledger.
- [Docs: Your master wallet](https://three.ws/docs/user-wallet): Every user account can own one custodial wallet: the master wallet, the financial hub for the person rather than the bot. Provision it, read balances, send SOL or any SPL token, fund an agent, and read its on-chain history, with the spend safeguards on each route.
+- [Docs: Alpha-drip](https://three.ws/docs/alpha-drip): Alpha-drip lets a copy-trading leader price the latency of their own signal: $THREE holders in higher tiers see the copy intent first, everyone else after a delay the leader sets. It delays the reveal, never the record.
- [Docs: Copy Trading](https://three.ws/docs/copy-trading): Copy trading lets one wallet follow another's real trades. Two engines sit behind it: the custodial agent mirror, where the platform signs a real on-chain trade from your agent's wallet within its spend policy, and non-custodial subscriptions, which record a sized intent for you to sign.
- [Docs: On-chain Deployments](https://three.ws/docs/deployments): /deployments is the live, cross-chain feed of agent identities landing on-chain: every ERC-8004 Identity Registry registration on EVM and every Metaplex Core agent mint on Solana, in one chronological stream, as each one lands. It is a read-only public surface.
- [Docs: CA to x402](https://three.ws/docs/ca2x402): Paste a token contract address, get back a live, agent-payable x402 market-intel endpoint for that exact token. The generated endpoint costs a small USDC payment per call, is discoverable in the x402 bazaar, and needs no keys, no backend, and no deploy from the person who generated it.
diff --git a/public/sitemap/index.html b/public/sitemap/index.html
index bf73e5c6b..2f533b2ec 100644
--- a/public/sitemap/index.html
+++ b/public/sitemap/index.html
@@ -88,7 +88,7 @@
<main class="sm-wrap">
<div class="sm-hero">
<h1>Sitemap</h1>
- <p>All 902 pages on three.ws, grouped by purpose. Looking for the machine-readable versions?</p>
+ <p>All 903 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>
@@ -100,7 +100,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 902 pages by name, path, or description…" aria-label="Filter pages" autocomplete="off" spellcheck="false" />
+ <input id="sm-filter-input" type="search" placeholder="Filter 903 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>
@@ -2470,7 +2470,7 @@
<section class="sm-section" id="learn">
<header>
- <h2>Learn<span class="sm-count" data-count>413</span></h2>
+ <h2>Learn<span class="sm-count" data-count>414</span></h2>
<p class="sm-section-desc">Docs, tutorials, and reference.</p>
</header>
<ul class="sm-list">
@@ -4077,6 +4077,13 @@
<span class="sm-desc">Every user account can own one custodial wallet: the master wallet, the financial hub for the person rather than the bot. Provision it, read balances, send SOL or any SPL token, fund an agent, and read its on-chain history, with the spend safeguards on each route.</span>
</a>
</li>
+ <li>
+ <a href="/docs/alpha-drip">
+ <span class="sm-title">Docs: Alpha-drip</span>
+ <span class="sm-path">/docs/alpha-drip</span>
+ <span class="sm-desc">Alpha-drip lets a copy-trading leader price the latency of their own signal: $THREE holders in higher tiers see the copy intent first, everyone else after a delay the leader sets. It delays the reveal, never the record.</span>
+ </a>
+ </li>
<li>
<a href="/docs/copy-trading">
<span class="sm-title">Docs: Copy Trading</span>