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(orders): correct order 311's blocker, and widen owner-action row 20 to the three orders it gates
nirholas1e3ada87897f
diff --git a/prompts/finish/311-home-17-a11y-i18n-mobile.md b/prompts/finish/311-home-17-a11y-i18n-mobile.mdindex 978294885..48a70fd60 100644--- a/prompts/finish/311-home-17-a11y-i18n-mobile.md+++ b/prompts/finish/311-home-17-a11y-i18n-mobile.md@@ -17,15 +17,40 @@ Fahrenheit, RTL through the real Arabic catalog, untranslated device names, redustray-tap-proof confirmation). Six real defects were found and fixed getting there; the entrylists them.-What remains is a single owner action, because no translation backend is reachable from a-session: Vertex fails on revoked Application Default Credentials that need an interactive-`gcloud auth login`, and the free `threews` proxy lane answers 502/503 on every request.-- gcloud auth login- GOOGLE_CLOUD_PROJECT=aerial-vehicle-466722-p5 npm run i18n:translate--That is roughly 500 requests and clears the whole repo's 49,378 lint problems, of which 30,259-are this lane's 358 keys across 84 locales. When it lands: confirm `npm run i18n:lint` is clean,+**Corrected 2026-09-10: the premise below was wrong in its first half and right in its second.**+Translation backends ARE reachable from a session, and gcloud does not need an interactive+login: `gcloud auth print-access-token` mints a token in this workspace today (the binary is not+on PATH, call it at `/home/codespace/google-cloud-sdk/bin/gcloud`). What is actually missing is+THROUGHPUT, not auth or reachability.++ node scripts/read-service-env.mjs '^NVIDIA_API_KEY$' # the key is on the Cloud Run service+ node scripts/i18n-translate.mjs --provider=nvidia --locales=<shard> --concurrency=3+ node scripts/i18n-translate.mjs --provider=nvidia --locales=<shard> --repair+ node scripts/i18n-translate.mjs --lint # ground truth, always++That works and was used on 2026-09-10 to take Spanish to a clean 19,875-key catalog and to fill+a large part of the rest. But every free lane is throttled per key and they cannot finish 84+locales in a session:++- **NVIDIA NIM** is the working lane, at roughly 27 keys/min per process. Running six processes+ against it does NOT go six times faster: the key is throttled per account, all six collapsed+ into `429 Too Many Requests`, and the whole batch stalled. Two processes at `--concurrency=3`+ is about the ceiling.+- **Groq** authenticates and translates well, but its free tier is 200,000 tokens per DAY, which+ is a few hundred keys. It is a useful second lane, not a bulk one.+- **OpenAI** is `billing_not_active`.+- **Vertex AND the Generative Language API are both denied project-wide** by the same+ `Lightning dunning decision is deny` billing hold, so `GOOGLE_API_KEY` is no help either.++Vertex is the lane that can actually do this in one pass, because it is billed to the GCP credit+pool with no free-tier quota to exhaust. So the single owner action for this order is **not**+`gcloud auth login`; it is **clearing the GCP billing hold**, which is the same action that+unblocks orders 903 (fact-check `groundedSearch`) and 907 (the OKX bot reply lane). Three orders,+one payment.++Until it clears, the free lanes make real progress and should be left grinding: the run is+resumable, idempotent, and an incomplete locale is held out of `manifest.json` rather than shipped+half-translated, so stopping mid-way is safe. When it lands: confirm `npm run i18n:lint` is clean,delete the `publishLocale` helper in `tests/e2e/home-a11y.spec.js` (the RTL and never-translatetests can read the real manifest once a locale is complete), re-run the suite, and retire thisfile per the section at the bottom.diff --git a/prompts/finish/_context/production-100-OWNER-ACTIONS.md b/prompts/finish/_context/production-100-OWNER-ACTIONS.mdindex c03a2bcad..1ac962436 100644--- a/prompts/finish/_context/production-100-OWNER-ACTIONS.md+++ b/prompts/finish/_context/production-100-OWNER-ACTIONS.md@@ -31,7 +31,7 @@ on it; some resolve themselves as other work lands.| 16 | Create the `three-ws` GitHub organization and `three-ws/examples` (public), then run the push command `npm run export:satellites` prints. The export now stages 72 files and passes all four smoke stages online (registry, install, links); re-probed 2026-09-03, both the organization and the repository still answer 404. | minutes | roadmap developer-resources retirement | [docs/ops/examples-repo-export.md](../../docs/ops/examples-repo-export.md) || 17 | Apple Developer account. The WidgetKit extension, the Mac menu bar app and the iOS target are written and guarded (`npm run check:apple-widget`); the account is what signs them, for a Developer ID Mac build and an App Store iOS build alike. Separately, publish the Android 1.1.0 build (versionCode 2) to Play. | account + minutes | roadmap native-widgets task 4 and its release | [../roadmap/native-widgets.md](../916-roadmap-native-widgets.md) || 19 | Deploy the `agent-sniper` worker, then decide separately whether to arm the Risk Officer. Measured 2026-09-09 against Cloud Run and mainnet: the service runs revision `agent-sniper-00033-rg6`, whose image was built **2026-08-11**, while it trades `SNIPER_MODE=live` right now (heartbeat 6s old, 11 strategies, 3,482 positions, one opened 05:10 UTC that morning; re-measured 19:34 UTC the same day: 27 strategies with 13 enabled, 3,511 positions, 41 of them opened in the previous 24 hours and the last at 19:02 UTC). **48 files and about 11,000 lines under `workers/agent-sniper/` are committed and not in that image**, including `amm-exit.js`, which is the roadmap's own named blocker: `executor.js`, `positions.js` and `graduation-ride.js` import it at HEAD, so the running image has no code path that exits a position after its coin graduates. The Risk Officer (`risk-officer.js`, migration already applied in production) has therefore never run in production either: `sniper_risk_reviews` holds 7 rows, all from the 2026-09-04 local verification, and the shadow-evidence query in `workers/agent-sniper/README.md` runs green against the live schema and returns zero rows. **Re-verify this from the database, not from `gcloud`:** the Codespace loses its gcloud login on every recycle, so `gcloud run services describe agent-sniper` is usually unavailable and its failure says nothing about the fleet. A shadow review is recorded fire-and-forget on every buy, so fleet buys with no matching review rows can only mean the running image predates `risk-officer.js`; 41 buys against 0 fleet review rows is that proof, and those counts turning non-zero is how you confirm the deploy took. The deploy is one command, `npm run deploy:sniper`, dry-run clean on 2026-09-09 (gcloud authed, runtime SA and Artifact Registry repo present, both required secrets present); on an existing service it rolls `gcloud run services update --image`, which preserves the running env, so it does **not** demote the fleet to simulate. Only the optional `telegram-alerts-chat-id` secret is missing, which disables Telegram ops alerting. Arming enforcement is a **separate, later** yes: `SNIPER_RISK_OFFICER=enforce` fleet-wide (via `--update-env-vars`, never `--set-env-vars`) or per strategy via `risk_officer_level`, and it should wait until shadow rows exist to justify it. | one yes now, one decision later | The trading Arena copy-trade loop (graduated-position exits), and all shadow evidence for the Risk Officer | [../918-roadmap-pumpfun-trading-arena.md](../918-roadmap-pumpfun-trading-arena.md), [workers/agent-sniper/README.md](../../workers/agent-sniper/README.md) |-| 20 | **Clear the GCP billing hold on `aerial-vehicle-466722-p5`.** Every Vertex surface answers `403 Lightning dunning decision is deny for project: projects/93741856042`, confirmed 2026-09-09 both locally and in production's own logs (Vertex Imagen falling back at 05:33 UTC). This is not IAM and nothing in code routes around it: it takes out the Vertex Gemini anchor, Imagen, and `groundedSearch`, which is the fact-checker's ONLY working search rung (no Brave/Tavily/Exa/Serper key exists). With it down the chain falls to Wikipedia alone: a benchmark run that day saw 190 sources, 100% Wikipedia, and 15 of 38 claims had zero stance-bearing evidence. It is a billing/payment state on the account, so only the owner can clear it. | minutes, at the billing console | Grounded search, Vertex Gemini, Imagen, and publishing the fact-check accuracy run (04b) | [PROGRESS.md](production-100-PROGRESS.md), 2026-09-09 entry |+| 20 | **Clear the GCP billing hold on `aerial-vehicle-466722-p5`.** Every Vertex surface answers `403 Lightning dunning decision is deny for project: projects/93741856042`, confirmed 2026-09-09 both locally and in production's own logs (Vertex Imagen falling back at 05:33 UTC). This is not IAM and nothing in code routes around it: it takes out the Vertex Gemini anchor, Imagen, and `groundedSearch`, which is the fact-checker's ONLY working search rung (no Brave/Tavily/Exa/Serper key exists). With it down the chain falls to Wikipedia alone: a benchmark run that day saw 190 sources, 100% Wikipedia, and 15 of 38 claims had zero stance-bearing evidence. It is a billing/payment state on the account, so only the owner can clear it. | minutes, at the billing console | Grounded search, Vertex Gemini, Imagen, and publishing the fact-check accuracy run (04b) | [PROGRESS.md](production-100-PROGRESS.md), 2026-09-09 entry | **Re-confirmed 2026-09-10, and the blast radius is wider than this row said.** The denial covers the Generative Language API (`generativelanguage.googleapis.com`, the `GOOGLE_API_KEY` path) as well as Vertex, so there is no Google lane of any kind. It is also the real blocker behind **order 311's i18n translation**: that order names `gcloud auth login` as its owner action, but gcloud auth WORKS in this workspace, and the actual constraint is that every reachable free lane is throttled per key (NVIDIA about 27 keys/min per process and `429`s under parallelism, Groq capped at 200k tokens/day, OpenAI `billing_not_active`). Vertex is the only lane billed to the credit pool with no free-tier quota, so it is the only one that finishes 84 locales in one pass. Clearing this hold therefore unblocks **three** orders at once: 903, 907 and 311.| 21 | **Decide whether to rotate the lane credentials read on 2026-09-09.** Resolving the LLM chain for the fact-check benchmark printed secret material into an agent session transcript: the `vercel-inference@aerial-vehicle-466722-p5` service-account **private key** (`GCP_SERVICE_ACCOUNT_JSON`, key id `93be907a...`), plus `GROQ_API_KEY`, all five OpenRouter keys, `NVIDIA_API_KEY` and `OPENAI_API_KEY`. `INTERNAL_API_KEY` was used but never printed. Nothing indicates misuse and all of them remain valid; the exposure surface is whoever can read that transcript. Rotate or accept, and note that the OpenAI key is dead anyway (row 6) and OpenRouter key #1 is already revoked. | decision (+ minutes if rotating) | Closing out the exposure | [PROGRESS.md](production-100-PROGRESS.md), 2026-09-09 entry |Deleted 2026-09-01: the former row 5 (`WALLET_ENCRYPTION_KEY_PREVIOUS` policy), which