Skip to content

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

docs: record the perks/planned split and the second accepted media source

ni3aa06db2ba428d
diff --git a/docs/announcement-factory.md b/docs/announcement-factory.md
index 519c0ac81..ee625f4b7 100644
--- a/docs/announcement-factory.md
+++ b/docs/announcement-factory.md
@@ -137,6 +137,11 @@ A recipe can ask for a five second loop, but the capture has the last word: it t
second apart, and when they are identical it writes the still and records `animated: false` in the
manifest. Nothing upstream can make that call, because the description of a page about motion
generation reads exactly like the description of a page that moves.
+A hand-authored pack can ship a committed card instead of a captured shot, declared on its queue
+item as `posts[].media[]` with its own alt text. `npm run check:announce` accepts either source and
+still fails a pack whose image carries no alt text, because that is the artifact the publisher
+actually sends.
+
A surface with no route (115 of the 316 planned announcements are a package, a worker, or a
service) gets a title card instead: [`api/_lib/announce/card.js`](../api/_lib/announce/card.js)
typesets its real name, its real description, the command a developer really runs, and the tools it
diff --git a/docs/announcements/README.md b/docs/announcements/README.md
index c6c20fd20..e96dddc24 100644
--- a/docs/announcements/README.md
+++ b/docs/announcements/README.md
@@ -42,7 +42,9 @@ output of any of them.
`npm run announce:media`. It drives the real route in a real Chromium and writes to
`public/announce/img/` with provenance (route, commit, time, sha256) beside the pixels. Shots
marked `auth` sign in with the QA account so the frame shows the working product rather than
- its sign-in gate.
+ its sign-in gate. A pack written by hand may instead ship a committed card, declared on its
+ queue item as `posts[].media[]` with alt text; the gate accepts either, and neither may go out
+ without alt text.
3. **Write.** One `<slug>.md` pack and one `<slug>.post.txt` holding the post itself. The `.txt`
exists so the bytes the gate checks are the bytes `post-tweet.mjs` sends; a post quoted only
in prose drifts from the file that ships.
diff --git a/docs/three-thesis.md b/docs/three-thesis.md
index 8f7eb37fe..446904139 100644
--- a/docs/three-thesis.md
+++ b/docs/three-thesis.md
@@ -462,7 +462,7 @@ Phase targets stated in the README: 10k avatars per day at launch; 1,000 test us
A thesis that hides the risks is a pitch. These are the risks the three.ws documentation states about itself, plus the structural ones any holder should weigh.
-1. **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.
+1. **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. Until 2026-09-20 the flag only governed the feature rows: the prose perk lines on the same tier cards still listed "Private worlds", "Priority MCP routing" and "Branded worlds" flatly, and `GET /api/pricing` served them the same way. `TIERS` now separates `perks` (delivered today) from `planned`, every surface renders the planned lines with the Planned flag, and `tests/three-tier-honesty.test.js` fails if an unenforced feature's label reappears in a `perks` list.
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.