Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
docs(three-thesis): stop claiming the $THREE pages show a real buyback ledger
nirholas4855b091eacb
diff --git a/docs/three-thesis.md b/docs/three-thesis.mdindex abfaa50bb..8f7eb37fe 100644--- a/docs/three-thesis.md+++ b/docs/three-thesis.md@@ -464,7 +464,7 @@ A thesis that hides the risks is a pitch. These are the risks the three.ws docum1. **Most holder perks are Planned, not Live.** Only two of seven registered gated features (`forge.high`, `forge.gameready`) are enforced today. The compute discount and quota multiplier are live. The `enforced` flag exists precisely so the platform never promises an unwired perk, but a holder buying for `worlds.private` or `names.first_dibs` is buying a roadmap.-2. **The burn policy was internally inconsistent, and is now reconciled.** `api/_lib/token/config.js` states "NO PLATFORM BURNS, supply is never destroyed," while until 2026-09-16 `api/three-token/[action].js` shipped an `AGENT_DEPLOY_BURN = 1000` constant, and `/api/three-token/burns`, `/three-live`, and `/dashboard/three-token` reported a "burned" total computed as agent count times 1,000 with no on-chain burn behind it. That derived figure is gone: the burns endpoint now answers `policy: "no_platform_burns"` with an empty ledger, and both surfaces show the real buyback ledger instead. Blog posts from May and June 2026 still describe a "planned buyback-and-burn"; the code policy (buyback, no platform burn) is authoritative.+2. **The burn policy was internally inconsistent, and is now reconciled.** `api/_lib/token/config.js` states "NO PLATFORM BURNS, supply is never destroyed," while until 2026-09-16 `api/three-token/[action].js` shipped an `AGENT_DEPLOY_BURN = 1000` constant, and `/api/three-token/burns`, `/three-live`, and `/dashboard/three-token` reported a "burned" total computed as agent count times 1,000 with no on-chain burn behind it. That derived figure is gone: the burns endpoint now answers `policy: "no_platform_burns"` with an empty ledger. Blog posts from May and June 2026 still describe a "planned buyback-and-burn"; the code policy (buyback, no platform burn) is authoritative.3. **Older blog claims predate current mechanics.** The May 2026 listing and CoinMarketCap posts describe buyback-and-burn and the Rider VR gate as the token's utility; the current code implements buyback-without-burn plus the tier ladder. The direction of travel is toward more utility, but the public record has drift.