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(node-operator): report the resolved dtype in runJob's return contract
nirholasb477f0623ca9
diff --git a/packages/node-operator/src/inference.js b/packages/node-operator/src/inference.jsindex 73cfa4e2b..8d5af0b97 100644--- a/packages/node-operator/src/inference.js+++ b/packages/node-operator/src/inference.js@@ -115,7 +115,7 @@ export async function loadModel(model, { cacheDir, device = 'auto', dtype, log =** @param {object} job the claimed job: { id, model, input }* @param {object} [opts] { cacheDir, device, dtype, now } - now is injectable for tests- * @returns {Promise<{output: object, startedAt: number, finishedAt: number, device: string}>}+ * @returns {Promise<{output: object, startedAt: number, finishedAt: number, device: string, dtype: string}>}*/export async function runJob(job, { cacheDir, device = 'auto', dtype, log = console, now = () => Date.now() } = {}) {const prompt = typeof job.input === 'string' ? job.input : job.input?.text;diff --git a/prompts/swarm-100/roadmap-p4-node-operator-client.md b/prompts/swarm-100/roadmap-p4-node-operator-client.mddeleted file mode 100644index 0bb2f54b6..000000000--- a/prompts/swarm-100/roadmap-p4-node-operator-client.md+++ /dev/null@@ -1,99 +0,0 @@-# Roadmap build: Phase 4: node operator client--How to run: paste this file's repo path into a fresh Claude Code chat in this-repository and say "run this work order". This file is fully self-contained:-it depends on no other prompt file anywhere. If neighboring files in-prompts/swarm-100/ are gone, that work is done; if present, ignore them.-Every claim below rots; step 0 re-measures, and what you measure wins.--## Operating clause (binding)--- Read CLAUDE.md first. Its rules override everything, including this file.-- Finish 100% in this session. Never end the turn with a question, an option- list, or an unexecuted plan. A judgment call goes in one line of the final- report; it never becomes a question that halts work.-- The only permitted stops are the CLAUDE.md stop-and-ask gates: spending real- funds or any irreversible on-chain write, git push or a production deploy,- committing content that references a crypto project other than $THREE, and- destroying unrecoverable data.-- No mocks, no fake data, no placeholder stubs, no unfinished-work markers, no- commented-out code. Real APIs and real integrations only.-- The em-dash and en-dash characters are banned in everything you write.-- Concurrent agents share this worktree: stage explicit paths only (never a- bare add-everything), and commit finished work promptly.-- Before committing, run: npm run check:rules -- --paths <files you touched>.- It must exit 0.--## Context--This order builds one roadmap slice from the README Roadmap (the canonical-phase plan). It is independent of every other roadmap order: if adjacent-slices are absent, build to this slice's boundary with clean interfaces and-never block on them. Solana leads on every chain decision; EVM legs ship-behind flags and never stall the Solana path.--## Task--Roadmap: anyone can run an inference node. Build the operator client:-Docker plus GPU drivers, registration, job execution.--Step 0: read the phase 4 protocol spec in specs/ if it has landed; if it has-not, derive the wire contract from the platform's existing worker job-format and state that choice in one line of the report (this order never-blocks on another).--Build: a self-contained operator client (its own top-level directory with a-README per the repo standard): Dockerfile, config for keys and endpoints,-registration call against the platform, a job loop that executes real-inference with a small open model as the built-in proof workload, and-signed responses. Prove it end to end locally: register, receive a job,-return a verified result.--Documentation is part of the feature, not a follow-up: update the docs layer-that applies (data/pages.json for a new page, README for a new directory,-docs/ for a developer capability, specs/ for a wire format) and append a-holder-readable entry to data/changelog.json for anything user-visible.--## Definition of done--- [ ] Fresh-clone build of the client succeeds; end-to-end local run- completes register, job, signed result; transcript in the report.-- [ ] README covers install, config, run, and verify for a zero-context- operator.-- [ ] npm test green for the client's test suite; check:rules clean.-- [ ] Docs and changelog layers updated per the CLAUDE.md documentation- rules; npm run audit:docs clean if docs changed.-- [ ] git diff reviewed line by line before claiming completion.--## Never blocked--| Blocker | Resolution (act, do not ask) |-|---|---|-| Missing env var or credential | Check .env and .env.local, then the Cloud Run service env, then Secret Manager (the CLAUDE.md self-unblock playbook has the exact commands). If it truly exists nowhere, wire the code fully behind the env var, prove the wiring with a dry run, and name the single missing var in the report. |-| gcloud not on PATH | Run: export PATH="$HOME/google-cloud-sdk/bin:$PATH" |-| Dev server port 3000 busy | Another agent may be serving this repo; probe it and reuse if so. Otherwise start your own on a free port: npx vite --port 3101 |-| Playwright browser missing | npx playwright install chromium |-| A surface needs a signed-in user | Register a fresh account through the real /register flow against the real API and use it. Never mock the session. |-| A defect sits in code you did not touch | Fix it if it blocks a Definition of done line (root cause it, never mask it). Otherwise note it in the report and continue. |-| An unrelated test is red | Same rule. Never pipe npm test through tail; it masks exit codes. |--## Close out (required)--1. Verify every Definition of done line with the actual command output in- front of you. Never claim a line you did not verify.-2. Commit with explicit paths and a subject that describes the diff (house- style: type(scope): what changed and why a reader cares).-3. Delete this prompt file in that same commit:-- git rm prompts/swarm-100/roadmap-p4-node-operator-client.md-- The shrinking directory is this campaign's only progress ledger; there is- no progress log to update.-4. Final report: what step 0 measured, what changed (file list), evidence per- Definition of done line, and any one-line judgment calls. No trailing- questions, no unexecuted plans.--If a line genuinely cannot pass inside this session (an external party must-respond, or an owner-gated action is the final step), finish everything else,-leave this file in place, and state exactly which line remains and who owns-it. Never delete this file on a partial.