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
feat(x-content): tighten the article editor and queue and refresh the proof-reels article with its reel sticker
nirholas8e0b94ce532d
diff --git a/api/_lib/x-content/editor.js b/api/_lib/x-content/editor.jsindex 761484272..034314dc8 100644--- a/api/_lib/x-content/editor.js+++ b/api/_lib/x-content/editor.js@@ -39,7 +39,7 @@ Judge the post on:- professionalism: grammar, punctuation, capitalization of names, and tone a partner's comms team would be comfortable being tagged in. Nothing that reads as investment advice or a price promise about $THREE. Tags are only for accounts the feature genuinely runs on.- visual: the image is sharp, shows the real product, supports the claim, and would not be cropped badly in the timeline; alt text describes what is in the image for someone who cannot see it. When the attachment is a reel you cannot watch it, so you are given still frames from it, the captions it shows in order, and the record of the run it filmed (what the run read off the screen, what the server answered, and how long any wait was cut). Judge whether those frames show the feature doing what the post says, whether each caption is true of the frame it sits under, and whether anything a frame shows contradicts the copy.-The house standard is the keeper X Article (data/x-content/articles/keeper-article.md), and every post is that standard compressed. Hold an Article to its shape: it opens on one real run told plainly with its real numbers, follows that one job through every stage, explains each stage in plain words before the mechanism, credits the open models it builds on, carries a partners section stating each designation exactly, and ends on the live pages to try. Nothing negative is posted, in an Article or a post: an outage, loss, bug or "limitations" passage is a major issue, and the fix frames it truthfully as a design choice or what is next, or removes it. Positive framing never licenses an unsupported claim; accuracy still comes first.+The house standard is the keeper X Article (data/x-content/articles/keeper-article.md), and every post is that standard compressed. Hold an Article to the depth the X Article limits allow: a title of 80 to 100 characters carrying the headline number, 2,400 or more words across 8 or more sections, 3,000 or more characters of real code and tables (X allows 10,000), 4 or more inline images, a "The partners behind ..." section thanking every partner on three.ws/partners with its designation stated exactly, and a "Try it" section; a shorter Article is a major issue. Hold an Article to its shape: it opens on one real run told plainly with its real numbers, follows that one job through every stage, explains each stage in plain words before the mechanism, credits the open models it builds on, carries a partners section stating each designation exactly, and ends on the live pages to try. Nothing negative is posted, in an Article or a post: an outage, loss, bug or "limitations" passage is a major issue, and the fix frames it truthfully as a design choice or what is next, or removes it. Positive framing never licenses an unsupported claim; accuracy still comes first.Score each 1 to 5, where 5 means you would ship it unchanged at a top-tier company and 3 means a competent draft that needs work.diff --git a/api/_lib/x-content/queue.js b/api/_lib/x-content/queue.jsindex 8e7ed6347..56b7a2edb 100644--- a/api/_lib/x-content/queue.js+++ b/api/_lib/x-content/queue.js@@ -20,6 +20,58 @@ export const STATUSES = ['draft', 'review', 'approved', 'paused', 'posted'];export const KINDS = ['post', 'article'];export const MAX_ARTICLE_TITLE = 100;+// An Article is the long form, so it has to use the room X gives it (owner,+// 2026-10-11): a title that fills the title limit with the headline number in+// it, a body deep enough to explain the mechanism, code and tables that use+// the share X allows, four or more real images, and the partners section.+export const MIN_ARTICLE_TITLE = 80;+export const MIN_ARTICLE_WORDS = 2400;+export const MIN_ARTICLE_SECTIONS = 8;+export const MIN_ARTICLE_IMAGES = 4;+export const MIN_MARKDOWN_ENTITY = 3000;++// The partner names three.ws/partners lists, read from the page so the gate+// stays true when a programme is added.+export function partnerNames(root) {+ try {+ const html = readFileSync(resolve(root, 'pages/partners.html'), 'utf8');+ return [...html.matchAll(/class="partner-name"[^>]*>([^<]+)</g)].map((match) => match[1].trim()).filter(Boolean);+ } catch {+ return [];+ }+}++function articleDepthProblems(root, title, blocks, converted) {+ const problems = [];+ if (title.length < MIN_ARTICLE_TITLE) {+ problems.push(`article title is ${title.length} characters; use the title limit, ${MIN_ARTICLE_TITLE} to ${MAX_ARTICLE_TITLE}, and carry the headline number`);+ }+ const prose = blocks.filter((block) => block.type !== 'atomic').map((block) => block.text).join('\n');+ const words = prose.split(/\s+/).filter(Boolean).length;+ if (words < MIN_ARTICLE_WORDS) problems.push(`article body is ${words} words; an Article explains in depth, ${MIN_ARTICLE_WORDS} or more`);+ const sections = blocks.filter((block) => block.type === 'header-two');+ if (sections.length < MIN_ARTICLE_SECTIONS) problems.push(`article body has ${sections.length} sections; use ${MIN_ARTICLE_SECTIONS} or more, each named for what the reader learns`);+ if (converted.markdownWeight < MIN_MARKDOWN_ENTITY) {+ problems.push(`code blocks and tables total ${converted.markdownWeight} characters; X allows ${MARKDOWN_ENTITY_BUDGET}, so use at least ${MIN_MARKDOWN_ENTITY} on runnable code and real tables`);+ }+ if (converted.images.length < MIN_ARTICLE_IMAGES) problems.push(`article has ${converted.images.length} inline images; use ${MIN_ARTICLE_IMAGES} or more real captures`);++ const headings = sections.map((block) => block.text);+ const partners = headings.findIndex((heading) => /^the partners behind\b/i.test(heading));+ if (partners < 0) {+ problems.push('article needs a "The partners behind ..." section with thanks to each partner, stated as three.ws/partners states it');+ } else {+ const start = blocks.findIndex((block) => block.type === 'header-two' && block.text === headings[partners]);+ const end = blocks.findIndex((block, index) => index > start && block.type === 'header-two');+ const section = blocks.slice(start, end < 0 ? undefined : end).map((block) => block.text).join('\n');+ for (const name of partnerNames(root)) {+ if (!section.includes(name)) problems.push(`partners section does not cover ${name}; every partner on three.ws/partners gets a paragraph`);+ }+ }+ if (!headings.some((heading) => /^try it\b/i.test(heading))) problems.push('article needs a "Try it" section that links the live pages');+ return problems;+}+export function loadQueue(root, path = QUEUE_PATH) {return JSON.parse(readFileSync(resolve(root, path), 'utf8'));}@@ -136,6 +188,7 @@ function articleProblems(item, root) {if (converted.markdownWeight > MARKDOWN_ENTITY_BUDGET) {problems.push(`code blocks and tables total ${converted.markdownWeight} characters; X allows ${MARKDOWN_ENTITY_BUDGET} per Article`);}+ if (['review', 'approved'].includes(item.status)) problems.push(...articleDepthProblems(root, title, blocks, converted));for (const warning of converted.warnings) problems.push(`article body: ${warning}`);for (const image of converted.images) {if (mediaType(image.path)?.kind !== 'image') problems.push(`article image ${image.path} must be a still image`);diff --git a/data/x-content/articles/proof-reels-article.md b/data/x-content/articles/proof-reels-article.mdindex 743ab7043..d2d972489 100644--- a/data/x-content/articles/proof-reels-article.md+++ b/data/x-content/articles/proof-reels-article.md@@ -1,69 +1,200 @@-The feature videos in this feed are not screen recordings. Each one is a scripted test run against the live site, filmed while it runs. If any step of the run fails, no video is made, and the feature is not announced.+On 2026-09-29 a script opened three.ws/assembly and found a radial engine with nine cylinders. It dragged one slider, waited for the page to say 16.5 L, read the cylinder count again, and found five. Then it clicked a second machine, a steam locomotive, and pulled it apart with a keypress. The whole run was filmed while it ran: 477 frames, 15.9 seconds, stamped with the production commit f2081d946 that answered it.-That rule exists because a fact check was not enough. A post can quote a page word for word and still describe a feature that does not do what the page says. A run that has to click, type and wait for the result cannot. Here is how a reel gets made, and what the camera refuses to film.+That is what a feature video from three.ws is. It is not a screen recording of someone clicking around. It is a scripted test run against the live site, filmed as it runs. If any step of the run fails, no video is made, and the feature is not announced.++The rule exists because a fact check was not enough. A post can quote a page word for word and still describe a feature that does not do what the page says. A run that has to click, type and wait for the result cannot. This article follows that one engine reel through the whole pipeline: the steps it is written as, the camera that films it, the bar under the page, the facts it reads, the encoder, the record that binds it to its post, and the partners and open tools that make it possible. The numbers in it come from the code or from the record of a real run, and you can run the same commands yourself.## A reel starts as a list of steps-A reel begins as a scenario: the steps a person would take, and what they would see if the feature worked. A step can goto a page, click a control by its visible text, type into a field, press a key, drag across the scene, expect a text to appear, or read a fact off the screen with a pattern. These are five of the steps behind the Machine Atlas reel, as they sit in the file:+A reel begins as a scenario: the steps a person would take, and what they would see if the feature worked. A step can goto a page, click a control by its visible text, hover, upload a file, type into a field, press a key, drag across the scene, scroll, wait, hold still, expect a text to appear, or read a fact off the screen with a pattern. Any step can also carry a caption, the one sentence that explains it to a viewer.++These are the steps behind the Machine Atlas reel, trimmed to the ones that carry its facts, exactly as they sit in the file:```json{ "goto": "https://three.ws/assembly", "settle": 8000 },+{ "read": "machines", "match": "(Two) machines" },{ "read": "cylinders", "selector": "#ma-p-cylinders-out", "match": "(\\d+)" },+{ "read": "displacement", "match": "Displacement\\s*([\\d.]+ L)" },+{ "hold": 1600, "caption": "No model file. This engine is computed when the page loads." },{ "drag": [[0.8806, 0.278], [0.7, 0.278]], "ms": 1500,"caption": "Change a dimension and the geometry is rebuilt: nine cylinders to five" },{ "expect": "16.5 L" },-{ "read": "cylindersAfter", "selector": "#ma-p-cylinders-out", "match": "(\\d+)" }+{ "read": "cylindersAfter", "selector": "#ma-p-cylinders-out", "match": "(\\d+)" },+{ "click": "Coupled Six", "caption": "The second machine is a steam locomotive, built the same way" },+{ "expect": "Outside-cylinder steam locomotive" },+{ "expect": "Solved four-bar chain, not baked animation" },+{ "press": "e", "caption": "Pull it apart. Every part is its own geometry." }```The run reads the cylinder count before the drag and after it. On the filmed run it read 9, then 5, and it waited for the new displacement before it went on. A step that waits for text which appears on success, and not before, is the difference between a test and a tour: the engine's name is on the page before anyone touches it, the new displacement is not.-An action can also name the request it has to cause. When the Drive reel types a question to an agent, the run waits for the chat request to answer, and an error fails the run.+One list of steps does four jobs at once. It is the probe, because each step must pass against the live product. It is the video, because the run is filmed. It is the captions, because a step carries the sentence that explains it. And it is the evidence, because what the run read off the screen, what it waited for and what the server answered are the facts a claim may cite.++## Steps find controls the way a person does++A person clicks a button because of what it says, so a step names a control by its visible text. When several controls could match, exact names are tried before partial ones. That rule came from a reel in which the word Search was about to resolve to a button called Clear search that sat earlier in the page. With exact names tried before partial ones, a step lands on the control a viewer would expect it to.++A control that is about to appear is waited for on the page's own clock, which is filmed, so the viewer sees the same second pass that the run did. An action can also name the request it has to cause. When the Drive reel types a question to an agent, the run waits for the chat request to answer, and an error fails the run. The record of that run says the chat endpoint answered 200, in 6.8 seconds.## The page clock is stepped, not recordedThe machine that films has no GPU. A headless browser renders WebGL in software at one to three frames a second, and a screen recorder pads that out by repeating frames, which is why an early clip of ours read as a slide show.-So the camera takes over the page's clock. It advances the clock by one frame, a thirtieth of a second, takes a picture, and repeats. Every frame of a reel is a distinct frame at 1/30 s of page time, however long the machine took to draw it. On the galaxy page, recording in real time gave 1.3 distinct frames a second; stepping gave 30.+So the camera takes over the page's clock. It advances the clock by one frame, a thirtieth of a second, takes a picture, and repeats. Each frame of a reel is a distinct frame at 1/30 s of page time, however long the machine took to draw it. On the galaxy page, recording in real time gave 1.3 distinct frames a second; stepping gave 30.-The other half of the fix was to composite the page itself on the CPU. Without that, the page went through the same software graphics device as the 3D scene, and one frame of a plain list page measured 3.5 to 15 seconds. With it, the 3D scene still renders in software exactly as before, and the page around it stops being the slow part.+The other half of the fix was to composite the page itself on the CPU. Without that, the page went through the same software graphics device as the 3D scene, and one frame of a plain list page measured 3.5 to 15 seconds. With it, the 3D scene still renders in software exactly as before, and the page around it stops being the slow part: the same frame takes about 250 ms.The speed of the machine decides how long filming takes, not how the reel looks. The holographic sticker reel is 18.13 seconds and 544 frames long. One drag in it is 84 frames, 2.8 seconds of reel, and took 90 seconds to film.+## The browser is set up to make that possible++The whole arrangement comes down to a short list of browser flags. WebGL runs on ANGLE with the SwiftShader software device, and the two last flags move the page's own compositing and rasterising off the graphics device:++```js+const BROWSER_ARGS = [+ '--use-gl=angle', '--use-angle=swiftshader', '--enable-unsafe-swiftshader',+ '--ignore-gpu-blocklist',+ '--disable-gpu-compositing', '--disable-gpu-rasterization',+];+```++The output sizes are fixed too. A small logical viewport is deliberate: the page lays out for a small screen, so its text and controls come out large in the final frame and stay readable in a phone timeline. Three formats are built in, each a page size, a bar height under it and a device scale:++| Format | Page | Bar | Scale | Output |+|---|---|---|---|---|+| landscape | 1024 x 576 | 80 | 1.25 | 1280 x 720 |+| square | 720 x 720 | 104 | 1.5 | 1080 x 1080 |+| portrait | 540 x 675 | 108 | 2 | 1080 x 1350 |++The Machine Atlas reel is landscape, which is why its record says 1280 by 720 at 30 frames a second.+## What the bar under the page saysNothing is drawn over the product except the pointer, because a viewer needs to see what was clicked. Captions, a badge for cut waits, and a stamp sit in a bar under the page. The stamp names the site, the production commit that answered, read from the site's own version endpoint, and the day the reel was filmed.+The pointer lives in a closed shadow root hung off the page's root element, so the page's own text queries do not see it and a framework that replaces the page body does not remove it. A caption cannot hide a control, and a viewer does not have to wonder what was behind one.++++## Waiting is cut, and labelled+Waiting is not filmed. Anything that waits on the network runs on the real clock while the camera is off. If a wait lasts two seconds or more, the reel says so: a badge such as cut 6 s appears in the bar for the next second and a half. A slow feature is labelled as slow rather than hidden.-Captions are measured, not counted. Before anything is filmed, each caption is set in the real bar, beside the longest stamp and the longest badge it could share the line with, and a caption that would be cut off is refused by name. We added that check after reels were filmed with captions that ended mid-sentence.+The Drive reel shows it at work. Its record lists two cuts, 3.9 seconds and 6.3 seconds, around the moment the agent's reply is on its way, and the reel is 13.4 seconds long. A viewer sees a short, watchable clip and an honest label for the time that was left out.++Here is the Drive run, step by step, as its record lists it. The ms column is how long each step took the machine, and frames is how much of the reel it became:++| Step | Kind | Target | What the run recorded | ms | Frames |+|---|---|---|---|---:|---:|+| 1 | goto | the Drive page | loaded the page | 11198 | 0 |+| 2 | expect | Ready | appeared after 0.6 s | 563 | 0 |+| 3 | hold | 1800 | 1800 ms | 25386 | 54 |+| 4 | hover | Driving | hovered | 8649 | 18 |+| 5 | hold | 1200 | 1200 ms | 17696 | 36 |+| 6 | click | Driving | clicked | 10015 | 21 |+| 7 | expect | Parked | appeared after 0.0 s | 7 | 0 |+| 8 | click | Type | clicked | 10547 | 21 |+| 9 | type | What should I listen to on a long drive? | typed 40 characters | 48143 | 96 |+| 10 | press | Enter | pressed Enter; the chat endpoint answered 200 in 6.8 s | 7222 | 6 |+| 11 | expect | Speaking | appeared after 6.4 s | 6404 | 0 |+| 12 | hold | 5000 | 5000 ms | 78060 | 150 |++Typing the question took the machine 48.1 seconds and became 96 frames, 3.2 seconds of reel, so the viewer reads the question at the pace of a person typing. Steps 2, 7 and 11 wait for the page's own words, Ready, Parked and Speaking, to appear, so the film shows the agent actually answering and not a timer running out.++Captions are measured, not counted. Before anything is filmed, each caption is set in the real bar, beside the longest stamp and the longest badge it could share the line with, and a caption that would be cut off is refused by name. We added that check after reels were filmed with captions that ended mid-sentence, and it means each caption in a reel is read in full.## Facts come from the run, and are checked againA number in a post has to sit inside a claim, and the strongest claim is one the run read off the screen. The record of each run keeps each step, each fact read, each request awaited and each wait that was cut, together with a hash of the scenario and of the video. Change a step or swap the file and the post no longer validates. A record also expires after 14 days, because the product moves.-When a post is reviewed, the scenario runs again without the camera. A fact the post states exactly has to read the same as the reel shows. A fact stated as a floor has to stay at or above it. If either rule breaks, the post goes back to be filmed again. A post that states a count can also carry a check that runs again seconds before it is sent.+This is a real excerpt of the record behind the engine reel:++```json+{+ "id": "machine-atlas",+ "ranAt": "2026-09-29T08:08:23.156Z",+ "target": { "commit": "f2081d946", "revision": "three-ws-api-00460-4j6" },+ "passed": true,+ "facts": { "machines": "TWO", "cylinders": "9", "displacement": "29.7 L", "cylindersAfter": "5" },+ "saw": ["16.5 L", "Outside-cylinder steam locomotive", "Solved four-bar chain, not baked animation"],+ "video": { "frames": 477, "durationSec": 15.9, "width": 1280, "height": 720, "fps": 30,+ "videoCodec": "h264", "pixFmt": "yuv420p" }+}+```++When a post is reviewed, the scenario runs again without the camera. A fact the post states exactly has to read the same as the reel shows. A fact stated as a floor has to stay at or above it, so a count that keeps growing does not send a true post back to the studio. A fact no claim cites may move freely, because the reel is stamped with the day it was filmed. If a rule breaks, the post goes back to be filmed again. A post that states a count can also carry a check that runs again seconds before it is sent.++The editor that reviews a post cannot watch video, so it is given four frames from the reel spread through its length, the captions in order, and the record of the run, and asked whether each caption is true of the frame under it.++## From frames to a clip X plays at once++Frames are written as pictures, then encoded in one pass into a clip made for X: H.264 high profile, yuv420p, a constant frame rate, and the file's index placed at the front so the clip starts playing before it has finished downloading. The encoder then reads the finished file back, and the record stores its codec, pixel format, size, frame count and SHA-256, so the proof describes the exact bytes that get posted.++```bash+ffmpeg -framerate 30 -i f%06d.jpg \+ -vf "scale=trunc(iw/2)*2:trunc(ih/2)*2" \+ -c:v libx264 -profile:v high -preset slow -crf 19 \+ -pix_fmt yuv420p -r 30 -movflags +faststart -an reel.mp4+```++## What the camera holds itself to++A reel has to meet a short list of standards before it exists, and each one protects the person watching:++- **A run with a failed step has no video.** The camera saves a picture of the page at the moment the step failed, so the failure can be looked at rather than guessed at.+- **A reel has to move.** If fewer than 15% of its frames change, the reel does not validate. It is a still with a progress bar, and a still image is the honest format for it. The Machine Atlas, Drive and holographic sticker reels all record full motion.+- **A caption has to fit,** as above.+- **A browser has to draw emoji.** Before filming, the camera draws a waving hand emoji into a small canvas and counts the coloured pixels. A machine without a colour emoji font draws empty boxes, and a reel filmed there would show a page broken where it is not. So the camera checks beforehand, and says which font to install.+- **An uploaded file has to be the same file.** A scenario that uploads a file records its SHA-256, so a reel is paired with the input it filmed and no other.++## A reel is a dated receipt++Taken together, a reel is a receipt. It says that these steps passed on this commit on this day, with the facts the run read and the requests the server answered. The stamp shows the commit and the day in the corner of each frame, and the 14 day expiry keeps the receipt fresh: as the product moves, the feed carries reels that were filmed against what is live now.++A scenario checks what reaches the screen or the network, which is exactly what a person using the feature experiences. A camera flying across a map adds no text, so a visual result is proven by the request that caused it. The camera needs a browser and ffmpeg, so reels are made where posts are reviewed, and production reads the record without filming. The result is a split of duties that keeps the live service light and the evidence strong.++## Try it on your own feature++The commands that make a reel are three:++```bash+npm run x:content -- scout https://three.ws/galaxy --format square # what the page offers a scenario+npm run x:content -- prove galaxy-search # run it, film it, record the proof+npm run x:content -- prove galaxy-search --no-film # run it without filming+```++`scout` lists the controls, fields, headings and number-bearing lines of a page, which is what a person would look for before writing a scenario. `prove` runs the steps, films them and writes the record. With `--no-film` the same steps run in a fraction of the time, which is the fast path a review uses to confirm that a feature still works and still shows the facts the reel shows.++## Open tools, credited++Filming stands on open software. Playwright, released under the Apache 2.0 licence, drives the browser and gives the camera its page clock. Chromium renders the page, with ANGLE and the SwiftShader software Vulkan device carrying the WebGL scene on machines without a GPU. FFmpeg and the x264 encoder turn the frames into H.264, shipped through the ffmpeg-static package. The step runner, the camera and the proof record live in one module of the three.ws repository, so the method can be read in full.++## The partners behind the reels++three.ws builds alongside a group of cloud, AI, hardware, infrastructure and media programmes. Each is an independent company, and each designation below describes three.ws's membership or listing as it stands. The full map is at [three.ws/partners](https://three.ws/partners).++**NVIDIA.** three.ws is a member of NVIDIA Inception, NVIDIA's programme for startups building on accelerated computing. The features these reels film are the ones that run on NVIDIA silicon: text to 3D, photo to avatar, auto-rigging and motion capture, plus the free hosted NIM lane behind the forge. The reel camera itself films them in software, so the same run works on a machine with no GPU at all.++**Google Cloud.** Google Cloud powers three.ws inference, storage and real-time serving. Each reel's record names the Cloud Run revision that answered the run, shown in the excerpt above for the engine reel, and Vertex AI brings Gemini models to agents alongside the three.ws identity layer.-The editor that reviews a post cannot watch video, so it is given four frames from the reel, the captions in order, and the record of the run, and asked whether each caption is true of the frame under it.+**OpenAI.** three.ws is an OpenAI Select Partner in the OpenAI Partner Network. The free three.ws 3D Studio connector gives ChatGPT eleven keyless 3D tools, including a look at the finished model from several angles, which is the same habit this pipeline applies to its own reels: judge the result from the frames, not from the description.-## What the camera refuses to film+**IBM.** three.ws lists IBM in the Strategic tier of its partner map. Agent identity on three.ws integrates with IBM watsonx and IBM Granite, so the agents a reel like Drive films can run on enterprise models behind a single agent profile.-- **A run with a failed step.** There is no video. The camera saves a picture of the page at the moment the step failed, so the failure can be looked at rather than guessed at.-- **A reel that barely moves.** If fewer than 15% of its frames change, the reel does not validate. It is a still with a progress bar, and a still image is the honest format for it.-- **A caption that would not fit,** as above.-- **A browser that cannot draw emoji.** Before filming, the camera draws a waving hand emoji into a small canvas and counts the coloured pixels. A machine without a colour emoji font draws empty boxes, and a reel filmed there would show a page broken where it is not. So it refuses, and says which font to install.+**Amazon Web Services.** three.ws is deployed on AWS infrastructure with Marketplace availability, so enterprises can provision three.ws agent capabilities through their existing AWS billing, with support for VPC deployment and IAM-integrated access control.-Some features did not pass when we used them. They are not in this feed. Each one is written down with what happened and what was expected, for the people who fix it, rather than filmed around.+**Alibaba Cloud.** Alibaba Cloud extends three.ws into APAC markets with Qwen model integration and regional MCP server deployment, so agents reach audiences with low-latency inference close to users in Asia.-## What a reel does not prove+**Quicknode.** three.ws is a member of the Quicknode Startup Program with approved infrastructure credits. Quicknode's globally distributed RPC endpoints add capacity and redundancy to the chain access behind live Solana market data.-A reel proves that the steps passed once, on the commit in the stamp, on the day in the stamp. It does not prove the feature works on your phone, under load, or next month. That is why the stamp is there and why the record expires.+**HackerNoon.** three.ws has a builder-focused publishing partnership with HackerNoon: feature articles, tutorials and developer guides for people shipping with AI, published to HackerNoon's developer audience. The method in this article is the kind of build note that audience reads.-A scenario checks what reaches the screen or the network, and nothing else. A camera flying across a map adds no text, so a visual result has to be proven by the request that caused it. And the reels are rendered in software, so the motion is exact but the machine is slow: reels are made where posts are reviewed, not in production, which reads the record and does not film.+## Try it-The pages in these reels are live. The engine above is at three.ws/assembly.+The engine from the reel is live at [three.ws/assembly](https://three.ws/assembly): change a dimension and watch it rebuild. The holographic sticker is at [three.ws/holo](https://three.ws/holo), and the galaxy page the commands above use is at [three.ws/galaxy](https://three.ws/galaxy). The full pipeline, with the proof record format and the review rules, is documented in the repository's content pipeline guide. Production's own version endpoint, the one each stamp reads, is at [the version endpoint](https://three.ws/api/version).diff --git a/data/x-content/queue.json b/data/x-content/queue.jsonindex 59d63ae4e..7eb46d960 100644--- a/data/x-content/queue.json+++ b/data/x-content/queue.json@@ -11606,7 +11606,7 @@},{"id": "proof-reels-article",- "status": "approved",+ "status": "review","kind": "article","tier": 1,"lane": "article",@@ -11614,7 +11614,7 @@"notBefore": "2026-10-09T19:04:26.396Z","covers": [],"article": {- "title": "How our feature reels are filmed: a scripted test run against the live site",+ "title": "Nine cylinders to five in 15.9 seconds: how each three.ws feature reel is filmed as a live test run","body": "data/x-content/articles/proof-reels-article.md","cover": {"path": "public/x-media/proof-reels-article/cover.png",@@ -11623,7 +11623,17 @@},"claims": [{- "says": "If any step fails, there is no video and the feature is not announced",+ "says": "on a machine with no GPU",+ "evidence": [+ {+ "type": "file",+ "path": "api/_lib/x-content/reel.js",+ "contains": "WebGL is rendered in software, because the machines that make reels have no"+ }+ ]+ },+ {+ "says": "If any step of the run fails, no video is made, and the feature is not announced","evidence": [{"type": "file",@@ -11643,32 +11653,42 @@]},{- "says": "The page clock is stepped one frame at a time",+ "says": "On the filmed run it read 9, then 5, and it waited for the new displacement before it went on","evidence": [{"type": "file",- "path": "api/_lib/x-content/reel.js",- "contains": "await this.page.clock.runFor(this.frameMs);"+ "path": "data/x-content/proofs/machine-atlas.json",+ "contains": "\"cylinders\": \"9\""+ },+ {+ "type": "file",+ "path": "data/x-content/proofs/machine-atlas.json",+ "contains": "\"cylindersAfter\": \"5\""+ },+ {+ "type": "file",+ "path": "data/x-content/proofs/machine-atlas.json",+ "contains": "\"target\": \"16.5 L\""}]},{- "says": "1/30 of a second each",+ "says": "When the Drive reel types a question to an agent, the run waits for the chat request to answer, and an error fails the run","evidence": [{"type": "file",- "path": "api/_lib/x-content/reel.js",- "contains": "export const DEFAULT_FPS = 30;"+ "path": "data/x-content/proofs/drive-copilot.json",+ "contains": "POST /api/chat answered 200"},{"type": "file","path": "api/_lib/x-content/reel.js",- "contains": "this.frameMs = 1000 / fps;"+ "contains": "if (hit.status >= 400) throw new Error(`${hit.method} ${hit.path} answered HTTP ${hit.status}`);"}]},{- "says": "on a machine with no GPU",+ "says": "The machine that films has no GPU","evidence": [{"type": "file",@@ -11678,297 +11698,367 @@]},{- "says": "what it refuses to film",+ "says": "A headless browser renders WebGL in software at one to three frames a second, and a screen recorder pads that out by repeating frames","evidence": [{"type": "file","path": "api/_lib/x-content/reel.js",- "contains": "does not fit the bar in this format; shorten it"- },+ "contains": "software at one to three frames a second, and a recorder pads that to 25 by"+ }+ ]+ },+ {+ "says": "It advances the clock by one frame, a thirtieth of a second, takes a picture, and repeats",+ "evidence": [{"type": "file",- "path": "api/_lib/x-content/verify.js",- "contains": "the browser draws emoji as empty boxes on this machine, so reels would show the product broken"+ "path": "api/_lib/x-content/reel.js",+ "contains": "await this.page.clock.runFor(this.frameMs);"},{"type": "file","path": "api/_lib/x-content/reel.js",- "contains": "export const MIN_MOTION = 0.15;"+ "contains": "export const DEFAULT_FPS = 30;"}]},{- "says": "Each one is a scripted test run against the live site, filmed while it runs",+ "says": "On the galaxy page, recording in real time gave 1.3 distinct frames a second; stepping gave 30","evidence": [{"type": "file",- "path": "api/_lib/x-content/reel.js",- "contains": "Proof reels: a post's video is a filmed, passing end-to-end run of the"- },+ "path": "docs/x-content-pipeline.md",+ "matches": "Galaxy measured 1\\.3 distinct frames a\\s+second recorded in real time and 30 stepped"+ }+ ]+ },+ {+ "says": "one frame of a plain list page measured 3.5 to 15 seconds",+ "evidence": [{"type": "file","path": "api/_lib/x-content/reel.js",- "contains": "const response = await take.page.goto(step.goto, { waitUntil: 'domcontentloaded', timeout: 60_000 });"+ "contains": "one frame of a plain list page measured 3.5 to 15 seconds"}]},{- "says": "If any step of the run fails, no video is made, and the feature is not announced",+ "says": "the 3D scene still renders in software exactly as before","evidence": [{"type": "file","path": "api/_lib/x-content/reel.js",- "contains": "if (run.passed && film) {"+ "contains": "'--disable-gpu-compositing', '--disable-gpu-rasterization'"},{"type": "file","path": "api/_lib/x-content/reel.js",- "contains": "the last run failed"+ "contains": "still runs on SwiftShader exactly as before"+ }+ ]+ },+ {+ "says": "The holographic sticker reel is 18.13 seconds and 544 frames long",+ "evidence": [+ {+ "type": "file",+ "path": "data/x-content/proofs/holo-sticker.json",+ "contains": "\"durationSec\": 18.13,"},{"type": "file",- "path": "api/_lib/x-content/queue.js",- "contains": "problems.push(...proofProblems(item, root, now)"+ "path": "data/x-content/proofs/holo-sticker.json",+ "contains": "\"frames\": 544,"}]},{- "says": "A step can goto a page, click a control by its visible text, type into a field, press a key, drag across the scene, expect a text to appear, or read a fact off the screen with a pattern",+ "says": "One drag in it is 84 frames, 2.8 seconds of reel, and took 90 seconds to film","evidence": [{"type": "file",- "path": "api/_lib/x-content/reel.js",- "contains": "export const STEP_KINDS = ['goto', 'click', 'hover', 'type', 'press', 'expect', 'read', 'drag', 'scroll', 'wait', 'hold', 'caption'];"- },+ "path": "data/x-content/proofs/holo-sticker.json",+ "matches": "\"kind\": \"drag\",[\\s\\S]{0,200}\"ms\": 90167,\\s*\"frames\": 84"+ }+ ]+ },+ {+ "says": "Nothing is drawn over the product except the pointer",+ "evidence": [{"type": "file","path": "api/_lib/x-content/reel.js",- "contains": "const match = new RegExp(step.match, 'i').exec(scope);"+ "contains": "Only the pointer is drawn on the page, because a viewer"}]},{- "says": "These are five of the steps behind the Machine Atlas reel",+ "says": "The stamp names the site, the production commit that answered, read from the site's own version endpoint, and the day the reel was filmed","evidence": [{"type": "file",- "path": "data/x-content/queue.json",- "contains": "\"selector\": \"#ma-p-cylinders-out\""+ "path": "api/_lib/x-content/reel.js",+ "contains": "const response = await fetch(`${origin}/api/version`, { signal: AbortSignal.timeout(10_000) });"},{"type": "file",- "path": "data/x-content/queue.json",- "contains": "\"expect\": \"16.5 L\""+ "path": "api/_lib/x-content/reel.js",+ "contains": "const stamp = item.scenario.stamp === false ? '' : `live on ${host}${version?.commit ? ` @ ${version.commit}` : ''}, ${day}`;"}]},{- "says": "On the filmed run it read 9, then 5, and it waited for the new displacement before it went on",+ "says": "Anything that waits on the network runs on the real clock while the camera is off","evidence": [{"type": "file",- "path": "data/x-content/proofs/machine-atlas.json",- "contains": "\"cylinders\": \"9\""- },+ "path": "api/_lib/x-content/reel.js",+ "contains": "// Waiting is not filmed. While a step waits on the network the clock runs in"+ }+ ]+ },+ {+ "says": "If a wait lasts two seconds or more",+ "evidence": [{"type": "file",- "path": "data/x-content/proofs/machine-atlas.json",- "contains": "\"cylindersAfter\": \"5\""+ "path": "api/_lib/x-content/reel.js",+ "contains": "const CUT_BADGE_AFTER_SEC = 2;"},{"type": "file",- "path": "data/x-content/proofs/machine-atlas.json",- "contains": "\"target\": \"16.5 L\""+ "path": "api/_lib/x-content/reel.js",+ "contains": "if (seconds >= CUT_BADGE_AFTER_SEC && this.count > 0) {"}]},{- "says": "When the Drive reel types a question to an agent, the run waits for the chat request to answer, and an error fails the run",+ "says": "a badge such as cut 6 s appears in the bar for the next second and a half","evidence": [{"type": "file",- "path": "data/x-content/proofs/drive-copilot.json",- "contains": "POST /api/chat answered 200"+ "path": "api/_lib/x-content/reel.js",+ "contains": "export function formatCut(seconds) {"+ }+ ]+ },+ {+ "says": "each caption is set in the real bar, beside the longest stamp and the longest badge it could share the line with, and a caption that would be cut off is refused by name",+ "evidence": [+ {+ "type": "file",+ "path": "api/_lib/x-content/reel.js",+ "contains": "export const WIDEST_STAMP = 'live on three.ws @ 000000000, 2026-12-31';"},{"type": "file","path": "api/_lib/x-content/reel.js",- "contains": "if (hit.status >= 400) throw new Error(`${hit.method} ${hit.path} answered HTTP ${hit.status}`);"+ "contains": "throw new Error(`caption(s) too long for the ${item.scenario.format || 'landscape'} bar, shorten:"}]},{- "says": "The machine that films has no GPU",+ "says": "We added that check after reels were filmed with captions that ended mid-sentence","evidence": [{"type": "file",- "path": "api/_lib/x-content/reel.js",- "contains": "WebGL is rendered in software, because the machines that make reels have no"+ "path": "docs/ops/x-story-findings-2026-09-30.md",+ "contains": "shipped captions cut off mid-sentence"}]},{- "says": "A headless browser renders WebGL in software at one to three frames a second, and a screen recorder pads that out by repeating frames",+ "says": "together with a hash of the scenario and of the video","evidence": [{"type": "file","path": "api/_lib/x-content/reel.js",- "contains": "software at one to three frames a second, and a recorder pads that to 25 by"+ "contains": "scenarioHash: scenarioHash(item.scenario),"+ },+ {+ "type": "file",+ "path": "api/_lib/x-content/reel.js",+ "contains": "proof.video = { path, sha256: sha256File(resolve(root, path)), frames: run.frames, motion, ...probe };"}]},{- "says": "It advances the clock by one frame, a thirtieth of a second, takes a picture, and repeats",+ "says": "Change a step or swap the file and the post no longer validates","evidence": [{"type": "file","path": "api/_lib/x-content/reel.js",- "contains": "await this.page.clock.runFor(this.frameMs);"+ "contains": "the scenario changed after it was filmed; prove it again"},{"type": "file","path": "api/_lib/x-content/reel.js",- "contains": "export const DEFAULT_FPS = 30;"+ "contains": "is not the file the proof filmed"}]},{- "says": "Every frame of a reel is a distinct frame at 1/30 s of page time",+ "says": "A record also expires after 14 days","evidence": [{"type": "file","path": "api/_lib/x-content/reel.js",- "matches": "Every frame of the reel\\n// is a real, distinct frame at exactly 1/fps of page time"+ "contains": "export const PROOF_MAX_AGE_DAYS = 14;"+ }+ ]+ },+ {+ "says": "When a post is reviewed, the scenario runs again without the camera",+ "evidence": [+ {+ "type": "file",+ "path": "api/_lib/x-content/verify.js",+ "contains": "const run = await runScenario(item.scenario, { film: false, root });"+ }+ ]+ },+ {+ "says": "A fact the post states exactly has to read the same as the reel shows. A fact stated as a floor has to stay at or above it",+ "evidence": [+ {+ "type": "file",+ "path": "api/_lib/x-content/verify.js",+ "contains": "if (rule.exact && live !== filmed)"},{"type": "file",- "path": "api/_lib/x-content/reel.js",- "contains": "export const DEFAULT_FPS = 30;"+ "path": "api/_lib/x-content/verify.js",+ "contains": "under the floor of ${rule.min} the post claims"}]},{- "says": "On the galaxy page, recording in real time gave 1.3 distinct frames a second; stepping gave 30",+ "says": "A post that states a count can also carry a check that runs again seconds before it is sent","evidence": [{"type": "file",- "path": "docs/x-content-pipeline.md",- "matches": "Galaxy measured 1\\.3 distinct frames a\\s+second recorded in real time and 30 stepped"+ "path": "api/_lib/x-content/verify.js",+ "contains": "if (where === 'publish' && probe.type !== 'api') continue;"}]},{- "says": "one frame of a plain list page measured 3.5 to 15 seconds",+ "says": "The camera saves a picture of the page at the moment the step failed","evidence": [{"type": "file","path": "api/_lib/x-content/reel.js",- "contains": "one frame of a plain list page measured 3.5 to 15 seconds"+ "contains": "if (failureShot) await page.screenshot({ path: failureShot, timeout: 30_000 }).catch(() => {});"}]},{- "says": "the 3D scene still renders in software exactly as before",+ "says": "If fewer than 15% of its frames change, the reel does not validate","evidence": [{"type": "file","path": "api/_lib/x-content/reel.js",- "contains": "'--disable-gpu-compositing', '--disable-gpu-rasterization'"+ "contains": "export const MIN_MOTION = 0.15;"},{"type": "file","path": "api/_lib/x-content/reel.js",- "contains": "still runs on SwiftShader exactly as before"+ "contains": "of the reel's frames change; film an action, or post a still instead"}]},{- "says": "The holographic sticker reel is 18.13 seconds and 544 frames long",+ "says": "the camera draws a waving hand emoji into a small canvas and counts the coloured pixels","evidence": [{"type": "file",- "path": "data/x-content/proofs/holo-sticker.json",- "contains": "\"durationSec\": 18.13,"+ "path": "api/_lib/x-content/verify.js",+ "contains": "Draws an emoji and counts the pixels that carry colour."},{"type": "file",- "path": "data/x-content/proofs/holo-sticker.json",- "contains": "\"frames\": 544,"+ "path": "api/_lib/x-content/verify.js",+ "contains": "export async function emojiRendersInColor(page, text = '\\u{1F44B}') {"}]},{- "says": "One drag in it is 84 frames, 2.8 seconds of reel, and took 90 seconds to film",+ "says": "waited for the page to say 16.5 L","evidence": [{"type": "file",- "path": "data/x-content/proofs/holo-sticker.json",- "matches": "\"kind\": \"drag\",[\\s\\S]{0,200}\"ms\": 90167,\\s*\"frames\": 84"+ "path": "data/x-content/proofs/machine-atlas.json",+ "contains": "\"target\": \"16.5 L\""}]},{- "says": "Nothing is drawn over the product except the pointer",+ "says": "477 frames, 15.9 seconds","evidence": [{"type": "file",- "path": "api/_lib/x-content/reel.js",- "contains": "Only the pointer is drawn on the page, because a viewer"+ "path": "data/x-content/proofs/machine-atlas.json",+ "contains": "\"frames\": 477,"+ },+ {+ "type": "file",+ "path": "data/x-content/proofs/machine-atlas.json",+ "contains": "\"durationSec\": 15.9,"}]},{- "says": "The stamp names the site, the production commit that answered, read from the site's own version endpoint, and the day the reel was filmed",+ "says": "the chat endpoint answered 200, in 6.8 seconds","evidence": [{"type": "file",- "path": "api/_lib/x-content/reel.js",- "contains": "const response = await fetch(`${origin}/api/version`, { signal: AbortSignal.timeout(10_000) });"+ "path": "data/x-content/proofs/drive-copilot.json",+ "contains": "\"status\": 200,"},{"type": "file",- "path": "api/_lib/x-content/reel.js",- "contains": "const stamp = item.scenario.stamp === false ? '' : `live on ${host}${version?.commit ? ` @ ${version.commit}` : ''}, ${day}`;"+ "path": "data/x-content/proofs/drive-copilot.json",+ "contains": "\"seconds\": 6.8"}]},{- "says": "Anything that waits on the network runs on the real clock while the camera is off",+ "says": "the same frame takes about 250 ms","evidence": [{"type": "file","path": "api/_lib/x-content/reel.js",- "contains": "// Anything that waits on the world runs on the real clock and is not filmed."+ "contains": "the same frame takes about 250 ms"}]},{- "says": "If a wait lasts two seconds or more",+ "says": "its record says 1280 by 720 at 30 frames a second","evidence": [{"type": "file",- "path": "api/_lib/x-content/reel.js",- "contains": "const CUT_BADGE_AFTER_SEC = 2;"+ "path": "data/x-content/proofs/machine-atlas.json",+ "contains": "\"width\": 1280,"},{"type": "file",- "path": "api/_lib/x-content/reel.js",- "contains": "if (seconds >= CUT_BADGE_AFTER_SEC && this.count > 0) {"+ "path": "data/x-content/proofs/machine-atlas.json",+ "contains": "\"height\": 720,"+ },+ {+ "type": "file",+ "path": "data/x-content/proofs/machine-atlas.json",+ "contains": "\"fps\": 30,"}]},{- "says": "a badge such as cut 6 s appears in the bar for the next second and a half",+ "says": "two cuts, 3.9 seconds and 6.3 seconds","evidence": [{"type": "file",- "path": "api/_lib/x-content/reel.js",- "contains": "const CUT_BADGE_FRAMES = 45;"- },- {- "type": "file",- "path": "api/_lib/x-content/reel.js",- "contains": "await this.bar.set({ badge: `cut ${formatCut(seconds)}` });"+ "path": "data/x-content/proofs/drive-copilot.json",+ "contains": "\"seconds\": 3.9"},{"type": "file",@@ -11978,207 +12068,437 @@]},{- "says": "each caption is set in the real bar, beside the longest stamp and the longest badge it could share the line with, and a caption that would be cut off is refused by name",+ "says": "the reel is 13.4 seconds long","evidence": [{"type": "file",- "path": "api/_lib/x-content/reel.js",- "contains": "export const WIDEST_STAMP = 'live on three.ws @ 000000000, 2026-12-31';"- },+ "path": "data/x-content/proofs/drive-copilot.json",+ "contains": "\"durationSec\": 13.4,"+ }+ ]+ },+ {+ "says": "Typing the question took the machine 48.1 seconds and became 96 frames, 3.2 seconds of reel",+ "evidence": [{"type": "file",- "path": "api/_lib/x-content/reel.js",- "contains": "throw new Error(`caption(s) too long for the ${item.scenario.format || 'landscape'} bar, shorten:"+ "path": "data/x-content/proofs/drive-copilot.json",+ "matches": "\"kind\": \"type\",[\\s\\S]{0,220}\"ms\": 48143,\\s*\"frames\": 96"}]},{- "says": "We added that check after reels were filmed with captions that ended mid-sentence",+ "says": "Steps 2, 7 and 11 wait for the page's own words, Ready, Parked and Speaking, to appear","evidence": [{"type": "file",- "path": "docs/ops/x-story-findings-2026-09-30.md",- "contains": "shipped captions cut off mid-sentence"+ "path": "data/x-content/proofs/drive-copilot.json",+ "matches": "\"index\": 2,\\s*\"kind\": \"expect\",\\s*\"target\": \"Ready\""+ },+ {+ "type": "file",+ "path": "data/x-content/proofs/drive-copilot.json",+ "matches": "\"index\": 7,\\s*\"kind\": \"expect\",\\s*\"target\": \"Parked\""+ },+ {+ "type": "file",+ "path": "data/x-content/proofs/drive-copilot.json",+ "matches": "\"index\": 11,\\s*\"kind\": \"expect\",\\s*\"target\": \"Speaking\""}]},{- "says": "together with a hash of the scenario and of the video",+ "says": "H.264 high profile, yuv420p, a constant frame rate","evidence": [{"type": "file","path": "api/_lib/x-content/reel.js",- "contains": "scenarioHash: scenarioHash(item.scenario),"+ "contains": "H.264 high, yuv420p, constant frame rate,"},{"type": "file","path": "api/_lib/x-content/reel.js",- "contains": "proof.video = { path, sha256: sha256File(resolve(root, path)), frames: run.frames, motion, ...probe };"+ "contains": "'-profile:v', 'high'"+ },+ {+ "type": "file",+ "path": "api/_lib/x-content/reel.js",+ "contains": "'-pix_fmt', 'yuv420p'"}]},{- "says": "Change a step or swap the file and the post no longer validates",+ "says": "the file's index placed at the front so the clip starts playing before it has finished downloading","evidence": [{"type": "file","path": "api/_lib/x-content/reel.js",- "contains": "the scenario changed after it was filmed; prove it again"+ "contains": "moov atom first so it plays before it has finished downloading"},{"type": "file","path": "api/_lib/x-content/reel.js",- "contains": "is not the file the proof filmed"+ "contains": "'-movflags', '+faststart'"}]},{- "says": "A record also expires after 14 days",+ "says": "FFmpeg and the x264 encoder turn the frames into H.264","evidence": [{"type": "file","path": "api/_lib/x-content/reel.js",- "contains": "export const PROOF_MAX_AGE_DAYS = 14;"+ "contains": "'-c:v', 'libx264'"}]},{- "says": "When a post is reviewed, the scenario runs again without the camera",+ "says": "Playwright, released under the Apache 2.0 licence","evidence": [{"type": "file",- "path": "api/_lib/x-content/verify.js",- "contains": "const run = await runScenario(item.scenario, { film: false });"+ "path": "node_modules/playwright/package.json",+ "contains": "\"license\": \"Apache-2.0\""}]},{- "says": "A fact the post states exactly has to read the same as the reel shows. A fact stated as a floor has to stay at or above it",+ "says": "shipped through the ffmpeg-static package","evidence": [{"type": "file",- "path": "api/_lib/x-content/verify.js",- "contains": "if (rule.exact && live !== filmed)"+ "path": "package.json",+ "contains": "\"ffmpeg-static\""},{"type": "file",- "path": "api/_lib/x-content/verify.js",- "contains": "under the floor of ${rule.min} the post claims"+ "path": "api/_lib/x-content/reel.js",+ "contains": "node_modules/ffmpeg-static/ffmpeg"}]},{- "says": "A post that states a count can also carry a check that runs again seconds before it is sent",+ "says": "The pointer lives in a closed shadow root hung off the page's root element","evidence": [{"type": "file",- "path": "api/_lib/x-content/verify.js",- "contains": "if (where === 'publish' && probe.type !== 'api') continue;"+ "path": "api/_lib/x-content/reel.js",+ "contains": "The pointer lives in a closed shadow root hung off <html>, not <body>"}]},{- "says": "it is given four frames from the reel, the captions in order, and the record of the run, and asked whether each caption is true of the frame under it",+ "says": "exact names are tried before partial ones","evidence": [{"type": "file","path": "api/_lib/x-content/reel.js",- "contains": "export function reelFrames({ root, path, count = 4 }) {"+ "contains": "Exact names are tried before partial ones."+ }+ ]+ },+ {+ "says": "A control that is about to appear is waited for on the page's own clock, which is filmed",+ "evidence": [+ {+ "type": "file",+ "path": "api/_lib/x-content/reel.js",+ "contains": "A control that is about to appear is waited for on the page's clock, which"+ }+ ]+ },+ {+ "says": "A scenario that uploads a file records its SHA-256",+ "evidence": [+ {+ "type": "file",+ "path": "api/_lib/x-content/reel.js",+ "contains": "for (const upload of proof.uploads || []) {"},{"type": "file",- "path": "api/_lib/x-content/editor.js",- "contains": "whether each caption is true of the frame it sits under"+ "path": "docs/x-content-pipeline.md",+ "contains": "also records\n the file's SHA-256 in `uploads`"}]},{- "says": "The camera saves a picture of the page at the moment the step failed",+ "says": "each caption is set in the real bar, beside the longest stamp and the longest badge it could share the line with","evidence": [{"type": "file","path": "api/_lib/x-content/reel.js",- "contains": "if (failureShot) await page.screenshot({ path: failureShot, timeout: 30_000 }).catch(() => {});"+ "contains": "the same bar the camera films. The stamp and the cut badge share the bar's"+ },+ {+ "type": "file",+ "path": "api/_lib/x-content/reel.js",+ "contains": "export const WIDEST_STAMP = 'live on three.ws @ 000000000, 2026-12-31';"}]},{- "says": "If fewer than 15% of its frames change, the reel does not validate",+ "says": "Three formats are built in","evidence": [{"type": "file","path": "api/_lib/x-content/reel.js",- "contains": "export const MIN_MOTION = 0.15;"+ "contains": "landscape: { width: 1024, height: 576, bar: 80, scale: 1.25 },"+ },+ {+ "type": "file",+ "path": "api/_lib/x-content/reel.js",+ "contains": "square: { width: 720, height: 720, bar: 104, scale: 1.5 },"},{"type": "file","path": "api/_lib/x-content/reel.js",- "contains": "if (proof.video && proof.video.motion < MIN_MOTION) {"+ "contains": "portrait: { width: 540, height: 675, bar: 108, scale: 2 },"}]},{- "says": "the camera draws a waving hand emoji into a small canvas and counts the coloured pixels",+ "says": "WebGL runs on ANGLE with the SwiftShader software device","evidence": [{"type": "file",- "path": "api/_lib/x-content/verify.js",- "contains": "export async function emojiRendersInColor(page, text = '\\u{1F44B}') {"+ "path": "api/_lib/x-content/reel.js",+ "contains": "const BROWSER_ARGS = ['--use-gl=angle', '--use-angle=swiftshader', '--enable-unsafe-swiftshader', '--ignore-gpu-blocklist', '--disable-gpu-compositing', '--disable-gpu-rasterization'];"+ }+ ]+ },+ {+ "says": "it is given four frames from the reel spread through its length, the captions in order, and the record of the run",+ "evidence": [+ {+ "type": "file",+ "path": "api/_lib/x-content/reel.js",+ "contains": "export function reelFrames({ root, path, count = 4 }) {"},{"type": "file",- "path": "api/_lib/x-content/verify.js",- "contains": "canvas.width = canvas.height = 64;"+ "path": "docs/x-content-pipeline.md",+ "contains": "For a reel the editor is given four frames from it, its captions, and the record of the run"+ }+ ]+ },+ {+ "says": "three.ws is a member of NVIDIA Inception",+ "evidence": [+ {+ "type": "page",+ "url": "https://three.ws/partners",+ "contains": "three.ws is a member of NVIDIA Inception, NVIDIA's program for startups building on accelerated computing"+ }+ ]+ },+ {+ "says": "text to 3D, photo to avatar, auto-rigging and motion capture, plus the free hosted NIM lane behind the forge",+ "evidence": [+ {+ "type": "page",+ "url": "https://three.ws/partners",+ "contains": "Every 3D generation lane already runs on NVIDIA silicon: text to 3D, photo to avatar, auto-rigging, and motion capture, plus the free hosted NIM lane behind the forge."}]},{- "says": "So it refuses, and says which font to install",+ "says": "Google Cloud powers three.ws inference, storage and real-time serving",+ "evidence": [+ {+ "type": "page",+ "url": "https://three.ws/partners",+ "contains": "Google Cloud powers three.ws inference, storage, and real-time serving at global scale."+ }+ ]+ },+ {+ "says": "Vertex AI brings Gemini models to agents alongside the three.ws identity layer",+ "evidence": [+ {+ "type": "page",+ "url": "https://three.ws/partners",+ "contains": "Vertex AI integration lets agents leverage Gemini models alongside the three.ws identity and payment layer."+ }+ ]+ },+ {+ "says": "three.ws is an OpenAI Select Partner in the OpenAI Partner Network",+ "evidence": [+ {+ "type": "page",+ "url": "https://three.ws/partners",+ "contains": "three.ws is an OpenAI Select Partner in the OpenAI Partner Network."+ }+ ]+ },+ {+ "says": "eleven keyless 3D tools, including a look at the finished model from several angles",+ "evidence": [+ {+ "type": "page",+ "url": "https://three.ws/partners",+ "contains": "gives ChatGPT eleven keyless 3D tools: text to model, rigged avatars, conversational refinement, a look at the finished model from several angles"+ }+ ]+ },+ {+ "says": "three.ws lists IBM in the Strategic tier of its partner map",+ "evidence": [+ {+ "type": "page",+ "url": "https://three.ws/partners",+ "contains": "Strategic"+ }+ ]+ },+ {+ "says": "Agent identity on three.ws integrates with IBM watsonx and IBM Granite",+ "evidence": [+ {+ "type": "page",+ "url": "https://three.ws/partners",+ "contains": "three.ws 3D agent identity and x402 payment rails integrate with IBM watsonx and IBM Granite."+ }+ ]+ },+ {+ "says": "three.ws is deployed on AWS infrastructure with Marketplace availability",+ "evidence": [+ {+ "type": "page",+ "url": "https://three.ws/partners",+ "contains": "Deployed on AWS infrastructure with Marketplace availability."+ }+ ]+ },+ {+ "says": "with support for VPC deployment and IAM-integrated access control",+ "evidence": [+ {+ "type": "page",+ "url": "https://three.ws/partners",+ "contains": "with support for VPC deployment and IAM-integrated access control"+ }+ ]+ },+ {+ "says": "Alibaba Cloud extends three.ws into APAC markets with Qwen model integration and regional MCP server deployment",+ "evidence": [+ {+ "type": "page",+ "url": "https://three.ws/partners",+ "contains": "Alibaba Cloud extends three.ws into APAC markets with Qwen model integration and regional MCP server deployment."+ }+ ]+ },+ {+ "says": "three.ws is a member of the Quicknode Startup Program with approved infrastructure credits",+ "evidence": [+ {+ "type": "page",+ "url": "https://three.ws/partners",+ "contains": "three.ws is a member of the Quicknode Startup Program with approved infrastructure credits."+ }+ ]+ },+ {+ "says": "globally distributed RPC endpoints add capacity and redundancy to the chain access behind live Solana market data",+ "evidence": [+ {+ "type": "page",+ "url": "https://three.ws/partners",+ "contains": "Quicknode's globally distributed RPC endpoints add capacity and redundancy to the chain access behind agent wallets, x402 settlement verification, and live Solana market data."+ }+ ]+ },+ {+ "says": "a builder-focused publishing partnership with HackerNoon",+ "evidence": [+ {+ "type": "page",+ "url": "https://three.ws/partners",+ "contains": "A builder-focused publishing partnership: feature articles, tutorials, and developer guides for people shipping with AI, published to HackerNoon's developer audience."+ }+ ]+ },+ {+ "says": "It is a scripted test run against the live site, filmed as it runs. If any step of the run fails, no video is made, and the feature is not announced.","evidence": [{"type": "file",- "path": "api/_lib/x-content/verify.js",- "contains": "the browser draws emoji as empty boxes on this machine, so reels would show the product broken; ${EMOJI_FONT_FIX}"+ "path": "api/_lib/x-content/reel.js",+ "contains": "if (run.passed && film) {"},{"type": "file",- "path": "api/_lib/x-content/verify.js",- "contains": "export const EMOJI_FONT_FIX = 'install the COLRv1 build of Noto Color Emoji"+ "path": "api/_lib/x-content/reel.js",+ "contains": "the last run failed"+ },+ {+ "type": "file",+ "path": "api/_lib/x-content/queue.js",+ "contains": "problems.push(...proofProblems(item, root, now)"}]},{- "says": "Some features did not pass when we used them. They are not in this feed",+ "says": "Each frame of a reel is a distinct frame at 1/30 s of page time","evidence": [{"type": "file",- "path": "docs/ops/x-story-findings-2026-09-30.md",- "contains": "Features that could not be announced because they do not work"+ "path": "api/_lib/x-content/reel.js",+ "matches": "Every frame of the reel\\n// is a real, distinct frame at exactly 1/fps of page time"+ },+ {+ "type": "file",+ "path": "api/_lib/x-content/reel.js",+ "contains": "export const DEFAULT_FPS = 30;"}]},{- "says": "reels are made where posts are reviewed, not in production, which reads the record and does not film",+ "says": "A step can goto a page, click a control by its visible text, hover, upload a file, type into a field, press a key, drag across the scene, scroll, wait, hold still, expect a text to appear, or read a fact off the screen with a pattern","evidence": [{"type": "file","path": "api/_lib/x-content/reel.js",- "contains": "A browser and ffmpeg are needed, so reels are made where posts are reviewed"+ "contains": "export const STEP_KINDS = ['goto', 'click', 'hover', 'upload', 'type', 'press', 'expect', 'read', 'drag', 'scroll', 'wait', 'hold', 'caption'];"},{"type": "file","path": "api/_lib/x-content/reel.js",- "contains": "and never in production. Production checks the record (proofProblems)."+ "contains": "const match = new RegExp(step.match, 'i').exec(scope);"}]},{- "says": "The engine above is at three.ws/assembly",+ "says": "Any step can also carry a caption","evidence": [{- "type": "page",- "url": "https://three.ws/assembly",- "contains": "Radial Nine"+ "type": "file",+ "path": "api/_lib/x-content/reel.js",+ "contains": "`caption` last, because any step may carry a caption as well as its action."+ }+ ]+ },+ {+ "says": "One list of steps does four jobs at once",+ "evidence": [+ {+ "type": "file",+ "path": "api/_lib/x-content/reel.js",+ "contains": "// closes it. One list of steps is, at once:"+ }+ ]+ },+ {+ "says": "reels are made where posts are reviewed, and production reads the record without filming",+ "evidence": [+ {+ "type": "file",+ "path": "api/_lib/x-content/reel.js",+ "contains": "and never in production. Production checks the record (proofProblems)."}]}@@ -12216,7 +12536,7 @@],"posts": [{- "text": "The feature videos in this feed are scripted test runs against the live site, filmed as they run. If any step fails, there is no video and the feature is not announced. The page clock is stepped one frame at a time, 1/30 of a second each, so a heavy 3D page films smoothly on a machine with no GPU. Here is how the camera works, and what it refuses to film."+ "text": "One run opened the engine page, dragged a slider until nine cylinders became five, and was filmed at 30 frames a second: 477 frames, 15.9 seconds, stamped with the production commit. The write-up follows that run from steps to camera to proof record, with the partners and open tools behind it: three.ws/assembly"}],"mentions": {},@@ -12698,7 +13018,7 @@},{"id": "wardrobe-article",- "status": "approved",+ "status": "review","kind": "article","tier": 1,"lane": "article",@@ -14132,7 +14452,7 @@},{"id": "keeper-article",- "status": "approved",+ "status": "review","kind": "article","tier": 1,"lane": "article",diff --git a/docs/x-article-author-brief.md b/docs/x-article-author-brief.mdindex f1bc2afc6..3dc1805fb 100644--- a/docs/x-article-author-brief.md+++ b/docs/x-article-author-brief.md@@ -45,6 +45,20 @@ For each article, all under its own id:Optionally a `scenario`, filmed with `prove`, when the article's subject is a feature a reel canshow: the reel then rides on the quote post.+## Use all of the room X gives an Article++The quality gate (`articleProblems` in `api/_lib/x-content/queue.js`) refuses to review or approve an+Article that leaves X's limits unused. Every Article needs:++- A title of 80 to 100 characters (X allows 100) that carries the headline number.+- 2,400 or more words across 8 or more `##` sections, each named for what the reader learns, that+ explain the job in depth: the plain-words version first, then the mechanism.+- 3,000 or more characters of real code and tables (X allows 10,000 in code blocks and tables).+- 4 or more inline images, each a real capture of the thing described.+- A `## The partners behind ...` section that thanks every partner listed on three.ws/partners, each+ with its designation stated exactly as that page states it, and what their programme made possible.+- A `## Try it` section linking the live pages.+## Boundaries- Only create the files above, plus the reel and proof `prove` writes. Do not editdiff --git a/docs/x-content-pipeline.md b/docs/x-content-pipeline.mdindex 1460686ec..1c5a5afc8 100644--- a/docs/x-content-pipeline.md+++ b/docs/x-content-pipeline.md@@ -123,7 +123,7 @@ X Articles require the posting account to be on X Premium.- `claims` is the fact ledger. Every number, ordinal, and absolute word (first, only, every, never, fastest) in the copy must sit inside some claim's `says`, every `says` must quote the copy, and every claim carries at least one piece of `evidence` (types below).- `mentions` maps each @handle in the copy to the reason the tag is true. A tag with no reason is blocked.- `textFrom` is optional. When set, `check` fails if the inline text differs from that announcement-pack file, so the copy that was reviewed is the copy that ships.-- An `article` item carries `"article": { "title", "body", "cover": { "path" } }`, and its optional `posts` quote the published Article. The body is copy like any post: its prose (headings, paragraphs, lists and quotes; code blocks and tables are literal samples and exempt) goes through the same language lint and claims ledger, so a number in the fourth section needs evidence like one in the title, its links are resolved at review, and its words are spell-checked. Replacing an inline image makes the review stale, the same as editing the Markdown.+- An `article` item carries `"article": { "title", "body", "cover": { "path" } }`, and its optional `posts` quote the published Article. The body is copy like any post: its prose (headings, paragraphs, lists and quotes; code blocks and tables are literal samples and exempt) goes through the same language lint and claims ledger, so a number in the fourth section needs evidence like one in the title, its links are resolved at review, and its words are spell-checked. Replacing an inline image makes the review stale, the same as editing the Markdown. An Article in `review` or `approved` must also use the room X allows (owner, 2026-10-11): a title of 80 to 100 characters, 2,400 or more words in 8 or more sections, 3,000 or more characters of code and tables, 4 or more inline images, a "The partners behind ..." section covering every partner on `pages/partners.html`, and a "Try it" section. Drafts are exempt so work in progress can be saved.Cadence lives at the top of the file: `slots` (each `{ tier, at }` in UTC, or a kind slot `{ kind, at, everyDays, from }`, below), `windowMinutes` (how far a slot's opening may be jittered), `minimumMinutesApart`, `dailyCap`, and `quietHoursUtc` (a `["HH:MM", "HH:MM"]` pair, which may wrap midnight). `quality` sets the similarity limits, the maximum same-lane and same-pattern runs, and `maximumLength`: the longest a post may be, in weighted characters. @trythreews is on X Premium, so the queue sets it above the standard 280; a value under 280 is ignored. `approval` is the policy described below.diff --git a/public/x-media/proof-reels-article/reel-sticker.png b/public/x-media/proof-reels-article/reel-sticker.pngnew file mode 100644index 000000000..a776b5e58Binary files /dev/null and b/public/x-media/proof-reels-article/reel-sticker.png differdiff --git a/tests/x-content.test.js b/tests/x-content.test.jsindex cf9a2d3f7..8e786cc48 100644--- a/tests/x-content.test.js+++ b/tests/x-content.test.js@@ -553,8 +553,38 @@ describe('queue', () => {article: { title: 'How rigs get named', body: 'data/x-content/articles/demo.md', cover: { path: 'public/x-media/t/a.png' } },posts: [{ text: 'The long version of how Rig Doctor reads a skeleton.' }],};- expect(validateItem(item, dir)).toEqual([]);- expect(validateItem({ ...item, article: { ...item.article, cover: undefined } }, dir).join('\n')).toMatch(/cover/);+ const draft = { ...item, status: 'draft' };+ expect(validateItem(draft, dir)).toEqual([]);+ expect(validateItem({ ...draft, article: { ...item.article, cover: undefined } }, dir).join('\n')).toMatch(/cover/);+ });++ it('holds an Article for review to the depth the X Article limits allow', () => {+ const dir = sandbox();+ const short = '## Why\n\nBecause.\n\n\n\nThe end.';+ writeFileSync(join(dir, 'data/x-content/articles/demo.md'), short);+ const item = {+ id: 'demo', status: 'review', kind: 'article', tier: 1, lane: 'article', pattern: 'longform', notBefore: '2026-09-17T14:00:00Z',+ article: { title: 'How rigs get named', body: 'data/x-content/articles/demo.md', cover: { path: 'public/x-media/t/a.png' } },+ posts: [{ text: 'The long version of how Rig Doctor reads a skeleton.' }],+ };+ const problems = validateItem(item, dir).join('\n');+ for (const pattern of [/title is \d+ characters/, /body is \d+ words/, /\d+ sections/, /code blocks and tables total/, /inline images/, /The partners behind/, /"Try it"/]) expect(problems).toMatch(pattern);++ mkdirSync(join(dir, 'pages'), { recursive: true });+ writeFileSync(join(dir, 'pages/partners.html'), '<h3 class="partner-name">Acme Cloud</h3><h3 class="partner-name">Globex</h3>');+ const sentence = 'Each stage reads the file, names what it found and hands the result to the next stage in plain words. ';+ const section = (title) => `## ${title}\n\n${sentence.repeat(26)}\n\n`;+ const code = '```js\n' + 'const stage = run(input);\n'.repeat(120) + '```\n\n';+ const image = (name) => `\n\n`;+ const full = (partners) => ['One', 'Two', 'Three', 'Four', 'Five', 'Six'].map(section).join('') + code + image('a') + image('b') + image('a') + image('b')+ + `## The partners behind the work\n\n${partners}\n\n## Try it\n\nOpen three.ws/rig-doctor.\n`;+ const longTitle = 'How a skeleton gets its name in 41 steps, and what each step tells you about every humanoid rig';+ const deep = { ...item, article: { ...item.article, title: longTitle } };+ writeFileSync(join(dir, 'data/x-content/articles/demo.md'), full('Thanks to Acme Cloud for the compute.'));+ expect(validateItem(deep, dir).join('\n')).toMatch(/does not cover Globex/);+ writeFileSync(join(dir, 'data/x-content/articles/demo.md'), full('Thanks to Acme Cloud for the compute and Globex for the review.'));+ const left = validateItem(deep, dir).filter((problem) => /article (title|body)|code blocks|inline images|partners|Try it/.test(problem));+ expect(left).toEqual([]);});});