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(home): correct run 3, the order retirement was partial and order 20 is still standing
nirholas6f1d85a35c4e
diff --git a/prompts/finish/_context/home-PROGRESS.md b/prompts/finish/_context/home-PROGRESS.mdindex 028a1b26c..a21f62a06 100644--- a/prompts/finish/_context/home-PROGRESS.md+++ b/prompts/finish/_context/home-PROGRESS.md@@ -2008,7 +2008,10 @@ contract says 409) is CLOSED: `tests/home-security.test.js` now passes that casepeer's own re-verification entry sits above this one. Run 2's finding 1 (the ledger erasedmid-campaign) is resolved differently: the owner retired all 30 orders themselves today andrecorded it in `_context/00-RETIRED-BY-OWNER.md`, which explicitly keeps this file as the record.-Order 20's file is therefore retired with the rest and this entry is its only record. Run 2's+The retirement landed PARTIAL, though: 9 order files were deleted and 21 remain+tracked at HEAD, including `314-home-20-launch-readiness.md` itself and seven other home orders+(302, 303, 304, 306, 310, 311, 313). So order 20 is still standing on disk, not retired, and this+entry is a run record rather than a closing one. Run 2'sfinding 3 (the injection proof unrunnable on a throttled chain) is fixed here in documentation.Finding 4 (i18n) is unchanged and worse.