Skip to content

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.

2.7 KB
Raw Blame

tasks/

Machine-written verification reports from sweep scripts: the x402 paid-endpoint rails, the asset-grading probes, and the Home lane's load and chaos runs. Nothing here is hand-authored: every file is regenerated by rerunning the script that produced it. These are audit evidence, not a product surface, and the server does not read this directory at runtime.

Contents

Directory Files Written by
x402-bazaar/ settle-sweep-report.json scripts/x402-bazaar-settle-sweep.mjs: pays each bazaar endpoint for real and records settlement results.
x402-ring/ COVERAGE.md, coverage-report.json scripts/x402-ring-coverage-sweep.js: verifies every ring endpoint (402 challenge, Solana accept, settle signature, response, business effect) and writes the human table plus the machine record.
x402-ring/ datapoint-seed-report.json scripts/x402-seed-datapoints.mjs: seeds datapoints and records the outcome.
sim-readiness/ probe-<date>.json scripts/sim-readiness-probe.mjs: pulls real GLBs off the live site and grades each one for simulation readiness (watertightness, metric scale, mass and inertia, convex proxy), recording the per-asset report and the pass rate per source.
home/ envelope-<date>.json scripts/home-load.mjs: opens real WebSocket connections to a fleet of real Home Assistant containers and measures what each one costs (heap, RSS, descriptors, action latency, SSE fan-out, cold start), each measurement in its own fresh process so a heap delta means something.
home/ chaos-<date>.json scripts/home-chaos.mjs: injects the seven failures the Home lane has to survive (a house offline, a house flapping, a revoked token, our instance recycled mid-stream, the database gone, a slow house beside a fast one, a 624 entity house at ten updates a second) and records a transcript for each.

Adding a file

A new sweep or verification script that produces a durable report should write into tasks/<campaign>/, one directory per campaign, and name the file after what it records (<thing>-report.json, plus a Markdown table if humans need to read it). Prompt documents and work orders do not belong here; those live in ../prompts/.

A *.local.json in here is deliberately gitignored: it is live state about containers on one machine, and tasks/home/fleet.local.json in particular holds real access tokens to them. Report files are committed; local state is not.