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(finish): trim order 958 to the owner-gated go-live steps now that the payout flow, page and crons are committed
nirholas0099440d22a2
diff --git a/prompts/finish/958-creator-fee-payouts.md b/prompts/finish/958-creator-fee-payouts.mdindex bf5a027be..96156f959 100644--- a/prompts/finish/958-creator-fee-payouts.md+++ b/prompts/finish/958-creator-fee-payouts.md@@ -1,9 +1,8 @@-Public creator earnings exist (api/agents/[id]/earnings.js, api/leaderboard/earnings.js, the 30 minute snapshot cron) and collection runs every five minutes in api/cron/launcher-claimer.js with hourly distribution crons. What a creator cannot do is register a payout wallet with a signature, see the breakdown of earned, held, pending and sent with each distribution listed, or understand when money moves.+Creator-fee payouts are built and committed: the signed payout wallet with step-up and 48 hour change cooldown, the distribution ledger with held reasons, the distribute and reconcile crons, owner notifications, the /creator/payouts page with CSV export and the live schedule and per-$100 explainer, and the payouts block on the public earnings API and card (docs/creator-payouts.md, tests/creator-payouts.test.js). What remains is owner-gated or needs a live environment:-Build the payout wallet flow: register or change a payout wallet by signing a message with that wallet (Ed25519 for Solana, with timestamp and nonce), with step-up and the cooldown for changes, and with the wallet shown on the earnings page. Expand the earnings API to return totalEarned, totalClaimed, totalSent, totalPending and totalHeld per agent and per coin, plus recentDistributions with transaction signatures, and state why anything is held (below minimum, wallet not registered, cooldown). Add a creator earnings page section that explains the schedule from the cron definitions in vercel.json rather than typed text, a per-$100 flow explainer generated from the split policy in api/_lib/token/config.js, and CSV export.+1. Deploy, then sync Cloud Scheduler so the two new crons (/api/cron/creator-payout-distribute, /api/cron/creator-payout-reconcile) exist. Command: `npm run deploy:gcp:full`.+2. Exercise /creator/payouts in a real browser against the deployed API (register a wallet with a connected wallet and step-up, cancel a staged change, export the CSV). The local dev server could not start during the build because node_modules was mid-install.+3. Switch sending on with `gcloud run services update three-ws-api --region us-central1 --update-env-vars CREATOR_PAYOUTS_LIVE=true` only after the owner has looked at the first recorded distributions (until then every share is recorded and held as payouts_paused). This is the first real spend path, so it stops at the owner's explicit yes.+4. After the first live claim, confirm the reconcile cron reports no drift in creator_payout_reconcile_runs.-Notify the creator when fees are distributed or held. Reconcile on-chain vault balances against our records in a scheduled check that alerts on drift. Tests for the held reasons and the signature replay case.-------This brief is standalone. Assume no other brief has run, and keep working if others run at the same time: use names unique to this work for tables, routes and files, give migrations a fresh timestamp, append to shared files instead of rewriting them, and re-read a shared file before you edit it. CLAUDE.md governs everything, including its spend gate (anything that signs or moves funds shows recipient, amount, asset and chain and waits for an explicit yes; test with devnet, simulation or paper mode) and the rule that nothing naming another crypto project is committed without the owner's approval, so list any new third-party names you introduce in your report. Never name any competitor in a committed file. Finish it fully: wire it, document it, add the changelog entry, verify it for real, and report what you observed.+Delete this order once items 1 to 4 are done.