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.
Announcement packs
One file per feature we are announcing, plus the exact bytes that get posted.
three.ws has shipped 430 surfaces and posted about roughly 50. The other 320 are not a roadmap, they are inventory that already works, and the audit that established this lives in announcement-coverage.md. Working that backlog down is what this directory is for.
Which pack to make next is not decided in this directory. Use the
marketing command center for the scheduled campaign, owner, audience,
call to action, and measurement plan. Run npm run announce:rank -- --probe when the current repository inventory needs
to be re-scored, then build the selected evidence pack here.
How a pack gets made
npm run announce:rank -- --probe --write # what to announce next, and why
npm run announce:plan # when each one goes out, in what shape
npm run announce:kit -- --count 3 --capture # brief, frame, draft, pack, queue item
npm run check:announce # gate the pack before anyone reads it
announce:plan and announce:kit are the announcement factory,
which does steps 1 to 4 below for a whole batch at a time: it gathers the checkable facts, shoots
the frame (or typesets a title card for a surface with no route), has the model chain draft the
post from those facts alone, holds the draft against every gate the queue enforces, and writes the
pack plus its queue item. A pack written by hand is still a pack: drop the draft at
data/announce-plan/drafts/<id>.json and the factory runs it through the same checks.
The steps below are what each of those stages does, and they are worth reading before trusting the output of any of them.
- Rank.
scripts/announce-rank.mjsre-derives the inventory fromdata/pages.json,packages/,workers/andservices/, reads the announced status out of the coverage audit, probes each route, scores what is left, and writesdata/announcements.json. That ledger is generated, not committed, so this is the command that creates it. The score's weights come from the engagement archive, not from taste; the sources are named in announce-voice.md. - Capture. Add a shot to
data/announce-media.jsonand runnpm run announce:media. It drives the real route in a real Chromium and writes topublic/announce/img/with provenance (route, commit, time, sha256) beside the pixels. Shots markedauthsign in with the QA account so the frame shows the working product rather than its sign-in gate. A pack written by hand may instead ship a committed card, declared on its queue item asposts[].media[]with alt text; the gate accepts either, and neither may go out without alt text. - Write. One
<slug>.mdpack and one<slug>.post.txtholding the post itself. The.txtexists so the bytes the gate checks are the bytespost-tweet.mjssends; a post quoted only in prose drifts from the file that ships. - Gate.
npm run check:announceenforces media, alt text, length, voice, cross-pack uniqueness, and the coin gate.
Ranking is a hypothesis; the capture is the test. Two of the first batch's highest-scoring
surfaces were deferred once their frames were looked at: /genome sells an empty stud market and
/portfolio is an address input with nothing in it. The reasons are recorded on their entries in
the ledger, which is why the capture step comes before the writing step.
The coin gate
A frame captured from a live trading surface bakes whatever tickers were on screen into a
committed file, and the operating rules require owner approval before committing anything that
references a crypto project other than $THREE. check:announce fails such a pack, and the
affected files are kept out of the tree by .gitignore until approval is recorded on the shot as
thirdPartyMarketDataApproved.
Posting
Nothing here posts. Publishing to an external channel is owner-gated every time. A finished pack
becomes an item in the X content queue: its post names the pack file in
textFrom, so npm run x:content:check fails if the queued text drifts from the reviewed bytes,
and its media points at the captured frame. Preview exactly what would be sent:
npm run x:content -- run --dry-run --id <slug>
The queue publishes an item only after the owner sets it to approved. For a one-off post outside
the queue, node scripts/post-tweet.mjs --file docs/announcements/<slug>.post.txt --dry-run still works.
Packs
| Pack | Surface | Stage |
|---|---|---|
| genesis.md | /genesis |
drafted, awaiting approval to post |
| open-source-friday.md | /rig-doctor |
drafted, awaiting approval to post |
| openai-partner-benefits.md | /openai |
drafted, awaiting approval to post |