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
prompts(partners): log order 088's owner-gated Discord registration step
nirholas653b44cbeb3e
diff --git a/prompts/finish/088-partners-05-discord-activity.md b/prompts/finish/088-partners-05-discord-activity.mdindex f269179bc..a4471cf5d 100644--- a/prompts/finish/088-partners-05-discord-activity.md+++ b/prompts/finish/088-partners-05-discord-activity.md@@ -1,5 +1,7 @@# partners 05: A three.ws Discord Activity+**Evolve status (2026-10-13):** Everything except a live Discord verification is done. The Activity is built: a shared Forge room ([`src/discord-activity/app.js`](../../src/discord-activity/app.js), [`pages/discord-activity.html`](../../pages/discord-activity.html)), the OAuth entry point mapping a verified Discord identity (re-checked against Discord's own `/users/@me`, never trusted from the client) to a room-scoped session ([`api/gateway/discord-activity-token.js`](../../api/gateway/discord-activity-token.js), [`api/gateway/discord-activity-session.js`](../../api/gateway/discord-activity-session.js), [`api/_lib/gateway/discord-activity-auth.js`](../../api/_lib/gateway/discord-activity-auth.js)), the room API and SSE stream ([`api/gateway/discord-activity-room/[id].js`](../../api/gateway/discord-activity-room/[id].js), [`api/_lib/gateway/discord-activity-store.js`](../../api/_lib/gateway/discord-activity-store.js)), `patchUrlMappings` for Discord's `/.proxy/` CDN host, an agent reaction line ([`api/_lib/gateway/discord-activity-agent.js`](../../api/_lib/gateway/discord-activity-agent.js)), the migration, docs, STRUCTURE.md row, changelog entry, and the submission packet with exact Developer Portal settings and Discovery copy ([`marketing/growth/submissions/discord-activity.md`](../../marketing/growth/submissions/discord-activity.md)). Task 5 (in-app purchases) is deliberately omitted: the room is free, nothing is sold, and the docs and submission packet both say so explicitly, which is the task's own stated alternative to building a purchase flow. `tests/discord-activity-store.test.js` (4/4) and `tests/discord-activity-auth.test.js` (9/9) pass; the OAuth2 token exchange was proven live against Discord's real `https://discord.com/api/oauth2/token` (a placeholder client returns Discord's real, documented `invalid_client` 400). What cannot be verified from this workspace: no Discord application has ever been registered in production (`node scripts/read-service-env.mjs '^DISCORD' --names` returns zero matches), so the Definition of Done's "loads and works inside the Discord client in a test server, with two accounts seeing the same state" line is untestable until the owner registers an application. See [OWNER-ACTIONS row 52](_context/production-100-OWNER-ACTIONS.md) for the exact remaining steps. Leaving this file in place until that registration and live verification land.+How to run: paste this file's repo path into a fresh Claude Code chat in this repository and say "run this work order". Runnable now, no gate.## Operating clause (binding)diff --git a/prompts/finish/_context/production-100-OWNER-ACTIONS.md b/prompts/finish/_context/production-100-OWNER-ACTIONS.mdindex 0df6d3ecc..78c19d280 100644--- a/prompts/finish/_context/production-100-OWNER-ACTIONS.md+++ b/prompts/finish/_context/production-100-OWNER-ACTIONS.md@@ -65,6 +65,7 @@ on it; some resolve themselves as other work lands.| 50 | **Publish the CC0 bulk animation library to production** (added 2026-10-13 by the evolve loop closing out order 085-partners-02). `GET /api/animations/library` currently answers `total: 0` in production: the bulk motion library (previously baked from Mixamo, which Adobe's own Mixamo FAQ says may not be redistributed as raw files) has been rebuilt from two CC0 1.0 Universal sources, Quaternius's Universal Animation Library 2 and Mesh2Motion's human animation packs, 219 clips retargeted and verified locally (0 failures, every entry carries `source`/`license`). The only remaining step is to run `node scripts/cc0-animation-library.mjs --upload` with the production R2 credentials (`node scripts/read-service-env.mjs` to read them from the `three-ws-api` Cloud Run service if not already in `.env.local`), which publishes the staged manifest to the live bucket the endpoint reads at request time, no code deploy required. This was deliberately not run this session: it is a production-publish action (CLAUDE.md gate 2) that makes 219 clips reachable to real users and third-party mirrors immediately. Separately, and not blocking this row: the Adobe Mixamo redistribution-permission letter is drafted and ready at [`marketing/growth/submissions/adobe-mixamo-permission.md`](../../marketing/growth/submissions/adobe-mixamo-permission.md); sending it is owner order 938. | one upload command | Makes the openly-licensed bulk animation library live on `/animations` and `GET /api/animations/library` | [085-partners-02-animation-library-license.md](../085-partners-02-animation-library-license.md) || 51 | **Publish and submit the LiveKit and Pipecat avatar integrations** (added 2026-10-13 by the evolve loop closing out order 087-partners-04). Both packages (`integrations/livekit/livekit-plugins-threews/`, `integrations/pipecat/pipecat-threews/`) are built, tested (unit tests, ruff lint/format), and verified end to end against a real local `livekit-server` with real browser automation driving the actual avatar lipsync and gesture off a live agent/bot in both frameworks (Playwright specs, both passing; the Pipecat run also captured the 30-60s demo video `COMMUNITY_INTEGRATIONS.md` asks for, saved locally and gitignored). Three remaining steps are all owner actions (CLAUDE.md gate 2, external posting/publishing): (a) `python -m build && twine upload` (or equivalent) to publish each package to PyPI as `livekit-plugins-threews` and `pipecat-threews`; (b) open the LiveKit plugin pull request against `livekit/agents` using the title, description and verification packet in [`marketing/growth/submissions/livekit-avatar-plugin.md`](../../marketing/growth/submissions/livekit-avatar-plugin.md), then apply to the LiveKit Startups program; (c) open the Pipecat documentation pull request against `pipecat-ai/pipecat` using the three files in `integrations/pipecat/pipecat-threews/docs-submission/` and the text in [`marketing/growth/submissions/pipecat-integration.md`](../../marketing/growth/submissions/pipecat-integration.md), attaching the local demo video. | two PyPI publishes + two pull requests + one program application | LiveKit plugin PR 938/Startups 939, Pipecat community-integration listing | [087-partners-04-livekit-pipecat-avatar.md](../087-partners-04-livekit-pipecat-avatar.md) |+| 52 | **Register the Discord application and verify the Activity in a real Discord client** (added 2026-10-13 by the evolve loop closing out order 088-partners-05). The shared Forge room Activity ([`src/discord-activity/app.js`](../../src/discord-activity/app.js), [`api/gateway/discord-activity-*`](../../api/gateway/), migration [`20261015050000_discord_activity_rooms.sql`](../../api/_lib/migrations/20261015050000_discord_activity_rooms.sql)) is built and unit-tested (`tests/discord-activity-store.test.js`, `tests/discord-activity-auth.test.js`, 13/13 passing), and the OAuth2 token-exchange path was proven live against Discord's real endpoint (`curl` to `https://discord.com/api/oauth2/token` with a placeholder client returned Discord's real, documented `invalid_client` 400, matching the error path the code already surfaces). No Discord application has ever been registered in this production project (`node scripts/read-service-env.mjs '^DISCORD' --names` returns zero matches), so nothing past that point is testable from this workspace. Full step-by-step with exact Developer Portal settings and the Discovery listing copy: [`marketing/growth/submissions/discord-activity.md`](../../marketing/growth/submissions/discord-activity.md). Summary: (a) create the Discord application and enable Activities, pointing the root URL Mapping at `/discord-activity` and adding a `cdn` URL Mapping for the R2 host; (b) set the OAuth2 redirect and `identify` scope; (c) `gcloud run services update three-ws-api --region us-central1 --update-env-vars DISCORD_CLIENT_ID=...,DISCORD_CLIENT_SECRET=...,DISCORD_PUBLIC_KEY=...` (never `--set-env-vars`); (d) `npm run db:status` then `npm run db:migrate` to create the `discord_activity_rooms`/`discord_activity_events` tables (applies immediately, no dry run); (e) create a test Discord server, invite two accounts, open the Activity in a voice channel on both, and confirm both see the same prompt/generation/vote state (screenshots); (f) submit the Discovery listing using the exact copy in the submission file. | one Developer Portal app + one env update + one migration apply + one live two-account verification + one Discovery submission | Turns on the Discord Activity for real users; completes order 088's two-accounts-in-Discord Definition of Done line | [088-partners-05-discord-activity.md](../088-partners-05-discord-activity.md), [marketing/growth/submissions/discord-activity.md](../../marketing/growth/submissions/discord-activity.md) |Deleted 2026-09-01: the former row 5 (`WALLET_ENCRYPTION_KEY_PREVIOUS` policy), whichdeclared itself "delete on reading" and had outlived that by three weeks.