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.

guards(catalog): register the new guard entries the docs and page already describe

nirholas5c280ee6782d
diff --git a/data/guards.json b/data/guards.json
index fdd59719d..bff1eeffc 100644
--- a/data/guards.json
+++ b/data/guards.json
@@ -1196,6 +1196,27 @@
"kind": "live",
"reason": "Serves pages/ibm/ from a throwaway origin and lets it talk to a real three.ws over the network, because the thing under test is the browser enforcing cross-origin rules against live response headers. Any stub or proxy would answer for three.ws and satisfy CORS on the browser behalf, blinding the audit to the only failure it exists to catch."
}
+ },
+ {
+ "id": "check-model-viewer-version",
+ "script": "scripts/check-model-viewer-version.mjs",
+ "npm": "check:model-viewer",
+ "title": "One <model-viewer> build across the whole tree",
+ "protects": "Every model-viewer URL in tracked source names the same version, no version is served under two different integrity hashes, and the vendored copy under pages/ibm/vendor/ hashes to the build the rest of the tree points at.",
+ "why": "model-viewer registers itself as a custom element, so a second customElements.define for it in one document throws and the later surface renders nothing at all. A three.ws embed pasted onto a page that already carries another three.ws surface is exactly that document, so a split pin is a blank viewer for somebody else, on their site, with nothing failing on ours. It had already drifted: eight of eighty-one references sat a major version behind, two of them still carrying SRI hashes for the older build, which is the shape a half-finished bump leaves. Delivery legitimately differs per surface (a top-level document pins SRI, a server-interpolated embed cannot, the Vite pages walk a CDN failover chain); the version never does.",
+ "stages": [
+ "gate"
+ ],
+ "needs": "none",
+ "proof": {
+ "summary": "A model-viewer reference bumped to a version the rest of the tree does not use.",
+ "violation": {
+ "write": {
+ "pages/guard-proof-model-viewer.html": "<!doctype html>\n<script type=\"module\" src=\"https://ajax.googleapis.com/ajax/libs/model-viewer/9.9.9/model-viewer.min.js\"></script>\n"
+ }
+ },
+ "expect": "9.9.9"
+ }
}
],
"exempt": [
diff --git a/docs/guards.md b/docs/guards.md
index ce6438545..b57c50518 100644
--- a/docs/guards.md
+++ b/docs/guards.md
@@ -94,6 +94,7 @@ Run `npm run audit:guards` to print the current count and per-stage breakdown. T
| No unbounded outbound call | `npm run check:fetch-timeouts` | Every fetch to a third-party host carries a deadline, so one stalled upstream cannot hold a request until the platform kills it. |
| Hard rules, diff scoped | `npm run check:rules` | The CLAUDE.md hard rules on the lines you changed. |
| The guard registry | `npm run audit:guards` | Every guard is registered and every stage claim is true. |
+| One `<model-viewer>` build | `npm run check:model-viewer` | Every `<model-viewer>` reference in tracked source names one version, no version is served under two integrity hashes, and the vendored copy matches. |
| Design-token ratchet | `npm run audit:tokens` | Hardcoded colour hexes cannot creep back past a committed baseline. |
| Credential material | `npm run check:secrets` | No dotenv file, private key, keystore, or downloaded cloud credential becomes a tracked file, and no added line carries a provider-issued key. |
| iOS app icon | `npm run check:ios-icons` | The committed iOS icon and launch images are exactly what the current brand mark produces, and the icon carries no alpha channel. |
diff --git a/public/guards.json b/public/guards.json
index fdd59719d..bff1eeffc 100644
--- a/public/guards.json
+++ b/public/guards.json
@@ -1196,6 +1196,27 @@
"kind": "live",
"reason": "Serves pages/ibm/ from a throwaway origin and lets it talk to a real three.ws over the network, because the thing under test is the browser enforcing cross-origin rules against live response headers. Any stub or proxy would answer for three.ws and satisfy CORS on the browser behalf, blinding the audit to the only failure it exists to catch."
}
+ },
+ {
+ "id": "check-model-viewer-version",
+ "script": "scripts/check-model-viewer-version.mjs",
+ "npm": "check:model-viewer",
+ "title": "One <model-viewer> build across the whole tree",
+ "protects": "Every model-viewer URL in tracked source names the same version, no version is served under two different integrity hashes, and the vendored copy under pages/ibm/vendor/ hashes to the build the rest of the tree points at.",
+ "why": "model-viewer registers itself as a custom element, so a second customElements.define for it in one document throws and the later surface renders nothing at all. A three.ws embed pasted onto a page that already carries another three.ws surface is exactly that document, so a split pin is a blank viewer for somebody else, on their site, with nothing failing on ours. It had already drifted: eight of eighty-one references sat a major version behind, two of them still carrying SRI hashes for the older build, which is the shape a half-finished bump leaves. Delivery legitimately differs per surface (a top-level document pins SRI, a server-interpolated embed cannot, the Vite pages walk a CDN failover chain); the version never does.",
+ "stages": [
+ "gate"
+ ],
+ "needs": "none",
+ "proof": {
+ "summary": "A model-viewer reference bumped to a version the rest of the tree does not use.",
+ "violation": {
+ "write": {
+ "pages/guard-proof-model-viewer.html": "<!doctype html>\n<script type=\"module\" src=\"https://ajax.googleapis.com/ajax/libs/model-viewer/9.9.9/model-viewer.min.js\"></script>\n"
+ }
+ },
+ "expect": "9.9.9"
+ }
}
],
"exempt": [