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-grok): log order 041, creation JSON-LD shipped and xAI documents no user-agent token

nirholascfc272364626
diff --git a/prompts/finish/_context/x-grok-PROGRESS.md b/prompts/finish/_context/x-grok-PROGRESS.md
index aca8fd329..99979541b 100644
--- a/prompts/finish/_context/x-grok-PROGRESS.md
+++ b/prompts/finish/_context/x-grok-PROGRESS.md
@@ -26,3 +26,10 @@ Cross-session handoff for the `x-grok-` orders ([x-grok-00-CONTEXT.md](x-grok-00
- Shipped `ab198d4ff`: migration `api/_lib/migrations/20261008170000_x_mention_events.sql`, `api/_lib/x-mention-store.js` (`recordMention`, `updateDecision`, `countByAuthor`, `recentDecisions`, `getMentionEvent`, `getCursor`, `advanceCursor`, `cursorKey`), 18 PGlite tests in `tests/x-mention-store.test.js` built from the migration file itself, including the dedupe race (three concurrent inserts, one wins).
- Schema notes for later orders: `decision` is null until decided and also allows `pending` (052 follow-ups) and `paused` (055 kill switch) beyond the order's list. `reply_tweet_id` is set once and never replaced. Cursor key is `x_mentions_cursor:<kind>:<ref>` and only moves forward (numeric compare in SQL).
- Remaining DoD line: "`npm run db:migrate` applied". Not run because `db:status` showed another pending migration, `20261008150000_revenue_direct_settle_backfill.sql`, untracked (uncommitted, another session's in-flight work) and a payout-ledger backfill, and the owner instruction for this run was not to apply when that is the case. Owner of the last step: whoever lands that backfill (or the owner). Then `npm run db:status` and `npm run db:migrate` apply both; or apply just this one with `node scripts/apply-migrations.mjs --apply --file 20261008170000_x_mention_events.sql`. Until then `db:check` reports it pending and blocks a deploy, as it already did for the backfill.
+
+## 2026-10-08: order 041 (legible to Grok) done
+
+- Shipped `3ce212575`: `api/_lib/creation-jsonld.js` (one builder for creation structured data: GLB as a `model/gltf-binary` MediaObject `encoding`, `/api/render/glb` PNG as `thumbnailUrl`, creator, date, `/legal/tos` as `license`), `server/creation-head.mjs` (per-creation head on `/m/:id` for every User-Agent, wired into `server/index.mjs` and the Vite dev server), enriched JSON-LD on `/forge/share/:id`, `/avatars/:id` and `/agents/:id`, `public/robots.txt`, `docs/seo.md`, changelog, tests in `tests/legible-to-grok.test.js` plus three handler suites. Order file deleted in that commit.
+- Measured: xAI documents NO crawler or live-user user-agent token. Checked `docs.x.ai/llms.txt`, the full `llms-full.txt` (1.6 MB, zero `user-agent`/`robots` hits) and the Grok Bot security docs, which only say hosted computers egress through shared static IPs available from the account team. Third-party directories list `GrokBot`, `xAI-Grok`, `Grok-DeepSearch`, `xAI-SearchBot`, but none is xAI-published, so none was added. Grok falls to `User-agent: *`, which now allows `/api/render/glb`.
+- Measured: the production render endpoint returns a real 1200x630 PNG for a live forge GLB (195 KB), so every creation card and thumbnail points at a working image.
+- For later orders: Grok Bot browses with a stock browser UA, so the UA-routed crawler pages (`/avatars/:id`, `/agents/:id`, vercel.json `has` user-agent lists) never reach it; `/m/:id` is the only creation page whose structured data every reader gets. Extending the same head rewrite to the avatar and agent shells is the follow-up if Grok Bot reads those links.