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 965 to the browser check, deploy and first confirmed rule now that the ledger, rules and pages are committed
nirholase63a5ade99a8
diff --git a/prompts/finish/965-revenue-ledger-reinvest.md b/prompts/finish/965-revenue-ledger-reinvest.mdindex 76f12be44..92bfbaab1 100644--- a/prompts/finish/965-revenue-ledger-reinvest.md+++ b/prompts/finish/965-revenue-ledger-reinvest.md@@ -1,9 +1,7 @@-Agents earn from several places and nothing shows it together. Creator fees (api/agents/[id]/earnings.js), paid skill and service calls (api/agent-skill-price.js, api/x402/agents.js), marketplace royalties (api/skill-royalties), invoice income and realised trading PnL each live in their own table and page. The only reinvest rule that exists is auto_claim_reinvest_pct in api/agent/launcher.js.+The revenue ledger, reconcile cron, reinvest rules, the /earnings console and the public /agents/:id/earnings page are built, documented (docs/revenue-ledger.md) and committed. Backend tests pass (tests/revenue-ledger.test.js) and the /api/revenue routes answer on a local server. What remains:-Build one revenue ledger per agent and per owner that joins every income source, each row linked to its transaction, with totals by source and period, CSV and JSON export, charts that follow the dataviz skill's guidance, and a how-it-is-calculated drawer. Reconcile it against on-chain and database sources on a schedule and alert on drift.+1. Browser check (agent can do once a Vite build works): run `npm run dev`, open /earnings signed in and /agents/<id>/earnings with the toggle on, and confirm no console errors, the chart tooltip and table view, the how-calculated drawer, export links, and the rule form, preview and confirmation table. The pages were syntax-checked but not exercised in a browser because node_modules was mid-install by another agent.+2. Deploy and cron sync (owner approval, gate 2): `npm run deploy:gcp:full` ships the pages and the `revenue-ledger-reconcile` and `revenue-reinvest` schedules.+3. First live reinvest rule (owner, gate 1): create a rule on /earnings, read the confirmation table (recipient, asset, chain, amount) and confirm it in the browser. Transfers over the spend policy land in /approvals and wait for a yes.-On top of it build reinvest rules: an owner states a split ("20 percent of income to model credits, 20 percent into a DCA of the agent's own coin, 10 percent to a tools budget, keep the rest") and a worker executes it each period with idempotency keys, per-run receipts and hard caps. Every leg that sends funds to a new address stops at the explicit confirmation table. Show projections only from trailing real history with the window stated, never invented growth. Notify on milestones and on any rule failure. This is the "agents as companies" story, so give each agent a /earnings page that can be made public with a toggle, honest and fully sourced.-------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 file once 1 is verified and 2 is done.