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.

chore(x-content): record today's editorial reviews of the embed, holo material and MCP articles

nirholas527d2d0ebbe0
diff --git a/data/x-content/reviews/embed-article.json b/data/x-content/reviews/embed-article.json
index dfb538e56..7ebc71a08 100644
--- a/data/x-content/reviews/embed-article.json
+++ b/data/x-content/reviews/embed-article.json
@@ -1,16 +1,19 @@
{
"id": "embed-article",
"contentHash": "afd2885a04c5fa5fdcf572c533309f3e76a4657eee862a3e54b54e6a2721da8b",
- "reviewedAt": "2026-10-01T19:22:29.309Z",
- "passed": true,
- "blockers": [],
+ "reviewedAt": "2026-10-08T04:31:53.197Z",
+ "passed": false,
+ "blockers": [
+ "evidence:file scripts/publish-lib.mjs: file does not contain \"[major]: { tracks: `>=${major}.0.0 <${Number(major) + 1}.0.0` }\"",
+ "editor verdict is revise"
+ ],
"texts": [
"One HTML tag puts a live 3D avatar on any page, already idling when it appears",
"A live 3D avatar on any web page takes one script line and one <agent-3d> tag pointed at a body. The element stays hidden until the idle has rendered, so the avatar appears standing naturally, on Mixamo, VRM and other rigs alike. The write-up walks through each step between the tag and that frame, and what reduced motion does to it."
],
"lint": [],
"verification": {
- "ok": true,
+ "ok": false,
"checks": [
{
"claim": "One HTML tag puts a live 3D avatar on any page",
@@ -114,8 +117,8 @@
"claim": "The 1 in the script path tracks the 1.x line of the element",
"kind": "evidence:file",
"target": "scripts/publish-lib.mjs",
- "ok": true,
- "detail": "file supports the claim"
+ "ok": false,
+ "detail": "file does not contain \"[major]: { tracks: `>=${major}.0.0 <${Number(major) + 1}.0.0` }\""
},
{
"claim": "boots it once it comes within 300 pixels of the viewport",
@@ -461,25 +464,40 @@
]
},
"editor": {
- "verdict": "publish",
+ "verdict": "revise",
"scores": {
- "accuracy": 5,
+ "accuracy": 4,
"clarity": 5,
"specificity": 5,
"voice": 5,
"professionalism": 5,
- "visual": 5
+ "visual": 4
},
- "issues": [],
+ "issues": [
+ {
+ "severity": "major",
+ "area": "accuracy",
+ "quote": "The `1` in the script path tracks the 1.x line of the element, so fixes reach your page without you editing it.",
+ "problem": "One of the two evidence items for this claim failed verification: scripts/publish-lib.mjs does not contain the cited tracking code. The live versions.json check did pass and shows \">=1.0.0 <2.0.0\", so the claim itself is supported by the live product, but the pack must not carry a failed check. Either the file evidence is stale or the mechanism changed.",
+ "fix": "Confirm scripts/publish-lib.mjs and re-run the check. If the file no longer contains the version-range logic, revise the article sentence to state only what the passing live check shows, e.g. \"The `1` in the script path is the 1.x channel, and the served manifest pins it to >=1.0.0 <2.0.0, so fixes reach your page without you editing it.\""
+ },
+ {
+ "severity": "minor",
+ "area": "visual",
+ "quote": "each rendered live by its own agent-3d element in the same relaxed idle pose",
+ "problem": "The still image cannot show that the avatars are live element renders idling; it shows three static characters. Alt text should describe what is visible rather than assert the capture method.",
+ "fix": "Alt text: \"Three 3D avatars side by side on a dark background in the same relaxed standing pose: a woman in a dark top and purple leggings, a character in a cropped top, yellow trousers and round pink glasses, and a man in a white T-shirt, light jeans and green trainers\""
+ }
+ ],
"rewrite": {
"posts": [
"A live 3D avatar on any web page takes one script line and one <agent-3d> tag pointed at a body. The element stays hidden until the idle has rendered, so the avatar appears standing naturally, on Mixamo, VRM and other rigs alike. The write-up walks through each step between the tag and that frame, and what reduced motion does to it."
],
"altText": [
- "Three 3D avatars standing side by side on a dark blue background, each rendered live by its own agent-3d element in the same relaxed idle pose: a woman in a purple top and leggings, a character in a cropped top, yellow trousers and round pink glasses, and a man in a white T-shirt, light jeans and green trainers"
+ "Three 3D avatars side by side on a dark background in the same relaxed standing pose: a woman in a dark top and purple leggings, a character in a cropped top, yellow trousers and round pink glasses, and a man in a white T-shirt, light jeans and green trainers"
]
},
- "summary": "Every claim in the post and article is backed by a passing verification against the live docs page, source files, or API probes, and the cover image matches its alt text and the article's description of the three rigs running one idle clip. Voice, length, and linking all conform to the contract; ship as is.",
+ "summary": "The post text itself is fully verified, specific, and on voice. The flagged problems sit in the article body and alt text: the publish-lib.mjs evidence for the version-tracking claim failed its check (the live versions.json supports the claim, so fix the evidence or reword), and the cover alt text asserts live rendering the still cannot show.",
"model": "nvidia:moonshotai/kimi-k3",
"fallbacks": [
"Vertex 403: {\n \"error\": {\n \"code\": 403,\n \"message\": \"Request had insufficient authentication scopes.\",\n \"status\": \"PERMISSION_DENIED\",\n \"details\": [\n {\n \"@type\": \"type.googleapis.com/goog",
diff --git a/data/x-content/reviews/holo-material-article.json b/data/x-content/reviews/holo-material-article.json
index 81a75c268..55734f9af 100644
--- a/data/x-content/reviews/holo-material-article.json
+++ b/data/x-content/reviews/holo-material-article.json
@@ -1,11 +1,10 @@
{
"id": "holo-material-article",
"contentHash": "82add87cfae43ed4c3b5cca79f504b5bd5782659c78b964208569d2501469a54",
- "reviewedAt": "2026-10-01T19:24:15.580Z",
+ "reviewedAt": "2026-10-08T04:34:09.953Z",
"passed": false,
"blockers": [
"evidence:file src/holo.js: file does not contain \"peelUniforms.uRadius.value = 0.17 + amount * 0.18;\"",
- "editor (accuracy): This sentence is in the published article body and its only verification check failed: src/holo.js does not contain \"peelUniforms.uRadius.value = 0.17 + amount * 0.18;\". The numbers 0.17 and 0.18 are unverified and must not publish.",
"editor verdict is revise"
],
"texts": [
@@ -732,31 +731,38 @@
"editor": {
"verdict": "revise",
"scores": {
- "accuracy": 4,
- "clarity": 5,
+ "accuracy": 5,
+ "clarity": 4,
"specificity": 5,
"voice": 5,
"professionalism": 5,
- "visual": 5
+ "visual": 4
},
"issues": [
{
- "severity": "blocking",
- "area": "accuracy",
- "quote": "The radius grows as you peel, from 0.17 units at rest by another 0.18 at full peel.",
- "problem": "This sentence is in the published article body and its only verification check failed: src/holo.js does not contain \"peelUniforms.uRadius.value = 0.17 + amount * 0.18;\". The numbers 0.17 and 0.18 are unverified and must not publish.",
- "fix": "Delete the sentence from the \"The peel happens in the vertex shader\" section of the article. The post text itself does not contain it, so only the article body changes. No replacement claim is possible because no passing check verifies any radius value."
+ "severity": "major",
+ "area": "voice",
+ "quote": "Each step, with the code's own numbers, from the cut to the vertex-shader peel.",
+ "problem": "The post carries no link. The house contract requires one link to the surface the post is about, and for an article-format post the head must still let a reader reach the thing. The verified URL https://three.ws/holo is absent from the post text.",
+ "fix": "Append the link as its own sentence: 'The full piece and the live sticker: https://three.ws/holo'"
+ },
+ {
+ "severity": "minor",
+ "area": "clarity",
+ "quote": "A die-cut foil sticker with no image behind it",
+ "problem": "The opening is a fragment and says 'no image behind it', which is accurate but abstract; a first-time reader may not grasp that 'no image behind it' means the whole sticker is computed in the browser rather than rendered from an image file. The live page wording supports saying this directly.",
+ "fix": "Recast the first line to state the mechanism plainly: the sticker's outline, foil, light and peeling corner are all computed in the browser with no image or model files, per the live page text already verified."
}
],
"rewrite": {
"posts": [
- "A die-cut foil sticker with no image behind it: the mark is drawn into a 640 pixel canvas, grown by a 28 pixel disc the way a cutter adds a margin, traced back into outlines with marching squares, and lit by a thin film 120 to 480 nanometres thick. Each step, with the code's own numbers, from the cut to the vertex-shader peel."
+ "A die-cut foil sticker with no image behind it: the mark is drawn into a 640 pixel canvas, grown by a 28 pixel disc the way a cutter adds a margin, traced back into outlines with marching squares, and lit by a thin film 120 to 480 nanometres thick. Each step, with the code's own numbers, from the cut to the vertex-shader peel. The full piece and the live sticker: https://three.ws/holo"
],
"altText": [
"A die-cut holographic foil sticker of three slanted bars floating on black, tilted toward the viewer, its rim shifting from green to violet and its top corner curling up where it peels, rendered live on the three.ws Holo Sticker page"
]
},
- "summary": "The post text, cover image, and alt text are all verified, specific, and on voice. One blocking issue sits in the article body: the peel-radius sentence (0.17 at rest, 0.18 at full peel) failed verification against src/holo.js and must be cut before publishing.",
+ "summary": "The copy is accurate, specific, and in voice: every number in the post text (640, 28, marching squares, 120 to 480) passed verification against the code and the live page. The one fix needed is the missing link to three.ws/holo, which the house contract requires; the failed radius verification affects only an article-body sentence, not this post.",
"model": "nvidia:moonshotai/kimi-k3",
"fallbacks": [
"Vertex 403: {\n \"error\": {\n \"code\": 403,\n \"message\": \"Request had insufficient authentication scopes.\",\n \"status\": \"PERMISSION_DENIED\",\n \"details\": [\n {\n \"@type\": \"type.googleapis.com/goog",
diff --git a/data/x-content/reviews/mcp-article.json b/data/x-content/reviews/mcp-article.json
index 10b403cb3..527a82d5a 100644
--- a/data/x-content/reviews/mcp-article.json
+++ b/data/x-content/reviews/mcp-article.json
@@ -1,10 +1,17 @@
{
"id": "mcp-article",
"contentHash": "d09851ce31b2f4af94bd01e55b5b5f5d95c6a3dd86a1811f0e2ef8f1b86e3f2f",
- "reviewedAt": "2026-10-01T19:25:10.639Z",
+ "reviewedAt": "2026-10-08T04:36:54.710Z",
"passed": false,
"blockers": [
- "evidence:file docs/mcp-studio.md: file does not contain \"`tools/list` returns exactly **eleven** tools\""
+ "evidence:page https://three.ws/docs/mcp-studio: live page does not show \"All eleven are free and keyless.\"",
+ "evidence:file docs/mcp-studio.md: file does not contain \"`tools/list` returns exactly **eleven** tools\"",
+ "evidence:page https://three.ws/docs/mcp-studio: live page does not show \"All eleven are free and keyless.\"",
+ "probe:api the free server still lists eleven tools to a keyless client: result.tools.length is 14",
+ "probe:browser the docs page says all eleven tools are free: locator.waitFor: Timeout 45000ms exceeded.",
+ "editor (accuracy): The count failed verification three ways: the live docs page does not show \"All eleven are free and keyless.\", docs/mcp-studio.md no longer contains \"`tools/list` returns exactly **eleven** tools\", and the live probe of the MCP server returned result.tools.length is 14, not 11. The product has changed and the copy is stale. Every article section built on \"eleven\" (the title, \"What the eleven tools do\", \"not one of these eleven tools\") and the session screenshot alt text (\"lists all eleven tools\") is wrong against the live server.",
+ "editor (visual): The session image (session.png) shows a tools/list of eleven; the live server now returns fourteen. Per the source-of-truth rule the screenshot is stale, and the fix is to recapture, not to edit the copy to match.",
+ "editor verdict is revise"
],
"texts": [
"Eleven free 3D tools for Claude Code and any MCP client, from one address",
@@ -18,8 +25,8 @@
"claim": "Eleven free 3D tools",
"kind": "evidence:page",
"target": "https://three.ws/docs/mcp-studio",
- "ok": true,
- "detail": "live page shows \"All eleven are free and keyless.\""
+ "ok": false,
+ "detail": "live page does not show \"All eleven are free and keyless.\""
},
{
"claim": "Eleven free 3D tools",
@@ -53,8 +60,8 @@
"claim": "runs an MCP server that needs no account and no API key",
"kind": "evidence:page",
"target": "https://three.ws/docs/mcp-studio",
- "ok": true,
- "detail": "live page shows \"All eleven are free and keyless.\""
+ "ok": false,
+ "detail": "live page does not show \"All eleven are free and keyless.\""
},
{
"claim": "runs an MCP server that needs no account and no API key",
@@ -402,8 +409,8 @@
{
"kind": "probe:api",
"target": "the free server still lists eleven tools to a keyless client",
- "ok": true,
- "detail": "HTTP 200, expectations met"
+ "ok": false,
+ "detail": "result.tools.length is 14"
},
{
"kind": "probe:api",
@@ -426,8 +433,8 @@
{
"kind": "probe:browser",
"target": "the docs page says all eleven tools are free",
- "ok": true,
- "detail": "2 steps passed"
+ "ok": false,
+ "detail": "locator.waitFor: Timeout 45000ms exceeded."
},
{
"kind": "link",
@@ -456,25 +463,47 @@
]
},
"editor": {
- "verdict": "publish",
+ "verdict": "revise",
"scores": {
- "accuracy": 5,
+ "accuracy": 2,
"clarity": 4,
- "specificity": 5,
+ "specificity": 4,
"voice": 5,
"professionalism": 5,
- "visual": 4
+ "visual": 3
},
- "issues": [],
+ "issues": [
+ {
+ "severity": "blocking",
+ "area": "accuracy",
+ "quote": "eleven free 3D tools",
+ "problem": "The count failed verification three ways: the live docs page does not show \"All eleven are free and keyless.\", docs/mcp-studio.md no longer contains \"`tools/list` returns exactly **eleven** tools\", and the live probe of the MCP server returned result.tools.length is 14, not 11. The product has changed and the copy is stale. Every article section built on \"eleven\" (the title, \"What the eleven tools do\", \"not one of these eleven tools\") and the session screenshot alt text (\"lists all eleven tools\") is wrong against the live server.",
+ "fix": "Do not publish any count until the docs and article are re-verified against the live server. Recapture the session screenshot so it shows the current tools/list response, update docs/mcp-studio.md and the docs page to the true count, and re-run the probe. In the X post, drop the number entirely and say \"free 3D tools\", which is supported by the passing keyless-handshake probe and the passing per-tool evidence. The article needs the same treatment before it ships: its headline and tool-list section claim eleven."
+ },
+ {
+ "severity": "blocking",
+ "area": "visual",
+ "quote": "lists all eleven tools with the two read-only ones marked",
+ "problem": "The session image (session.png) shows a tools/list of eleven; the live server now returns fourteen. Per the source-of-truth rule the screenshot is stale, and the fix is to recapture, not to edit the copy to match.",
+ "fix": "Re-run the documented session against https://three.ws/api/mcp-studio with no credentials and recapture session.png so the tool list matches the live response; update its alt text to match what the new frame actually shows."
+ },
+ {
+ "severity": "major",
+ "area": "accuracy",
+ "quote": "one address",
+ "problem": "Harmless in itself, but it rides on the same claims block whose headline number failed; confirm the connector instructions in docs/prompts.md still reflect the current server after the tool-count fix lands.",
+ "fix": "Re-verify docs/prompts.md against the live server after the docs are corrected; no text change needed in the post."
+ }
+ ],
"rewrite": {
"posts": [
- "Add one address to Claude Code or any MCP client and the assistant gets eleven free 3D tools, with no account or key: text or an image to a textured model, rigged avatars, rigging, refinement, and look_at_model, which renders a model so the assistant can check its own work. The write-up includes a real session against the server."
+ "Add one address to Claude Code or any MCP client and the assistant gets a set of free 3D tools, with no account or key: text or an image to a textured GLB, rigged and animation-ready avatars, rigging a model you already have, refinement by describing the change, and look_at_model, which renders up to six angles of any public GLB so the assistant can check its own work and regenerate with the fault named. The write-up includes a real session run against the server with no credentials."
],
"altText": [
"A vintage film camera rendered in the browser 3D viewer against a dark background, seen from the front three-quarter angle with its three-lens turret, speed dial and textured olive body; the model is the one the look_at_model tool inspected in the session described in the article"
]
},
- "summary": "The one failed evidence check is a stale doc quote, but the load-bearing claim (eleven free keyless tools) is corroborated by the live docs page and two passing API probes, so nothing in the post is unsupported. The cover image matches the article's described camera and the alt text is accurate; copy is in voice, specific, and partner-safe.",
+ "summary": "The post's central number is wrong against the live product: the server now lists fourteen tools, the docs no longer say eleven, and the session screenshot is stale. Everything else verified; strip the count from the post, then update the docs, recapture the session image, and re-verify before the article ships.",
"model": "nvidia:moonshotai/kimi-k3",
"fallbacks": [
"Vertex 403: {\n \"error\": {\n \"code\": 403,\n \"message\": \"Request had insufficient authentication scopes.\",\n \"status\": \"PERMISSION_DENIED\",\n \"details\": [\n {\n \"@type\": \"type.googleapis.com/goog",
@@ -482,6 +511,7 @@
"openai 429: {\n \"error\": {\n \"message\": \"Your account is not active, please check your billing details on our website.\",\n \"type\": \"billing_not_active\",\n \"param\": null,\n \"code\": \"billi"
],
"rewriteFindings": [
+ "claims: claim \"renders a model so the assistant can check its own work\" does not appear in the copy; claims must quote the post",
"claims: claim \"runs an MCP server that needs no account and no API key\" does not appear in the copy; claims must quote the post",
"claims: claim \"the tools are there the next time a session starts\" does not appear in the copy; claims must quote the post",
"claims: claim \"the address goes in as a custom connector with authentication set to None\" does not appear in the copy; claims must quote the post",