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(nvidia): stamp the Inception five-ask email as sent on 2026-09-04

nirholas20b1bd378da0
diff --git a/docs/nvidia-apps-catalog-listing.md b/docs/nvidia-apps-catalog-listing.md
index 62d3012f0..320256531 100644
--- a/docs/nvidia-apps-catalog-listing.md
+++ b/docs/nvidia-apps-catalog-listing.md
@@ -35,7 +35,7 @@ Remove and leave unchecked:
### 2. Ask for the catalog listing
-The portal has no "publish to catalog" button, so the request goes to the program team. Send the email in [nvidia-apps-catalog-request.md](./nvidia-apps-catalog-request.md) to `[email protected]` after the record corrections above are saved, and note the send date there.
+The portal has no "publish to catalog" button, so the request goes to the program team. Send the email in [nvidia-apps-catalog-request.md](./nvidia-apps-catalog-request.md) to `[email protected]` after the record corrections above are saved, and note the send date there. **Sent 2026-09-04.** The ask is now with NVIDIA; nothing further to submit unless they ask for a form or assets.
---
diff --git a/docs/nvidia-apps-catalog-request.md b/docs/nvidia-apps-catalog-request.md
index b76cde18c..bb80c452b 100644
--- a/docs/nvidia-apps-catalog-request.md
+++ b/docs/nvidia-apps-catalog-request.md
@@ -7,7 +7,7 @@ The Inception portal has no "publish to the catalog" control. A product record m
- **Subject:** three.ws (Inception member): catalog listing, Showcase, and co-marketing
- **From:** the address on the Inception portal account
-- **Sent:** not yet sent. Record the date here when it goes out.
+- **Sent:** 2026-09-04, 2:20 PM, from [email protected]. Follow up on ask 1 only if there is no reply by **2026-09-25**, and use the "Maximize Your Membership" webinar Q&A to raise asks 2 and 3 live in the meantime.
---
@@ -192,7 +192,7 @@ Screenshots are deliberately not attached. The email offers them on request, whi
## After you send
-1. Record the send date in the **Sent** field at the top of this doc.
+1. Send date recorded in the **Sent** field at the top of this doc.
2. File the second product record, the `<agent-3d>` digital-human embed. Copy is ready in [nvidia-apps-catalog-listing.md](./nvidia-apps-catalog-listing.md) under "Second product record". It targets the Digital Humans workload filter that the main record does not, and it is independent of the reply.
3. Route each reply:
diff --git a/docs/nvidia-visibility-map.md b/docs/nvidia-visibility-map.md
index 5ef216c00..7d4fcda84 100644
--- a/docs/nvidia-visibility-map.md
+++ b/docs/nvidia-visibility-map.md
@@ -247,13 +247,19 @@ Recorded so the next person does not repeat the search.
One thread, one address. Every ask in Tier 1 goes to the same inbox, so batch
them into a single email rather than sending four.
-**Done: the batched email is written.** [nvidia-apps-catalog-request.md](./nvidia-apps-catalog-request.md)
-now carries all five asks (catalog listing, Showcase nomination, co-marketing kit,
-ACE redirect, GTC pavilion and event slots) in one thread. Do not start a second
-one. It is still gated on the portal record correction, which is step 1 of
-[nvidia-apps-catalog-listing.md](./nvidia-apps-catalog-listing.md): as filed the
-record reads as a CUDA consumer, which undercuts the first two asks. Correct the
-record, save it, then send and stamp the date in the request doc.
+**Sent 2026-09-04.** [nvidia-apps-catalog-request.md](./nvidia-apps-catalog-request.md)
+carries all five asks (catalog listing, Showcase nomination, co-marketing kit,
+ACE redirect, GTC pavilion and event slots) and went to the inbox in one thread
+from [email protected]. **Do not start a second thread.** Tier 1 items 2 and 4
+above are now pending NVIDIA rather than pending us. Reply routing for each ask,
+and the 2026-09-25 follow-up date, live in the request doc.
+
+Still ours to finish regardless of the reply: the portal record correction (step 1
+of [nvidia-apps-catalog-listing.md](./nvidia-apps-catalog-listing.md)), because a
+curator who opens the record after reading the email should not find a CUDA
+consumer with DeepVariant checked, and the second product record for the
+`<agent-3d>` embed, which targets the Digital Humans workload filter the main
+record does not.
## Verification log