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.

docs(x-content): make the keeper X Article the standard every future post and article is written and reviewed against

nirholas209473437b3b
diff --git a/api/_lib/x-content/editor.js b/api/_lib/x-content/editor.js
index 6b9bae1e4..45b2dcb32 100644
--- a/api/_lib/x-content/editor.js
+++ b/api/_lib/x-content/editor.js
@@ -39,6 +39,8 @@ 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.
+
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.
Rules for your output:
diff --git a/docs/x-article-author-brief.md b/docs/x-article-author-brief.md
index 4a8d90224..ee9aed75c 100644
--- a/docs/x-article-author-brief.md
+++ b/docs/x-article-author-brief.md
@@ -17,9 +17,14 @@ they finish. The boundaries below are what keep them from overwriting each other
2. [docs/announce-voice.md](./announce-voice.md): the contract the AI editor holds every word to.
3. [docs/x-story-authoring.md](./x-story-authoring.md): claims, evidence, probes and scenarios. An
article uses the same machinery as a post.
-4. The worked example: the item `three-hold-article` in `data/x-content/queue.json` and its body
- `data/x-content/articles/three-hold-to-access.md`. Plain first person plural, a concrete opening,
- real numbers, one code sample that shows the mechanism, and the limits said out loud.
+4. **The worked example, and the standard every future Article and post is held to** (owner,
+ 2026-10-10): the item `keeper-article` in `data/x-content/queue.json`, its body
+ [`data/x-content/articles/keeper-article.md`](../data/x-content/articles/keeper-article.md), and
+ its media under `public/x-media/keeper-article/`. Read it end to end before writing a word. It
+ opens on one real job told as a story with its real numbers, follows that one job through every
+ stage of the pipeline, explains each mechanism in plain language before the technical detail,
+ shows a call any reader can run, credits the open models it builds on, carries a full partners
+ section, and ends on the pages to try. Match its shape, voice, depth and framing.
5. [docs/ops/x-story-findings-2026-09-30.md](./ops/x-story-findings-2026-09-30.md): surfaces found
broken or not filmable. Do not build an article on one of them.
@@ -61,21 +66,48 @@ show: the reel then rides on the quote post.
## What good looks like
-- **Title:** under 100 characters, a plain statement of what the reader learns. Not a teaser.
-- **Length:** 800 to 1,600 words. Long enough to teach something, short enough to finish.
-- **Opening:** the strongest true thing first, as news, in two or three sentences. A reader who
- stops after the first paragraph should still know what we built and why it matters.
-- **Shape:** three to six `##` sections. Each section earns its place with a mechanism, a number,
- a picture or a limit. One code block at most where it shows the mechanism better than prose
- (code and tables share a 10,000 character budget).
-- **Images:** two to four inline images, each a real capture of the live product or a frame from a
- filmed reel, each with a caption that says what the reader is looking at. No stock art, no
+Every bullet below is something the keeper article does; open it beside your draft and check each one.
+
+- **Title:** under 100 characters, a plain statement of what the reader learns, with the headline
+ number in it when there is one. Not a teaser. Keeper: "One sentence to a rigged, talking 3D
+ character in 197 seconds: each stage, as it ran".
+- **Opening:** one real run, told as a short story, in plain words anyone can follow: what we sent,
+ what came back, how long it took, with the real numbers. Then one paragraph that says what the
+ article covers and that every number in it can be checked. A reader who stops there still knows
+ what we built and why it matters.
+- **One thread through the whole piece:** pick one real job (one prompt, one avatar, one request)
+ and follow it from start to finish, quoting what the server actually said at each stage. Every
+ section advances the same job, so the article reads as one story rather than a feature list.
+- **Plain first, technical after:** each section opens with what the stage does and why it exists in
+ a sentence a newcomer understands ("A mesh is a statue. To move, it needs joints"), then gives
+ the mechanism, the model, the hardware and the measured numbers.
+- **Length:** expand. 1,800 to 2,800 words, as much relevant, verified information as the subject
+ holds. Never trim a draft for length; cut only what is untrue or unverifiable.
+- **Shape:** eight to twelve `##` sections, each named for what the reader learns in it. One or two
+ short code blocks where they show the mechanism better than prose, ideally a request the reader
+ can paste and run unchanged (code and tables share a 10,000 character budget).
+- **Images:** three or four inline images, each a real capture of the live product or a frame from a
+ filmed run, each with a caption that says exactly what the reader is looking at. No stock art, no
mockups, no generated illustrations of things that do not exist.
- **Cover:** 1600x900, the product itself at its most striking (a real capture with site chrome
hidden), no words on it. X crops covers on the card, so keep the subject centred.
-- **Limits:** say what it does not do yet, plainly. It is what makes the rest believable.
-- **Ending:** where to try it, with the link. No call-to-action slogans.
-- **Quote post:** 150 to 400 characters that stand on their own as news and point at the article.
+- **Positive framing only:** nothing negative is posted. No losses, outages, incidents, bugs,
+ "honest limitations" sections or disparaging contrasts. A fallback is told as resilience ("the
+ ladder delivered a reference picture without waiting on any single provider"), a boundary as a
+ design choice, and anything unfinished as what is next ("rolling out", "on the roadmap"). Never
+ fabricate to fill the gap: if a fact cannot be framed positively and truthfully, leave it out.
+- **Credit open work:** name the open models and research the feature builds on, with their licence
+ and venue, in their own short section.
+- **Partners section, every time:** a `## The partners behind ...` section near the end, one bold
+ paragraph per programme, each stating the designation exactly as
+ [three.ws/partners](https://three.ws/partners) states it and then how that partner shows up in
+ this article's feature. Never upgrade a designation, and never present a pending listing as live.
+ Copy the keeper article's list as the starting point and re-verify each line against `/partners`.
+- **Ending:** a `## Try it` section with the live pages to use, each as a link: the browser version,
+ the developer docs, and the free tools that let a reader check the result. No call-to-action
+ slogans.
+- **Quote post:** 150 to 400 characters that stand on their own as news: the headline result with
+ its numbers, then what the article covers.
## How to work
diff --git a/docs/x-story-author-brief.md b/docs/x-story-author-brief.md
index f9287dfb2..dfddb43c6 100644
--- a/docs/x-story-author-brief.md
+++ b/docs/x-story-author-brief.md
@@ -9,10 +9,17 @@ finish, so the boundaries below are what keep ten authors from overwriting each
1. [docs/x-story-authoring.md](./x-story-authoring.md): how to write and film a story.
2. [docs/announce-voice.md](./announce-voice.md): the contract the AI editor holds every post to.
-3. `data/x-content/queue.json`: the item `wardrobe` is the worked example that passed review with
- a 5 on every dimension. Match its quality. Read the text of every item with status `posted`
- so you do not repeat one.
-4. [docs/ops/x-story-findings-2026-09-30.md](./ops/x-story-findings-2026-09-30.md): the surfaces
+3. `data/x-content/queue.json`: the item `wardrobe` is the worked example of a post's format
+ (reel, head, replies) that passed review with a 5 on every dimension. Read the text of every
+ item with status `posted` so you do not repeat one.
+4. **The house standard for voice and framing** (owner, 2026-10-10): the X Article
+ [`data/x-content/articles/keeper-article.md`](../data/x-content/articles/keeper-article.md) and
+ its quote post (item `keeper-article`). Every post is held to it, compressed: lead with one real
+ result and its real numbers, say what it does in plain words before the mechanism, frame
+ everything positively, and name the partner programme the feature genuinely runs on. The
+ article brief's [What good looks like](./x-article-author-brief.md#what-good-looks-like) lists
+ each quality.
+5. [docs/ops/x-story-findings-2026-09-30.md](./ops/x-story-findings-2026-09-30.md): the surfaces
already found broken or not filmable. Do not spend time on those.
## The deliverable
@@ -81,7 +88,9 @@ production and has been filmed, so that `public/x-media/<id>/reel.mp4` and
off in the story's format (about 40 characters is safe in square).
- Head post that opens with the strongest true statement as news, in plain words, and stands on
its first 280 characters; then the mechanism. 250 to 600 characters is the usual range.
-- One or two replies with the detail, the limits and what to do next.
+- One or two replies with the detail, the partner it runs on and what to do next. Nothing negative:
+ a boundary is a design choice, anything unfinished is what is next, and a fact that cannot be
+ framed positively and truthfully is left out.
- One link, in the head or the first reply as assigned; alternate between stories.
- Openings that differ from each other and from every posted item.
- `"notBefore"` set to tomorrow, `"probes"` starting with `{ "type": "scenario" }`, an `api`
diff --git a/docs/x-story-authoring.md b/docs/x-story-authoring.md
index 374056098..b6b1bd11c 100644
--- a/docs/x-story-authoring.md
+++ b/docs/x-story-authoring.md
@@ -194,7 +194,12 @@ The reel shows that it works. The post says why anyone should care.
- **Go long when there is more to say.** Posts over 280 characters measure about twice the likes
of shorter ones on this account. Long is not padded: every sentence carries a fact.
- **A thread for the detail.** The head makes the point. One or two replies carry the numbers,
- the limits, and what to do next.
+ the partner it runs on, and what to do next.
+- **Positive framing only.** Nothing negative goes out: no outages, losses, bugs or "limitations".
+ A fallback is resilience, a boundary is a design choice, unfinished work is what is next. Never
+ fabricate to fill the gap. The keeper X Article
+ ([`keeper-article.md`](../data/x-content/articles/keeper-article.md)) is the house standard for
+ voice and framing; a post is that article compressed.
- **One link, to the surface.** Put it in the head or in the first reply. The queue measures both
placements, so alternate: if the last story you wrote linked in the head, link this one in the
reply.