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(guards): spell out that wiring a guard also means moving it in the registry
nirholas04d93ccf4a88
diff --git a/docs/ops/guard-wiring.md b/docs/ops/guard-wiring.mdindex cf25bef71..bf8b8225a 100644--- a/docs/ops/guard-wiring.md+++ b/docs/ops/guard-wiring.md@@ -68,6 +68,26 @@ functions, so `npm test` runs them. The fourth, `findMissingDistAssets()`, returin `gate`. It only means anything after a build, so it is wired into `deploy:gcp:submit` aheadof the upload, where a missing decoder asset (the /scene Draco outage) is still cheap to fix.+## Wiring a guard is three edits, not one++`data/guards.json` is the registry that `/guards` and [../guards.md](../guards.md) render, and+it records the stage each guard runs in. Wiring a guard into `gate` without updating its+`stages` leaves the public answer wrong in the confident direction: four guards went on+claiming they were on-demand while the gate was already running them.+`scripts/audit-guards.mjs` verifies a claim against the real npm chain, and+[tests/audit-guards.test.js](../../tests/audit-guards.test.js) fails if a gate step has no+registry entry at all. So:++1. Wire it into the chain in `package.json`.+2. Set its `stages` in `data/guards.json`, then `npm run build:guards` to refresh+ `public/guards.json`.+3. Add a wiring assertion in [tests/guard-wiring.test.js](../../tests/guard-wiring.test.js).++`audit:deploy` needed a fourth: it runs in `deploy:gcp:submit`, which was not a stage the+auditor could verify (it knew only `prebuild`, `gate`, `build:gcp` and `pre-push`).+`deploy:submit` is now a real stage, checked against the real chain and described for readers+in both the registry and the runbook.+## Reds fixed in this pass| Guard | Finding | Fix |diff --git a/prompts/finish/_context/production-100-PROGRESS.md b/prompts/finish/_context/production-100-PROGRESS.mdindex d5651a35c..30d1cfa97 100644--- a/prompts/finish/_context/production-100-PROGRESS.md+++ b/prompts/finish/_context/production-100-PROGRESS.md@@ -527,6 +527,12 @@ Did:fails if a newly unwired guard has no row in the doc. Doc linked from `docs/ops/README.md`.Wiring commit f8058bc64. Changelog 798c0f692.+- **The registry had to move with the wiring.** `data/guards.json` records the stage each guard+ runs in and is what `/guards` renders, so wiring seven guards into `gate` left four of them+ publicly claiming they run on demand. Fixed, plus `audit:deploy` had no honest stage to claim:+ `deploy:gcp:submit` was not a stage `scripts/audit-guards.mjs` could verify. `deploy:submit`+ is now a real, verified stage described in the registry and in `docs/guards.md` (9989c6356).+Left:- **Nothing deleted.** `audit:deploy` was the only delete candidate and moved to the deploy pathinstead; `check:docs-search` looked like a decoy but three open `prompts/finish/` orders invoke