Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
docs(x-content): describe the three-a-day quota, the yielding veto and the missed-slot alerts
nirholas2195b8245aa6
diff --git a/docs/x-content-pipeline.md b/docs/x-content-pipeline.mdindex 2d6027b43..8e545535e 100644--- a/docs/x-content-pipeline.md+++ b/docs/x-content-pipeline.md@@ -131,7 +131,14 @@ Cadence lives at the top of the file: `slots` (each `{ tier, at }` in UTC), `win**When:** three slots a day, one per tier, eight hours apart, every day of the week: T3 at 04:00 UTC, T2 at 12:00, T1 at 20:00. That cadence is the owner's (2026-09-20): three a day, weekends included. It replaced a tighter window drawn from the volume study, which measured every original post against 1-minute candles of the $THREE pool and found that a post between 12:00 and 20:00 UTC was followed by a volume response about 1.7 times as often as one outside it. Two of the three slots still sit in that window; the third takes the off-peak turn so the day stays evenly spaced. Each slot opens at a minute only the production seed can reproduce (up to `windowMinutes` late), and stays open for three hours (`slotOpenMinutes`), so a missed run or a deploy still posts, but no slot is ever spent twice. Slots are at least `minimumMinutesApart` apart even at their latest opening, so an earlier post never blocks a later slot. There are no quiet hours: with fixed slots eight hours apart, the slot times already say when the account posts. `flagshipWeekdaysOnly` would withhold the T1 slot on Saturday and Sunday and keep T1 posts out of the lower slots too; the queue no longer sets it, and it is the one lever that would return the account to weekdays-only flagships.-**What:** the slot's own tier first, highest priority first. Priority leads with **volume**, not engagement: [`data/x-content/volume-model.json`](../data/x-content/volume-model.json) is a logistic model fitted on every original post moment, and it gives each draft a chance of being followed by a volume response on the pool (the first hour after the post running at least twice the hour before). Pool volume is what pays creator rewards, so it outranks attention. The model rewards what the data rewarded: announcing something shipped, partner or recognition language, naming a tier-1 company, more than 180 characters, and a thread rather than a single post. `npm run x:content -- plan` prints each post's chance and the attributes found on it. If the model file is missing, the older engagement estimate takes over. Refit and re-export it from the study repo with `node analyze/volume-chart.mjs --asset three --export-model <this repo>/data/x-content/volume-model.json --export-exclude cryptoNative`. An empty tier falls to the next tier down, so the best available post always gets the best time. A higher tier only fills a lower slot when it has more than one post ready, so the last flagship post is kept for prime time. When nothing is ready, nothing posts: three a day is a ceiling, not a quota.+**Three a day is a quota** (owner, 2026-09-30), so a slot is never left empty while a post exists+to fill it. A post the policy released is embargoed only so the owner can take it back; when a slot+opens with nothing else ready, that embargo yields, the post goes out, and an alert says so. An+embargo the owner set by hand is never shortened. A tick that finds an open slot with nothing to+post raises an alert at once, and any slot that closed unfilled in the last day is raised once as+missed. The cure for either is stock: `npm run x:content -- advance --ship`.++**What:** the slot's own tier first, highest priority first. Priority leads with **volume**, not engagement: [`data/x-content/volume-model.json`](../data/x-content/volume-model.json) is a logistic model fitted on every original post moment, and it gives each draft a chance of being followed by a volume response on the pool (the first hour after the post running at least twice the hour before). Pool volume is what pays creator rewards, so it outranks attention. The model rewards what the data rewarded: announcing something shipped, partner or recognition language, naming a tier-1 company, more than 180 characters, and a thread rather than a single post. `npm run x:content -- plan` prints each post's chance and the attributes found on it. If the model file is missing, the older engagement estimate takes over. Refit and re-export it from the study repo with `node analyze/volume-chart.mjs --asset three --export-model <this repo>/data/x-content/volume-model.json --export-exclude cryptoNative`. An empty tier falls to the next tier down, so the best available post always gets the best time. A higher tier only fills a lower slot when it has more than one post ready, so the last flagship post is kept for prime time. When nothing is ready, nothing posts, and the tick says so loudly (see the quota paragraph above).**Priority** is a sum of named parts, and `npm run x:content:plan` prints them for every post: