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-account-appeal): say where appeal #2 gets filed, and name the second queue

nirholas09bb5a9bcaeb
diff --git a/docs/x-account-appeal.md b/docs/x-account-appeal.md
index af30fdfc6..2f1518dcf 100644
--- a/docs/x-account-appeal.md
+++ b/docs/x-account-appeal.md
@@ -337,7 +337,20 @@ reviewer to link two accounts that X has no reason to look at together.
## 5b. Appeal #2, drafted and ready to file
**Status: written, NOT yet filed.** Filing is the owner's action; add a line
-to the filing log the moment it goes in. Appeal #1 was denied on 2026-09-05,
+to the filing log the moment it goes in.
+
+**Where it goes:**
+[`help.x.com/en/forms/account-access/appeals`](https://help.x.com/en/forms/account-access/appeals),
+logged in as `@nichxbt` so the handle and email pre-fill, which is the same
+form appeal #1 went through. There is a second, non-duplicate channel worth
+using alongside it:
+[`help.x.com/en/forms/account-restoration/locked`](https://help.x.com/en/forms/account-restoration/locked)
+("Your Account is locked"). X's own denial calls this a lock, so filing the
+lock form is answering X in X's own terms rather than refiling the same
+appeal twice, and it puts the notice-versus-state discrepancy in front of a
+different queue. Both render only in a real browser. An EU variant of the
+lock form exists (`account-restoration/locked-eu`) and does not apply from
+the US; see section 7 point 5 on why EU routes are not available here. Appeal #1 was denied on 2026-09-05,
so section 6 step 5 applies: reworded, and carrying a fact the first one did
not have. It carries three.