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(marketing): add the twelve-week $THREE utility season rebuilt around what works in production

Nicholasa34987dd4944
diff --git a/marketing/three-utility-season/01-access-tiers.md b/marketing/three-utility-season/01-access-tiers.md
new file mode 100644
index 000000000..31499f260
--- /dev/null
+++ b/marketing/three-utility-season/01-access-tiers.md
@@ -0,0 +1,83 @@
+# Edition 01: What $THREE does this week, hold-to-access tiers
+
+| Field | Value |
+|---|---|
+| Campaign id | `MKT-2026-09-THREE-ACCESS` |
+| Publish date | 2026-09-18 |
+| Chapter | Access |
+| Audience | community and holders |
+| Campaign anchor (campaigns.csv) | https://three.ws/three-token |
+| Surface used in this pack | /three |
+| Verified status (2026-09-16) | **Live** |
+
+## Verification
+
+**Substitute:** None. The copy links `/three` (the tier page) instead of the campaign anchor `/three-token` (the token overview), because the tier check happens on `/three`.
+
+- Route: `vercel.json` maps `/three/?` to `pages/three.html`; the page is driven by `src/three-tier-page.js`.
+- API: `GET https://three.ws/api/three/tier` (handler `api/three/[action].js`, ladder in `api/_lib/three-tier.js`) answered 200 on 2026-09-16 with the five-level ladder. Passing `?wallet=<address>` returned a resolved tier for a real holder wallet.
+- Perk registry: `GET https://three.ws/api/three/access` (from `api/_lib/three-access.js`) reports `forge.high` and `forge.gameready` with `enforced: true`; the other five perks are `enforced: false` and the page labels them PLANNED.
+
+## The three questions
+
+- **What can a holder do now?** Open `/three`, connect a Solana wallet, read the tier shown, then open one LIVE perk (Forge Max at `/forge-max`).
+- **Where does $THREE enter?** Nowhere is $THREE spent. The platform reads the USD value of $THREE held in the connected wallet and maps it to a tier (Member $0, Bronze $25, Silver $100, Gold $500, Genesis $2,500).
+- **What verifiable result comes out?** The page shows the wallet's tier, the USD still needed for the next one, and which perks are LIVE versus PLANNED. The same resolution is readable as JSON at `/api/three/tier?wallet=`.
+
+## Numbers and their sources
+
+| Stable fact | Source and capture date |
+|---|---|
+| Tier thresholds: $25 / $100 / $500 / $2,500 held | `/api/three/tier` ladder, captured 2026-09-16 |
+| Bronze perks marked LIVE: High-quality generation, Game-Ready export | `/api/three/access`, captured 2026-09-16 |
+| 2 of 7 registered perks enforced | `/api/three/access` (`enforced: true` count), captured 2026-09-16 |
+
+## Media
+
+- File: [`images/01-access-tiers.png`](./images/01-access-tiers.png), 1600x900, captured 2026-09-16 from `/three` by `node marketing/three-utility-season/capture.mjs --only 01`.
+- Alt text (required on every post):
+
+> The three.ws $THREE Tiers page: a Connect wallet button above the tier ladder. Bronze requires $25 held and lists 5% off compute, 2x free quota, and two perks marked LIVE: high-quality generation and Game-Ready export. Silver's private worlds are marked PLANNED.
+
+## X post
+
+Weighted length: **174 characters** (URL counted as 23, as `scripts/post-tweet.mjs` does).
+
+```text
+Your $THREE tier on three.ws is read live from your wallet. Bronze starts at $25 held and opens High-quality Forge and Game-Ready export. Check yours: https://three.ws/three?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-09-three-access&utm_content=utility-post
+```
+
+## Telegram
+
+```text
+What $THREE does this week: hold-to-access tiers.
+Open three.ws/three and connect a Solana wallet. The page reads the $THREE you hold (nothing is spent) and shows your tier.
+Live at Bronze ($25 held): High-quality Forge generation and Game-Ready export.
+Silver and above list perks marked Planned. Those are not switched on yet, and the page says so.
+https://three.ws/three?utm_source=telegram&utm_medium=community&utm_campaign=mkt-2026-09-three-access&utm_content=utility-telegram
+```
+
+## User action
+
+Open `/three`, connect a Solana wallet, read the tier shown, then open one LIVE perk (Forge Max at `/forge-max`).
+
+## KPI and where to read it
+
+Tier checks and benefit uses. Read UTM sessions for `utm_campaign=mkt-2026-09-three-access` in web analytics; read tier resolutions from Cloud Run request logs for `/api/three/tier` and `/api/three/tier-pass` (`gcloud logging read 'resource.type="cloud_run_revision" resource.labels.service_name="three-ws-api" httpRequest.requestUrl:"/api/three/tier"' --freshness=7d`).
+
+Record the 24-hour and seven-day rows in the format in [measurement.md](../growth/measurement.md).
+
+## Posting-day checklist
+
+- [ ] Re-open the linked surface in a clean browser and confirm it loads without errors.
+- [ ] `curl -s https://three.ws/api/three/access` still shows `forge.high` and `forge.gameready` with `enforced: true`.
+- [ ] The ladder thresholds in `/api/three/tier` still match the post ($25 Bronze).
+- [ ] Re-run `node marketing/three-utility-season/capture.mjs --only 01` and confirm the frame shows LIVE and PLANNED badges.
+- [ ] Attach the image and paste the alt text.
+- [ ] Owner presses publish. Nothing in this pack posts automatically.
+
+## Do not
+
+- Do not list Silver, Gold, or Genesis perks as available. Five of seven are Planned.
+- Do not mention the token price or what $25 of $THREE is worth in tokens.
+- No price, return, urgency, or "moon" language. No hashtags, no emoji.
diff --git a/marketing/three-utility-season/02-holder-free-quota.md b/marketing/three-utility-season/02-holder-free-quota.md
new file mode 100644
index 000000000..8579cde69
--- /dev/null
+++ b/marketing/three-utility-season/02-holder-free-quota.md
@@ -0,0 +1,86 @@
+# Edition 02: What $THREE does this week, lower-cost platform access
+
+| Field | Value |
+|---|---|
+| Campaign id | `MKT-2026-09-THREE-DISCOUNT` |
+| Publish date | 2026-09-25 |
+| Chapter | Access |
+| Audience | community and creators |
+| Campaign anchor (campaigns.csv) | https://three.ws/pricing |
+| Surface used in this pack | /forge |
+| Verified status (2026-09-16) | **Not live (planned surface is wired but switched off). Substitute used.** |
+
+## Verification
+
+**Substitute:** The planned story, paying for Pro at 20% off in $THREE on `/pricing`, cannot be completed in production today. The substitute is the live holder free-quota multiplier on the free Forge lane, which lowers the cost of access without a payment.
+
+- Planned surface: `/pricing` renders "Pay in USDC, SOL, or $THREE, 20% off in $THREE", and `GET https://three.ws/api/payments/solana/plans` returns `three_discount_bps: 2000` and Pro at $39.20 in $THREE.
+- Blocker: a signed-in `POST /api/payments/solana/checkout` with `{"plan":"pro","asset":"THREE"}` returned `503 not_configured: Solana payment recipient not configured` on 2026-09-16 (also for USDC). `PAYMENT_RECIPIENT_SOLANA` is not set on the `three-ws-api` Cloud Run service (`api/payments/_config.js`).
+- Substitute: `api/forge.js` `freeLaneMultiplier()` lifts the free-lane hourly limit by the tier multiplier from a verified tier pass (`api/_lib/rate-limit.js` `mcp3dGenerateFreeTiered`). The ladder in `/api/three/tier` lists `rate_multiplier` 2, 3, 5, 10. The `/forge` page shows "Hold $THREE for up to 10x free generations".
+
+## The three questions
+
+- **What can a holder do now?** Open `/forge`, connect a wallet holding at least Bronze, and generate past the default hourly free limit.
+- **Where does $THREE enter?** Held, not spent. A signed tier pass derived from the wallet's $THREE balance travels with each free generation request and raises that wallet's hourly free limit.
+- **What verifiable result comes out?** More free generations per hour for the same wallet: 2x at Bronze, 3x Silver, 5x Gold, 10x Genesis.
+
+## Numbers and their sources
+
+| Stable fact | Source and capture date |
+|---|---|
+| Multipliers 2x / 3x / 5x / 10x | `/api/three/tier` `rate_multiplier`, captured 2026-09-16 |
+| "Hold $THREE for up to 10x free generations" on `/forge` | captured frame, 2026-09-16 |
+
+| Volatile figure (read on posting day) | Source |
+|---|---|
+| The base hourly free limit is deployment config (`FORGE_FREE_HOURLY_SELFHOST`); do not quote an absolute number | n/a |
+
+## Media
+
+- File: [`images/02-holder-free-quota.png`](./images/02-holder-free-quota.png), 1600x900, captured 2026-09-16 from `/forge` by `node marketing/three-utility-season/capture.mjs --only 02`.
+- Alt text (required on every post):
+
+> The three.ws Forge page: a prompt box, quality options Draft, Standard, and High with a $THREE badge, a Generate button, and a line under it reading "Hold $THREE for up to 10x free generations" next to a Connect wallet button.
+
+## X post
+
+Weighted length: **170 characters** (URL counted as 23, as `scripts/post-tweet.mjs` does).
+
+```text
+Holding $THREE lifts your free Forge generation limit: 2x at Bronze, up to 10x at Genesis. Nothing is spent; the balance is read from your wallet. https://three.ws/forge?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-09-three-discount&utm_content=utility-post
+```
+
+## Telegram
+
+```text
+What $THREE does this week: more free generations.
+Forge on three.ws is free to use. Holding $THREE raises how many free generations your wallet gets per hour: 2x at Bronze ($25 held), up to 10x at Genesis.
+Nothing is spent. Connect a wallet on three.ws/forge and generate.
+Paying for Pro in $THREE is shown on /pricing but checkout is not switched on yet, so this week is about holding.
+https://three.ws/forge?utm_source=telegram&utm_medium=community&utm_campaign=mkt-2026-09-three-discount&utm_content=utility-telegram
+```
+
+## User action
+
+Open `/forge`, connect a wallet holding at least Bronze, and generate past the default hourly free limit.
+
+## KPI and where to read it
+
+THREE-tier free generations. Read UTM sessions for `mkt-2026-09-three-discount`; read generations by tier from `forge_creations` (backend and status per generation) joined with tier-pass usage in `/api/forge` logs. Checkout completions stay at zero until the recipient is configured.
+
+Record the 24-hour and seven-day rows in the format in [measurement.md](../growth/measurement.md).
+
+## Posting-day checklist
+
+- [ ] Re-open the linked surface in a clean browser and confirm it loads without errors.
+- [ ] Re-test the planned story: signed-in `POST /api/payments/solana/checkout` with asset THREE. If it now returns an intent, the owner may switch this edition back to the `/pricing` story (the frame and copy would need re-capture and rewriting).
+- [ ] Confirm `/forge` still shows the "up to 10x free generations" line.
+- [ ] Re-run `capture.mjs --only 02`.
+- [ ] Attach the image and paste the alt text.
+- [ ] Owner presses publish. Nothing in this pack posts automatically.
+
+## Do not
+
+- Do not say "pay in $THREE for 20% off" until a real checkout completes.
+- Do not quote an hourly generation number.
+- No price, return, urgency, or "moon" language. No hashtags, no emoji.
diff --git a/marketing/three-utility-season/03-gated-embed-mcp.md b/marketing/three-utility-season/03-gated-embed-mcp.md
new file mode 100644
index 000000000..cb0086896
--- /dev/null
+++ b/marketing/three-utility-season/03-gated-embed-mcp.md
@@ -0,0 +1,83 @@
+# Edition 03: What $THREE does this week, marketplace settlement
+
+| Field | Value |
+|---|---|
+| Campaign id | `MKT-2026-10-THREE-MARKET` |
+| Publish date | 2026-10-02 |
+| Chapter | Creation |
+| Audience | creators and agents |
+| Campaign anchor (campaigns.csv) | https://three.ws/marketplace |
+| Surface used in this pack | /docs/mcp (tool `create_gated_embed`) |
+| Verified status (2026-09-16) | **Not demonstrable. Substitute used.** |
+
+## Verification
+
+**Substitute:** Marketplace settlement in $THREE has no completed sale to show and its payment rail is switched off. The substitute is the live MCP tool `create_gated_embed`, which lets an agent (or its owner) make holder-only 3D content.
+
+- Planned surface: `GET https://three.ws/api/marketplace/analytics` on 2026-09-16 returned `totalSales: 0`, `uniqueBuyers: 0`, `totalTrials: 11312`, `trialFunnel.converted: 0`.
+- Payment rail: signed-in `POST /api/token/quote` (purposes `consumption` and `marketplace_sale`) returned `treasury_unavailable`; `GET /api/token/config` reports `treasury_configured: false`, `rewards_configured: false`.
+- Listing UI: an agent with $THREE `skill_prices` in `/api/marketplace/agents/<id>` does not render those prices on its marketplace page, and the Skills tab "Paid" entries are USDC x402 skills.
+- Code risk: `api/_lib/solana/gasless-tx.js` builds the purchase transfer with the legacy token program, while the $THREE mint is Token-2022 (confirmed with `getAccountInfo`: owner `spl-token-2022`).
+- Substitute: tool definition at `api/_mcp/tools/embed.js` line 227, backed by `api/embed/gate-create.js`; documented at `/docs/mcp` (section `create_gated_embed`, 200 on 2026-09-16). Calling the MCP endpoint requires sign-in (OAuth); an unauthenticated `tools/list` answered with a 402 challenge, so the tool call itself was not exercised in this pass.
+
+## The three questions
+
+- **What can a holder do now?** Connect an MCP client to `https://three.ws/api/mcp`, sign in, and call `create_gated_embed` with an owned `asset_id` and a `min_amount`.
+- **Where does $THREE enter?** Held, by the viewer. The gate defaults to the $THREE mint when `mint` is omitted; a viewer must hold at least `min_amount` to open the scene.
+- **What verifiable result comes out?** A `gate_id`, the gate terms, and a paste-ready embed snippet that shows a locked teaser below the bar and the live 3D scene above it.
+
+## Numbers and their sources
+
+| Stable fact | Source and capture date |
+|---|---|
+| Omitting `mint` defaults the gate to $THREE | `docs/token-gated-3d-embeds.md` and `api/_mcp/tools/embed.js`, captured 2026-09-16 |
+
+## Media
+
+- File: [`images/03-gated-embed-mcp-tool.png`](./images/03-gated-embed-mcp-tool.png), 1600x900, captured 2026-09-16 from `github.com/nirholas/three.ws/blob/main/api/_mcp/tools/embed.js#L227` by `node marketing/three-utility-season/capture.mjs --only 03`.
+- Alt text (required on every post):
+
+> Source of the three.ws MCP server on GitHub, file api/_mcp/tools/embed.js, highlighting line 227: name create_gated_embed, title "Create a token-gated embed", with the description "Turn an avatar or on-chain agent you own into a holder-only interactive 3D embed".
+
+## X post
+
+Weighted length: **163 characters** (URL counted as 23, as `scripts/post-tweet.mjs` does).
+
+```text
+Agents can gate 3D content too. The three.ws MCP tool create_gated_embed turns an avatar you own into a scene only $THREE holders can open. https://three.ws/docs/mcp?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-10-three-market&utm_content=utility-post
+```
+
+## Telegram
+
+```text
+What $THREE does this week: agents that gate content.
+The three.ws MCP server has a create_gated_embed tool. Point it at an avatar you own and set a minimum; leave the mint empty and the gate uses $THREE.
+The result is an embed snippet that stays locked for wallets below the bar.
+Marketplace sales in $THREE are not running yet, so this week shows the part that is.
+https://three.ws/docs/mcp?utm_source=telegram&utm_medium=community&utm_campaign=mkt-2026-10-three-market&utm_content=utility-telegram
+```
+
+## User action
+
+Connect an MCP client to `https://three.ws/api/mcp`, sign in, and call `create_gated_embed` with an owned `asset_id` and a `min_amount`.
+
+## KPI and where to read it
+
+Gates created by agents. Read UTM sessions for `mkt-2026-10-three-market`; count new rows in `embed_gates` created during the week (1 row existed on 2026-09-16).
+
+Record the 24-hour and seven-day rows in the format in [measurement.md](../growth/measurement.md).
+
+## Posting-day checklist
+
+- [ ] Re-open the linked surface in a clean browser and confirm it loads without errors.
+- [ ] From a real MCP client, call `create_gated_embed` once end to end and open the returned preview URL.
+- [ ] Re-check `/api/marketplace/analytics` and `/api/token/config`. If `totalSales` is above 0 and `treasury_configured` is true, the owner can restore the marketplace story.
+- [ ] Re-run `capture.mjs --only 03`.
+- [ ] Attach the image and paste the alt text.
+- [ ] Owner presses publish. Nothing in this pack posts automatically.
+
+## Do not
+
+- Do not describe the marketplace as settling in $THREE until a confirmed sale exists.
+- Do not quote the trial count as usage.
+- No price, return, urgency, or "moon" language. No hashtags, no emoji.
diff --git a/marketing/three-utility-season/04-forge-max-holder.md b/marketing/three-utility-season/04-forge-max-holder.md
new file mode 100644
index 000000000..5a4fd1705
--- /dev/null
+++ b/marketing/three-utility-season/04-forge-max-holder.md
@@ -0,0 +1,80 @@
+# Edition 04: What $THREE does this week, agent labor and escrow
+
+| Field | Value |
+|---|---|
+| Campaign id | `MKT-2026-10-THREE-LABOR` |
+| Publish date | 2026-10-09 |
+| Chapter | Agent work |
+| Audience | agent builders and community |
+| Campaign anchor (campaigns.csv) | https://three.ws/labor-market |
+| Surface used in this pack | /forge-max |
+| Verified status (2026-09-16) | **Enabled but off. Substitute used.** |
+
+## Verification
+
+**Substitute:** The labor market escrow is not configured in production. The substitute is the live Forge Max holder perk: an agent builder can give an agent a maximum-quality body by holding Bronze.
+
+- Planned surface: `/labor-market` (route to `pages/labor-market.html`) loads, but `GET https://three.ws/api/labor/feed` returned `escrow_configured: false`, `settled_jobs: 0`, `open_bounties: 0` on 2026-09-16; the page shows "ESCROW Offline". `LABOR_ESCROW_SECRET_BASE58` is absent on `three-ws-api`, so `api/_lib/labor-escrow.js` refuses to hold funds (typed 503).
+- Substitute: `/forge-max` (in `data/pages.json`) loads; `api/forge.js` calls `requireFeatureAccess(req, res, 'forge.high')`, and `/api/three/access` lists `forge.high` with `enforced: true`, minimum Bronze.
+
+## The three questions
+
+- **What can a holder do now?** Sign in with a wallet holding Bronze, open `/forge-max`, and run one High generation.
+- **Where does $THREE enter?** Held. Bronze ($25 of $THREE held) is checked through a signed tier pass before a High generation runs. The pay-per-generation alternative shown on the page settles through the $THREE token rail, which is currently unavailable (see edition 03), so the copy only describes holding.
+- **What verifiable result comes out?** A High-tier generation: up to 200,000-polygon geometry with PBR textures, downloadable as GLB.
+
+## Numbers and their sources
+
+| Stable fact | Source and capture date |
+|---|---|
+| "up to 200,000 polygons", "Requires Bronze" | captured frame of `/forge-max`, 2026-09-16 |
+
+## Media
+
+- File: [`images/04-forge-max-holder.png`](./images/04-forge-max-holder.png), 1600x900, captured 2026-09-16 from `/forge-max` by `node marketing/three-utility-season/capture.mjs --only 04`.
+- Alt text (required on every post):
+
+> The three.ws Forge Max page with High quality selected and a lock card reading "Requires Bronze, hold $THREE", with Get $THREE and Sign in buttons; the details line says High renders up to 200,000 polygons.
+
+## X post
+
+Weighted length: **171 characters** (URL counted as 23, as `scripts/post-tweet.mjs` does).
+
+```text
+Forge Max builds up to 200,000-polygon models with PBR textures. Holding $25 of $THREE (Bronze) opens it, verified from your wallet, nothing spent. https://three.ws/forge-max?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-10-three-labor&utm_content=utility-post
+```
+
+## Telegram
+
+```text
+What $THREE does this week: a better body for your agent.
+Forge Max on three.ws builds up to 200,000-polygon models with PBR textures. Holding $25 of $THREE (Bronze) opens it. The balance is checked, not spent.
+Standard generation stays free for everyone.
+The agent labor market with $THREE escrow is built but its escrow is offline in production, so it is not this week's walkthrough.
+https://three.ws/forge-max?utm_source=telegram&utm_medium=community&utm_campaign=mkt-2026-10-three-labor&utm_content=utility-telegram
+```
+
+## User action
+
+Sign in with a wallet holding Bronze, open `/forge-max`, and run one High generation.
+
+## KPI and where to read it
+
+High generations by holders. UTM sessions for `mkt-2026-10-three-labor`; `forge_creations` rows with the High tier during the week.
+
+Record the 24-hour and seven-day rows in the format in [measurement.md](../growth/measurement.md).
+
+## Posting-day checklist
+
+- [ ] Re-open the linked surface in a clean browser and confirm it loads without errors.
+- [ ] Run one High generation from a Bronze wallet and confirm the lock card clears.
+- [ ] Re-check `/api/labor/feed`. If `escrow_configured` is true and a bounty settles, the owner can restore the labor story.
+- [ ] Re-run `capture.mjs --only 04`.
+- [ ] Attach the image and paste the alt text.
+- [ ] Owner presses publish. Nothing in this pack posts automatically.
+
+## Do not
+
+- Do not mention escrow, bounties, or agent wages.
+- Do not promote the "Pay $0.50 per generation" button until a $THREE quote succeeds.
+- No price, return, urgency, or "moon" language. No hashtags, no emoji.
diff --git a/marketing/three-utility-season/05-gated-embed-create.md b/marketing/three-utility-season/05-gated-embed-create.md
new file mode 100644
index 000000000..0d89cb448
--- /dev/null
+++ b/marketing/three-utility-season/05-gated-embed-create.md
@@ -0,0 +1,82 @@
+# Edition 05: What $THREE does this week, token-gated 3D content
+
+| Field | Value |
+|---|---|
+| Campaign id | `MKT-2026-10-THREE-GATE` |
+| Publish date | 2026-10-16 |
+| Chapter | Creation |
+| Audience | creators and community |
+| Campaign anchor (campaigns.csv) | https://three.ws/studio |
+| Surface used in this pack | /docs/token-gated-3d-embeds |
+| Verified status (2026-09-16) | **Live (API and MCP). No creation UI in `/studio`.** |
+
+## Verification
+
+**Substitute:** None for the utility. The link moves from `/studio` to the documentation page, because Widget Studio has no gate control; creation happens through `POST /api/embed/gate-create` or the MCP tool.
+
+- Handlers: `api/embed/gate-create.js` and `api/embed/gate-verify.js`. An unauthenticated create returned `401 sign in required to gate an embed` (the expected guard) on 2026-09-16.
+- Verify path: `POST /api/embed/gate-verify` for the existing demo gate returned a SIWS message with a nonce and `gate: { mint: FeMb...pump, minAmount: 1 }` on 2026-09-16.
+- Doc: `/docs/token-gated-3d-embeds` answered 200 and shows "Verified against the code".
+- Gap: `src/studio/` contains no gate-create control, so the campaign anchor `/studio` cannot perform the action.
+
+## The three questions
+
+- **What can a holder do now?** Sign in, pick an owned avatar, `POST /api/embed/gate-create` with `{ assetId, gate: { minAmount, chain: "solana" } }`, and paste the returned snippet on a page.
+- **Where does $THREE enter?** Held, by the viewer. The server issues a single-use signed-message nonce, reads the wallet's live $THREE balance, and only then returns a short-lived access token for the scene.
+- **What verifiable result comes out?** Below the bar, a designed locked teaser ("Hold N $THREE to unlock"). Above it, the interactive 3D scene. Raising the minimum invalidates earlier access tokens.
+
+## Numbers and their sources
+
+| Stable fact | Source and capture date |
+|---|---|
+| Gate defaults to $THREE when `mint` is omitted | `docs/token-gated-3d-embeds.md`, captured 2026-09-16 |
+
+## Media
+
+- File: [`images/05-gated-embed-docs.png`](./images/05-gated-embed-docs.png), 1600x900, captured 2026-09-16 from `/docs/token-gated-3d-embeds` by `node marketing/three-utility-season/capture.mjs --only 05`.
+- Alt text (required on every post):
+
+> The three.ws documentation page "Token-gated 3D embeds", marked Verified against the code, explaining that the scene only renders for a visitor who holds enough of a specific token, verified with a real on-chain balance read, with $THREE-holder-only content as the canonical use case.
+
+## X post
+
+Weighted length: **167 characters** (URL counted as 23, as `scripts/post-tweet.mjs` does).
+
+```text
+A token-gated embed renders its 3D scene only for a wallet holding enough $THREE, checked by a signed message and a live on-chain balance read. https://three.ws/docs/token-gated-3d-embeds?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-10-three-gate&utm_content=utility-post
+```
+
+## Telegram
+
+```text
+What $THREE does this week: holder-only 3D scenes.
+Any avatar you own on three.ws can become an embed that only renders for wallets holding enough $THREE. The check is a signed message plus a live on-chain balance read, done on the server.
+Below the bar, visitors see a locked teaser instead of the model.
+Create one with the API or the MCP tool; the guide is at three.ws/docs/token-gated-3d-embeds.
+https://three.ws/docs/token-gated-3d-embeds?utm_source=telegram&utm_medium=community&utm_campaign=mkt-2026-10-three-gate&utm_content=utility-telegram
+```
+
+## User action
+
+Sign in, pick an owned avatar, `POST /api/embed/gate-create` with `{ assetId, gate: { minAmount, chain: "solana" } }`, and paste the returned snippet on a page.
+
+## KPI and where to read it
+
+Gates created and verified unlocks. New `embed_gates` rows for the week; successful `gate-verify` phase-two responses in `three-ws-api` logs; UTM sessions for `mkt-2026-10-three-gate`.
+
+Record the 24-hour and seven-day rows in the format in [measurement.md](../growth/measurement.md).
+
+## Posting-day checklist
+
+- [ ] Re-open the linked surface in a clean browser and confirm it loads without errors.
+- [ ] Create one gate from a real account and open it with a wallet above and below the bar.
+- [ ] Confirm `/docs/token-gated-3d-embeds` still returns 200.
+- [ ] Re-run `capture.mjs --only 05`.
+- [ ] Attach the image and paste the alt text.
+- [ ] Owner presses publish. Nothing in this pack posts automatically.
+
+## Do not
+
+- Do not say "in Studio". There is no Studio control yet.
+- Do not suggest gating with any other token in the post.
+- No price, return, urgency, or "moon" language. No hashtags, no emoji.
diff --git a/marketing/three-utility-season/07-holder-scene-unlock.md b/marketing/three-utility-season/07-holder-scene-unlock.md
new file mode 100644
index 000000000..1f7f7bbdc
--- /dev/null
+++ b/marketing/three-utility-season/07-holder-scene-unlock.md
@@ -0,0 +1,81 @@
+# Edition 07: What $THREE does this week, live world access and purchases
+
+| Field | Value |
+|---|---|
+| Campaign id | `MKT-2026-10-THREE-WORLD` |
+| Publish date | 2026-10-30 |
+| Chapter | Community |
+| Audience | community and holders |
+| Campaign anchor (campaigns.csv) | https://three.ws/play |
+| Surface used in this pack | live gated embed (`/embed/v1/gated.html`) |
+| Verified status (2026-09-16) | **Not live for $THREE. Substitute used.** |
+
+## Verification
+
+**Substitute:** `/play` is open to everyone and its $THREE purchases are switched off. The substitute is the viewer side of a real holder gate: a community member unlocks a holder-only 3D scene with one signature.
+
+- World access: the `/play` holder gate is off because neither `PLAY_GATE_MINT` nor `THREE_MINT` is set on `three-ws-api` or `three-ws-multiplayer` (`api/_lib/play-pass.js`: "An empty mint means the gate is OFF").
+- Purchases: the `three-ws-multiplayer` service env holds only `NODE_ENV`, `ALLOWED_ORIGINS`, `HOLDER_PASS_SECRET`, and Redis settings. Without `GAME_TOKEN_TREASURY` or `PAYMENT_RECIPIENT_SOLANA`, `multiplayer/src/game-token.js` `treasuryWallet()` throws in production, so boutique sales and paid spins cannot settle.
+- Substitute: `https://three.ws/embed/v1/gated.html?asset=avatar%3Abf2d5c4b-...` renders the locked teaser for the platform's demo gate (min 1 $THREE); `POST /api/embed/gate-verify` issued a SIWS nonce for it on 2026-09-16.
+
+## The three questions
+
+- **What can a holder do now?** Open the gated embed link, connect a Solana wallet holding 1 $THREE, sign the message, and view the scene.
+- **Where does $THREE enter?** Held, by the visitor. Connecting a wallet and signing one message lets the server read the $THREE balance; at 1 or more the scene opens.
+- **What verifiable result comes out?** The locked teaser is replaced by the interactive 3D scene. No tokens move.
+
+## Numbers and their sources
+
+| Stable fact | Source and capture date |
+|---|---|
+| Demo gate minimum: 1 $THREE | `gate-verify` response and captured frame, 2026-09-16 |
+
+## Media
+
+- File: [`images/07-holder-scene-unlock.png`](./images/07-holder-scene-unlock.png), 1600x900, captured 2026-09-16 from `/embed/v1/gated.html?asset=avatar%3Abf2d5c4b-2536-4593-bf15-ec934a6c9f48` by `node marketing/three-utility-season/capture.mjs --only 07`.
+- Alt text (required on every post):
+
+> A locked three.ws 3D embed: a padlock icon, the heading "Hold 1 $THREE to unlock", the note that "Gate Demo Avatar" is a token-gated 3D embed on three.ws, a Connect wallet button, and the $THREE contract address beneath.
+
+## X post
+
+Weighted length: **165 characters** (URL counted as 23, as `scripts/post-tweet.mjs` does).
+
+```text
+This 3D scene stays locked until a wallet proves it holds 1 $THREE. Connect, sign one message, and it opens. Nothing is spent or transferred. https://three.ws/embed/v1/gated.html?asset=avatar%3Abf2d5c4b-2536-4593-bf15-ec934a6c9f48&utm_source=x&utm_medium=social&utm_campaign=mkt-2026-10-three-world&utm_content=utility-post
+```
+
+## Telegram
+
+```text
+What $THREE does this week: open a holder-only scene.
+This three.ws embed stays locked until a wallet proves it holds 1 $THREE. Connect, sign one message, and the 3D scene opens. Nothing is spent or transferred.
+Contract address: FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump
+The /play world is open to everyone. Its $THREE shop is not switched on yet.
+https://three.ws/embed/v1/gated.html?asset=avatar%3Abf2d5c4b-2536-4593-bf15-ec934a6c9f48&utm_source=telegram&utm_medium=community&utm_campaign=mkt-2026-10-three-world&utm_content=utility-telegram
+```
+
+## User action
+
+Open the gated embed link, connect a Solana wallet holding 1 $THREE, sign the message, and view the scene.
+
+## KPI and where to read it
+
+Verified unlocks. Successful phase-two `POST /api/embed/gate-verify` responses for gate `6ohPMCQSv5LY` in `three-ws-api` logs; UTM sessions for `mkt-2026-10-three-world`.
+
+Record the 24-hour and seven-day rows in the format in [measurement.md](../growth/measurement.md).
+
+## Posting-day checklist
+
+- [ ] Re-open the linked surface in a clean browser and confirm it loads without errors.
+- [ ] Unlock the demo gate once with a real wallet holding 1 $THREE and confirm the scene renders.
+- [ ] Re-check `three-ws-multiplayer` env. If a treasury is configured and a boutique sale settles, the owner can restore the world-purchase story.
+- [ ] Re-run `capture.mjs --only 07`.
+- [ ] Attach the image and paste the alt text.
+- [ ] Owner presses publish. Nothing in this pack posts automatically.
+
+## Do not
+
+- Do not say $THREE buys cosmetics or spins in `/play` yet.
+- Do not mention the wheel of fortune in any edition.
+- No price, return, urgency, or "moon" language. No hashtags, no emoji.
diff --git a/marketing/three-utility-season/08-tier-api-for-agents.md b/marketing/three-utility-season/08-tier-api-for-agents.md
new file mode 100644
index 000000000..932ba4a6e
--- /dev/null
+++ b/marketing/three-utility-season/08-tier-api-for-agents.md
@@ -0,0 +1,83 @@
+# Edition 08: What $THREE does this week, pay for agent tools over x402
+
+| Field | Value |
+|---|---|
+| Campaign id | `MKT-2026-11-THREE-X402` |
+| Publish date | 2026-11-06 |
+| Chapter | Agent work |
+| Audience | agent and API builders |
+| Campaign anchor (campaigns.csv) | https://three.ws/x402 |
+| Surface used in this pack | `GET /api/three/tier` |
+| Verified status (2026-09-16) | **Advertised but not settleable. Substitute used.** |
+
+## Verification
+
+**Substitute:** Paying x402 endpoints in $THREE cannot settle today. The substitute is the public tier endpoint any agent can call to read a wallet's $THREE standing before it serves or discounts a request.
+
+- Planned surface: a 402 challenge from `https://three.ws/api/x402/token-intel` lists a second `accepts` entry with the $THREE mint on Solana (`X402_ACCEPT_THREE_SOLANA` defaults to true in `api/_lib/env.js`).
+- Blocker: the configured facilitator is self-hosted (`X402_FACILITATOR_URL_SOLANA=https://three.ws/api/x402-facilitator`). `api/_lib/x402/self-facilitator.js` only accepts transfers under the legacy token program and rejects any other program with `program_not_allowed`. $THREE is a Token-2022 mint, so a $THREE payment cannot pass verification.
+- The `/x402` page itself says settlement is "in USDC".
+- Substitute: `GET https://three.ws/api/three/tier` answered 200 without auth on 2026-09-16 with `tier`, `next.usd_to_go`, and the ladder; `?wallet=<address>` returned a resolved tier for a mainnet holder.
+- Docs gap: this public endpoint is not documented in `docs/api-reference.md`.
+
+## The three questions
+
+- **What can a holder do now?** Call `curl "https://three.ws/api/three/tier?wallet=<address>"` from an agent and branch on `tier.level`.
+- **Where does $THREE enter?** Held. The endpoint values the $THREE the wallet holds and returns its level, `discount_bps`, and `rate_multiplier`.
+- **What verifiable result comes out?** A JSON tier verdict an agent can act on, with no API key and no signature.
+
+## Numbers and their sources
+
+| Stable fact | Source and capture date |
+|---|---|
+| Unauthenticated, `?wallet=` supported, fields `tier`, `next`, `ladder` | live response, 2026-09-16 |
+
+## Media
+
+- File: [`images/08-tier-api.png`](./images/08-tier-api.png), 1600x900, captured 2026-09-16 from `/api/three/tier` by `node marketing/three-utility-season/capture.mjs --only 08`.
+- Alt text (required on every post):
+
+> Raw JSON from three.ws/api/three/tier: signed_in false, tier Member, next tier Bronze with usd_to_go 25, and the ladder of Member, Bronze, Silver, Gold, and Genesis with discount_bps and rate_multiplier for each.
+
+## X post
+
+Weighted length: **161 characters** (URL counted as 23, as `scripts/post-tweet.mjs` does).
+
+```text
+An agent can read any Solana wallet's $THREE tier with one unauthenticated GET: level, perks, and the USD still to go. No key, no signup. https://three.ws/api/three/tier?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-11-three-x402&utm_content=utility-post
+```
+
+## Telegram
+
+```text
+What $THREE does this week: a tier check any agent can call.
+GET three.ws/api/three/tier?wallet=<address> returns that wallet's $THREE tier, its perks, and how far it is from the next tier. No key, no signup.
+Builders can use it to decide what a holder gets from their own agent or API.
+Paying x402 endpoints in $THREE is not working yet; payments settle in USDC today.
+https://three.ws/api/three/tier?utm_source=telegram&utm_medium=community&utm_campaign=mkt-2026-11-three-x402&utm_content=utility-telegram
+```
+
+## User action
+
+Call `curl "https://three.ws/api/three/tier?wallet=<address>"` from an agent and branch on `tier.level`.
+
+## KPI and where to read it
+
+External tier reads. Count `/api/three/tier` requests carrying `wallet=` and a non-browser user agent in `three-ws-api` request logs for the week; UTM sessions for `mkt-2026-11-three-x402`.
+
+Record the 24-hour and seven-day rows in the format in [measurement.md](../growth/measurement.md).
+
+## Posting-day checklist
+
+- [ ] Re-open the linked surface in a clean browser and confirm it loads without errors.
+- [ ] `curl` the endpoint with and without `?wallet=` and confirm 200.
+- [ ] Re-test a $THREE x402 payment. If the facilitator settles one, the owner can restore the x402 story.
+- [ ] Re-run `capture.mjs --only 08`.
+- [ ] Attach the image and paste the alt text.
+- [ ] Owner presses publish. Nothing in this pack posts automatically.
+
+## Do not
+
+- Do not say agents can pay in $THREE over x402.
+- The `perks` strings in the JSON include Planned perks; do not quote them as available.
+- No price, return, urgency, or "moon" language. No hashtags, no emoji.
diff --git a/marketing/three-utility-season/09-buyback-ledger.md b/marketing/three-utility-season/09-buyback-ledger.md
new file mode 100644
index 000000000..2a40d3e7e
--- /dev/null
+++ b/marketing/three-utility-season/09-buyback-ledger.md
@@ -0,0 +1,87 @@
+# Edition 09: What $THREE does this week, public utility receipts
+
+| Field | Value |
+|---|---|
+| Campaign id | `MKT-2026-11-THREE-RECEIPTS` |
+| Publish date | 2026-11-13 |
+| Chapter | Transparency |
+| Audience | community and technical evaluators |
+| Campaign anchor (campaigns.csv) | https://three.ws/three-token |
+| Surface used in this pack | /three-token |
+| Verified status (2026-09-16) | **Live (the ledger is live and currently reads zero).** |
+
+## Verification
+
+**Substitute:** None.
+
+- `GET https://three.ws/api/three-token/stats` answered 200 on 2026-09-16 with `buyback.enabled: false`, `committed_usd: 0`, `runs: 0`, `microbuy.enabled: false`, and `protocol.total_revenue_usd: 0`.
+- `/three-token` renders the same state: "$0.00 in platform revenue earned so far, $0.00 committed to buybacks at 50%".
+- Gap: `/api/three-token/burns` and `/three-live` report "$THREE burned" as `agent count x 1000` (`api/three-token/[action].js` `fetchBurnEvents()` reads `agent_identities`), not from any on-chain burn, and `/dashboard/three-token` says every deploy burns 1,000 $THREE permanently. The token config states the platform never burns. Do not use those figures.
+
+## The three questions
+
+- **What can a holder do now?** Open `/three-token`, scroll to Programmatic Buybacks, and compare with `/api/three-token/stats`.
+- **Where does $THREE enter?** Reported, not used. The ledger shows whether platform revenue has been converted into $THREE buys.
+- **What verifiable result comes out?** Anyone can check the buyback switch and totals without trusting a post.
+
+## Numbers and their sources
+
+| Stable fact | Source and capture date |
+|---|---|
+| Committed share: 50% (`commit_pct`) | `/api/three-token/stats`, captured 2026-09-16 |
+
+| Volatile figure (read on posting day) | Source |
+|---|---|
+| `{COMMITTED_USD}`: `buyback.committed_usd` (was 0 on 2026-09-16) | `/api/three-token/stats`, read on posting day |
+| If `buyback.enabled` is true or `runs` is above 0 on posting day, use the variant below | `/api/three-token/stats` |
+
+## Media
+
+- File: [`images/09-buyback-ledger.png`](./images/09-buyback-ledger.png), 1600x900, captured 2026-09-16 from `/three-token` by `node marketing/three-utility-season/capture.mjs --only 09`.
+- Alt text (required on every post):
+
+> The three.ws $THREE token page scrolled to the Programmatic Buybacks panel, which reads 50% of all platform revenue to $THREE buybacks, $0.00 in platform revenue earned so far, and $0.00 committed to buybacks at 50%, with a note that each buy will appear with its Solscan receipt.
+
+## X post
+
+Weighted length: **175 characters** (URL counted as 23, as `scripts/post-tweet.mjs` does; counted with the 2026-09-16 values filled in).
+
+```text
+The $THREE buyback ledger is public. It reads {COMMITTED_USD} committed today because revenue buybacks have not started; each buy will post there with a receipt. https://three.ws/three-token?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-11-three-receipts&utm_content=utility-post
+```
+
+**Variant:** If buybacks have started on posting day: `The $THREE buyback ledger on three.ws now shows {RUNS} buys and {THREE_BOUGHT} $THREE bought from platform revenue, each with an on-chain receipt: <link>` (count it before posting).
+
+## Telegram
+
+```text
+What $THREE does this week: receipts you can check.
+The $THREE buyback ledger on three.ws/three-token is public. Today it reads {COMMITTED_USD} committed and the buyback switch is off, because revenue buybacks have not started.
+When a buy runs it appears there with its on-chain receipt. The raw numbers are at three.ws/api/three-token/stats.
+https://three.ws/three-token?utm_source=telegram&utm_medium=community&utm_campaign=mkt-2026-11-three-receipts&utm_content=utility-telegram
+```
+
+## User action
+
+Open `/three-token`, scroll to Programmatic Buybacks, and compare with `/api/three-token/stats`.
+
+## KPI and where to read it
+
+Stats endpoint reads and linked utility actions. `three-ws-api` request logs for `/api/three-token/stats` during the week; UTM sessions for `mkt-2026-11-three-receipts`.
+
+Record the 24-hour and seven-day rows in the format in [measurement.md](../growth/measurement.md).
+
+## Posting-day checklist
+
+- [ ] Re-open the linked surface in a clean browser and confirm it loads without errors.
+- [ ] Read `/api/three-token/stats` within the hour before posting and fill `{COMMITTED_USD}` exactly.
+- [ ] Owner decision: publishing a zero ledger is honest transparency but is a public statement that no revenue has been committed. Confirm before posting.
+- [ ] Re-run `capture.mjs --only 09`.
+- [ ] Attach the image and paste the alt text.
+- [ ] Owner presses publish. Nothing in this pack posts automatically.
+
+## Do not
+
+- Do not cite burn totals from `/three-live`, `/api/three-token/burns`, or the dashboard.
+- Do not cite price, market cap, or volume from the same page.
+- No price, return, urgency, or "moon" language. No hashtags, no emoji.
diff --git a/marketing/three-utility-season/10-gameready-holder.md b/marketing/three-utility-season/10-gameready-holder.md
new file mode 100644
index 000000000..b5f0e6ca8
--- /dev/null
+++ b/marketing/three-utility-season/10-gameready-holder.md
@@ -0,0 +1,79 @@
+# Edition 10: What $THREE does this week, creator earnings and royalties
+
+| Field | Value |
+|---|---|
+| Campaign id | `MKT-2026-11-THREE-CREATOR` |
+| Publish date | 2026-11-20 |
+| Chapter | Creation |
+| Audience | 3D creators and community |
+| Campaign anchor (campaigns.csv) | https://three.ws/marketplace |
+| Surface used in this pack | /three (Game-Ready export perk) |
+| Verified status (2026-09-16) | **Not live. Substitute used.** |
+
+## Verification
+
+**Substitute:** Creator earnings in $THREE have no confirmed sale and the payment rail is off (see edition 03). The substitute is the live Game-Ready export holder perk, which gives 3D creators an engine-ready asset by holding Bronze.
+
+- Planned surface: same evidence as edition 03 (`totalSales: 0`, token rail `treasury_unavailable`). The marketplace skill fee knob `MARKETPLACE_PLATFORM_FEE_BPS` is unset, so a sale would pay the full list price to the creator once purchases work.
+- Substitute: `api/forge-gameready.js` gates through `forge.gameready`, listed `enforced: true`, minimum Bronze, in `/api/three/access` on 2026-09-16. The client (`src/forge-gameready.js`) sends the tier pass and polls the real remesh job.
+
+## The three questions
+
+- **What can a holder do now?** Generate a model on `/forge`, then press Game-Ready export from a wallet holding Bronze and download the FBX.
+- **Where does $THREE enter?** Held. Bronze is verified with a signed tier pass before the retopology job starts.
+- **What verifiable result comes out?** A retopologized mesh delivered as GLB plus FBX for Unity or Unreal.
+
+## Numbers and their sources
+
+| Stable fact | Source and capture date |
+|---|---|
+| Game-Ready export marked LIVE at Bronze | `/three` captured frame and `/api/three/access`, 2026-09-16 |
+
+## Media
+
+- File: [`images/10-gameready-holder.png`](./images/10-gameready-holder.png), 1600x900, captured 2026-09-16 from `/three (scrolled to the ladder)` by `node marketing/three-utility-season/capture.mjs --only 10`.
+- Alt text (required on every post):
+
+> The $THREE tier ladder on three.ws: Bronze lists High-quality generation and Game-Ready export (Unity/Unreal retopo plus PBR), both marked LIVE; Silver, Gold, and Genesis perks such as private worlds, branded worlds, and early access to drops are marked PLANNED.
+
+## X post
+
+Weighted length: **163 characters** (URL counted as 23, as `scripts/post-tweet.mjs` does).
+
+```text
+Game-Ready export retopologizes a Forge model into a GLB plus FBX for Unity or Unreal. Holding $25 of $THREE (Bronze) opens it on three.ws. https://three.ws/three?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-11-three-creator&utm_content=utility-post
+```
+
+## Telegram
+
+```text
+What $THREE does this week: engine-ready exports for creators.
+Game-Ready export on three.ws turns a Forge model into a clean GLB plus FBX for Unity or Unreal. Holding $25 of $THREE (Bronze) opens it; the balance is checked, not spent.
+Earning $THREE from marketplace sales is not running yet. It will get its own walkthrough when the first sale settles.
+https://three.ws/three?utm_source=telegram&utm_medium=community&utm_campaign=mkt-2026-11-three-creator&utm_content=utility-telegram
+```
+
+## User action
+
+Generate a model on `/forge`, then press Game-Ready export from a wallet holding Bronze and download the FBX.
+
+## KPI and where to read it
+
+Game-Ready exports by holders. `forge-gameready` job completions in `three-ws-api` logs for the week; UTM sessions for `mkt-2026-11-three-creator`.
+
+Record the 24-hour and seven-day rows in the format in [measurement.md](../growth/measurement.md).
+
+## Posting-day checklist
+
+- [ ] Re-open the linked surface in a clean browser and confirm it loads without errors.
+- [ ] Run one Game-Ready export from a Bronze wallet end to end.
+- [ ] Re-check marketplace sales. If a confirmed $THREE sale exists, the owner can restore the creator-earnings story.
+- [ ] Re-run `capture.mjs --only 10`.
+- [ ] Attach the image and paste the alt text.
+- [ ] Owner presses publish. Nothing in this pack posts automatically.
+
+## Do not
+
+- Do not mention royalties, earnings, or payouts.
+- Do not describe Planned perks visible in the frame as available.
+- No price, return, urgency, or "moon" language. No hashtags, no emoji.
diff --git a/marketing/three-utility-season/11-built-in-public.md b/marketing/three-utility-season/11-built-in-public.md
new file mode 100644
index 000000000..73e0b2c09
--- /dev/null
+++ b/marketing/three-utility-season/11-built-in-public.md
@@ -0,0 +1,81 @@
+# Edition 11: What $THREE does this week, utility built in public
+
+| Field | Value |
+|---|---|
+| Campaign id | `MKT-2026-11-THREE-BUILD` |
+| Publish date | 2026-11-27 |
+| Chapter | Transparency |
+| Audience | community and open-source builders |
+| Campaign anchor (campaigns.csv) | https://github.com/nirholas/three.ws |
+| Surface used in this pack | `api/_lib/three-access.js` on GitHub |
+| Verified status (2026-09-16) | **Live.** |
+
+## Verification
+
+**Substitute:** None. Primary channel is GitHub Discussions; the X post below is the secondary channel.
+
+- Repository `github.com/nirholas/three.ws` is public; `api/_lib/three-access.js` on `main` documents the `enforced` flag (lines 30 to 46) and lists the two enforced perks.
+- The `/three` page reads that flag through `/api/three/access` and renders LIVE or PLANNED (`src/three-tier-page.js`).
+
+## The three questions
+
+- **What can a holder do now?** Read `api/_lib/three-access.js`, compare it with `/three`, and open an issue or discussion reply.
+- **Where does $THREE enter?** In code. The registry decides which holder perks the product may call live.
+- **What verifiable result comes out?** Anyone can audit which $THREE perks are wired and open an issue when the page and the code disagree.
+
+## Numbers and their sources
+
+| Stable fact | Source and capture date |
+|---|---|
+| 2 of 7 perks `enforced: true` | source on `main` and `/api/three/access`, captured 2026-09-16 |
+
+## Media
+
+- File: [`images/11-built-in-public.png`](./images/11-built-in-public.png), 1600x900, captured 2026-09-16 from `github.com/nirholas/three.ws/blob/main/api/_lib/three-access.js#L30` by `node marketing/three-utility-season/capture.mjs --only 11`.
+- Alt text (required on every post):
+
+> Source of api/_lib/three-access.js on GitHub: a comment block explains that the enforced flag is true only when a gate is wired and live, so the tier page never makes an aspirational claim, and names forge.high and forge.gameready as the gates enforced today.
+
+## X post
+
+Weighted length: **172 characters** (URL counted as 23, as `scripts/post-tweet.mjs` does).
+
+```text
+Every $THREE perk in the three.ws code carries an enforced flag, so the tier page can only say Live when a gate really checks it. Read the registry: https://github.com/nirholas/three.ws/blob/main/api/_lib/three-access.js?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-11-three-build&utm_content=utility-post
+```
+
+## Telegram
+
+```text
+What $THREE does this week: the code behind the claims.
+Every $THREE holder perk on three.ws is registered in open source with an enforced flag. The tier page only says Live when that flag is true, which today means two perks.
+Read it, and open an issue if the page and the code ever disagree: github.com/nirholas/three.ws
+https://github.com/nirholas/three.ws/blob/main/api/_lib/three-access.js?utm_source=telegram&utm_medium=community&utm_campaign=mkt-2026-11-three-build&utm_content=utility-telegram
+```
+
+## GitHub Discussions (primary channel)
+
+GitHub Discussions post (title: "How $THREE holder perks are marked Live or Planned"): link `api/_lib/three-access.js`, explain the `enforced` flag in two sentences, list the two enforced gates with their handler files (`api/forge.js`, `api/forge-gameready.js`), and ask for issues where a surface claims more than the registry. Add the production configuration gaps from this season's README only if the owner approves making them public.
+
+## User action
+
+Read `api/_lib/three-access.js`, compare it with `/three`, and open an issue or discussion reply.
+
+## KPI and where to read it
+
+Repo visits, discussions, and issues. GitHub Insights traffic for the week; new issues and discussion replies that reference `three-access` or `$THREE`.
+
+Record the 24-hour and seven-day rows in the format in [measurement.md](../growth/measurement.md).
+
+## Posting-day checklist
+
+- [ ] Re-open the linked surface in a clean browser and confirm it loads without errors.
+- [ ] Confirm the lines and enforced count on `main` are unchanged.
+- [ ] Re-run `capture.mjs --only 11`.
+- [ ] Attach the image and paste the alt text.
+- [ ] Owner presses publish. Nothing in this pack posts automatically.
+
+## Do not
+
+- Do not quote star or fork counts from the frame.
+- No price, return, urgency, or "moon" language. No hashtags, no emoji.
diff --git a/marketing/three-utility-season/12-quarter-recap.md b/marketing/three-utility-season/12-quarter-recap.md
new file mode 100644
index 000000000..0f99b6f5b
--- /dev/null
+++ b/marketing/three-utility-season/12-quarter-recap.md
@@ -0,0 +1,81 @@
+# Edition 12: What $THREE does this week, verified utility outcomes (quarter recap)
+
+| Field | Value |
+|---|---|
+| Campaign id | `MKT-2026-12-THREE-QUARTER` |
+| Publish date | 2026-12-04 |
+| Chapter | Transparency |
+| Audience | community and holders |
+| Campaign anchor (campaigns.csv) | https://three.ws/three-token |
+| Surface used in this pack | /three |
+| Verified status (2026-09-16) | **Live (recap of live state; figures read on posting day).** |
+
+## Verification
+
+**Substitute:** The link moves to `/three`, where the Live and Planned count is visible.
+
+- `/api/three/access` returns every registered perk with `enforced`; on 2026-09-16 the count was 2 of 7.
+- Season results come from the seven-day result rows recorded under `marketing/growth/measurement.md` for each campaign id above.
+
+## The three questions
+
+- **What can a holder do now?** Open `/three`, use the most relevant LIVE perk, and reply with the next walkthrough to cover.
+- **Where does $THREE enter?** Summary of the season: where $THREE was held or checked, and what each walkthrough produced.
+- **What verifiable result comes out?** A count anyone can reproduce from `/api/three/access`, plus the action totals the team recorded per edition.
+
+## Numbers and their sources
+
+| Volatile figure (read on posting day) | Source |
+|---|---|
+| `{LIVE_COUNT}`: number of features with `enforced: true` | `/api/three/access`, read on posting day |
+| `{TOTAL_COUNT}`: number of features listed | `/api/three/access`, read on posting day |
+
+## Media
+
+- File: [`images/12-quarter-recap.png`](./images/12-quarter-recap.png), 1080x1350, captured 2026-09-16 from `/three` by `node marketing/three-utility-season/capture.mjs --only 12`.
+- Alt text (required on every post):
+
+> Vertical capture of the three.ws $THREE Tiers page showing all tiers from Member to Genesis, with Bronze perks marked LIVE and Silver and Gold perks marked PLANNED.
+
+## X post
+
+Weighted length: **149 characters** (URL counted as 23, as `scripts/post-tweet.mjs` does; counted with the 2026-09-16 values filled in).
+
+```text
+{LIVE_COUNT} of {TOTAL_COUNT} $THREE holder perks on three.ws are Live today and the rest are marked Planned. Which one should we walk through next? https://three.ws/three?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-12-three-quarter&utm_content=utility-post
+```
+
+## Telegram
+
+```text
+What $THREE did this quarter.
+{LIVE_COUNT} of the {TOTAL_COUNT} $THREE holder perks on three.ws are Live today, and the rest are marked Planned on three.ws/three.
+This season's walkthroughs: tiers, free-quota multipliers, gated 3D embeds, Forge Max, deploy fees from the MCP server, the tier API, the buyback ledger, Game-Ready export, and the open-source perk registry.
+Reply with the one you want walked through next.
+https://three.ws/three?utm_source=telegram&utm_medium=community&utm_campaign=mkt-2026-12-three-quarter&utm_content=utility-telegram
+```
+
+## User action
+
+Open `/three`, use the most relevant LIVE perk, and reply with the next walkthrough to cover.
+
+## KPI and where to read it
+
+Utility actions across the series: sum the per-edition seven-day results; replies naming a next walkthrough.
+
+Record the 24-hour and seven-day rows in the format in [measurement.md](../growth/measurement.md).
+
+## Posting-day checklist
+
+- [ ] Re-open the linked surface in a clean browser and confirm it loads without errors.
+- [ ] Fill `{LIVE_COUNT}` and `{TOTAL_COUNT}` from `/api/three/access` within the hour before posting.
+- [ ] If any substituted edition was restored during the quarter, add it to the Telegram list only if its seven-day result row exists.
+- [ ] Re-run `capture.mjs --only 12`.
+- [ ] Attach the image and paste the alt text.
+- [ ] Owner presses publish. Nothing in this pack posts automatically.
+
+## Do not
+
+- Do not add totals that were not recorded in a result row.
+- Do not describe the quarter in price terms.
+- No price, return, urgency, or "moon" language. No hashtags, no emoji.
diff --git a/marketing/three-utility-season/README.md b/marketing/three-utility-season/README.md
new file mode 100644
index 000000000..8035c9c65
--- /dev/null
+++ b/marketing/three-utility-season/README.md
@@ -0,0 +1,112 @@
+# The $THREE utility season: "What $THREE does this week"
+
+Twelve weekly editions, owned by Growth, scheduled as the `utility` rows of
+[`marketing/growth/campaigns.csv`](../growth/campaigns.csv). Each edition shows one thing a holder can
+do on three.ws today, where `$THREE` enters that action, and what anyone can check afterwards. This
+directory holds the finished kit: verified status, copy, media, alt text, the user action, the KPI, and
+a posting-day checklist per edition. Publishing stays with the owner.
+
+`$THREE` contract address (Solana): `FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump`
+
+## The editorial rule
+
+**Show the action, not the ticker.** Every post answers the three questions from the
+[operating plan](../OPERATING-PLAN.md): what can a holder do now, where does `$THREE` enter, and what
+verifiable result comes out. On top of that, every post follows [the announcement voice](../../docs/announce-voice.md):
+
+- 100 to 179 weighted characters on X (a URL counts as 23), one checkable claim, one link, real media.
+- No hashtags, no emoji, no price, return, urgency, or "moon" language.
+- Live and planned are stated plainly. A feature that does not work in production today is not written
+ as live. When the scheduled surface failed verification, the edition uses the closest live substitute
+ and says so in its pack.
+- Every number is either a stable fact with its capture date or a placeholder read from a named endpoint
+ on posting day.
+
+## What verification found (2026-09-16)
+
+Every scheduled surface was traced from `vercel.json` to its handler and exercised against
+production. Seven of the twelve scheduled stories could not be run as written (six are substituted, one is narrowed to the MCP server), because the `$THREE`
+spend paths are switched off or broken in production. Every hold-based utility checked out. The season
+was rebuilt around what works, and each substitution is recorded in its pack.
+
+| Finding | Evidence | Editions affected |
+|---|---|---|
+| The `$THREE` token payment rail refuses every quote | Signed-in `POST /api/token/quote` returns `treasury_unavailable`; `GET /api/token/config` shows `treasury_configured: false`, `rewards_configured: false` (`THREE_TREASURY_WALLET` and `THREE_REWARDS_WALLET` unset) | 03, 04, 10 (pay-per-use, marketplace, holder rewards) |
+| Plan checkout cannot create an intent in any asset | Signed-in `POST /api/payments/solana/checkout` returns `503 not_configured` (`PAYMENT_RECIPIENT_SOLANA` unset) | 02 |
+| Marketplace has no confirmed sale, `$THREE` skill prices are not rendered, and the gasless purchase builder uses the legacy token program for a Token-2022 mint | `/api/marketplace/analytics`: `totalSales: 0`; `api/_lib/solana/gasless-tx.js` | 03, 10 |
+| Labor market escrow is offline | `/api/labor/feed`: `escrow_configured: false` (`LABOR_ESCROW_SECRET_BASE58` unset) | 04 |
+| `/play` token gate is off and boutique sales cannot settle | No `PLAY_GATE_MINT` or `THREE_MINT`; `three-ws-multiplayer` has no `GAME_TOKEN_TREASURY` | 07 |
+| x402 advertises `$THREE` but the self-hosted facilitator rejects Token-2022 transfers | `api/_lib/x402/self-facilitator.js` only allows the legacy token program | 08 |
+| Holder deploy discount exists only in the MCP server; the browser deployer charges no fee, and `/deploy` is the model viewer | `src/deploy-onchain.js`, `vercel.json` | 06 |
+| Premium Data API pass cannot quote `$THREE` and builds with the legacy token program | Signed-in `POST /api/premium/quote` returns `quote_failed` for THREE and USDC (SOL works) | not used |
+| Public "burned" figures are computed, not on-chain | `/api/three-token/burns` and `/three-live` report `agents x 1000`; the token config says the platform never burns | 09 (do not cite) |
+
+## Schedule
+
+| Date | Edition | Surface used | Verified status | File | X length |
+|---|---|---|---|---|---|
+| 2026-09-18 | 01 hold-to-access tiers | `/three` | Live | [01-access-tiers.md](./01-access-tiers.md) | 174 |
+| 2026-09-25 | 02 lower-cost access | `/forge` (holder free-quota multiplier) | Plan checkout not live; substitute | [02-holder-free-quota.md](./02-holder-free-quota.md) | 170 |
+| 2026-10-02 | 03 marketplace settlement | `/docs/mcp` (`create_gated_embed`) | Marketplace not demonstrable; substitute | [03-gated-embed-mcp.md](./03-gated-embed-mcp.md) | 163 |
+| 2026-10-09 | 04 agent labor and escrow | `/forge-max` (Bronze holder perk) | Escrow enabled but off; substitute | [04-forge-max-holder.md](./04-forge-max-holder.md) | 171 |
+| 2026-10-16 | 05 token-gated 3D content | `/docs/token-gated-3d-embeds` | Live (API and MCP; no Studio control) | [05-gated-embed-create.md](./05-gated-embed-create.md) | 167 |
+| 2026-10-23 | 06 holder deployment benefits | deploy MCP server fee schedule | Live in the MCP server only | [06-deploy-fee-waiver.md](./06-deploy-fee-waiver.md) | 175 |
+| 2026-10-30 | 07 world access and purchases | live gated embed unlock | `/play` purchases off; substitute | [07-holder-scene-unlock.md](./07-holder-scene-unlock.md) | 165 |
+| 2026-11-06 | 08 agent tools over x402 | `GET /api/three/tier` | `$THREE` over x402 not settleable; substitute | [08-tier-api-for-agents.md](./08-tier-api-for-agents.md) | 161 |
+| 2026-11-13 | 09 public utility receipts | `/three-token` buyback ledger | Live (reads zero) | [09-buyback-ledger.md](./09-buyback-ledger.md) | 175 |
+| 2026-11-20 | 10 creator earnings | `/three` (Game-Ready export perk) | Creator earnings not live; substitute | [10-gameready-holder.md](./10-gameready-holder.md) | 163 |
+| 2026-11-27 | 11 built in public | `api/_lib/three-access.js` on GitHub | Live | [11-built-in-public.md](./11-built-in-public.md) | 172 |
+| 2026-12-04 | 12 quarter recap | `/three` | Live (figures read on posting day) | [12-quarter-recap.md](./12-quarter-recap.md) | 149 |
+
+X lengths for 09 and 12 are counted with the 2026-09-16 values filled into their placeholders.
+
+If the production configuration is fixed before an edition's date, its pack names the check that proves
+it (a real checkout, a settled sale, a settled bounty) and the owner can restore the original story.
+Restoring means rewriting and re-capturing that edition; the substitute copy does not describe the
+original surface.
+
+## Files
+
+- `NN-<slug>.md`: one pack per edition.
+- `images/`: the captured media, 1600x900 (edition 12 is 1080x1350 for a vertical placement).
+- `capture.mjs`: re-captures every image from the live site. Run it on posting day so the frame matches
+ the figures in the post:
+
+ ```bash
+ node marketing/three-utility-season/capture.mjs --only 09
+ ```
+
+ It hides floating site chrome (getting-started stack, walking companion, language picker) and nothing
+ else, and it exits non-zero when a frame cannot be captured.
+
+## How to run a week
+
+1. **Monday:** open the edition pack. Re-run every check in its posting-day checklist. If a
+ check fails, do not post; move the edition and tell the owner which check failed.
+2. **Re-read figures:** fill any `{PLACEHOLDER}` from the named endpoint within the hour before posting,
+ then recount the post (`node -e` with the weighting in `scripts/post-tweet.mjs`, or
+ `node scripts/post-tweet.mjs --file <file> --dry-run`, which prints the count and posts nothing).
+3. **Re-capture:** `node marketing/three-utility-season/capture.mjs --only NN`, then open the image and
+ confirm it is not blank, erroring, or mid-load.
+4. **Publish (owner):** X post with the image and alt text, then the Telegram version. Edition 11 goes to
+ GitHub Discussions first.
+5. **24 hours and seven days:** record the result row with the campaign id, following
+ [measurement.md](../growth/measurement.md), using the KPI source named in the pack. Unique wallets
+ and repeat actions are the season's primary measure.
+6. **Update `campaigns.csv`:** change the row's status only after the post is live and its URL is recorded.
+
+## Owner actions that unblock the original schedule
+
+These are configuration choices about where real funds are received, so they are the owner's to make.
+Each is a single `gcloud run services update --update-env-vars` on the named service.
+
+| Variable | Service | Unblocks |
+|---|---|---|
+| `THREE_TREASURY_WALLET`, `THREE_REWARDS_WALLET` | `three-ws-api` | `$THREE` pay-per-use (Forge High, Game-Ready), marketplace token rail, holder rewards |
+| `PAYMENT_RECIPIENT_SOLANA` | `three-ws-api` | Plan checkout in USDC, SOL, and `$THREE` (edition 02 original) |
+| `LABOR_ESCROW_SECRET_BASE58` | `three-ws-api` | Labor market escrow (edition 04 original) |
+| `GAME_TOKEN_TREASURY` (and `PLAY_GATE_MINT` if the world should be gated) | `three-ws-multiplayer` | `/play` boutique and paid spins (edition 07 original) |
+
+Three need code changes, not configuration: Token-2022 support in the x402 self-facilitator (edition 08),
+in the marketplace gasless purchase builder and the Premium pass quote builder (editions 03 and 10), and
+the deploy fee in the browser deployer at `/deploy-onchain` (edition 06).
diff --git a/marketing/three-utility-season/capture.mjs b/marketing/three-utility-season/capture.mjs
index a18ec129c..84e6965f6 100644
--- a/marketing/three-utility-season/capture.mjs
+++ b/marketing/three-utility-season/capture.mjs
@@ -40,22 +40,23 @@ const GH = 'https://github.com/nirholas/three.ws/blob/main';
const RECIPES = [
{ id: '01', file: '01-access-tiers.png', route: '/three', size: [1600, 900] },
{ id: '02', file: '02-holder-free-quota.png', route: '/forge', size: [1600, 900] },
- { id: '03', file: '03-gated-embed-mcp-tool.png', route: `${GH}/api/_mcp/tools/embed.js#L227`, scrollText: "name: 'create_gated_embed'", offset: 260, size: [1600, 900] },
+ { id: '03', file: '03-gated-embed-mcp-tool.png', route: `${GH}/api/_mcp/tools/embed.js#L227`, size: [1600, 900] },
{ id: '04', file: '04-forge-max-holder.png', route: '/forge-max', size: [1600, 900] },
{ id: '05', file: '05-gated-embed-docs.png', route: '/docs/token-gated-3d-embeds', size: [1600, 900] },
- { id: '06', file: '06-deploy-fee-waiver.png', route: `${GH}/packages/metaplex-agent-mcp/src/config.js#L87`, scrollText: 'the deploy fee and the holder waiver', offset: 40, size: [1600, 900] },
+ { id: '06', file: '06-deploy-fee-waiver.png', route: `${GH}/packages/metaplex-agent-mcp/src/config.js#L110`, size: [1600, 900] },
{ id: '07', file: '07-holder-scene-unlock.png', route: '/embed/v1/gated.html?asset=avatar%3Abf2d5c4b-2536-4593-bf15-ec934a6c9f48', size: [1600, 900] },
{ id: '08', file: '08-tier-api.png', route: TIER_API, prettyPrint: true, size: [1600, 900] },
- { id: '09', file: '09-buyback-ledger.png', route: '/three-token', scrollText: 'in platform revenue earned so far', offset: 420, size: [1600, 900] },
+ { id: '09', file: '09-buyback-ledger.png', route: '/three-token', scrollText: 'committed to buybacks', offset: 330, size: [1600, 900] },
{ id: '10', file: '10-gameready-holder.png', route: '/three', scrollY: 470, size: [1600, 900] },
- { id: '11', file: '11-built-in-public.png', route: `${GH}/api/_lib/three-access.js#L30`, scrollText: 'enforced ', offset: 160, size: [1600, 900] },
+ { id: '11', file: '11-built-in-public.png', route: `${GH}/api/_lib/three-access.js#L30`, size: [1600, 900] },
{ id: '12', file: '12-quarter-recap.png', route: '/three', size: [1080, 1350] },
];
async function frame(page, recipe) {
if (recipe.prettyPrint) {
// Chromium's JSON viewer: tick its own Pretty-print toggle so the payload reads.
- await page.getByLabel('Pretty-print').check().catch(() => page.locator('input[type=checkbox]').first().check());
+ const box = page.locator('input[type=checkbox]').first();
+ if (await box.count()) await box.click({ force: true });
await page.waitForTimeout(800);
}
if (recipe.scrollY) {
@@ -64,9 +65,20 @@ async function frame(page, recipe) {
return page.screenshot();
}
if (recipe.scrollText) {
- const loc = page.getByText(recipe.scrollText, { exact: false }).first();
- await loc.scrollIntoViewIfNeeded({ timeout: 15000 });
- await page.evaluate((dy) => window.scrollBy(0, -dy), recipe.offset ?? 140);
+ // Put the first element whose own text contains scrollText at the top of the
+ // viewport, then back off by `offset` pixels so its heading has context.
+ const found = await page.evaluate(({ text, offset }) => {
+ const walker = document.createTreeWalker(document.body, NodeFilter.SHOW_TEXT);
+ for (let n = walker.nextNode(); n; n = walker.nextNode()) {
+ if (n.textContent.includes(text)) {
+ const top = n.parentElement.getBoundingClientRect().top + window.scrollY;
+ window.scrollTo(0, Math.max(0, top - offset));
+ return true;
+ }
+ }
+ return false;
+ }, { text: recipe.scrollText, offset: recipe.offset ?? 140 });
+ if (!found) throw new Error(`text not found on page: ${recipe.scrollText}`);
await page.waitForTimeout(1200);
return page.screenshot();
}
diff --git a/marketing/three-utility-season/images/03-gated-embed-mcp-tool.png b/marketing/three-utility-season/images/03-gated-embed-mcp-tool.png
index d97f19112..d57cf72a1 100644
Binary files a/marketing/three-utility-season/images/03-gated-embed-mcp-tool.png and b/marketing/three-utility-season/images/03-gated-embed-mcp-tool.png differ
diff --git a/marketing/three-utility-season/images/09-buyback-ledger.png b/marketing/three-utility-season/images/09-buyback-ledger.png
index 712499ac8..93abf7901 100644
Binary files a/marketing/three-utility-season/images/09-buyback-ledger.png and b/marketing/three-utility-season/images/09-buyback-ledger.png differ
diff --git a/marketing/three-utility-season/images/10-gameready-holder.png b/marketing/three-utility-season/images/10-gameready-holder.png
index 613969615..3fcce3c30 100644
Binary files a/marketing/three-utility-season/images/10-gameready-holder.png and b/marketing/three-utility-season/images/10-gameready-holder.png differ
diff --git a/marketing/three-utility-season/images/11-built-in-public.png b/marketing/three-utility-season/images/11-built-in-public.png
index 98ce2af60..4ac3ffa40 100644
Binary files a/marketing/three-utility-season/images/11-built-in-public.png and b/marketing/three-utility-season/images/11-built-in-public.png differ