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
fix(x402): give an unfundable fee payer its own reject class, not simulation_failed
nirholasaa0e4a74bf1a
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 465b35586..648a128f4 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -7,6 +7,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr## 2026-09-09- **Docs · Fade Radar** (`/docs/fade-radar`): How the Fade Radar scores a coin's buy side: what makes a wallet a reverse indicator, the 0 to 100 fade score, the verdict bands, and the out-of-sample measurement behind them.+- **Docs · Rivalries** (`/docs/rivalries`): What changed on the trader board: who passed whom, who just arrived, and who is closing. Derived from close timestamps rather than a snapshot table, so the matchups work retroactively and cannot disagree with the leaderboard.- **Fade Radar: the wallets that are never right** (`/fade`): The inverse of the Smart Money Radar. Every pump.fun coin ranked by how much of its buy side comes from wallets with a judged on-chain record and not one winner in it, with the measured, out-of-sample odds behind each verdict.- **A link that opens your house in 3D now really opens it in 3D**: The live home page remembers whether you last looked at your house in 3D or as a room list, which is what you want when you open it yourself. It was also overruling links that asked for one view by name: once you had used the 2D view even once on a device, every /smart-home/<id>?view=3d link on that device quietly opened flat again. That matters for the two cases the parameter exists for, a link you share with someone in the house and the address a kitchen or wall display is pinned to. A view asked for in the link now wins, for 3D, 2D and the floorplan alike, and following such a link no longer overwrites the preference that device chose for itself. (`/docs/home-scene`) `[fix]`- **An app key can no longer say yes to unlocking your door**: A person saying yes is the one thing that stands between an agent and your front door, and we found a way around it. If you had ever issued an API key or connected an app to your three.ws account, that key could send an unlock request with the "the owner already approved this" flag set, and the lock opened, with nobody asked and nothing to click. We reproduced it against a real house and a real deadbolt before fixing it. Two things changed. Only a signed-in browser session can say yes now: a key or a connected app can ask to unlock, open or disarm, and is always answered with "a person has to approve this", exactly as the agent in your chat window already was. And the home permissions you approve when you connect an app are now actually enforced on every home request, so an app you gave read-only access to, or one you never gave home access at all, is refused instead of let through. Nothing legitimate changed: your agent still asks, you still approve, the door still opens. (`/smart-home`) `[security, fix]`@@ -15,6 +16,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **Connecting a home: the page now says which state it is in, out loud**: Two moments on /smart-home were doing the right thing silently. Typing an address that can never work (a 192.168 number, a .local name) has always put the reason under the field straight away, before anything is sent, but the message was carried by colour alone and a screen reader never read it out; it is now announced the moment it appears, and marked in a way that does not depend on seeing red. And a house that has stopped answering, is refusing the stored token, or has simply gone quiet is now labelled as such by the page itself rather than only in the sentence on its card. Nothing about what you see moves: the last known summary of your house stays exactly where it was, with how long ago it last answered, because a home that went quiet should never look like a home that was deleted. (`/smart-home`) `[improvement, fix]`- **Endpoint Shopper fits a phone, and says something useful when a run finds nothing to buy**: A full audit of /shopper, the page where you describe a task, set a budget, and let an agent shop the x402 Bazaar for endpoints that can answer it. Three things were wrong. A run that came back with no plan and no answer, which is what happens when nothing in the Bazaar matches the task or everything that does prices above your ceiling, painted an empty white column and stopped: no explanation, no way forward. That case now says no endpoints matched, quotes the task back, and offers the three things that change the outcome (rewrite the task, raise the budget, browse the Bazaar) plus a button to run again. Second, when the request could not reach us at all, the page showed the browser's own wording for a dropped connection, which names no cause and suggests no fix; it now says the agent service could not be reached and what to do about it. Third, on a phone narrower than 560px the four navigation links were squeezed into a strip about 76px wide and had to be dragged sideways a few pixels at a time to read; they now wrap onto their own full-width row. Alongside those: the results column announces itself to a screen reader while a run is in flight and when it settles, the Task label sits above its box as intended rather than beside it, and an internal ticket number that had been sitting in the page's headline label since launch is gone. (`/shopper`) `[fix, improvement]`- **Ethereum wallets load on the portfolio page again, keylessly, and every token logo shows up**: A full audit of /portfolio, where you paste any Solana or Ethereum address and get a live portfolio. The Ethereum half had gone dark: the single provider behind it ran out of monthly capacity, so every 0x address answered "Data source unavailable" with nothing behind it. Ethereum now has the same keyless floor Solana has always had. The ETH balance comes from the public Ethereum nodes the rest of the platform already uses, the token list with its prices and icons comes from a public block explorer, and the 24h move comes from the same market source the Solana side uses, with the coverage it achieved stated on the card. The Data panel names whichever lane actually answered, so you can see whether you are reading the paid provider or the free one. Token logos were another visible break: the page pointed your browser straight at an IPFS gateway, which the browser refuses on cross-origin grounds, so every holding fell back to a three-letter monogram and your address bar handed your IP to the gateway on every load. Logos now come through three.ws, sized for the row. Keyboard users could tab onto a slice of the allocation donut and get nothing: the tooltip was wired to an event handler property that browsers do not actually support, so it never fired once; the slice now names its asset and share, and Escape dismisses it. When a lookup fails, the page now shows the reason the server actually sent instead of a generic sentence, and clicking Retry after a rejected address no longer silently reloads the wallet you looked at before it. Underneath, the fallback that names Solana tokens when the primary metadata source is out of quota had never run at all, because of a missing import; token symbols and names come back on that path. (`/portfolio`) `[fix, improvement]`+- **Fact-check now reads the part of a source that is actually about your claim**: When the fact-checker fell back to Wikipedia, it only ever read each article's opening summary. An opening summary says what a page is about, so it carries the answer only when your claim is about the page's subject. Ask whether Napoleon was unusually short and it read the first lines of "Napoleon", "Napoleon III" and "Napoleonic Wars", none of which mention height at all, so every source was scored as saying nothing and the verdict came back "not enough evidence" while the passage about his height sat further down the same article. The checker now reads each article in full and picks the paragraphs that actually discuss your claim, so that question returns the "Appearance and image" and "Napoleon's height" sections instead. Reference lists are skipped, since they repeat your words without asserting anything, and the deeper read is bounded by the time the check already had, so a slow source can never cost you the evidence that already arrived. (`/docs/fact-check`) `[improvement]`- **Fade Radar: the wallets that have never once been right, and the coins they are crowding into**: The Smart Money Radar tells you which proven winners are buying a coin. Fade Radar is the other half of that question, and on pump.fun it turns out to be the sharper one: how much of a coin's buy side is money that has never been right. A wallet joins the reverse-indicator board only after five coins it bought have a known outcome and not one of them won, which is a bar a surprising number of addresses clear. The new page ranks every launch from the last few hours by how much of its observed buy side belongs to those wallets, by wallet count and by SOL, and carries a second board of the wallets themselves with their full record. The number above the board is the part we care most about: it is measured, not asserted. We rebuild the reverse-indicator group using only coins whose outcome was known before the coins it is graded on existed, then check what actually happened. Coins where a quarter or more of the buyers were reverse indicators went on to win 1.8 percent of the time, against 22.1 percent for coins with none, across 26,626 labelled coins. Nothing here is a short and nothing signs anything: on a bonding curve the only tradeable form of a fade is not buying, so every action on the page is a link out to the coin, its intel, or a wallet's track record. Wallet links also now open directly on the Smart Money Radar, so an address cited anywhere on the platform lands on its record instead of a board you have to scan by eye. (`/fade`) `[feature]`- **Homes connected through the relay now follow the house when you rearrange it**: If your Home Assistant is only reachable inside your house, three.ws reaches it through the three.ws integration you install there, which dials out to us. Those homes were building their room list once, when the connection opened, and then quietly ignoring changes: assign a lamp to the kitchen, rename a floor, add a device, and the 3D house kept showing the old arrangement until the connection happened to be rebuilt. Homes connected by a direct address never had this problem, and the split was in the relay, which was not carrying the four small notices Home Assistant sends when its rooms, floors, devices or entities change. It carries them now, so both kinds of connection track the house the same way and updates land in seconds. The notices only say that something changed; the relay already read the full room and floor lists, so nothing new about your house is exposed by this. (`/smart-home`) `[fix, infra]`- **Oracle: a failed request now says so, instead of claiming no coins have been scored**: A full audit of /oracle, the fused conviction board for pump.fun launches. When a panel's request failed, the page told you the opposite of the truth: the live feed claimed "Oracle is warming up" and said the engine ships with its backend, the movers, proof, agent-ranking, activity and 3D-graph panels each claimed there was simply nothing to show, and the performance record said the edge was still proving itself. Every one of those is now a real error state that names what went wrong (offline, rate limited, or an engine error) and offers a retry that actually recovers. The Proof gallery had a second bug behind that one: opening it for the first time while the request failed painted nothing at all, not even a skeleton. Searching a symbol Oracle has not scored used to make the results dropdown vanish with no explanation, which reads as a broken search box; it now says there is no match, and says so differently when search itself is down. The conviction-breadth bar's tier segments and legend chips were 10 and 15 pixels tall, too small to reliably tap on a phone, and now carry a full 24-pixel target without changing how the bar looks. Screen readers can finally move from a tab into the panel it opens, every button declares its type, and if a browser is holding a cached copy of an older release the 3D graph explains that and offers a reload instead of retrying a module that can never load. (`/oracle`) `[fix, improvement]`@@ -30,6 +32,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **Sign Language Avatars is usable the moment the page opens**: The signing avatar on /sign-language is a multi-megabyte model, and until it finished downloading the page had nothing to say: an empty box, an empty status line, and buttons that had not been wired yet, so an early click on Sign it did nothing at all. The stage now shows a breathing silhouette while the avatar loads, every control is wired before the download starts, and anything you type, click or open with a ?say= link in the meantime is queued and signed the moment the avatar lands. If the model fails to download, the stage says so and offers Retry the avatar plus a link to the sign API below, which runs on the server and works without the 3D preview; the vocabulary chips and the Sign it button now explain why they cannot sign instead of doing nothing. An avatar with no signing skeleton says so in the same words. (`/sign-language`) `[improvement, fix]`- **Sign Mirror tells you why the camera did not start where you are actually looking**: On /sign-mirror, pressing "Turn the camera on" and being refused, or being on a device with no camera, put the explanation on the far side of the page: it appeared in the status strip over the 3D avatar, in the other column, while the box directly above the button you had just pressed carried on giving the same idle tip as before. The button snapped back to "Turn the camera on" with nothing visibly changed beside it, so a refused camera read as a button that simply did not work. Every camera and hand-tracker failure now lands in that box beside the button, in both the side-by-side and the stacked phone layout, and the box turns amber and solid-edged so a problem no longer looks like a coaching tip. The sentences themselves are unchanged and still say what to do next, naming the browser permission prompt, a camera busy in another app, a missing camera, or a hand tracker that could not be downloaded. Picking another letter clears the warning and returns the box to its normal hint. (`/sign-mirror`) `[fix, improvement]`- **Signal Marketplace: publisher avatars appear, prices read like money, and a feed page no longer goes blank for signed-out readers**: A full audit of /signals, the directory of paid trading feeds ranked by proven edge. Four real defects came out of it. Every publisher without a profile picture showed an empty grey square: the generated fallback avatar is an image, and the card was assigning it to a CSS background, which browsers ignore, so it never painted. A publisher whose profile picture had gone missing showed the browser's broken-image icon; both now render as an image that quietly falls back to the generated avatar. Prices were printed as raw numbers, so a feed charging 12.345678 USDC advertised exactly that; amounts are now grouped and rounded the way money reads, while a genuine sub-cent price keeps its digits instead of rounding to zero. Subscriber counts skipped the same shortening every other number on the card uses and printed as 1234567. Worst of all, opening any live feed's own page while signed out crashed the render and left a blank panel where the sign-in prompt belongs, which is exactly the reader that panel exists to convert. Each card's screen-reader description now carries every number a sighted reader sees (rank, edge, hit rate, average ROI, signal counts, subscribers and price) instead of just the headline score, and the loading skeleton's shimmer now sweeps across the card rather than starting halfway off it. (`/signals`) `[fix, improvement]`+- **Smart Home: the connection pool now sizes itself to the server it is running on**: The number of houses one server holds open at once was set by hand, in a different place from the memory that has to hold them, and the two drifted apart three times. Left alone, that ends with a server running out of memory and taking the whole API down with it, which every part of three.ws would feel, not just Smart Home. The pool now reads the memory its own container actually has and refuses to hold more houses than fit, saying so in the health endpoint when it does. When there is less room it connects fewer houses per server and keeps working, instead of risking an outage for everybody. (`/docs/smart-home`) `[infra, fix]`- **The "have you tried" card no longer hangs off the side of the screen on a phone**: The small suggestion card that appears in the bottom corner of the site was drawn 34 pixels wider than the space it asked for, because its padding and border were being added on top of its width instead of counted inside it. On a phone that pushed the card 22 pixels past the left edge of the screen, so its kicker, title and description were all cut off mid-word and the button inside it ran wider than the card itself. This only happened on the pages that do not load the main site stylesheet, which includes the whole markets family: the screener, coin pages, categories, the heatmap and about thirty others. The card now sits fully on screen with an even gutter on both sides at every width, and its button fits inside it. (`/screener`) `[fix]`- **The 3D Playground recovers when a model will not load, and now works from the keyboard**: Dropping a .glb into /playground had exactly one failure mode: a dimmed screen and a spinner that never stopped. If the file was corrupt, the download stalled, or the 3D viewer script itself was blocked, nothing on the page said so and there was no way back. That spinner is now a shimmer inside the viewer frame instead of a curtain over the whole page, so the controls stay usable while a model streams, and a failure lands in a designed error card that names what went wrong and offers Retry or a file picker. A load that never finishes gives up after 25 seconds rather than hanging forever. The lighting presets no longer strand the scene on the previous preset’s exposure. The page also gained the structure it was missing: a real heading that says what it is for, headings on every control group, an accessible name on each switch, slider and field, a focus ring on everything you can tab to, and an upload button the keyboard can actually reach (it was hidden with display:none, which drops it out of the tab order entirely). On a phone the top navigation scrolls instead of vanishing. Animation names read out of an uploaded file are rendered as text, never as markup. (`/playground`) `[fix, improvement]`- **The agent-wallet demo pays again when an endpoint asks the buyer to cover its own network fee**: On /play/agent-wallet a 3D avatar walks up to a paid x402 endpoint and buys a live market signal with real USDC on Solana. The page had gone quiet. three.ws's own paid endpoints switch to a self-pay payment challenge whenever the wallet that normally sponsors the Solana network fee cannot co-sign, and the bridge behind the page only knew how to build a sponsored payment, so every price quote came back as a server error and the demo never got past its connecting state. The bridge now signs both kinds: when no sponsor is offered, the agent wallet pays its own network fee, exactly as the platform's own payment ring already does. Four smaller things came with it. The page no longer offers a Pay button it knows will fail: when the agent wallet cannot cover the quoted price it says so and leaves the deposit address in front of you. Switching between BTC, ETH and SOL re-prices immediately instead of waiting for the next payment. The wallet balance and the Pay button stop reverting to placeholder text a few seconds after they load, which the translation pass had been overwriting. And the page carries a real page heading for screen readers and search engines, which it had been missing entirely. (`/play/agent-wallet`) `[fix, improvement]`@@ -47,6 +50,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **The Oracle reference now reads the model it is describing**: The complete Oracle documentation at /oracle/docs described version 2 of the conviction model while production had moved on to version 3, and the difference was not cosmetic. Version 3 changed the question the score answers: earlier versions ranked the odds of a spike, and version 3 ranks the odds of a spike that holds, counting a launch as a hit only if a holder who bought at first sight is still up. A coin that ran 3x and gave it all back was a success under the old target and is a miss under the new one, which is why the base rate underneath every figure on the page is far lower than it used to be. The page had the old target, the old tier probabilities and the old holdout numbers throughout, and its roadmap still promised fitted weights and calibration that had already shipped. Every model figure on the page is now read live from the published model card when you open it, because the engine refits itself every six hours behind a promotion gate and any number typed into a document goes stale on a clock. When that read fails the page says so, shows the values it was published with, explains that they may trail production, and offers a retry rather than a blank space. Two public endpoints that existed but were undocumented are now in the reference: the one that publishes the whole scoring machine, weights and holdout curve and the record of every fit ever refused, and the one that publishes the realized win rate per conviction band from real fills. The tier ladder used to truncate its own evidence, cutting off the sample counts on every band below the top, and now gives each band a full line. In light mode the tier names were near-white on a white card and the strongest bands were invisible; they now have their own ramp. (`/oracle/docs`) `[docs, fix]`- **The partner page gets its footer back, fits a narrow phone, and stops naming three partners it does not have**: An end-to-end audit of /partners found it was the only page on the site that carried a footer slot but never loaded the footer, so the whole bottom of the page was missing. It is back. On a 320px phone the partner cards were 38px wider than the screen and the overhanging text was silently cut off, because a card header could not shrink past its logo, name and category chip on one line; the chip now wraps and every card fits. The page description search engines and link previews read was also stale: it advertised Intel, Microsoft and Oracle, none of which have a card, and left out OpenAI and HackerNoon, which do. The AWS card said View on AWS Marketplace above a link to our own AWS page, so it now says what it actually opens. Beyond that: the 8 partners and 22 chains counters are no longer hidden from screen readers and the partner number is now counted from the cards themselves, keyboard users get a visible ring on every card and button, the card lift is dropped for anyone who asks for reduced motion, and the page eyebrow, the four benefit headings and every card call to action are translatable instead of staying English on a translated page. The floating walk companion also got a full-size dismiss, avatar-swap and narration button on touch devices, everywhere it appears. (`/partners`) `[fix, improvement]`- **The partnership page works properly on the partner's own site**: The IBM partnership page is published once onto IBM's own domain and then keeps itself current by reading from three.ws, so everything it loads is a cross-origin read and anything we get wrong there is invisible on three.ws itself. Three things were wrong. The site-wide command palette asked the partner's server for our page index and for the ranking module it imports, so it never opened and logged an error on every visit: the index now travels with the code the way the language catalogs already do, and both files are readable from other sites. And a build step that adds the site's mobile stylesheet to every page was reaching the partner artifacts too, even though they are copied out untouched by design, so the hosted copy asked IBM's server for a stylesheet only we have. All three are closed, and the audit that loads the page from a foreign domain now passes all four of its checks: the live update applies, the language switcher mounts, the paid demo arms, and the console is clean. `[fix]`+- **The payments dashboard now says whose wallet ran out of SOL**: When a Solana payment cannot go through because the wallet paying the network fee is too low, the chain reports it as a generic simulation failure. Our status page grouped all of those together, so the platform's own fee wallet running low looked exactly like a buyer signing from an empty wallet, and both were also counted as payment-network faults. They are now three separate, named outcomes, so the status page says whether the money problem is ours to fix, the buyer's, or neither. Today's reject book was 1,438 rows of the first kind reading as the third. `[fix, infra]`- **The pitch deck now shows the whole character, and says so when the 3D cannot load**: The live 3D figure on the deck at /pitch was framed by a camera that cut it off above the chest and pointed at its back, so the slide that says "give your AI a face" showed neither a head nor a face. Both stages now frame the full character from the front. Each stage also ships a still frame rendered from the same glTF file: it fills the panel while the model streams instead of leaving an empty box, and if the 3D runtime is blocked or fails outright the panel says so in the open, drops the "Live" badge that used to sit over nothing, and offers a retry. Navigation got the same pass: the slide dots are now full-size tap targets and step out of the way on a phone, the language picker no longer lands on the slide counter, slide copy no longer runs underneath the nav bar on a tablet, links on hidden slides are out of the keyboard tab order, and every button and link has a visible focus ring. (`/pitch`) `[fix, improvement]`- **The press kit reads in the three.ws typeface, fits a phone, and quotes every mark at its true size**: Every paragraph on the press kit was rendering in the browser default serif on a bare white-ish ground: the page styled its own cards and headings but never applied the site typeface, colour, or background to the document itself, so the one page a journalist opens looked nothing like the rest of three.ws. It now uses the platform design tokens throughout, in both light and dark mode. On a 320px phone the two OpenAI announcement cards were sliced off at the right edge, taking their Download PNG buttons with them, and because the page clips rather than scrolls sideways there was no way to reach what was cut; both card grids now fold to a single full-width column instead. The pixel dimensions printed under each mark were also all slightly wrong, off by a pixel or two from the artwork they labelled, which is the number a designer laying out a conference programme actually acts on. They are corrected, and the brand asset renderer now writes them back from the PNG headers on every build the way it already did for the archive size, so they cannot drift again. Last, the Copy buttons beside the boilerplate did nothing at all when the browser withheld clipboard access; they now select the passage in place and tell you which keys to press. (`/press`) `[fix, improvement]`- **The Pump Visualizer's live counters stopped freezing a few seconds after the page opened**: A full audit of /pump-visualizer, the 3D scene of live pump.fun mints. The status bar across the top counts the tokens in the scene, the mint rate per minute and the total market cap, and about fifteen seconds into every visit all three froze: the counter sat at 0 and the rate and total sat at a dash while the scene behind them kept filling with new coins. The cause was the page's own translation pass. Those three numbers were written inside blocks of translated copy, so the moment the language file arrived the browser rebuilt that copy and threw away the very elements the page was writing into. The numbers now live beside their labels instead of inside them, so the labels still translate into all 85 languages and the values keep counting for as long as the page is open. The per-minute and per-hour units now translate too, which they never did once the page switched between live mints and migrations. The page also gained a heading and a labelled search box for screen readers, and its browser tab now reads Pump.fun Visualizer, three.ws instead of a retired product name. (`/pump-visualizer`) `[fix, improvement]`@@ -58,10 +62,12 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **The sniper scoreboard now links out to the pages that explain what it is showing you**: A full audit of /sniper/experiments, the live board comparing rule-driven sniper agents against LLM-judged ones on the same market. The board is dense with terms it could only gloss in a hover tooltip: earned autonomy tiers, moon bags, the reasoning ledger behind every verdict, the exit ladder. A reader who wanted the real explanation had nowhere to go. The page now ends with a row of links to the seven surfaces that write each of those up, from the live Sniper Arena floor to the earned-autonomy docs and the page where you arm your own agent. Four smaller fixes came with it. The Best arm tile printed its profit in plain white even when that number was a loss, so a losing leader read as a win at a glance; it is now coloured like every other figure on the board. An arm or a judge with no model recorded against it used to crash the whole render; it now reads as unattributed and the rest of the board keeps working. Both tables label their column headers properly, so a screen reader can pair a figure with the column it belongs to across nine columns. And the time-window buttons are declared as buttons rather than defaulting to form submits. (`/sniper/experiments`) `[improvement, fix]`- **The spend policy dry run stops contradicting its own counters**: The simulator at /pay/simulator reports what an agent budget actually buys, and its headline sentence disagreed with the numbers directly beneath it. An endpoint that answers without asking for payment is free: it costs nothing and is never checked against your policy. The counters knew that, and the sentence did not, so the very first run on the page announced that all seven calls settle while the tile beside it said six. Calls that could not be priced at all vanished the same way, counted nowhere the reader could see. Both now have their own tile, and the verdict sentence is built from the counts it is describing, so settled, free, unpriced and refused always add up to the total in front of you. A run that fails now says why: an unusable line used to produce a bare "Simulation failed (HTTP 400)", and now quotes the endpoint the simulator could not read along with what a working line looks like. A budget left blank was quietly costed against one dollar, giving you a verdict for a budget you never proposed; the answer now says when that substitution happened. On a phone the little question marks beside each field were fifteen pixels wide and their explanations opened off the side of the screen, so the help was unreadable exactly where it was needed most: the tap targets are now large enough to hit and the explanations stay on the page at every width. (`/pay/simulator`) `[fix, improvement]`- **The Splat Viewer keeps its recenter and download controls, and its errors say what went wrong**: Loading a scene on /splat used to erase the viewer's own controls: writing the scene label into the HUD replaced the recenter and download buttons with plain text, so from the first render onward neither existed. Both now live beside the label and survive every scene swap, and the download always offers the scene you are actually looking at rather than a previous one. The error state was worse than useless: it showed a heading over an empty space because the explanation was being written into an element that was not on the page. Now a failed load tells you what happened and what to do, including the advice to download and upload a file whose host blocks cross-origin requests. Clicking a sample or picking a file also shows the loading state immediately instead of sitting on an idle stage while the splat engine downloads in silence, and an engine that fails to load says so rather than leaving the page frozen. (`/splat`) `[fix, improvement]`+- **The trading arena now says who just passed whom**: The live leaderboard on the arena told you who was ahead and nothing about what had changed, so a place changing hands, which happens several times a week on its own, went unnoticed. A grudge-match strip now sits under the standings: each trader is paired with the one directly above them, labelled as an overtake, a debut or a standing chase, with the profit or loss both sides settled in the last 24 hours as the reason. It is worked out from the same closed on-chain trades the board is ranked from, by rebuilding what the board actually said 24 hours ago out of the trade timestamps rather than trusting a stored snapshot, so the matchups reach back over history the platform already has and can never disagree with the leaderboard or with either trader's profile. Every line is written from those numbers: it will not call a trader behind when they in fact hold more SOL and rank lower on consistency, and it will not say someone booked nothing when they simply did not trade. Each matchup links to the leader's verified record and to a ghost-copy of them with no money at risk. Also available to agents and scripts at /api/sniper/rivalries. (`/play/arena`) `[feature]`- **The Windows 11 widget draws its card again, and a new check keeps the board honest**: The Agent glance widget on the Windows 11 widgets board renders an Adaptive Card, and the board fills that card in with its own expression engine rather than with JavaScript. Our card asked for the three stat rows the way JavaScript reads an array, which that engine treats as a syntax error, and it refuses the whole card rather than skipping the one line: a pinned widget came up empty with nothing to show for it anywhere else. The card now uses the syntax the board expects, and there is a new check that fills it in with the board's own engine before anything ships, alongside checks that the manifest, the service worker and the two endpoints still agree with each other. The board is the one surface we cannot open from a build machine, so the checks that stand in for it are the ones that have to be real. (`/glance`) `[fix, infra]`- **Three fades now stop when you ask the site to stop moving**: Turn on reduced motion in your operating system and three.ws is supposed to hold still: every animation timing on the site is named rather than spelled out, so one switch can zero all of them at once. Three places had drifted off that and spelled their own timing instead, which meant the object library card fade, the avatar picker chips and the Money Pulse rows kept animating for people who had explicitly asked them not to. One of them was pointing at a timing name that does not exist, so the value it fell back to was never the one anyone chose. All three are back on the named ladder at the same speed they always looked, and the reduced-motion switch reaches them again. (`/objects`) `[fix, improvement]`- **When the payment wallets look empty, the self-heal now says whether they are empty or just fenced**: The x402 payment rail keeps a set of platform wallets topped up from one funding root, and a recovery run reports why it could not draw on each source. Every source that held less than its configured floor reported the same thing: "at or below floor". That single phrase covered two opposite situations. A wallet holding nothing needs money added from outside. A wallet holding real funds behind a floor somebody set does not: the platform already owns that money, and a floor decision releases it. Because the two printed identically, three separate investigations of the same stalled rail concluded the platform was out of funds while one of its own wallets held roughly forty-five times what the stalled wallet was short. A skipped source now reports how much it is holding and the line it had to stay above, and every run totals the funds it left behind, so an operator can tell at a glance whether the recovery needs a deposit or a decision. The health page and the operations runbook now point at that total instead of asserting that money is required. `[fix, infra]`- **Your monthly agent turns now count, and locking up never does**: Talking to the agent about your house is the one part of the smart-home lane that can really cost money: the room graph makes a home prompt large, and on a paid model a single turn costs several weeks of holding that house’s connection open. Those turns were being counted but never actually limited. They are now, against the monthly allowance shown on your plan page, and if you run out the agent says so in a sentence that names the limit, the date it resets and where to raise it, instead of failing at you. Two things are deliberately left outside that limit. Asking the agent what the house is doing still works, because you have to be able to see which door is open. And telling it to lock a door, close a garage or a valve, or arm the alarm still runs, over quota, on a paused home, in every state we can put an account in: the safe direction is free, always, on every plan. If our own billing lookup fails, the turn is allowed through rather than refused. (`/smart-home/plan`) `[feature, improvement]`+- **Your own agent now stands in your live house**: The 3D home at /smart-home/<id> always drew a generic figure standing in your rooms, even when you had given your agent a face months ago. It now shows your agent: the same avatar the walk world, /play and the voice satellite use, read from the one record the whole platform treats as "my agent". Switch agents in another tab and the body in the house follows, with no reload. It is fetched after the house has already drawn, so nothing waits on it, and the platform's default body stands in when you have no agent yet, no avatar yet, or an avatar you keep private, which by design publishes no model for any page to read. (`/docs/home-scene`) `[improvement]`- **Your private avatars load on the dashboard again, and say so when they cannot**: Avatars you have not made public were failing to load on your dashboard, with nothing on the page to say why. The dashboard was being handed a temporary direct link into our storage provider rather than a link back through three.ws. When storage stopped accepting our credential, that direct link was refused in a way browsers deliberately hide, so the page could not tell the difference between a refusal and a dead connection: it just showed nothing. Private avatars now load through three.ws itself, which checks that the avatar is yours exactly as before, and which already knows how to fall back to a second copy when storage is having a bad day. As a side effect these links no longer expire, so a dashboard tab left open for an hour still shows your avatars when you come back to it. (`/dashboard/avatars`) `[fix]`## 2026-09-08diff --git a/api/_lib/ops/x402-settle-health.js b/api/_lib/ops/x402-settle-health.jsindex 4783d155d..169fa7e2f 100644--- a/api/_lib/ops/x402-settle-health.js+++ b/api/_lib/ops/x402-settle-health.js@@ -109,7 +109,14 @@ const FEE_GOVERNOR = /^fee_runway_exhausted/i;// arrives either as the 503 prose or as the raw floor signature.// `insufficient_lamports_for_fee` is the same starvation reported from inside// the settle path (see runway-lab's bucketer, which files it under floor too).-const SPONSOR_FLOOR = /^(settlement temporarily unavailable|fee_wallet_below_floor|sponsor_sol_floor|sol_floor|insufficient_lamports_for_fee)/i;+// `sponsor_fee_unfunded` is the chain's own verdict on the same wallet, raised by+// assertSettleable() when simulation returns InsufficientFundsForRent on account+// index 0 (the fee payer, by definition) and that fee payer is OUR sponsor. It+// belongs here and not in RAIL_SIGNATURE: before it had its own class it read as+// `simulation_failed`, which /simulation/ matches, so a starved sponsor was+// counted as a rail fault. The buyer-side twin `payer_fee_unfunded` deliberately+// stays out: that wallet is not ours and needs no operator action.+const SPONSOR_FLOOR = /^(settlement temporarily unavailable|fee_wallet_below_floor|sponsor_sol_floor|sol_floor|insufficient_lamports_for_fee|sponsor_fee_unfunded)/i;/*** Why did the settle rate fall? Two failure shapes are indistinguishable in thediff --git a/api/_lib/x402/self-facilitator.js b/api/_lib/x402/self-facilitator.jsindex 3184c9801..edcba8456 100644--- a/api/_lib/x402/self-facilitator.js+++ b/api/_lib/x402/self-facilitator.js@@ -869,7 +869,26 @@ async function assertSettleable({ tx, connection, requirement, decoded }) {// A dry sponsor is a platform condition, not this payment's fault: record// it so the 402 challenge stops advertising a Solana accept that cannot// settle, rather than rejecting one payment and inviting the next.- noteSponsorRentFailure(simErr, decoded?.feePayer);+ const sponsorDry = noteSponsorRentFailure(simErr, decoded?.feePayer);+ // Give the fee-payer verdict its own reason CLASS, because every consumer+ // of this string groups on the token before the first ':'. /api/healthz+ // exposes only that prefix, and isRailFault() in ops/x402-settle-health.js+ // matches /simulation/, so folding this into `simulation_failed` filed+ // the platform's own unfundable sponsor under the same bucket as a buyer+ // signing from an empty ATA, AND counted it as a rail fault. Measured in+ // production on 2026-09-09: `simulation_failed` sat at the top of the+ // verify book with 1,438 rejects in 24h and every single row was+ // {"InsufficientFundsForRent":{"account_index":0}} on our sponsor, a+ // wallet 0.00083 SOL under its floor. Read as a rail fault it points an+ // operator at the RPC lanes, which is the one thing this class is never+ // about. Account index 0 is the fee payer by definition, so the split is+ // exact, not a heuristic: `sponsor_fee_unfunded` is ours to fund,+ // `payer_fee_unfunded` is the buyer's own wallet and needs nothing.+ if (isFeePayerRentFailure(simErr)) {+ const cls = sponsorDry ? 'sponsor_fee_unfunded' : 'payer_fee_unfunded';+ const who = decoded?.feePayer ? String(decoded.feePayer) : 'unknown';+ return { ok: false, reason: `${cls}:${who}`.slice(0, 160) };+ }return { ok: false, reason: `simulation_failed:${s}`.slice(0, 160) };}return { ok: true };diff --git a/data/changelog.json b/data/changelog.jsonindex d53718551..944039deb 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -1,6 +1,24 @@{"$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-09-09",+ "title": "The trading arena now says who just passed whom",+ "summary": "The live leaderboard on the arena told you who was ahead and nothing about what had changed, so a place changing hands, which happens several times a week on its own, went unnoticed. A grudge-match strip now sits under the standings: each trader is paired with the one directly above them, labelled as an overtake, a debut or a standing chase, with the profit or loss both sides settled in the last 24 hours as the reason. It is worked out from the same closed on-chain trades the board is ranked from, by rebuilding what the board actually said 24 hours ago out of the trade timestamps rather than trusting a stored snapshot, so the matchups reach back over history the platform already has and can never disagree with the leaderboard or with either trader's profile. Every line is written from those numbers: it will not call a trader behind when they in fact hold more SOL and rank lower on consistency, and it will not say someone booked nothing when they simply did not trade. Each matchup links to the leader's verified record and to a ghost-copy of them with no money at risk. Also available to agents and scripts at /api/sniper/rivalries.",+ "tags": [+ "feature"+ ],+ "link": "/play/arena"+ },+ {+ "date": "2026-09-09",+ "title": "The payments dashboard now says whose wallet ran out of SOL",+ "summary": "When a Solana payment cannot go through because the wallet paying the network fee is too low, the chain reports it as a generic simulation failure. Our status page grouped all of those together, so the platform's own fee wallet running low looked exactly like a buyer signing from an empty wallet, and both were also counted as payment-network faults. They are now three separate, named outcomes, so the status page says whether the money problem is ours to fix, the buyer's, or neither. Today's reject book was 1,438 rows of the first kind reading as the third.",+ "tags": [+ "fix",+ "infra"+ ]+ },{"date": "2026-09-09","title": "The partnership page works properly on the partner's own site",@@ -27810,6 +27828,34 @@"fix"],"link": "/docs/home-scene"+ },+ {+ "date": "2026-09-09",+ "title": "Your own agent now stands in your live house",+ "summary": "The 3D home at /smart-home/<id> always drew a generic figure standing in your rooms, even when you had given your agent a face months ago. It now shows your agent: the same avatar the walk world, /play and the voice satellite use, read from the one record the whole platform treats as \"my agent\". Switch agents in another tab and the body in the house follows, with no reload. It is fetched after the house has already drawn, so nothing waits on it, and the platform's default body stands in when you have no agent yet, no avatar yet, or an avatar you keep private, which by design publishes no model for any page to read.",+ "tags": [+ "improvement"+ ],+ "link": "/docs/home-scene"+ },+ {+ "date": "2026-09-09",+ "title": "Smart Home: the connection pool now sizes itself to the server it is running on",+ "summary": "The number of houses one server holds open at once was set by hand, in a different place from the memory that has to hold them, and the two drifted apart three times. Left alone, that ends with a server running out of memory and taking the whole API down with it, which every part of three.ws would feel, not just Smart Home. The pool now reads the memory its own container actually has and refuses to hold more houses than fit, saying so in the health endpoint when it does. When there is less room it connects fewer houses per server and keeps working, instead of risking an outage for everybody.",+ "tags": [+ "infra",+ "fix"+ ],+ "link": "/docs/smart-home"+ },+ {+ "date": "2026-09-09",+ "title": "Fact-check now reads the part of a source that is actually about your claim",+ "summary": "When the fact-checker fell back to Wikipedia, it only ever read each article's opening summary. An opening summary says what a page is about, so it carries the answer only when your claim is about the page's subject. Ask whether Napoleon was unusually short and it read the first lines of \"Napoleon\", \"Napoleon III\" and \"Napoleonic Wars\", none of which mention height at all, so every source was scored as saying nothing and the verdict came back \"not enough evidence\" while the passage about his height sat further down the same article. The checker now reads each article in full and picks the paragraphs that actually discuss your claim, so that question returns the \"Appearance and image\" and \"Napoleon's height\" sections instead. Reference lists are skipped, since they repeat your words without asserting anything, and the deeper read is bounded by the time the check already had, so a slow source can never cost you the evidence that already arrived.",+ "tags": [+ "improvement"+ ],+ "link": "/docs/fact-check"}]}diff --git a/docs/ops/payment-outcomes.md b/docs/ops/payment-outcomes.mdindex 956a758b8..ff0d14065 100644--- a/docs/ops/payment-outcomes.md+++ b/docs/ops/payment-outcomes.md@@ -91,10 +91,15 @@ rate so a wallet sliding toward its budget shows up before the rate does.A rent-exemption failure on the fee payer (`InsufficientFundsForRent` onaccount index 0, in either spelling the RPCs use) wears a rail-shaped reason-token (`simulation_failed`, `sweep_broadcast_failed`) while being the opposite-of a rail fault: the transaction never reached the rail because the sponsor-could not pay for it. The sensor flags those rows from the full `error_msg`-and counts them as floor signals, not faults, so a dry sponsor reads as+token (`sweep_broadcast_failed`, and `simulation_failed` on any path that has+not yet been split) while being the opposite of a rail fault: the transaction+never reached the rail because the sponsor could not pay for it. The verify+path stopped relying on that reconstruction on 2026-09-09 and now raises the+verdict as its own class, `sponsor_fee_unfunded` when the dry fee payer is our+sponsor and `payer_fee_unfunded` when it is the buyer's own wallet, so the+token alone carries the meaning. The sensor flags the remaining rail-shaped+rows from the full `error_msg` and counts both kinds as floor signals, not+faults, so a dry sponsor reads as`cause: sponsor_floor` rather than pointing the operator at duplicatesignatures and RPC preflight (which is what happened for three hours on2026-08-28). Because a sponsor under its floor is a hard stop, those attemptsdiff --git a/docs/ops/production-log-triage.md b/docs/ops/production-log-triage.mdindex 681d4d1a5..36ba5ff1e 100644--- a/docs/ops/production-log-triage.md+++ b/docs/ops/production-log-triage.md@@ -300,11 +300,29 @@ HTTP 502/503 GET|POST /api/x402/*, /api/mcp ua: threews-x402-autonomous/1.0 orthe rail. The sponsor held 0.000899107 SOL against the 0.02 SOL floor, whichis 0.0000082 SOL of spendable headroom, less than two transaction fees, soevery transaction it fee-paid failed at simulation:- `simulation_failed:{"InsufficientFundsForRent":{"account_index":0}}` on the- verify path and `sweep_broadcast_failed:Simulation failed ... account (0) with- insufficient funds for rent` on the sweep path. **Account index 0 of a- compiled Solana message is the fee payer**, so that error is never about the- buyer's USDC: it is the sponsor being too poor to sign.+ `sponsor_fee_unfunded:<sponsor pubkey>` on the verify path (spelled+ `simulation_failed:{"InsufficientFundsForRent":{"account_index":0}}` before+ 2026-09-09, see below) and `sweep_broadcast_failed:Simulation failed ...+ account (0) with insufficient funds for rent` on the sweep path. **Account+ index 0 of a compiled Solana message is the fee payer**, so that error is+ never about the buyer's USDC: it is the sponsor being too poor to sign.++ Since 2026-09-09 the verify path gives that verdict its own reason class, so+ you can read it straight off `/api/healthz`+ (`x402.self_facilitator.verify.reject_reasons`, which groups on the token+ before the first `:`):++ | Class | Who is out of SOL | What to do |+ |---|---|---|+ | `sponsor_fee_unfunded` | our sponsor (`X402_FEE_PAYER_SOLANA`) | fund it; this is the platform's problem |+ | `payer_fee_unfunded` | the buyer's own wallet in a self-pay settle | nothing; not ours to fund |+ | `simulation_failed` | neither: some other revert | read the suffix, it carries the raw error |++ Under the old single `simulation_failed` spelling those three shared one+ bucket, and because `isRailFault()` matches `/simulation/` the platform's own+ dry sponsor was also counted as a payment-rail fault. Measured on 2026-09-09,+ that bucket sat at the top of the verify book with 1,438 rejects in 24 hours+ and every row was the sponsor.Why the quiet variant's guard did not catch it: `sponsorKnownBelowFloor()` wasonly ever written by `getBalance`, and all four paid Solana RPC lanes were overdiff --git a/prompts/finish/_context/backlog-PROGRESS.md b/prompts/finish/_context/backlog-PROGRESS.mdindex e0d1b84a8..f5cdd5abe 100644--- a/prompts/finish/_context/backlog-PROGRESS.md+++ b/prompts/finish/_context/backlog-PROGRESS.md@@ -1864,6 +1864,97 @@ long-term. Recorded in[docs/ops/x402-discovery-listings.md](../../docs/ops/x402-discovery-listings.md)under the owner-gated step.+## 2026-09-09 (later): 01 x402 settle runway, the largest reject class was misfiled++Re-measured live, nothing carried forward. Production `880bdcef8`, revision+`three-ws-api-00420-ljh`. The capital decision from the entry below is unchanged+and still the owner's; `gcloud` auth is dead in this codespace this session+(`Reauthentication failed`), so even the config lever could not be applied here.++| Fact | Value | Source |+|---|---|---|+| `x402_settle` | **down**, 0.0% (0/125 paid attempts, 3h), `cause: sponsor_floor` | `/api/healthz` |+| Sponsor / economy master `Wwwu…T3WwW` | 1,167,627 lamports, spendable 0, floor 2,000,000 | on chain + `/api/x402/runway-lab` |+| Shortfall to the floor | **832,373 lamports (0.000832 SOL)** | same |+| Treasury `wwwww…ccrU` | 54,994,966 lamports (0.055 SOL) + 0.06 USDC, fenced behind `minSol` 0.1 | on chain |+| Ring payer `X4o2…stML` | 812,444 lamports + 4.163 USDC | on chain |+| Settle rejects, 24h | `fee_wallet_below_floor` 227 of 227, `fee_runway_exhausted` absent | `/api/healthz` |+| Verify rejects, 24h | `simulation_failed` **1,438 of 1,438** | same |++### The finding: 1,438 of 1,438 verify rejects were our own sponsor, filed as a rail fault++The verify book's single largest class was read straight out of the production+table rather than off the healthz prefix, which is what made it visible:++```+1438 | verify | simulation_failed:{"InsufficientFundsForRent":{"account_index":0}}+```++Every row, identical. Account index 0 of a compiled Solana message is the fee+payer by definition, so not one of those 1,438 was about a buyer: they are all+the sponsor being too poor to sign. Two things went wrong with that spelling:++1. `/api/healthz` exposes only the token before the first `:` (deliberately, the+ suffix can carry wallet addresses), so the platform's own dry sponsor shared+ one bucket with a buyer signing from an empty ATA. An operator reading the+ book sees `simulation_failed 1438` at the top and has no way to tell which.+2. `isRailFault()` in `api/_lib/ops/x402-settle-health.js` matches `/simulation/`.+ So the class was also counted as a payment-RAIL fault, which is the one thing+ this order's own "Do not do these" warns against attributing it to. The 2026-08-28+ post-mortem in that module already names this trap and mitigates it with a+ separate `rent` flag reconstructed from the full `error_msg`; the reason token+ itself was never fixed.++This is the same defect shape as the `at_or_below_floor` ambiguity fixed earlier+today: one string covering two opposite operator situations.++### Landed (no funds moved, no config changed, deployable)++- `assertSettleable()` in `api/_lib/x402/self-facilitator.js` now raises the+ fee-payer verdict as its own reason class, using the exact `isFeePayerRentFailure()`+ test that was already computed on that line and thrown away:+ `sponsor_fee_unfunded:<pubkey>` when the dry fee payer is ours+ (`X402_FEE_PAYER_SOLANA`), `payer_fee_unfunded:<pubkey>` when it is the buyer's+ own wallet in a self-pay settle, and `simulation_failed` for everything else.+ The split is exact rather than heuristic. The suffix keeps the pubkey as evidence.+- `SPONSOR_FLOOR` in `api/_lib/ops/x402-settle-health.js` gained+ `sponsor_fee_unfunded`, so the sensor classifies it from the token alone instead+ of depending on the reconstructed `rent` flag. `payer_fee_unfunded` deliberately+ stays out: that wallet is not ours to fund and must never trip the sponsor hint.+- Five tests: three in `tests/x402-self-facilitator-settleable.test.js` (sponsor,+ buyer, and a rent failure on a NON-fee-payer account which must stay+ `simulation_failed`), two in `tests/api/x402-settle-health.test.js` (the new+ class reads as `sponsor_floor` with zero faults and no `rent` flag; the buyer+ twin raises no floor signal and no funding hint). 113 green across the 5 suites+ that touch these modules.+- `docs/ops/production-log-triage.md` gained a three-row table mapping each class+ to who is out of SOL and what to do; `docs/ops/payment-outcomes.md` corrected.+ `npm run audit:docs` clean (1,590 files). `data/changelog.json` entry added+ (`fix`, `infra`), `npm run build:pages` regenerated the feed.+- `npm run check:rules --paths <the 7 touched files>`: clean.++Nothing here changes what settles. It changes what the dashboard says while the+rail is down, which is what the next reader of this order will act on.++### Still open, still one owner decision++Unchanged from the entry below, restated with today's numbers. The sponsor is+**0.000832 SOL** under its floor and the treasury holds **66 times that**, fenced.+Both options move SOL, so both are stop-and-ask gate 1:++1. Lower `pump-x402-launcher`'s `minSol` from 0.1 to ~0.02 in+ `api/_lib/solana-signers.js`, then run `POST /api/cron/treasury-topup` without+ `?dry=1`. Path `wwwww…ccrU` to `Wwwu…T3WwW` to `X4o2…stML`. No owner capital.+2. Send SOL to `WwwuGbqHrwF5RG89KhUbmRWEvjnRH9k5kVM5p7T3WwW` and nowhere else.+ 0.1 SOL restarts settlement, 2 SOL clears the fleet deficit with real runway.++Either also needs `gcloud` re-auth in this codespace and a deploy (gate 2) for the+reason-class work above to reach production.++DoD lines 1 and 3 stay open behind that decision. Line 2 passes+(`fee_runway_exhausted` absent from the book). Lines 4 to 6 done. The prompt file+stays on disk.+## 2026-09-09: 01 x402 settle runway (the deploy landed; the fleet is not empty, it is fenced)Everything below was read live today, not carried forward.@@ -2015,3 +2106,48 @@ Left: one owner action. Mint an "Admin Read & Write" R2 token for `chatty-storagput it in `.env.local` as `R2_ACCESS_KEY_ID`/`R2_SECRET_ACCESS_KEY`, run`node scripts/set-r2-cors.mjs`, confirm with `--probe`. The work order stays on diskbecause its "policy applied" line is that action.++## 2026-09-09 (15:00 UTC): 09 telegram-bots-durability (re-verified after the fix, one gate left)++Measured, independently of the earlier pass in this file and without `gcloud`,+which is unusable in this codespace: every call answers `Reauthentication failed.+cannot prompt during non-interactive execution`, and the org reauth policy cannot+be satisfied non-interactively. So the work order's own `/stats` recipe could not+run, and the feeds were confirmed from the public Telegram surface instead, which+is the stronger signal anyway: a post proves the deployed service decoded a real+event and delivered it, not merely that a container is `Ready`.++- Firehose `@pumpfunclaimed` (`-1003905427189`): posting continuously, four posts+ in the four seconds around 14:50:58 UTC, latest content a+ `CLAIMS DIGEST last 1m 20 claims $57 total` with per-claim rows. That is the+ ~20 claims/min baseline this order set, hit on the nose, eight hours after the+ fix deployed.+- Tracker `@trackpumpfun` (`-1003965305979`): a supergroup, so `t.me/s/` returns+ 302 and the id-embed walk is the way in. 16 posts in 187 s (ids 67971 to+ 67987), latest content a decoded launch with market cap, dev launch count and+ chart links.+- Neither is a local process: no `node` under `pump-fun-sdk` in `/proc/*/cwd`,+ and `localhost:3900` and `3901` both refuse the connection. Cloud Run is the+ source.+- Both channels answer `getChat` on their numeric ids with distinct titles and+ usernames, so the separate-identity line still holds.++Re-checked in the sibling repo at `2a12ec3a` (HEAD, clean worktree): the endpoint+list, the 20-second traffic-based liveness check, the rotating reconnect in both+`claim-monitor.ts` and `channel-bot/src/event-monitor.ts`, the cleared heartbeat+timer, and `activeWs`/`wsEventsReceived` on `/stats` are all present. Test counts+match the claim exactly: 95 passing in allclaims (7 files), 205 in channel-bot+(14 files). Both `.env` files carry the publicnode plus mainnet-beta lists with no+magicblock. Both deploy scripts pin the build and runtime service accounts and use+`--env-vars-file`, never `--set-env-vars`. `DECODERS.md` records the canonical+copy and now the matching transport rule.++Did: added the `gcloud`-free verification recipe to the work order's Verify+section, since the documented one is unusable on a recycled codespace and its+absence is what would stall the next person, plus the re-proof line on the first+definition-of-done box.++Left: one owner action, the last box on that order. Approve committing the+launchpad-referencing update into three.ws under the coin gate. Nothing technical+remains; the code and the deploys landed in the sibling repo, which the gate+exempts.diff --git a/public/changelog-recent.json b/public/changelog-recent.jsonindex 57cd1647b..076268600 100644--- a/public/changelog-recent.json+++ b/public/changelog-recent.json@@ -1,11 +1,11 @@{- "generated_at": "2026-09-09T07:20:21.694Z",+ "generated_at": "2026-09-09T15:09:28.073Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws","url": "https://three.ws"},- "total": 3634,+ "total": 3640,"complete": false,"full_feed": "/changelog.json","entries": [@@ -19,6 +19,16 @@"launch"]},+ {+ "date": "2026-09-09",+ "type": "launch",+ "title": "Docs · Rivalries",+ "summary": "What changed on the trader board: who passed whom, who just arrived, and who is closing. Derived from close timestamps rather than a snapshot table, so the matchups work retroactively and cannot disagree with the leaderboard.",+ "link": "/docs/rivalries",+ "tags": [+ "launch"+ ]+ },{"date": "2026-09-09","type": "launch",@@ -104,6 +114,16 @@"improvement"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "Fact-check now reads the part of a source that is actually about your claim",+ "summary": "When the fact-checker fell back to Wikipedia, it only ever read each article's opening summary. An opening summary says what a page is about, so it carries the answer only when your claim is about the page's subject. Ask whether Napoleon was unusually short and it read the first lines of \"Napoleon\", \"Napoleon III\" and \"Napoleonic Wars\", none of which mention height at all, so every source was scored as saying nothing and the verdict came back \"not enough evidence\" while the passage about his height sat further down the same article. The checker now reads each article in full and picks the paragraphs that actually discuss your claim, so that question returns the \"Appearance and image\" and \"Napoleon's height\" sections instead. Reference lists are skipped, since they repeat your words without asserting anything, and the deeper read is bounded by the time the check already had, so a slow source can never cost you the evidence that already arrived.",+ "link": "/docs/fact-check",+ "tags": [+ "improvement"+ ]+ },{"date": "2026-09-09","type": "update",@@ -269,6 +289,17 @@"improvement"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "Smart Home: the connection pool now sizes itself to the server it is running on",+ "summary": "The number of houses one server holds open at once was set by hand, in a different place from the memory that has to hold them, and the two drifted apart three times. Left alone, that ends with a server running out of memory and taking the whole API down with it, which every part of three.ws would feel, not just Smart Home. The pool now reads the memory its own container actually has and refuses to hold more houses than fit, saying so in the health endpoint when it does. When there is less room it connects fewer houses per server and keeps working, instead of risking an outage for everybody.",+ "link": "/docs/smart-home",+ "tags": [+ "infra",+ "fix"+ ]+ },{"date": "2026-09-09","type": "update",@@ -453,6 +484,17 @@"fix"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "The payments dashboard now says whose wallet ran out of SOL",+ "summary": "When a Solana payment cannot go through because the wallet paying the network fee is too low, the chain reports it as a generic simulation failure. Our status page grouped all of those together, so the platform's own fee wallet running low looked exactly like a buyer signing from an empty wallet, and both were also counted as payment-network faults. They are now three separate, named outcomes, so the status page says whether the money problem is ours to fix, the buyer's, or neither. Today's reject book was 1,438 rows of the first kind reading as the third.",+ "link": null,+ "tags": [+ "fix",+ "infra"+ ]+ },{"date": "2026-09-09","type": "update",@@ -574,6 +616,16 @@"improvement"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "The trading arena now says who just passed whom",+ "summary": "The live leaderboard on the arena told you who was ahead and nothing about what had changed, so a place changing hands, which happens several times a week on its own, went unnoticed. A grudge-match strip now sits under the standings: each trader is paired with the one directly above them, labelled as an overtake, a debut or a standing chase, with the profit or loss both sides settled in the last 24 hours as the reason. It is worked out from the same closed on-chain trades the board is ranked from, by rebuilding what the board actually said 24 hours ago out of the trade timestamps rather than trusting a stored snapshot, so the matchups reach back over history the platform already has and can never disagree with the leaderboard or with either trader's profile. Every line is written from those numbers: it will not call a trader behind when they in fact hold more SOL and rank lower on consistency, and it will not say someone booked nothing when they simply did not trade. Each matchup links to the leader's verified record and to a ghost-copy of them with no money at risk. Also available to agents and scripts at /api/sniper/rivalries.",+ "link": "/play/arena",+ "tags": [+ "feature"+ ]+ },{"date": "2026-09-09","type": "update",@@ -618,6 +670,16 @@"improvement"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "Your own agent now stands in your live house",+ "summary": "The 3D home at /smart-home/<id> always drew a generic figure standing in your rooms, even when you had given your agent a face months ago. It now shows your agent: the same avatar the walk world, /play and the voice satellite use, read from the one record the whole platform treats as \"my agent\". Switch agents in another tab and the body in the house follows, with no reload. It is fetched after the house has already drawn, so nothing waits on it, and the platform's default body stands in when you have no agent yet, no avatar yet, or an avatar you keep private, which by design publishes no model for any page to read.",+ "link": "/docs/home-scene",+ "tags": [+ "improvement"+ ]+ },{"date": "2026-09-09","type": "update",@@ -1550,72 +1612,6 @@"fix","docs"]- },- {- "date": "2026-09-04",- "type": "update",- "title": "Daily Match reads on a phone, and its live ticker finally matches its board",- "summary": "The Daily Match board tracks which agent ships the most real output each UTC day. Two things were wrong with it. On a narrow screen the eight-column standings table was being silently clipped instead of scrolled, so P&L and Score, the two columns the whole page is about, simply could not be reached on a phone; the table now scrolls inside its own region, with edge shadows that show up only while there is more to reach and keyboard focus so you can scroll it without a mouse. And the Live output ticker only ever read one of the four activity sources the board scores, so an agent that shipped a launch, a trade or a paid skill sale could rank first on a board sitting next to a panel claiming the day was quiet; the ticker now reads all four and labels each entry with what it was. The board also got wider on desktop so every column fits without scrolling, a designed loading and failure state for the ticker, and a refresh that no longer wipes good standings off the screen when a single poll fails: it says live updates are paused and puts them back when the next one lands.",- "link": "/daily-match",- "tags": [- "fix",- "improvement"- ]- },- {- "date": "2026-09-04",- "type": "update",- "title": "DeFi tables stop showing broken logos when a coin icon disappears",- "summary": "The protocol and chain logos on the fees, DeFi, DEX volumes, chain, protocol and exchange pages were loaded straight from a third-party icon host. When that host renamed or removed an icon, the row rendered a broken-image glyph and every reader's browser recorded a failed request. Those logos now come from three.ws itself: we fetch and resize them on our side, cache them, and hand back an empty answer for an icon that no longer exists, so the row shows the same neutral disc a protocol without a logo already gets. Pages load a little faster too, since a 24-pixel icon no longer arrives at full size, and your browser no longer talks to an outside host on every table paint.",- "link": "/fees",- "tags": [- "fix",- "improvement"- ]- },- {- "date": "2026-09-04",- "type": "update",- "title": "Every 3D viewer on the site now runs the same build",- "summary": "The 3D preview you see on three.ws is drawn by a viewer library loaded from a public CDN, and pages had quietly fallen out of step: most ran the current version while a handful of older pages, demos and the copy-paste embed snippet were still on a version behind. That split is worse than it sounds. Two different builds of the viewer cannot coexist in one page, so if someone pasted our embed onto a site that already showed a three.ws model, the second one would refuse to start and show nothing. Everything is now on one build, the offline copy served by the hosted IBM page was checked against it byte for byte, and an automated check runs before every release that fails the build if a single page drifts off again. Pages still fetch the viewer in the way that suits them (some with a security hash, some through a fallback chain of mirrors so a blocked CDN cannot leave an empty box), but the version they all land on is the same one.",- "link": null,- "tags": [- "fix",- "improvement"- ]- },- {- "date": "2026-09-04",- "type": "update",- "title": "Generated models are checked for the invisible surface detail that makes them look real",- "summary": "A 3D model can have perfect shape and still look like plastic, because the colour picture painted onto it is only half of what makes a surface look real. The other half is invisible detail: which parts are bumpy, which are shiny, which sit in shadow. Without it, leather, wool and glass all catch the light in exactly the same flat way, and an object can read as though it were cast in dull metal rather than made of what you asked for. There was no way to check which of those layers a model actually carried, so we built one and pointed it at real generations from the live engines, then wrote down what each engine does and does not produce. That measurement is now published alongside the texturing service instead of being guessed at, and the checker refuses to pass a model missing a layer it should have, so the gap cannot quietly reopen.",- "link": null,- "tags": [- "docs",- "improvement"- ]- },- {- "date": "2026-09-04",- "type": "update",- "title": "Generation jobs can now push their result to your server, and the health page finally watches the editing tools",- "summary": "Two additions for anyone who builds on the forge. First, webhooks for generation jobs: subscribe to forge.completed and forge.failed and three.ws POSTs you the finished model instead of making you poll for it. A generation outlives the request that started it, so until now an integration had to keep asking. The completion event rides the single writer every lane finishes through, so it arrives exactly once whether the job ran on the free lane, a paid call, or the background finalizer that picks up abandoned work; the failure event deliberately stays quiet while a job is being retried on another engine, so it only ever means the job is really over. Payloads and a runnable example are in the developer platform docs. Second, the forge health report now live-probes the editing tools as well as the generation engines: remesh, stylize, segment, background removal, text to motion, auto-rig and retexture each get checked for real. Those tools have buttons in the result panel, so a user can hit them, but none of them were being watched; retexture had in fact been offline the whole time and nothing said so.",- "link": "/changelog",- "tags": [- "feature",- "sdk",- "improvement"- ]- },- {- "date": "2026-09-04",- "type": "update",- "title": "Knock on a stranger and get your money back if they never answer",- "summary": "A door that takes escrowed knocks now shows the option on its own page, next to paying up front. Choose it and your payment goes into an on-chain vault instead of the recipient's wallet: they are paid by answering you, and if they decline or the window runs out, every unit comes back to you. Before anything is signed, a dialog states the amount, who it reaches, and the exact deadline. Afterwards the page counts down to that deadline, and the moment it passes, a button hands your payment back. three.ws holds no key that can move it either way.",- "link": null,- "tags": [- "feature"- ]}]}diff --git a/public/changelog.json b/public/changelog.jsonindex 6463e5d73..d8bb0f7c3 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-09T07:20:21.658Z",+ "generated_at": "2026-09-09T15:09:28.022Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws",@@ -16,6 +16,16 @@"launch"]},+ {+ "date": "2026-09-09",+ "type": "launch",+ "title": "Docs · Rivalries",+ "summary": "What changed on the trader board: who passed whom, who just arrived, and who is closing. Derived from close timestamps rather than a snapshot table, so the matchups work retroactively and cannot disagree with the leaderboard.",+ "link": "/docs/rivalries",+ "tags": [+ "launch"+ ]+ },{"date": "2026-09-09","type": "launch",@@ -101,6 +111,16 @@"improvement"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "Fact-check now reads the part of a source that is actually about your claim",+ "summary": "When the fact-checker fell back to Wikipedia, it only ever read each article's opening summary. An opening summary says what a page is about, so it carries the answer only when your claim is about the page's subject. Ask whether Napoleon was unusually short and it read the first lines of \"Napoleon\", \"Napoleon III\" and \"Napoleonic Wars\", none of which mention height at all, so every source was scored as saying nothing and the verdict came back \"not enough evidence\" while the passage about his height sat further down the same article. The checker now reads each article in full and picks the paragraphs that actually discuss your claim, so that question returns the \"Appearance and image\" and \"Napoleon's height\" sections instead. Reference lists are skipped, since they repeat your words without asserting anything, and the deeper read is bounded by the time the check already had, so a slow source can never cost you the evidence that already arrived.",+ "link": "/docs/fact-check",+ "tags": [+ "improvement"+ ]+ },{"date": "2026-09-09","type": "update",@@ -266,6 +286,17 @@"improvement"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "Smart Home: the connection pool now sizes itself to the server it is running on",+ "summary": "The number of houses one server holds open at once was set by hand, in a different place from the memory that has to hold them, and the two drifted apart three times. Left alone, that ends with a server running out of memory and taking the whole API down with it, which every part of three.ws would feel, not just Smart Home. The pool now reads the memory its own container actually has and refuses to hold more houses than fit, saying so in the health endpoint when it does. When there is less room it connects fewer houses per server and keeps working, instead of risking an outage for everybody.",+ "link": "/docs/smart-home",+ "tags": [+ "infra",+ "fix"+ ]+ },{"date": "2026-09-09","type": "update",@@ -450,6 +481,17 @@"fix"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "The payments dashboard now says whose wallet ran out of SOL",+ "summary": "When a Solana payment cannot go through because the wallet paying the network fee is too low, the chain reports it as a generic simulation failure. Our status page grouped all of those together, so the platform's own fee wallet running low looked exactly like a buyer signing from an empty wallet, and both were also counted as payment-network faults. They are now three separate, named outcomes, so the status page says whether the money problem is ours to fix, the buyer's, or neither. Today's reject book was 1,438 rows of the first kind reading as the third.",+ "link": null,+ "tags": [+ "fix",+ "infra"+ ]+ },{"date": "2026-09-09","type": "update",@@ -571,6 +613,16 @@"improvement"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "The trading arena now says who just passed whom",+ "summary": "The live leaderboard on the arena told you who was ahead and nothing about what had changed, so a place changing hands, which happens several times a week on its own, went unnoticed. A grudge-match strip now sits under the standings: each trader is paired with the one directly above them, labelled as an overtake, a debut or a standing chase, with the profit or loss both sides settled in the last 24 hours as the reason. It is worked out from the same closed on-chain trades the board is ranked from, by rebuilding what the board actually said 24 hours ago out of the trade timestamps rather than trusting a stored snapshot, so the matchups reach back over history the platform already has and can never disagree with the leaderboard or with either trader's profile. Every line is written from those numbers: it will not call a trader behind when they in fact hold more SOL and rank lower on consistency, and it will not say someone booked nothing when they simply did not trade. Each matchup links to the leader's verified record and to a ghost-copy of them with no money at risk. Also available to agents and scripts at /api/sniper/rivalries.",+ "link": "/play/arena",+ "tags": [+ "feature"+ ]+ },{"date": "2026-09-09","type": "update",@@ -615,6 +667,16 @@"improvement"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "Your own agent now stands in your live house",+ "summary": "The 3D home at /smart-home/<id> always drew a generic figure standing in your rooms, even when you had given your agent a face months ago. It now shows your agent: the same avatar the walk world, /play and the voice satellite use, read from the one record the whole platform treats as \"my agent\". Switch agents in another tab and the body in the house follows, with no reload. It is fetched after the house has already drawn, so nothing waits on it, and the platform's default body stands in when you have no agent yet, no avatar yet, or an avatar you keep private, which by design publishes no model for any page to read.",+ "link": "/docs/home-scene",+ "tags": [+ "improvement"+ ]+ },{"date": "2026-09-09","type": "update",diff --git a/public/changelog.xml b/public/changelog.xmlindex 616cb834b..0fd1da07a 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -14,6 +14,14 @@<category>launch</category><description>How the Fade Radar scores a coin's buy side: what makes a wallet a reverse indicator, the 0 to 100 fade score, the verdict bands, and the out-of-sample measurement behind them.</description></item>+ <item>+ <title>Docs · Rivalries</title>+ <link>https://three.ws/docs/rivalries</link>+ <guid isPermaLink="false">2026-09-09:Docs · Rivalries</guid>+ <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>+ <category>launch</category>+ <description>What changed on the trader board: who passed whom, who just arrived, and who is closing. Derived from close timestamps rather than a snapshot table, so the matchups work retroactively and cannot disagree with the leaderboard.</description>+ </item><item><title>Fade Radar: the wallets that are never right</title><link>https://three.ws/fade</link>@@ -78,6 +86,14 @@<category>fix</category><description>A full audit of /portfolio, where you paste any Solana or Ethereum address and get a live portfolio. The Ethereum half had gone dark: the single provider behind it ran out of monthly capacity, so every 0x address answered "Data source unavailable" with nothing behind it. Ethereum now has the same keyless floor Solana has always had. The ETH balance comes from the public Ethereum nodes the rest of the platform already uses, the token list with its prices and icons comes from a public block explorer, and the 24h move comes from the same market source the Solana side uses, with the coverage it achieved stated on the card. The Data panel names whichever lane actually answered, so you can see whether you are reading the paid provider or the free one. Token logos were another visible break: the page pointed your browser straight at an IPFS gateway, which the browser refuses on cross-origin grounds, so every holding fell back to a three-letter monogram and your address bar handed your IP to the gateway on every load. Logos now come through three.ws, sized for the row. Keyboard users could tab onto a slice of the allocation donut and get nothing: the tooltip was wired to an event handler property that browsers do not actually support, so it never fired once; the slice now names its asset and share, and Escape dismisses it. When a lookup fails, the page now shows the reason the server actually sent instead of a generic sentence, and clicking Retry after a rejected address no longer silently reloads the wallet you looked at before it. Underneath, the fallback that names Solana tokens when the primary metadata source is out of quota had never run at all, because of a missing import; token symbols and names come back on that path.</description></item>+ <item>+ <title>Fact-check now reads the part of a source that is actually about your claim</title>+ <link>https://three.ws/docs/fact-check</link>+ <guid isPermaLink="false">2026-09-09:Fact-check now reads the part of a source that is actually about your claim</guid>+ <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>+ <category>improvement</category>+ <description>When the fact-checker fell back to Wikipedia, it only ever read each article's opening summary. An opening summary says what a page is about, so it carries the answer only when your claim is about the page's subject. Ask whether Napoleon was unusually short and it read the first lines of "Napoleon", "Napoleon III" and "Napoleonic Wars", none of which mention height at all, so every source was scored as saying nothing and the verdict came back "not enough evidence" while the passage about his height sat further down the same article. The checker now reads each article in full and picks the paragraphs that actually discuss your claim, so that question returns the "Appearance and image" and "Napoleon's height" sections instead. Reference lists are skipped, since they repeat your words without asserting anything, and the deeper read is bounded by the time the check already had, so a slow source can never cost you the evidence that already arrived.</description>+ </item><item><title>Fade Radar: the wallets that have never once been right, and the coins they are crowding into</title><link>https://three.ws/fade</link>@@ -198,6 +214,14 @@<category>fix</category><description>A full audit of /signals, the directory of paid trading feeds ranked by proven edge. Four real defects came out of it. Every publisher without a profile picture showed an empty grey square: the generated fallback avatar is an image, and the card was assigning it to a CSS background, which browsers ignore, so it never painted. A publisher whose profile picture had gone missing showed the browser's broken-image icon; both now render as an image that quietly falls back to the generated avatar. Prices were printed as raw numbers, so a feed charging 12.345678 USDC advertised exactly that; amounts are now grouped and rounded the way money reads, while a genuine sub-cent price keeps its digits instead of rounding to zero. Subscriber counts skipped the same shortening every other number on the card uses and printed as 1234567. Worst of all, opening any live feed's own page while signed out crashed the render and left a blank panel where the sign-in prompt belongs, which is exactly the reader that panel exists to convert. Each card's screen-reader description now carries every number a sighted reader sees (rank, edge, hit rate, average ROI, signal counts, subscribers and price) instead of just the headline score, and the loading skeleton's shimmer now sweeps across the card rather than starting halfway off it.</description></item>+ <item>+ <title>Smart Home: the connection pool now sizes itself to the server it is running on</title>+ <link>https://three.ws/docs/smart-home</link>+ <guid isPermaLink="false">2026-09-09:Smart Home: the connection pool now sizes itself to the server it is running on</guid>+ <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>+ <category>infra</category>+ <description>The number of houses one server holds open at once was set by hand, in a different place from the memory that has to hold them, and the two drifted apart three times. Left alone, that ends with a server running out of memory and taking the whole API down with it, which every part of three.ws would feel, not just Smart Home. The pool now reads the memory its own container actually has and refuses to hold more houses than fit, saying so in the health endpoint when it does. When there is less room it connects fewer houses per server and keeps working, instead of risking an outage for everybody.</description>+ </item><item><title>The "have you tried" card no longer hangs off the side of the screen on a phone</title><link>https://three.ws/screener</link>@@ -334,6 +358,14 @@<category>fix</category><description>The IBM partnership page is published once onto IBM's own domain and then keeps itself current by reading from three.ws, so everything it loads is a cross-origin read and anything we get wrong there is invisible on three.ws itself. Three things were wrong. The site-wide command palette asked the partner's server for our page index and for the ranking module it imports, so it never opened and logged an error on every visit: the index now travels with the code the way the language catalogs already do, and both files are readable from other sites. And a build step that adds the site's mobile stylesheet to every page was reaching the partner artifacts too, even though they are copied out untouched by design, so the hosted copy asked IBM's server for a stylesheet only we have. All three are closed, and the audit that loads the page from a foreign domain now passes all four of its checks: the live update applies, the language switcher mounts, the paid demo arms, and the console is clean.</description></item>+ <item>+ <title>The payments dashboard now says whose wallet ran out of SOL</title>+ <link>https://three.ws/changelog</link>+ <guid isPermaLink="false">2026-09-09:The payments dashboard now says whose wallet ran out of SOL</guid>+ <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>When a Solana payment cannot go through because the wallet paying the network fee is too low, the chain reports it as a generic simulation failure. Our status page grouped all of those together, so the platform's own fee wallet running low looked exactly like a buyer signing from an empty wallet, and both were also counted as payment-network faults. They are now three separate, named outcomes, so the status page says whether the money problem is ours to fix, the buyer's, or neither. Today's reject book was 1,438 rows of the first kind reading as the third.</description>+ </item><item><title>The pitch deck now shows the whole character, and says so when the 3D cannot load</title><link>https://three.ws/pitch</link>@@ -422,6 +454,14 @@<category>fix</category><description>Loading a scene on /splat used to erase the viewer's own controls: writing the scene label into the HUD replaced the recenter and download buttons with plain text, so from the first render onward neither existed. Both now live beside the label and survive every scene swap, and the download always offers the scene you are actually looking at rather than a previous one. The error state was worse than useless: it showed a heading over an empty space because the explanation was being written into an element that was not on the page. Now a failed load tells you what happened and what to do, including the advice to download and upload a file whose host blocks cross-origin requests. Clicking a sample or picking a file also shows the loading state immediately instead of sitting on an idle stage while the splat engine downloads in silence, and an engine that fails to load says so rather than leaving the page frozen.</description></item>+ <item>+ <title>The trading arena now says who just passed whom</title>+ <link>https://three.ws/play/arena</link>+ <guid isPermaLink="false">2026-09-09:The trading arena now says who just passed whom</guid>+ <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>+ <category>feature</category>+ <description>The live leaderboard on the arena told you who was ahead and nothing about what had changed, so a place changing hands, which happens several times a week on its own, went unnoticed. A grudge-match strip now sits under the standings: each trader is paired with the one directly above them, labelled as an overtake, a debut or a standing chase, with the profit or loss both sides settled in the last 24 hours as the reason. It is worked out from the same closed on-chain trades the board is ranked from, by rebuilding what the board actually said 24 hours ago out of the trade timestamps rather than trusting a stored snapshot, so the matchups reach back over history the platform already has and can never disagree with the leaderboard or with either trader's profile. Every line is written from those numbers: it will not call a trader behind when they in fact hold more SOL and rank lower on consistency, and it will not say someone booked nothing when they simply did not trade. Each matchup links to the leader's verified record and to a ghost-copy of them with no money at risk. Also available to agents and scripts at /api/sniper/rivalries.</description>+ </item><item><title>The Windows 11 widget draws its card again, and a new check keeps the board honest</title><link>https://three.ws/glance</link>@@ -454,6 +494,14 @@<category>feature</category><description>Talking to the agent about your house is the one part of the smart-home lane that can really cost money: the room graph makes a home prompt large, and on a paid model a single turn costs several weeks of holding that house’s connection open. Those turns were being counted but never actually limited. They are now, against the monthly allowance shown on your plan page, and if you run out the agent says so in a sentence that names the limit, the date it resets and where to raise it, instead of failing at you. Two things are deliberately left outside that limit. Asking the agent what the house is doing still works, because you have to be able to see which door is open. And telling it to lock a door, close a garage or a valve, or arm the alarm still runs, over quota, on a paused home, in every state we can put an account in: the safe direction is free, always, on every plan. If our own billing lookup fails, the turn is allowed through rather than refused.</description></item>+ <item>+ <title>Your own agent now stands in your live house</title>+ <link>https://three.ws/docs/home-scene</link>+ <guid isPermaLink="false">2026-09-09:Your own agent now stands in your live house</guid>+ <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>+ <category>improvement</category>+ <description>The 3D home at /smart-home/<id> always drew a generic figure standing in your rooms, even when you had given your agent a face months ago. It now shows your agent: the same avatar the walk world, /play and the voice satellite use, read from the one record the whole platform treats as "my agent". Switch agents in another tab and the body in the house follows, with no reload. It is fetched after the house has already drawn, so nothing waits on it, and the platform's default body stands in when you have no agent yet, no avatar yet, or an avatar you keep private, which by design publishes no model for any page to read.</description>+ </item><item><title>Your private avatars load on the dashboard again, and say so when they cannot</title><link>https://three.ws/dashboard/avatars</link>diff --git a/tests/api/x402-settle-health.test.js b/tests/api/x402-settle-health.test.jsindex 5ecee1209..a0815bda7 100644--- a/tests/api/x402-settle-health.test.js+++ b/tests/api/x402-settle-health.test.js@@ -439,6 +439,33 @@ describe('classifySettleBuckets: a dry sponsor is not a rail fault', () => {expect(v.status).toBe('unknown');});+ it('classifies sponsor_fee_unfunded as floor even with no rent flag set', () => {+ // The verify path now raises the fee-payer verdict as its own reason class+ // (api/_lib/x402/self-facilitator.js), so the token itself carries the+ // meaning and the sensor no longer depends on a `rent` flag reconstructed+ // from the full error_msg. That matters because the old spelling,+ // `simulation_failed`, matches RAIL_SIGNATURE's /simulation/: a caller that+ // aggregates by token alone counted a starved sponsor as a rail fault.+ const v = classifySettleBuckets([+ { success: false, paid: false, reason: 'sponsor_fee_unfunded', n: 95 },+ ]);+ expect(v.cause).toBe('sponsor_floor');+ expect(v.floorSignals).toBe(95);+ expect(v.faults).toBe(0);+ });++ it('leaves the buyer-side twin off the sponsor floor', () => {+ // `payer_fee_unfunded` is a buyer whose OWN wallet cannot pay the fee. It is+ // not the platform's to fund, so it must never trip the sponsor hint that+ // tells an operator to send SOL.+ const v = classifySettleBuckets([+ { success: false, paid: false, reason: 'payer_fee_unfunded', n: 95 },+ ]);+ expect(v.floorSignals ?? 0).toBe(0);+ expect(v.cause).not.toBe('sponsor_floor');+ expect(v.hint ?? '').not.toMatch(/treasury-topup/);+ });+it('a bucket with no rent flag behaves exactly as it always did', () => {const withFlag = classifySettleBuckets([{ success: true, paid: true, n: 90 },diff --git a/tests/x402-self-facilitator-settleable.test.js b/tests/x402-self-facilitator-settleable.test.jsindex 4acfb8118..56eca3244 100644--- a/tests/x402-self-facilitator-settleable.test.js+++ b/tests/x402-self-facilitator-settleable.test.js@@ -56,6 +56,7 @@ function buildSelfPayPayment({ amount = AMOUNT_ATOMIC } = {}) {return {payTo: recipientOwner.publicKey.toBase58(),+ feePayer: buyer.publicKey.toBase58(),requirement: {network: 'solana',asset: mint.toBase58(),@@ -69,10 +70,12 @@ function buildSelfPayPayment({ amount = AMOUNT_ATOMIC } = {}) {let prevPayTo;let prevAssetMint;let prevThreeMint;+let prevFeePayer;beforeEach(() => {prevPayTo = process.env.X402_PAY_TO_SOLANA;prevAssetMint = process.env.X402_ASSET_MINT_SOLANA;prevThreeMint = process.env.THREE_TOKEN_MINT;+ prevFeePayer = process.env.X402_FEE_PAYER_SOLANA;});afterEach(() => {if (prevPayTo === undefined) delete process.env.X402_PAY_TO_SOLANA;@@ -81,6 +84,8 @@ afterEach(() => {else process.env.X402_ASSET_MINT_SOLANA = prevAssetMint;if (prevThreeMint === undefined) delete process.env.THREE_TOKEN_MINT;else process.env.THREE_TOKEN_MINT = prevThreeMint;+ if (prevFeePayer === undefined) delete process.env.X402_FEE_PAYER_SOLANA;+ else process.env.X402_FEE_PAYER_SOLANA = prevFeePayer;});describe('verifyRingPayment settleability gate', () => {@@ -226,3 +231,76 @@ describe('mint pin (2026-07-23 audit: junk-mint sponsor drain)', () => {expect(out.reason).toMatch(/^mint_not_settleable:/);});});++// An unfundable FEE PAYER gets its own reason class, separate from every other+// simulation revert.+//+// Every consumer of `invalidReason` groups on the token before the first ':'.+// /api/healthz exposes only that prefix, and isRailFault() in+// api/_lib/ops/x402-settle-health.js matches /simulation/, so while this verdict+// was spelled `simulation_failed` a starved platform sponsor was (a) bucketed+// with buyers signing from empty ATAs and (b) counted as a payment-RAIL fault.+// Production on 2026-09-09: 1,438 verify rejects in 24h, top of the book, every+// one of them {"InsufficientFundsForRent":{"account_index":0}} on our own+// sponsor. Account index 0 is the fee payer by definition, so the split is exact.+describe('fee-payer rent failures are their own reason class', () => {+ const RENT_ERR = { InsufficientFundsForRent: { account_index: 0 } };++ it('names the platform sponsor when the dry fee payer is ours', async () => {+ const p = buildSelfPayPayment();+ process.env.X402_PAY_TO_SOLANA = p.payTo;+ process.env.X402_FEE_PAYER_SOLANA = p.feePayer;+ const conn = {+ simulateTransaction: async () => ({ value: { err: RENT_ERR } }),+ getTokenAccountBalance: async () => { throw new Error('should not be called'); },+ };+ const res = await verifyRingPayment({+ paymentPayload: p.paymentPayload,+ requirement: p.requirement,+ conn,+ });+ expect(res.isValid).toBe(false);+ expect(res.invalidReason.split(':')[0]).toBe('sponsor_fee_unfunded');+ // The suffix keeps the evidence: which wallet the chain refused.+ expect(res.invalidReason).toContain(p.feePayer);+ });++ it('names the buyer when the dry fee payer is not ours', async () => {+ const p = buildSelfPayPayment();+ process.env.X402_PAY_TO_SOLANA = p.payTo;+ process.env.X402_FEE_PAYER_SOLANA = Keypair.generate().publicKey.toBase58();+ const conn = {+ simulateTransaction: async () => ({ value: { err: RENT_ERR } }),+ getTokenAccountBalance: async () => { throw new Error('should not be called'); },+ };+ const res = await verifyRingPayment({+ paymentPayload: p.paymentPayload,+ requirement: p.requirement,+ conn,+ });+ expect(res.isValid).toBe(false);+ // A broke buyer must never wear the platform's class: nothing to fund.+ expect(res.invalidReason.split(':')[0]).toBe('payer_fee_unfunded');+ });++ it('leaves every other simulation revert as simulation_failed', async () => {+ const p = buildSelfPayPayment();+ process.env.X402_PAY_TO_SOLANA = p.payTo;+ process.env.X402_FEE_PAYER_SOLANA = p.feePayer;+ const conn = {+ // A rent failure on a NON-fee-payer account is a different condition and+ // must not be reclassified: only index 0 is the fee payer.+ simulateTransaction: async () => ({+ value: { err: { InsufficientFundsForRent: { account_index: 3 } } },+ }),+ getTokenAccountBalance: async () => { throw new Error('should not be called'); },+ };+ const res = await verifyRingPayment({+ paymentPayload: p.paymentPayload,+ requirement: p.requirement,+ conn,+ });+ expect(res.isValid).toBe(false);+ expect(res.invalidReason.split(':')[0]).toBe('simulation_failed');+ });+});