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(events): add turnkey kits for IBM event two, the November Three World Session, and the Open Source Friday contribution menu
nirholas231a26661d5f
diff --git a/docs/announcements/open-source-friday.md b/docs/announcements/open-source-friday.mdindex 4649ee46d..9d5bfabab 100644--- a/docs/announcements/open-source-friday.md+++ b/docs/announcements/open-source-friday.md@@ -29,6 +29,10 @@ a first issue now and it gets merged on air.| Teaching it a 12th is an open first issue | [#110](https://github.com/nirholas/three.ws/issues/110) (Apple / ARKit `_joint`), [#111](https://github.com/nirholas/three.ws/issues/111) (Kinect trailing-side), [#112](https://github.com/nirholas/three.ws/issues/112) (Reallusion numbered spine), all open and labelled `good first issue`, each naming its file and verification command || We merge it live | The owner is the reviewer on this repo, so a PR opened on stream can be reviewed and merged on stream. This is section 4 of the runsheet. |+**Re-check before posting (2026-09-17):** #110, #111, and #112 were all closed on 2026-09-14 and+2026-09-15, and the repo had no open issues, so "an open first issue" is not true until the owner+creates the new ones in the [contribution menu](../../marketing/growth/events/open-source-friday-menu.md).+The 0-of-10-joints framing belongs to #110 and #111 only. #112 is a two-joint spine gap on anotherwise-mapped skeleton, so do not describe it as a convention that maps nothing.diff --git a/docs/first-contribution.md b/docs/first-contribution.mdindex da62bccea..e8d29e4fe 100644--- a/docs/first-contribution.md+++ b/docs/first-contribution.md@@ -45,13 +45,13 @@ No scratch files in the repo root: probe the function straight from the shell.```bashnode --input-type=module -e "import { canonicalizeBoneName as c } from './src/glb-canonicalize.js';-for (const n of ['left_arm_joint', 'hips_joint', '左腕', 'upperarm_l']) console.log(n, '->', c(n));+for (const n of ['Character1Hips', 'hips_joint', '左腕', 'upperarm_l']) console.log(n, '->', c(n));"``````-left_arm_joint -> null Apple / ARKit rigs: not supported yet (issue #110)-hips_joint -> null+Character1Hips -> null HumanIK after three.js strips the colon: not supported yet+hips_joint -> Hips Apple / ARKit rigs: supported左腕 -> LeftArm MikuMikuDance: supported, added 2026-08-21upperarm_l -> LeftArm Unreal mannequin: supported```@@ -134,11 +134,13 @@ describe('MMD (MikuMikuDance) Japanese skeleton', () => {### Now do one that is actually open-MMD is done, so do not re-submit it. Pick a convention that still returns `null` and give it the same four-part treatment (alias map, tests, Rig Doctor fingerprint, docs row). Three are verified open and waiting, each with the file, the bones, and the verification command spelled out:+MMD is done, so do not re-submit it. So are Apple / ARKit, Kinect, and the Reallusion numbered spine: the three issues this section used to list were all merged in September 2026. Pick a convention that still returns `null` and give it the same four-part treatment (alias map, tests, Rig Doctor fingerprint, docs row). The next ones are verified open and written up with the file, the bones, and the verification command:-- [#110](https://github.com/nirholas/three.ws/issues/110): Apple / ARKit rigs, which suffix every joint with `_joint` (`hips_joint`, `left_arm_joint`). 0 of 10 joints map today.-- [#111](https://github.com/nirholas/three.ws/issues/111): Kinect rigs, which put the side word last (`ShoulderLeft`, `ElbowLeft`, `SpineBase`). 0 of 10 map today.-- [#112](https://github.com/nirholas/three.ws/issues/112): Reallusion Character Creator 3/4, whose numbered spine chain (`CC_Base_Spine01`, `CC_Base_Spine02`) returns `null` while the rest of the CC skeleton already maps. A smaller gap than the other two, and a good first one if you want the shape of the change without the full ten joints.+- **HumanIK after three.js loads it.** `Character1:Hips` maps, but three.js deletes the colon when it loads a model, and the runtime retargeter then sees `Character1Hips`, which maps to nothing. The smallest of the three.+- **3ds Max Biped fingers.** The body maps; `Bip01 L Finger0`, `Finger01`, and the rest of the numbered finger chain do not.+- **Source engine skeletons.** `ValveBiped.Bip01_Pelvis` and the rest of the `ValveBiped` rig map to nothing, and Rig Doctor does not recognise the convention.++Find them under the [`good first issue`](https://github.com/nirholas/three.ws/labels/good%20first%20issue) label. If a label search comes back empty, the ready-to-file bodies are in [marketing/growth/events/osf-issues/](../marketing/growth/events/osf-issues/01-rig-humanik-sanitized-names.md), and you can work from them directly.Comment on the one you are taking, then:diff --git a/docs/ibm-next-event.md b/docs/ibm-next-event.mdindex 9295c7b9c..390e71c33 100644--- a/docs/ibm-next-event.md+++ b/docs/ibm-next-event.md@@ -10,6 +10,14 @@ This document is the proposal for the second one. It exists so the conversationstarts from a concrete run of show rather than a format debate, and so the engineering workis scoped before a date is promised.+**The turnkey kit for event two** (event page, both IBM emails, every post, a minute-by-minute+run of show inside `/play`, and three October dates) is+[marketing/growth/events/ibm-event-two.md](../marketing/growth/events/ibm-event-two.md). It+runs a one-hour in-world session that can serve as the Forge-Off Open's kickoff. One claim below+needs re-checking before it is used in IBM copy: `api/_lib/publish-safety.js` now screens with an+NVIDIA NemoGuard classifier, not Granite Guardian, so the responsible-AI argument under Option A+no longer matches the code.+**The goal is not another audience. It is usage.** A webinar is measured in registrationsand a recording. This event is measured in how many people typed something into three.wswho never had before, and how many of them came back the next day. Everything below isdiff --git a/docs/open-source-friday-plan.md b/docs/open-source-friday-plan.mdindex 3cc059a5d..f3c0a37bc 100644--- a/docs/open-source-friday-plan.md+++ b/docs/open-source-friday-plan.md@@ -6,6 +6,7 @@**Criteria:** [admin/project-criteria.md](https://github.com/githubevents/open-source-friday/blob/main/admin/project-criteria.md)**Request form:** https://github.com/githubevents/open-source-friday/issues/new?template=osf-guest-invite.yml**Our request:** https://github.com/githubevents/open-source-friday/issues/254 (opened 2026-08-25)+**Contribution menu and booking reply:** [marketing/growth/events/open-source-friday-menu.md](../marketing/growth/events/open-source-friday-menu.md) (approved; all six August issues are closed, so the menu carries seven new verified issue bodies)---@@ -114,7 +115,7 @@ This follows the order and length in their own [Streaming Guide](https://github.| 0:05-0:08 | What is your project? | Prompt to rigged avatar to embedded on a blank page, narrated, no slides || 0:08-0:18 | Demo | (a) generate an avatar live and watch it animate, (b) one `<agent-3d>` tag in an empty `index.html`, drive mood from the console, (c) upload an unsupported rig to [Rig Doctor](https://three.ws/rig-doctor) and show exactly which joints will not move. Fallback GLB staged in case a worker is slow || 0:18-0:23 | Motivation / how it started | Why "3D agent" was a dead end until rendering and runtime could talk; what broke the first three times |-| 0:23-0:33 | How can people contribute? | Done live: take [#110](https://github.com/nirholas/three.ws/issues/110) or [#111](https://github.com/nirholas/three.ws/issues/111), write the mapping, write the test, run `npx vitest run tests/glb-canonicalize.test.js`, open the PR on air, merge it on air |+| 0:23-0:33 | How can people contribute? | Done live: take the HumanIK issue (issue 1 in the [contribution menu](../marketing/growth/events/open-source-friday-menu.md); #110 and #111, the original picks, were closed on 2026-09-15), write the mapping, write the test, run `npx vitest run tests/glb-canonicalize.test.js`, open the PR on air, merge it on air || 0:33-0:36 | Last thing pushed / next thing | Read it off the [public changelog](https://three.ws/changelog); it ships to Telegram on every release so the honest answer is the only one available || 0:36-0:42 | Audience questions | End with the `good first issue` list on screen, by number || 0:42-0:45 | Wrap-up questions | Best tip for new contributors: comment on the issue before you start, one line. They also ask favourite song, an emoji, and an ice cream flavour; have answers, do not improvise on air |@@ -190,7 +191,9 @@ Every hard criterion is met, stars included. What remains is one click, polish,| 2026-08-25 | **Issue submitted**: [open-source-friday#254](https://github.com/githubevents/open-source-friday/issues/254) | Done || 2026-08-25 | Reply to Andrea's X thread with the issue link (draft: [x-posts/osf-issue-reply.md](x-posts/osf-issue-reply.md)) | Owner || 2026-08-28+ | Booking link arrives on approval, book the slot | Owner |-| ~2026-09-11 | Stream (earliest date satisfying the two-week rule) | Owner |+| 2026-09-01 | Approved; booking bot asked for a date | Done |+| 2026-09-17 | All six August issues closed; seven new issue bodies and the booking reply written ([menu](../marketing/growth/events/open-source-friday-menu.md)) | Done |+| Next | Book a Friday (earliest October 2), reply on #254, create the menu issues | Owner |---diff --git a/marketing/growth/README.md b/marketing/growth/README.mdindex 4a58154b8..fb5b2270f 100644--- a/marketing/growth/README.md+++ b/marketing/growth/README.md@@ -27,6 +27,9 @@ This directory is the operational layer above the repo's deeper source material:- [Measurement](./measurement.md): the UTM convention, campaign scorecard, and weekly review.- [Co-marketing templates](./templates.md): a one-page partner brief, social amplificationrequest, event invitation, and post-campaign proof note.+- [Community event kits](./events/README.md): the turnkey kits for IBM Community event two,+ the monthly Three World Session template with the November session filled in, and the Open+ Source Friday contribution menu with its booking reply.The existing [partnership pipeline](../../docs/partners/opportunities.md) remains the sourceof truth for the state of a listing or partner program. The existing@@ -179,10 +182,12 @@ wording.The execution order is deliberately narrow:1. Book the approved [GitHub Open Source Friday issue #254](https://github.com/githubevents/open-source-friday/issues/254),- then activate the existing announcement and stream plan.+ then activate the existing announcement and stream plan. The booking reply and the seven+ first issues to create are in the [contribution menu](./events/open-source-friday-menu.md).2. Send one IBM relationship note covering the second event, the promised IBM-domain page,the promised social co-promotion, and Partner Plus marketing access. Send the Agent Connect- `APP_ID` request separately to its program inbox.+ `APP_ID` request separately to its program inbox. Both emails, the event page, every post,+ and the run of show are in the [event two kit](./events/ibm-event-two.md).3. Submit the prepared OpenAI Showcase packet and request that three.ws be made visible in theOpenAI Partner Locator if it is absent from the authenticated partner record.4. Publish one finished NVIDIA technical post, then use the live NVIDIA-domain URL as the@@ -239,5 +244,6 @@ partner response are recorded.| What exists on Hugging Face? | [Hugging Face index](../../docs/huggingface.md) || What can be claimed about $THREE utility? | [$THREE thesis](../../docs/three-thesis.md) || What is the Open Source Friday state? | [Stream plan](../../docs/open-source-friday-plan.md) |+| What runs at the next community event? | [Community event kits](./events/README.md) |Last verified: **2026-09-15**.diff --git a/marketing/growth/events/README.md b/marketing/growth/events/README.mdnew file mode 100644index 000000000..865e806e0--- /dev/null+++ b/marketing/growth/events/README.md@@ -0,0 +1,38 @@+# Community event kits++Turnkey kits for the next three community events in the+[marketing command center](../README.md). Each kit is paste-ready: copy, dates, emails, posts+for every beat, a minute-by-minute run of show on verified product surfaces, the event config,+and the owner's steps in order. The owner books a date and presses send; nothing here posts,+emails, or creates anything by itself.++| Event | Kit | Campaign | Date | State |+|---|---|---|---|---|+| IBM Community event two: Give an Agent a Body, Live | [ibm-event-two.md](./ibm-event-two.md) | `MKT-2026-09-IBM-EVENT` | Three October Thursdays offered; October 15 recommended | Kit ready; awaiting date, IBM speaker, and the two emails |+| Three World Session, November: An Agent Pays for Its Own Tool | [three-world-session.md](./three-world-session.md) (Part 2) | `MKT-2026-11-IBM-WORLD-2` | Tuesday, November 24, 2026 (November 17 as the fallback) | Kit ready; follows event two |+| GitHub Open Source Friday | [open-source-friday-menu.md](./open-source-friday-menu.md) and the [stream plan](../../../docs/open-source-friday-plan.md) | `MKT-2026-09-OSF` | Any bookable Friday from October 2, 2026 | Approved; booking reply and seven issue bodies ready |++## How the kits fit together++- **The package** is the T-21 to T+7 table in the command center+ ([the community becomes the stage](../README.md#3-the-community-becomes-the-stage)). Every kit+ implements it beat for beat.+- **The template** for any future monthly session is Part 1 of+ [three-world-session.md](./three-world-session.md): nine slots to decide, a fixed timeline, a+ fixed run-of-show frame, and the rules every kit follows.+- **One event at a time.** `public/event.json` holds a single window, so a session's config is+ written at its T-14 and cleared at its T+1 (`npm run event:schedule -- --clear --apply`) before+ the next one is written. `npm run check:event` fails the gate on an expired window.+- **Links and numbers** follow [measurement.md](../measurement.md): campaign IDs in every UTM,+ and no count in any post unless it was captured with its time.+- **IBM-facing wording** follows [badge-usage.md](../../ibm-partner-plus/badge-usage.md) and+ [docs/ibm.md](../../../docs/ibm.md).++## Files++| Path | What it is |+|---|---|+| [ibm-event-two.md](./ibm-event-two.md) | Event page copy, the IBM relationship email, the Agent Connect `APP_ID` email, posts for X, LinkedIn, Telegram, and IBM Community at T-14, T-7, T-1, live, T+1, and T+7, run of show, event config, pre-flight, measurement, feature verification |+| [three-world-session.md](./three-world-session.md) | The reusable monthly template and the filled-in November session |+| [open-source-friday-menu.md](./open-source-friday-menu.md) | Seven verified first issues, one `gh issue create` command each, and the booking reply for issue #254 |+| [osf-issues/](./osf-issues) | The seven issue bodies, used with `gh issue create --body-file` |diff --git a/marketing/growth/events/ibm-event-two.md b/marketing/growth/events/ibm-event-two.mdnew file mode 100644index 000000000..11f060ccd--- /dev/null+++ b/marketing/growth/events/ibm-event-two.md@@ -0,0 +1,656 @@+# IBM Community event two: the complete kit++**Campaign:** `MKT-2026-09-IBM-EVENT` in [campaigns.csv](../campaigns.csv) (the ID stays as+written even though the session lands in October; [measurement.md](../measurement.md) forbids+renaming a campaign). **Venue:** the Three.ws User Group on IBM Community, held inside the+`$THREE` home town at `three.ws/play`. **Package:** the T-21 to T+7 event package in the+[command center](../README.md#3-the-community-becomes-the-stage).++Everything below is paste-ready. The owner's work is: pick one of the three dates, send the two+emails, create the IBM Community event, deploy the event config, and press post on each beat.+The ordered checklist is in [Owner steps](#owner-steps-in-order).++Read [the event proposal](../../../docs/ibm-next-event.md) for why this format, and+[badge-usage.md](../../ibm-partner-plus/badge-usage.md) before editing any IBM-facing sentence.++---++## Decisions already made (reverse any in one line)++| Decision | Choice | Why | Alternative |+|---|---|---|---|+| Format | 60-minute live session inside `/play`: live build, forge-into-the-world, IBM guest segment, an agent paying for a tool, community showcase | Every segment runs on a shipped, verified surface (see [Feature verification](#feature-verification)). The Forge-Off Open in the proposal is a week-long program and a bigger ask; this session is its natural kickoff | Run the Forge-Off Open as event two and use this run of show as its Day 0 |+| Recommended date | **Thursday 2026-10-15, 16:00 to 17:00 UTC** | Thursday is the live-demo day in the [weekly rhythm](../README.md#weekly-operating-rhythm). T-21 falls on 2026-09-24, which leaves IBM four weeks to list and staff it | The two alternates below |+| Time | 16:00 UTC | 12:00 PM Eastern, 9:00 AM Pacific, 5:00 PM London (BST): the one hour that is daytime for both US coasts and Europe | 17:00 UTC matches the first meetup's slot |+| Souvenir | Optional, new item | The Meetup Laurel is promised as never granted again, so it must not be reused | Run without a drop |+| Granite demo | **Not live on stage** | Production has no `WATSONX_*` credentials: `GET https://three.ws/api/ibm/galaxy` answers `watsonx_not_configured` (checked 2026-09-17). The IBM segment is IBM's to fill | Restore the credentials first, then add a Granite beat |++### The three candidate dates++All three are Thursdays in October 2026. US daylight saving time ends 2026-11-01, so every+October date is on Eastern Daylight Time (UTC-4).++| Option | Date | UTC | US Eastern | T-21 | T-14 | T-7 | T-1 | T+1 | T+7 | Calendar notes |+|---|---|---|---|---|---|---|---|---|---|---|+| **A (recommended)** | Thursday, October 15, 2026 | 16:00 to 17:00 | 12:00 to 1:00 PM EDT | Sep 24 | Oct 1 | Oct 8 | Oct 14 | Oct 16 | Oct 22 | Same week as the Oct 13 anchor campaign; no Thursday conflict |+| B | Thursday, October 22, 2026 | 16:00 to 17:00 | 12:00 to 1:00 PM EDT | Oct 1 | Oct 8 | Oct 15 | Oct 21 | Oct 23 | Oct 29 | Same week as the Oct 20 AWS anchor |+| C | Thursday, October 29, 2026 | 16:00 to 17:00 | 12:00 to 1:00 PM EDT | Oct 8 | Oct 15 | Oct 22 | Oct 28 | Oct 30 | Nov 5 | Day before the Oct 30 "live world access" utility post, which can then point at the replay; UK is back on GMT, so London is 4:00 PM |++**The copy below is written for Option A.** If B or C is booked, apply this find-and-replace+across the kit before posting, and nothing else changes (agenda beats are minutes after the+start, so they move with it). It applies to sections 1, 4, 5 and 6 only: the two emails in+sections 2 and 3 go out before a date is booked and already name all three options.++| Find (Option A) | Replace for B | Replace for C |+|---|---|---|+| `Thursday, October 15, 2026` | `Thursday, October 22, 2026` | `Thursday, October 29, 2026` |+| `Thu Oct 15` | `Thu Oct 22` | `Thu Oct 29` |+| `October 15` | `October 22` | `October 29` |+| `2026-10-15T16:00:00Z` | `2026-10-22T16:00:00Z` | `2026-10-29T16:00:00Z` |+| `2026-10-15T17:00:00Z` | `2026-10-22T17:00:00Z` | `2026-10-29T17:00:00Z` |+| `5:00 PM London` | `5:00 PM London` | `4:00 PM London` |+| `6:00 PM Berlin` | `6:00 PM Berlin` | `5:00 PM Berlin` |+| `tomorrow` (T-1 posts, sent Oct 14) | sent Oct 21 | sent Oct 28 |++---++## 1. IBM Community event page++Create it from the group's [events page](https://community.ibm.com/community/user/groups/community-home/recent-community-events?communitykey=e71510cc-d953-408f-9a1c-019f5c0a7016)+(or send this section to the IBM community manager if IBM creates it). The first meetup's page,+[ibm-community-meetup-play.html](../../../docs/ibm-community-meetup-play.html), is the format+reference.++**Event image:** do not reuse the first meetup's banner (its date is baked in) and do not place+the IBM 8-bar on a new one: [badge-usage.md](../../ibm-partner-plus/badge-usage.md) says the mark+comes only from IBM's partner portal under IBM's terms. Use a `/play` photo-mode card captured at+rehearsal (see [Pre-flight](#pre-flight-and-rehearsal)); it is stamped with the event name.++### Title++```text+Give an Agent a Body, Live: Three.ws User Group Session Inside the 3D World+```++### Abstract++```text+Most AI agents still live in a text box. In this session the Three.ws User Group meets inside+a live 3D world instead of on a call, and builds the alternative in front of you: a rigged,+animated agent generated from a single sentence, walking around the same world you are+standing in.++You join from your browser as an avatar. No download, no install, no account. Walk up to+people to talk with spatial voice, or use text chat. In one hour you will watch a text prompt+become a rigged 3D agent and put it on, forge a 3D object from a sentence and see it appear in+the world for everyone, hear from a guest from IBM, and watch two AI agents complete a real+pay-per-call transaction on screen, with a public on-chain receipt.++Hosted by three.ws in the Three.ws User Group on IBM Community. three.ws is an IBM Business+Partner. IBM does not endorse three.ws, and three.ws is not an IBM product.+```++### Agenda++```text+12:00 PM ET Doors open in the plaza. Welcome, and how to move, talk, and emote.+12:06 PM ET Live build: one sentence to a rigged, animated 3D agent, then we wear it.+12:15 PM ET Forge into the world: type a sentence in chat, place the 3D object for everyone.+12:22 PM ET Guest segment: [IBM SPEAKER: name, title, and topic, supplied and approved by IBM]+12:37 PM ET An agent pays for a tool: two agents settle a real micropayment, receipt on screen.+12:42 PM ET Community showcase: members show the avatars and builds they brought.+12:50 PM ET Open Q&A. The skeptical questions are the useful ones.+12:57 PM ET Group photo, and the date of the next session.+```++### Event details table++```text+When: Thursday, October 15, 2026, 12:00 to 1:00 PM Eastern (16:00 to 17:00 UTC)+Your time: 9:00 AM San Francisco, 12:00 PM New York, 5:00 PM London, 6:00 PM Berlin+Where: https://three.ws/event (countdown, add-to-calendar, and the door into the world)+Cost: Free+What you need: A modern desktop or laptop browser. No download, no install, no account.+Optional: Make your own avatar beforehand at https://three.ws/create and bring it.+```++### Login instructions field++```text+No account or login is required. At the event time open https://three.ws/event and press the+button into the world, or open https://three.ws/play and choose the pinned $THREE world. You+enter as a guest with an avatar assigned automatically. Press V in the world to change it,+including to one you made at https://three.ws/create.++Voice is spatial: your browser asks for microphone permission like any web call. Allow it to+talk, or decline and use text chat (press Enter). First time in a 3D world? A short controls+guide opens on your first visit, and the team is at the spawn point from 11:45 AM ET.+```++### Speaker slot (for IBM to fill)++| Field | Value |+|---|---|+| Segment | 12:22 to 12:37 PM ET, 15 minutes including 3 minutes of questions |+| Speaker | [IBM SPEAKER: name and title, supplied by IBM] |+| Topic | [IBM SPEAKER TOPIC: chosen by IBM. Suggested fit: governing AI agents in production, or listing agent tools for enterprise catalogs] |+| Format | Speaker joins the world as an avatar and talks over spatial voice from the plaza, or shares slides in the stream and is shown on the host's screen. Rehearsal slot offered on T-2 |+| Approval | IBM approves this segment's title, the speaker's name and title, and every sentence that describes IBM's role before the page goes live |++### Registration CTA++For the IBM Community page's register button and the closing line of every post:++```text+Register on IBM Community to get the reminder, then add it to your calendar at three.ws/event.+```++---++## 2. Relationship email to IBM++**To:** the IBM marketing contact from the 2026-06-18 meetings, as a reply on that existing+thread (the contacts are in the owner's inbox; no address is recorded in this repo, so none is+written here). **From:** [email protected]. **Send by:** T-21 (Sep 24 for Option A); the+[opportunity register](../opportunities.md) schedules it for 2026-09-18. **One ask per+paragraph, one thread.** The Agent Connect request goes separately (section 3).++Subject:++```text+Three.ws User Group: event two in October, the three.ws page, co-promotion, and Partner Plus marketing access+```++Body:++```text+Hi [IBM CONTACT FIRST NAME],++Following up on our June 18 conversations with a concrete next step, and four small asks.++1. Event two. We are ready to run the second Three.ws User Group session, again inside the+three.ws 3D world rather than on a call: a live build of a rigged 3D agent from one sentence,+an object forged into the world by the audience, two agents completing a real pay-per-call+transaction on screen, and a community showcase. We hold three dates, all Thursdays at 12:00+PM Eastern (16:00 UTC): October 15, October 22, or October 29. We would like to confirm one by+[DATE: T-21 of the earliest option you can support].++We provide the venue, the event page copy, moderation, rehearsal, the recording, visual assets,+and a recap within 24 hours. Could IBM help with one 15-minute speaker segment (topic is yours;+agent governance or enterprise agent catalogs would fit the audience) and a listing on the IBM+Community events calendar? The full event page copy is ready to send.++2. The dedicated three.ws page on the IBM domain discussed in June. Is there a next step or a+draft we can review? We can supply copy, architecture notes, and assets in whatever format+your team uses.++3. IBM social co-promotion. Once the event date is set, would IBM's social team share the+event page, and the recap afterwards? We will send the post copy, alt text, and a 16:9 image at+least 48 hours ahead.++4. Partner Plus marketing access. As a Build track partner, could you enable our access to My+Digital Marketing and the Build track Partner Marketing Kit? We would use it for this event+series first.++Jessica's recap of the first in-world meetup is on the group blog:+https://community.ibm.com/community/user/blogs/jessica-swanson/2026/08/08/the-first-threews-user-group-meetup-ibm++Thank you,+Nich+three.ws+```++Before sending: replace the two bracketed values, and confirm that nothing in the body says IBM+endorses, co-hosts, or partners on the event (it does not as written).++---++## 3. Agent Connect `APP_ID` request (separate email)++**To:** `[email protected]`, the program inbox documented in+[agent-connect-listing.md](../../ibm-partner-plus/agent-connect-listing.md#step-0-the-one-blocking-email).+That file's Step 0 is the source of truth; this is the same email, repeated here so the kit is+self-contained. Allow 2 to 3 business days. Save the `APP_ID` from the reply, then the listing is+a transcription job from that file into IBM Concierge.++Subject:++```text+MCP APP_ID Request - three.ws+```++Body:++```text+Company name: three.ws+MCP server name: three.ws 3d studio+Submission type: BYOL++Brief description: A remote MCP server that turns text prompts, images, and video into+textured, rigged, animation-ready 3D models and returns them as inline interactive+artifacts. Also performs remeshing, retexturing, segmentation, optimisation, and+automatic rigging on existing models.++We are an existing IBM Business Partner. three.ws agents can run on IBM Granite foundation+models served through IBM watsonx.ai.+```++The last sentence previously said Granite runs "in production". That is not true while the+production service has no watsonx credentials, so both copies now use the safe claim from+[badge-usage.md](../../ibm-partner-plus/badge-usage.md#the-claims-ranked-from-safe-to-forbidden).++---++## 4. Posts++**Rules that apply to every post:** no hashtags, no emoji, no em or en dashes; one link; every X+post carries an image (voice rule 1 in [announce-voice.md](../../../docs/announce-voice.md)).+Do not tag `@IBM` (Granite is not serving, so voice rule 4 does not hold) and do not name the+IBM speaker until IBM has approved the wording. Check each X post before sending with+`node scripts/post-tweet.mjs --text "<post>" --dry-run`, which prints the weighted count.++**Images:** T-14 and T-1 use the rehearsal photo-mode card; T-7 uses a 20-second screen+recording of `/forge` in chat placing an object in the plaza; Live uses a live photo-mode card;+T+1 uses the replay clip; T+7 uses the group photo.++**Links:** every link is `https://three.ws/event` with UTMs per+[measurement.md](../measurement.md). The channel values are listed once here so the posts stay+readable:++| Channel | Link |+|---|---|+| X | `https://three.ws/event?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-09-ibm-event&utm_content=<beat>` |+| LinkedIn | `https://three.ws/event?utm_source=linkedin&utm_medium=social&utm_campaign=mkt-2026-09-ibm-event&utm_content=<beat>` |+| Telegram | `https://three.ws/event?utm_source=telegram&utm_medium=community&utm_campaign=mkt-2026-09-ibm-event&utm_content=<beat>` |+| IBM Community | `https://three.ws/event?utm_source=ibm-community&utm_medium=partner&utm_campaign=mkt-2026-09-ibm-event&utm_content=<beat>` |++`<beat>` is `t14`, `t7`, `t1`, `live`, `t1-recap`, or `t7-proof`. The posts below show the X+link fully resolved; swap `utm_source`/`utm_medium` for the other channels.++### T-14 (Oct 1): announce and open registration++X:++```text+The next IBM Community user group session meets inside a 3D world, not a call: one sentence becomes a rigged agent live. Thu Oct 15, 16:00 UTC, no account. https://three.ws/event?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-09-ibm-event&utm_content=t14+```++LinkedIn:++```text+Most AI agents still live in a text box. On Thursday, October 15, the Three.ws User Group on IBM Community meets somewhere else: inside a live 3D world, in the browser, as avatars.++In one hour:+- one sentence becomes a rigged, animated 3D agent, live, and we walk around in it+- the audience forges 3D objects from chat and places them in the world for everyone+- a guest segment for the IBM Community audience+- two AI agents complete a real pay-per-call transaction on screen, with a public on-chain receipt+- a community showcase and open Q&A++12:00 PM Eastern / 16:00 UTC. Free. No download, no install, no account.++Register on IBM Community for the reminder, and add it to your calendar here:+https://three.ws/event?utm_source=linkedin&utm_medium=social&utm_campaign=mkt-2026-09-ibm-event&utm_content=t14++three.ws is an IBM Business Partner. IBM does not endorse three.ws, and three.ws is not an IBM product.+```++Telegram (community group and the release channel):++```text+Next community session: Thursday, October 15, 16:00 UTC (12:00 PM Eastern), inside the $THREE home town on three.ws/play, hosted in our IBM Community user group.++Live build of a rigged agent from one sentence, forge objects into the plaza together, a guest segment, and two agents paying each other on screen with a Solana receipt. Then your showcase: bring an avatar or a build and we put you on stream.++Countdown and add-to-calendar: https://three.ws/event?utm_source=telegram&utm_medium=community&utm_campaign=mkt-2026-09-ibm-event&utm_content=t14+```++IBM Community (new discussion thread in the group, linking the event listing):++```text+Title: October 15: Give an Agent a Body, Live (Three.ws User Group session two)++The second Three.ws User Group session is on the calendar: Thursday, October 15, 12:00 to 1:00 PM Eastern (16:00 UTC). Like the first meetup, it happens inside the three.ws 3D world in your browser rather than on a call.++What we will do in the hour:+1. Build a rigged, animated 3D agent from a single sentence, live, and wear it in the world.+2. Forge 3D objects from chat and place them in the plaza, audience included.+3. A guest segment for this community.+4. Watch two AI agents complete a pay-per-call transaction on screen, with a public receipt.+5. A member showcase, then open Q&A.++How to join: open https://three.ws/event?utm_source=ibm-community&utm_medium=partner&utm_campaign=mkt-2026-09-ibm-event&utm_content=t14 at the start time. No download, no install, no account.++Want a showcase slot? Reply here with what you will bring (an avatar, a build, an agent) and we will reserve up to three.++Please register on the event listing in the group's Events tab so you get the reminder.+```++### T-7 (Oct 8): demo clip and community challenge++X:++```text+Type /forge and a sentence into the world chat and the 3D object lands in the plaza for everyone. Forge one before Oct 15; the best go on stream. https://three.ws/event?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-09-ibm-event&utm_content=t7+```++LinkedIn:++```text+A one-week challenge before our October 15 session.++In three.ws/play, type /forge followed by a sentence into chat. The platform generates a textured 3D model from it and hands it back into the world, where one click places it for every player present. It persists, so the plaza keeps what the community builds.++Forge something before Thursday, October 15, take a photo with P (photo mode stamps the world and the date), and share it. The best three go on stream during the session's community showcase.++Countdown and calendar: https://three.ws/event?utm_source=linkedin&utm_medium=social&utm_campaign=mkt-2026-09-ibm-event&utm_content=t7+```++Telegram:++```text+One week to the October 15 session. Challenge: forge something into the plaza before then.++In three.ws/play, press Enter and type /forge followed by what you want, for example /forge a stone bench with brass fish. Click to place it when it lands. Press P for a photo and post it here. The best three are shown on stream on Thursday, October 15.++https://three.ws/event?utm_source=telegram&utm_medium=community&utm_campaign=mkt-2026-09-ibm-event&utm_content=t7+```++IBM Community (reply in the T-14 thread, not a new thread):++```text+One week out. A small warm-up for anyone who wants to try the world before Thursday, October 15: open three.ws/play, press Enter to open chat, and type /forge followed by a short description of one object. It is generated as a real 3D model and placed into the shared world for everyone. Post a photo (press P) in this thread and we will show the best three during the showcase.++https://three.ws/event?utm_source=ibm-community&utm_medium=partner&utm_campaign=mkt-2026-09-ibm-event&utm_content=t7+```++### T-1 (Oct 14): reminder with exact times++X:++```text+Tomorrow the IBM Community user group meets inside the three.ws world: 16:00 UTC, 12:00 PM Eastern. Any browser, no account, no download. https://three.ws/event?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-09-ibm-event&utm_content=t1+```++LinkedIn:++```text+Tomorrow, Thursday, October 15: the Three.ws User Group session inside the 3D world.++16:00 UTC / 12:00 PM Eastern / 9:00 AM Pacific / 5:00 PM London. One hour. Open the link in a desktop browser at the start time and you walk in as an avatar. The team is at the spawn point 15 minutes early for anyone new to 3D worlds.++https://three.ws/event?utm_source=linkedin&utm_medium=social&utm_campaign=mkt-2026-09-ibm-event&utm_content=t1+```++Telegram:++```text+Tomorrow: 16:00 UTC (12:00 PM Eastern, 9:00 AM Pacific, 5:00 PM London). The countdown chip goes gold in the plaza 30 minutes before, and we are at spawn 15 minutes early. Bring your forged objects and your avatar.++https://three.ws/event?utm_source=telegram&utm_medium=community&utm_campaign=mkt-2026-09-ibm-event&utm_content=t1+```++IBM Community (reply in the T-14 thread):++```text+Reminder: tomorrow, Thursday, October 15, 12:00 to 1:00 PM Eastern (16:00 UTC). Open https://three.ws/event?utm_source=ibm-community&utm_medium=partner&utm_campaign=mkt-2026-09-ibm-event&utm_content=t1 in a desktop browser at the start time. We are at the spawn point from 11:45 AM Eastern to help anyone get moving and talking.+```++### Live (Oct 15, post at 12:00 PM ET)++X:++```text+Live now: the IBM Community user group session inside the three.ws world. Walk in from any browser, no account, and you are in the plaza in under a minute. https://three.ws/event?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-09-ibm-event&utm_content=live+```++LinkedIn:++```text+We are live inside the three.ws world for the Three.ws User Group session. Open the link in a desktop browser and you join the plaza as an avatar, no account needed. The live build starts at 12:06 PM Eastern.++https://three.ws/event?utm_source=linkedin&utm_medium=social&utm_campaign=mkt-2026-09-ibm-event&utm_content=live+```++Telegram:++```text+LIVE now in the $THREE home town. Doors are open, the live build starts in six minutes. Walk in: https://three.ws/event?utm_source=telegram&utm_medium=community&utm_campaign=mkt-2026-09-ibm-event&utm_content=live+```++IBM Community (reply in the T-14 thread):++```text+We are live. Join here: https://three.ws/event?utm_source=ibm-community&utm_medium=partner&utm_campaign=mkt-2026-09-ibm-event&utm_content=live+```++### T+1 (Oct 16): replay, links, next date++Fill the bracketed counts only from the [measurement](#measurement) capture. Never estimate.+If a count was not captured, delete its sentence.++X:++```text+Replay: one sentence became a rigged agent, the audience forged objects into the plaza, and two agents settled a payment on stream. Next: Tue Nov 24. https://three.ws/event?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-09-ibm-event&utm_content=t1-recap+```++LinkedIn:++```text+Yesterday's Three.ws User Group session, recapped in one clip.++What happened in the hour, in order: a single sentence became a rigged, animated agent, and the host walked around the plaza in it. Attendees forged 3D objects from chat and placed them in the shared world. [IBM SEGMENT SUMMARY: one sentence, approved by the IBM speaker]. Two AI agents completed a real pay-per-call transaction on screen, and the receipt is public on Solana: [EXPLORER URL FROM THE LIVE ROUND]. Members showed what they brought.++[ATTENDANCE SENTENCE, only from the captured peak count, for example: "[N] people were in the world at the peak."]++The next session is Tuesday, November 24: an agent buys a tool and comes back with a result you can verify.++https://three.ws/event?utm_source=linkedin&utm_medium=social&utm_campaign=mkt-2026-09-ibm-event&utm_content=t1-recap+```++Telegram:++```text+Thank you to everyone who came into the world yesterday. The replay clip is above. Everything you forged into the plaza is still standing, so go find it. Next session: Tuesday, November 24, 17:00 UTC.++https://three.ws/event?utm_source=telegram&utm_medium=community&utm_campaign=mkt-2026-09-ibm-event&utm_content=t1-recap+```++IBM Community (group blog post, the recap owed within 24 hours; draft it in+`docs/ibm-community-blog-session-2-recap.md` from the capture, then paste):++```text+Title: Session two recap: Give an Agent a Body, Live++Opening paragraph: what the session set out to show and that it ran inside the world.+Section per agenda beat, in order, each with one screenshot from the recording.+The receipt link from the agent payment round.+Only counts from the measurement capture, each with its capture time.+The next session date (Tuesday, November 24) and how to request a showcase slot.+The independence line: three.ws is an IBM Business Partner. IBM does not endorse three.ws, and three.ws is not an IBM product.+```++### T+7 (Oct 22): proof note to IBM, and a short community wrap++Send the [seven-day proof note](../templates.md#seven-day-proof-note) to the same IBM thread as+section 2, with the completed [measurement](#measurement) fields attached. The one next-level+ask it earns, per the [event series](../opportunities.md#the-ibm-event-series): a+partner-authored recap on an IBM surface, and confirmation of the November 24 slot.++X:++```text+The objects the audience forged at our in-world IBM Community session are still standing. Walk in and find them. Next session: Tue Nov 24. https://three.ws/play?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-09-ibm-event&utm_content=t7-proof+```++LinkedIn:++```text+One week on from the Three.ws User Group session inside the 3D world. The replay, the receipt from the live agent payment, and every object the audience forged are still there to inspect. Session three is Tuesday, November 24: an agent buys a tool over HTTP and comes back with a result anyone can verify.++https://three.ws/play?utm_source=linkedin&utm_medium=social&utm_campaign=mkt-2026-09-ibm-event&utm_content=t7-proof+```++Telegram:++```text+Week-after note: the plaza still has everything you built on the 15th. The November 24 session is where an agent pays for its own tool, and we want two community showcases again. Reply here if you want a slot.+```++IBM Community (reply in the recap post's comments):++```text+A week later: the world still holds the objects forged during the session, and the next session is set for Tuesday, November 24, 12:00 PM Eastern (17:00 UTC). Showcase requests are open in this thread.+```++---++## 5. Run of show (minute by minute)++Times are minutes relative to the 16:00 UTC start (12:00 PM EDT for Option A). **Roles:**+Host (on stream, drives the world), Producer (second browser as an attendee, watches chat and the+stream, holds the fallbacks), Moderator (IBM Community thread, Telegram, and in-world chat).++| Time | ET | Segment | Who | Exactly what happens, with the real control | Fallback |+|---|---|---|---|---|---|+| -45 | 11:15 | Tech check | All | Host and Producer open `https://three.ws/event`, enter the world, confirm voice both ways (mic button in the HUD). Producer runs one `/forge a small wooden crate` in chat to warm the free lane | If voice fails, run the whole session on the stream audio and use text chat for the audience |+| -30 | 11:30 | Preshow starts (automatic) | None | The countdown chip turns gold and a toast tells players to stay: this is the `preshow` phase in [play-live-events.md](../../../docs/play-live-events.md), driven by `public/event.json` | None needed |+| -15 | 11:45 | Doors | Host, Moderator | Host stands at spawn and greets arrivals over voice. Teaches four keys aloud: WASD to move, Enter to chat, hold Q for the emote wheel, V to change avatar. First-time visitors also get the onboarding overlay automatically | Moderator pastes the same four keys in chat every five minutes |+| 0 | 12:00 | Go live (automatic) | None | The chip reads LIVE, the go-live banner fires, and an opening fireworks volley goes up for everyone at once (deterministic, no network) | None needed |+| 0 | 12:00 | Welcome | Host | Thirty seconds: who we are, the agenda, and the independence line read once: "three.ws is an IBM Business Partner. IBM does not endorse three.ws, and three.ws is not an IBM product." Producer posts the Live beat on all four channels | None needed |+| 2 | 12:02 | Tour | Host | Walk the plaza: the agenda drawer (tap the chip), the Agent Exchange where NOVA and ORACLE stand, the build area, the Plaza Stage marquee | Skip to the live build if arrivals are still coming in |+| 6 | 12:06 | Live build: prompt to rigged agent | Host | Switch the stream to a tab on `https://three.ws/create`. Type one sentence (rehearsed prompt: "a friendly lighthouse keeper in a yellow raincoat"). Show the generated avatar rig and animate | Producer has the same prompt's avatar pre-made at T-2; show it if generation runs past 12:12 |+| 12 | 12:12 | Wear it | Host | Back in the world, press V, pick the new avatar from saved avatars, and the rig swaps for every peer live. Hold Q and wave | Paste the pre-made avatar's URL into the same panel |+| 15 | 12:15 | Forge into the world | Host, audience | Host presses Enter and types `/forge a glass lighthouse lantern`. Draft generation lands in roughly 30 to 60 seconds (90 on a cold GPU); the toast says it is forged; one click places it for everyone. Invite the audience to forge their own now. Press B to show build mode | If the lane is slow, Producer places the crate forged at -45 from their build palette |+| 22 | 12:22 | IBM guest segment | [IBM SPEAKER] | Host introduces the speaker by the approved name and title only. 12 minutes of talk, 3 minutes of questions the Moderator collects from chat | If the speaker drops, Host moves the community showcase up and the IBM segment becomes a recorded follow-up post only with IBM's approval |+| 37 | 12:37 | An agent pays for a tool | Host | Walk to NOVA and ORACLE, press E, trigger one round. The x402 jumbotron steps through challenge, sign, verify, settle, confirmed, and the receipt shows a Solana explorer link. Read the amount off the panel, never from memory. **Spend:** one real stablecoin micropayment on Solana from the platform's server-side x402 payer; the owner approves the round count before the event | If a round fails, show the jumbotron's platform-wide feed of recent paid calls and open `https://three.ws/agent-exchange` in a tab |+| 42 | 12:42 | Community showcase | Host, up to three members | Members reserved in the T-14 thread walk up and talk over spatial voice: their avatar, their forged object, or their build. Three minutes each. Fireworks density starts ramping at 12:45 for the closing fifteen minutes | Host shows the T-7 challenge photos from Telegram and the IBM thread |+| 50 | 12:50 | Open Q&A | Host, Moderator | Moderator reads questions from chat, the IBM thread, and Telegram in turn | None needed |+| 57 | 12:57 | Group photo and next date | Host | Everyone gathers at the coin totem in the plaza. Host presses Z (zen, hides panels) then P: the photo card is stamped with the event name. Announce Tuesday, November 24 and the showcase sign-up | None needed |+| 60 | 13:00 | End (automatic) | None | Window closes: the souvenir grant (if configured) stops, the chip enters `afterglow` for 20 minutes inviting a photo, then the layer tears itself down | None needed |+| +20 | 13:20 | Capture | Producer | Record the [measurement](#measurement) fields at once; they are the only numbers the recap may use | None needed |++**What not to show on this stream:** the Oracle Ribbon in the plaza (it draws a `$THREE` price+forecast, and price talk does not belong on an IBM Community stage), any wallet UI, and any+`.env`.++---++## 6. Event config (`public/event.json`)++Write this file exactly (it replaces the no-event resting document), then validate it. It is the+single source for the `/event` countdown and calendar file, the lobby banner, the in-world chip,+agenda, banners, fireworks, and the souvenir grant.++```json+{+ "id": "user-group-session-2",+ "name": "Three.ws User Group: Give an Agent a Body, Live",+ "tagline": "The IBM Community user group session, held inside the world.",+ "startsAt": "2026-10-15T16:00:00Z",+ "endsAt": "2026-10-15T17:00:00Z",+ "link": "/play?coin=FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump&name=three.ws&symbol=three",+ "linkLabel": "Join the session",+ "agenda": [+ { "atMin": 0, "title": "Doors open in the plaza", "detail": "Welcome and controls" },+ { "atMin": 6, "title": "Live build: prompt to rigged agent", "detail": "One sentence, then we wear it" },+ { "atMin": 15, "title": "Forge into the world", "detail": "Type /forge in chat" },+ { "atMin": 22, "title": "Guest segment", "detail": "Questions in chat" },+ { "atMin": 37, "title": "An agent pays for a tool", "detail": "At the Agent Exchange" },+ { "atMin": 42, "title": "Community showcase", "detail": "Members show what they brought" },+ { "atMin": 50, "title": "Open Q&A", "detail": "Ask anything" },+ { "atMin": 57, "title": "Group photo", "detail": "Gather at the totem" }+ ]+}+```++```bash+npm run event:schedule # validates with the deploy's own rules and prints the clock lines+git add public/event.json && git commit -m "feat(events): schedule Three.ws User Group session two for 2026-10-15 16:00 UTC"+```++The printed "announcement clock" lines must match the times in the posts above. Add the IBM+speaker's approved name to the `Guest segment` detail only once IBM confirms it.++**Souvenir (optional, agent-executable by T-14).** Do not point `souvenir.cosmeticId` at+`laurel-meetup`: that item is promised as never granted again. To give attendees a keepsake,+author a new `tier: 'event'`, `price: 0` item in `multiplayer/src/cosmetics-catalog.js`, generate+its GLB and poster, and add `"souvenir": { "cosmeticId": "<new id>" }`, following+[Adding a new souvenir](../../../docs/event-souvenirs.md#adding-a-new-souvenir). Then run+`npx vitest run tests/event-souvenir.test.js`.++**After the event, clear it.** `npm run check:event` is part of `npm run gate` and fails once a+window has ended, so the next deploy is blocked until the file returns to rest:++```bash+npm run event:schedule -- --clear --apply+git add public/event.json && git commit -m "chore(events): return the event config to rest after session two"+```++---++## Pre-flight and rehearsal++| When | Step | Command or action |+|---|---|---|+| T-14 | Config committed and deployed | Section 6, then the [deploy runbook](../../../CLAUDE.md#deploy-runbook-apifrontend) (owner-approved) |+| T-7 | Local rehearsal of every phase | `npm run event:schedule -- --rehearse 10 --apply`, then `npm run dev` and `npm run dev:walk-all` in two terminals, walk the whole run of show, take the photo-mode card for the T-1 image, then `git checkout -- public/event.json` |+| T-2 | Speaker rehearsal | 20 minutes in the world with the IBM speaker: voice, screen share, and their segment timing |+| T-2 | Pre-made fallbacks | Generate the live-build avatar and forge the lantern once; keep both URLs in the Producer's notes |+| T-1 | Production audit | `npm run audit:meetup -- --base https://three.ws` (drives the real layer with `?meetup=now`; exit 0 means every check passed) |+| T-1 | Agent Exchange rehearsal | One round in production. If it fails, run the `x402-economy-triage` agent before assuming the payer is empty |+| T-1 | Plaza Stage state | `GET https://three.ws/api/stage?coin=FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump` returns `{ stage: null }` while unclaimed (checked 2026-09-17), so the marquee reads "No host has claimed this stage". It is on the tour, not the agenda. Claiming it with a host agent (`POST /api/stage {action:'plaza'}`) is optional |++## Measurement++Capture at +20 minutes, again at 24 hours, and at 7 days, into the+[required campaign result](../measurement.md#required-campaign-result) fields. Sources that exist+today:++| Field | Where it comes from |+|---|---|+| Registrations | The IBM Community event listing's registrant count |+| Peak in-world population | The live population panel on `/event` during the session (screenshot it with its time) |+| Landing sessions | Web analytics filtered to `utm_campaign=mkt-2026-09-ibm-event`, split by `utm_source` |+| Forged objects placed | The plaza after the session (count what stands in the build area; photograph it) |+| Agent payment | The explorer receipt link from the live round |+| Partner response | IBM speaker, IBM listing, IBM social share: none, acknowledged, reposted, or authored |++No count goes into any post, recap, or proof note unless it is in this capture with its time.++---++## Feature verification++Every product claim in this kit, checked against the code on 2026-09-17:++| Claim | Source |+|---|---|+| `/play` needs no account or wallet | `src/game/play-gate.js` mounts only when a gate mint is pinned; the production service has no `PLAY_GATE*` variable |+| Countdown, agenda drawer, go-live banner, synchronized fireworks, `preshow` and `afterglow` phases | `src/game/meetup-event.js`, `src/game/meetup-schedule.js`, `src/game/fireworks.js`, [play-live-events.md](../../../docs/play-live-events.md) |+| `/event` countdown, add-to-calendar `.ics`, live population | `src/event-page.js` |+| Spatial voice by proximity | `src/game/voice-chat.js` |+| Keys: V avatar, Enter chat, hold Q emotes, E interact, B build, P photo, Z zen | `_bindInput` in `src/game/coincommunities.js`; listed for players in `src/game/play-onboard.js` |+| Swap avatar mid-session, including saved three.ws avatars and pasted URLs | `src/game/avatar-switcher.js` |+| `/forge <prompt>` in chat generates a prop on the free draft lane and places it for everyone | `_forgeProp` in `src/game/coincommunities.js`, `src/game/forge-prop.js` |+| NOVA pays ORACLE in a stablecoin on Solana through `/api/x402-pay`, only on an explicit E press, with an explorer receipt | `src/game/agent-commerce.js` |+| x402 jumbotron stepper and platform-wide paid-call feed | `src/game/x402-jumbotron.js`; `GET /api/x402-pay?feed=1` returned live items on 2026-09-17 |+| Photo mode stamps the event name | `src/game/photo-mode.js` |+| Plaza Stage marquee, unclaimed state | `src/game/plaza-stage.js`, `api/stage/index.js` |+| Souvenir window, world, and tier guards | [event-souvenirs.md](../../../docs/event-souvenirs.md), `multiplayer/src/event-drop.js` |++## Owner steps, in order++1. Pick Option A, B, or C (apply the find-and-replace table if not A).+2. Send the relationship email (section 2) on the June thread.+3. Send the Agent Connect email (section 3) to `[email protected]`.+4. When IBM confirms the speaker and wording, fill the three `[IBM SPEAKER]` fields and create+ the IBM Community event from section 1.+5. Commit section 6's `public/event.json` and deploy (T-14).+6. Approve the number of Agent Exchange rounds for rehearsal and the live session.+7. Post each beat of section 4 on its date.+8. Run the session from section 5; capture measurement at +20 minutes.+9. T+1: clear the event config and deploy; post the recap beats with captured numbers only.+10. T+7: send the proof note; update the `MKT-2026-09-IBM-EVENT` row's status in+ [campaigns.csv](../campaigns.csv).diff --git a/marketing/growth/events/open-source-friday-menu.md b/marketing/growth/events/open-source-friday-menu.mdnew file mode 100644index 000000000..3c588300b--- /dev/null+++ b/marketing/growth/events/open-source-friday-menu.md@@ -0,0 +1,95 @@+# Open Source Friday: the contribution menu++The ready-to-go set of first contributions for the GitHub Open Source Friday stream+(campaign `MKT-2026-09-OSF`), plus the booking reply for+[githubevents/open-source-friday#254](https://github.com/githubevents/open-source-friday/issues/254).+The stream itself, the criteria, and the runsheet are in the+[stream plan](../../../docs/open-source-friday-plan.md); this file supplies what that plan's+"How can people contribute?" segment needs now that its original issues are done.++## Why the menu was rebuilt++Read-only check on 2026-09-17 with+`gh issue list --repo nirholas/three.ws --state open --limit 100`: **the repo has zero open+issues.** All six curated first issues from August (#110 to #115) were closed between+2026-09-14 and 2026-09-15, which is good news and leaves the stream's live-contribution segment+with nothing to point at. Issue #254 is open and carries the `approved` label; the booking bot+asked for a date on 2026-09-01 and no date has been posted.++## The seven issues++Each was verified against `main` on 2026-09-17: the file paths exist, the probe in the body+reproduces the stated output, and every label below already exists on the repo. Bodies are+written for a contributor with no prior context.++| # | Title | Area | Size | Body file |+|---|---|---|---|---|+| 1 | Rig: map HumanIK joint names after three.js strips the namespace colon (`Character1Hips`) | rig | Small: one prefix rule and a test table | [01-rig-humanik-sanitized-names.md](./osf-issues/01-rig-humanik-sanitized-names.md) |+| 2 | Rig: map 3ds Max Biped finger chains (`Bip01 L Finger0`, `Finger01`) | rig | Small: one loop and a test table | [02-rig-biped-finger-chains.md](./osf-issues/02-rig-biped-finger-chains.md) |+| 3 | Rig: map Source engine `ValveBiped.Bip01_*` skeletons and teach Rig Doctor to name them | rig | Medium: prefix, three joints, a fingerprint, a docs row | [03-rig-source-engine-valvebiped.md](./osf-issues/03-rig-source-engine-valvebiped.md) |+| 4 | Upload check: `isValidGlbMagic` skips the declared-length check the server enforces | bug | Small: one check and a new test file | [04-glb-magic-declared-length.md](./osf-issues/04-glb-magic-declared-length.md) |+| 5 | Tests: cover the `safeUrl` and `sanitizeUrl` script-scheme guards | tests | Small: tests only | [05-tests-url-scheme-guards.md](./osf-issues/05-tests-url-scheme-guards.md) |+| 6 | Tests: lock in the anchored host allowlist in `isSafeQueryModelUrl` | tests | Small: tests only | [06-tests-model-url-allowlist.md](./osf-issues/06-tests-model-url-allowlist.md) |+| 7 | Money Pulse: compact numbers roll over into the wrong unit (`$1000`, `1000.0k`) | bug | Small: two functions and a test file | [07-pulse-format-unit-rollover.md](./osf-issues/07-pulse-format-unit-rollover.md) |++**Order of work for the stream.** Issue 1 is the on-air segment: it is the smallest change with+the most visible result (a rig that did not animate, animating), and it follows the worked+example in [docs/first-contribution.md](../../../docs/first-contribution.md) exactly. Issue 2+should land before issue 3, because Source skeletons reuse the Biped finger names. Issues 4 to 7+need no 3D knowledge at all, which is the point: they are the answer to "I am not a graphics+person, can I still help?"++## Create them (owner, one command each)++Run from the repo root. Titles use single quotes because several contain backticks. Create+issues 2 to 7 when the stream date is booked, so the community can claim them before air. Create+issue 1 the Monday before the stream so it is still open for the live segment.++```bash+gh issue create --repo nirholas/three.ws --title 'Rig: map 3ds Max Biped finger chains (`Bip01 L Finger0`, `Finger01`)' --label 'good first issue' --label 'area: rig' --label 'enhancement' --body-file marketing/growth/events/osf-issues/02-rig-biped-finger-chains.md++gh issue create --repo nirholas/three.ws --title 'Rig: map Source engine `ValveBiped.Bip01_*` skeletons and teach Rig Doctor to name them' --label 'good first issue' --label 'area: rig' --label 'enhancement' --body-file marketing/growth/events/osf-issues/03-rig-source-engine-valvebiped.md++gh issue create --repo nirholas/three.ws --title 'Upload check: `isValidGlbMagic` skips the declared-length check the server enforces' --label 'good first issue' --label 'bug' --body-file marketing/growth/events/osf-issues/04-glb-magic-declared-length.md++gh issue create --repo nirholas/three.ws --title 'Tests: cover the `safeUrl` and `sanitizeUrl` script-scheme guards' --label 'good first issue' --label 'area: tests' --body-file marketing/growth/events/osf-issues/05-tests-url-scheme-guards.md++gh issue create --repo nirholas/three.ws --title 'Tests: lock in the anchored host allowlist in `isSafeQueryModelUrl`' --label 'good first issue' --label 'area: tests' --body-file marketing/growth/events/osf-issues/06-tests-model-url-allowlist.md++gh issue create --repo nirholas/three.ws --title 'Money Pulse: compact numbers roll over into the wrong unit (`$1000`, `1000.0k`)' --label 'good first issue' --label 'bug' --body-file marketing/growth/events/osf-issues/07-pulse-format-unit-rollover.md+```++The Monday before the stream:++```bash+gh issue create --repo nirholas/three.ws --title 'Rig: map HumanIK joint names after three.js strips the namespace colon (`Character1Hips`)' --label 'good first issue' --label 'area: rig' --label 'enhancement' --body-file marketing/growth/events/osf-issues/01-rig-humanik-sanitized-names.md+```++Issue 3 says "tracked in the separate Biped finger-chain issue". Once issue 2 has a number, edit+that sentence on GitHub to link it.++## Book the stream++1. Pick a Friday at https://gh.io/osf-booking. The program asks for at least two weeks of lead+ time, so the earliest bookable Friday from 2026-09-17 is **October 2, 2026**. Fridays that+ stay clear of the IBM event two week (October 15) are October 2, October 9, and October 23.+ The stream is 1:00 PM Eastern.+2. Post the reply below on+ [#254](https://github.com/githubevents/open-source-friday/issues/254), replacing only+ `<DATE>` with the booked Friday written like `Friday, October 9, 2026`.+3. Create issues 2 to 7 with the commands above, then run the stream plan's T-7, T-1, T-0,+ and T+1 posts ([stream plan, section 5](../../../docs/open-source-friday-plan.md#5-what-githubs-own-account-tells-us-about-promotion)).++### Booking reply for issue #254++```text+Booked for <DATE> at 1:00 PM ET. Thank you!++Plan for the stream, in your Streaming Guide's order: a live demo that takes a text prompt to a rigged 3D avatar and then to a single embed tag on a blank page, then Rig Doctor showing exactly which joints of an unsupported skeleton will not move. For the contribution segment we will take one open good first issue that teaches the animation retargeter a new skeleton convention, write the mapping and the test, open the PR, and review and merge it on air. The open issues are here: https://github.com/nirholas/three.ws/labels/good%20first%20issue++We will be on wired ethernet at 1920x1080 with a fallback model staged in case a generation worker is slow. Happy to send a 16:9 card and a short demo clip ahead of your announcement; just let us know the format you prefer.+```++This reply replaces the shorter draft in+[templates.md](../templates.md#github-open-source-friday-booking-follow-through), which predates+the approval.diff --git a/marketing/growth/events/osf-issues/01-rig-humanik-sanitized-names.md b/marketing/growth/events/osf-issues/01-rig-humanik-sanitized-names.mdnew file mode 100644index 000000000..676b48020--- /dev/null+++ b/marketing/growth/events/osf-issues/01-rig-humanik-sanitized-names.md@@ -0,0 +1,50 @@+## Context++three.ws plays one shared animation library on any humanoid avatar by first rewriting every bone name to one canonical skeleton. The map lives in [`src/glb-canonicalize.js`](https://github.com/nirholas/three.ws/blob/main/src/glb-canonicalize.js), and the whole approach is explained in [docs/first-contribution.md](https://github.com/nirholas/three.ws/blob/main/docs/first-contribution.md).++Autodesk HumanIK / MotionBuilder rigs put every joint behind a character namespace: `Character1:Hips`, `Character1:LeftArm`. The raw glTF spelling already works, because `_lookupBone` strips a leading `identifier:` namespace, and `tests/glb-canonicalize.test.js` covers it.++The gap is the spelling the **runtime** sees. three.js's `GLTFLoader` passes every node name through `PropertyBinding.sanitizeNodeName`, which deletes `:` (along with `[`, `]`, `.`, `/`). So after loading, the same bone is named `Character1Hips`. The runtime retargeter in [`src/animation-retarget.js`](https://github.com/nirholas/three.ws/blob/main/src/animation-retarget.js) (`canonicalBoneEntries`) calls `canonicalizeBoneName(node.name)` on those loaded bones, and the fused name maps to nothing. Some exporters also write the underscore form `Character1_Hips`, which maps to nothing either.++Verified on `main`:++```bash+node --input-type=module -e "+import { canonicalizeBoneName as c } from './src/glb-canonicalize.js';+for (const n of ['Character1:Hips', 'Character1Hips', 'Character1LeftArm', 'Character1_Hips', 'Character1LeftHandIndex1']) console.log(n, '->', c(n));+"+```++```+Character1:Hips -> Hips+Character1Hips -> null+Character1LeftArm -> null+Character1_Hips -> null+Character1LeftHandIndex1 -> null+```++## What to change++In `_lookupBone` in `src/glb-canonicalize.js`, strip a leading HumanIK character prefix in its fused (`Character1Hips`) and underscore (`Character1_Hips`) forms, next to the existing vendor-prefix strips (`mixamorig`, `CH_`, `CC_Base_`, `Bip01`). Add a comment that says why the fused form exists (the three.js sanitizer), the same way the neighbouring strips explain themselves.++Require the digits (`Character` followed by one or more digits). A bare word like `CharacterMesh` must not be stripped.++## Acceptance criteria++- [ ] `Character1Hips`, `Character1Spine`, `Character1Neck`, `Character1Head`, and the left and right arm, forearm, hand, up-leg, leg, foot, and toe joints resolve to the same canonical names as their `Character1:` forms.+- [ ] The same holds for the underscore form (`Character1_LeftArm`) and for other character numbers (`Character2Hips`).+- [ ] Finger joints resolve too (`Character1LeftHandIndex1` to `LeftHandIndex1`, thumbs included), because fingers are most of every clip's tracks.+- [ ] Every existing `Character1:` case still passes, and no mapping crosses sides (test both sides).+- [ ] A name that only starts with `Character` without digits (`CharacterMesh`) still returns `null`.+- [ ] New cases live in `tests/glb-canonicalize.test.js`, in the file's `describe` + `it.each` table style, next to the existing HumanIK block.++## How to test++```bash+npx vitest run tests/glb-canonicalize.test.js+npm test+```++Re-run the probe above; every line should now print a canonical name.++Good first issue: one prefix rule, one comment, one test table. Comment "taking this" before you start.diff --git a/marketing/growth/events/osf-issues/02-rig-biped-finger-chains.md b/marketing/growth/events/osf-issues/02-rig-biped-finger-chains.mdnew file mode 100644index 000000000..6d7d08561--- /dev/null+++ b/marketing/growth/events/osf-issues/02-rig-biped-finger-chains.md@@ -0,0 +1,59 @@+## Context++three.ws plays one shared animation library on any humanoid avatar by rewriting every bone name to one canonical skeleton first. The map is [`src/glb-canonicalize.js`](https://github.com/nirholas/three.ws/blob/main/src/glb-canonicalize.js); [docs/first-contribution.md](https://github.com/nirholas/three.ws/blob/main/docs/first-contribution.md) walks through how a convention is added.++3ds Max Biped rigs already map for the body: `_lookupBone` strips the `Bip01` / `Bip001` prefix, so `Bip01 L UpperArm` becomes `LeftArm`. **The fingers do not map.** Biped numbers its fingers instead of naming them:++| Biped name | Finger | Segment | Canonical |+|---|---|---|---|+| `Bip01 L Finger0` | thumb | 1 | `LeftHandThumb1` |+| `Bip01 L Finger01` | thumb | 2 | `LeftHandThumb2` |+| `Bip01 L Finger02` | thumb | 3 | `LeftHandThumb3` |+| `Bip01 L Finger1` | index | 1 | `LeftHandIndex1` |+| `Bip01 L Finger11` | index | 2 | `LeftHandIndex2` |+| `Bip01 L Finger2` / `21` / `22` | middle | 1 / 2 / 3 | `LeftHandMiddle1` / `2` / `3` |+| `Bip01 L Finger3` / `31` / `32` | ring | 1 / 2 / 3 | `LeftHandRing1` / `2` / `3` |+| `Bip01 L Finger4` / `41` / `42` | pinky | 1 / 2 / 3 | `LeftHandPinky1` / `2` / `3` |++The rule is unambiguous: one digit is the finger at segment 1; two digits are the finger and then the segment minus one.++This matters more than it looks. Most of the tracks in every clip address a finger joint, so a rig whose hands do not map scores low on retarget coverage (the MMD section of the onboarding doc explains the number).++Verified on `main`:++```bash+node --input-type=module -e "+import { canonicalizeBoneName as c } from './src/glb-canonicalize.js';+for (const n of ['Bip01 L UpperArm', 'Bip01 L Finger0', 'Bip01 L Finger01', 'Bip01_L_Finger1', 'Bip001 R Finger42', 'Bip01_L_Toe0']) console.log(n, '->', c(n));+"+```++```+Bip01 L UpperArm -> LeftArm+Bip01 L Finger0 -> null+Bip01 L Finger01 -> null+Bip01_L_Finger1 -> null+Bip001 R Finger42 -> null+Bip01_L_Toe0 -> null+```++## What to change++Add the Biped finger chain (and `Toe0` to `LeftToeBase` / `RightToeBase`) to `src/glb-canonicalize.js`. After the `Bip` prefix strip, a Biped finger reaches the lookup as a key like `lfinger01`; the `EXTRA_ALIASES` block and its `put()` helper are the natural home, generated in a loop the way the MikuMikuDance finger chains are. Say in a comment how the numbering works.++## Acceptance criteria++- [ ] All 15 finger joints per hand map as in the table, for both `Bip01` and `Bip001`, and for the space (`Bip01 L Finger0`) and underscore (`Bip01_L_Finger0`) spellings. The underscore spelling is what three.js hands the runtime after sanitizing names.+- [ ] `Bip01 L Toe0` and `Bip01 R Toe0` map to `LeftToeBase` and `RightToeBase`.+- [ ] No mapping crosses sides: every `L` name maps to a `Left*` bone and every `R` name to a `Right*` bone.+- [ ] Existing Biped body cases still pass.+- [ ] Tests in `tests/glb-canonicalize.test.js`, in the file's `describe` + `it.each` style.++## How to test++```bash+npx vitest run tests/glb-canonicalize.test.js+npm test+```++Good first issue: the whole change is a loop and a test table. Comment "taking this" before you start.diff --git a/marketing/growth/events/osf-issues/03-rig-source-engine-valvebiped.md b/marketing/growth/events/osf-issues/03-rig-source-engine-valvebiped.mdnew file mode 100644index 000000000..ca0b027bd--- /dev/null+++ b/marketing/growth/events/osf-issues/03-rig-source-engine-valvebiped.md@@ -0,0 +1,51 @@+## Context++three.ws plays one shared animation library on any humanoid avatar by rewriting every bone name to one canonical skeleton. The map is [`src/glb-canonicalize.js`](https://github.com/nirholas/three.ws/blob/main/src/glb-canonicalize.js), and [Rig Doctor](https://three.ws/rig-doctor) ([`src/rig-report.js`](https://github.com/nirholas/three.ws/blob/main/src/rig-report.js)) names which convention an uploaded skeleton follows.++Characters from Valve's Source engine (and models exported from its tools) use a Biped-derived skeleton behind a `ValveBiped.` prefix: `ValveBiped.Bip01_Pelvis`, `ValveBiped.Bip01_L_UpperArm`, `ValveBiped.Bip01_Spine4`, `ValveBiped.Bip01_Neck1`, `ValveBiped.Bip01_Head1`. None of them map today, in either the raw glTF spelling or the spelling three.js produces at runtime (its `PropertyBinding.sanitizeNodeName` deletes the `.`, giving `ValveBipedBip01_Pelvis`). Rig Doctor also reports these rigs as unrecognised, because its `biped` fingerprint only matches names that start with `Bip`.++Verified on `main`:++```bash+node --input-type=module -e "+import { canonicalizeBoneName as c } from './src/glb-canonicalize.js';+for (const n of ['ValveBiped.Bip01_Pelvis', 'ValveBipedBip01_Pelvis', 'ValveBiped.Bip01_L_UpperArm', 'Bip01_L_UpperArm', 'Bip01_Spine4', 'Bip01_Neck1', 'Bip01_Head1']) console.log(n, '->', c(n));+"+```++```+ValveBiped.Bip01_Pelvis -> null+ValveBipedBip01_Pelvis -> null+ValveBiped.Bip01_L_UpperArm -> null+Bip01_L_UpperArm -> LeftArm+Bip01_Spine4 -> null+Bip01_Neck1 -> null+Bip01_Head1 -> null+```++The fourth line is the good news: once the `ValveBiped` prefix is gone, the existing 3ds Max Biped handling already maps the limbs. What is left is the prefix and the few joints Source numbers differently.++## What to change++1. In `_lookupBone` in `src/glb-canonicalize.js`, strip a leading `ValveBiped` prefix (with or without the `.`) before the existing `Bip<NN>` strip, with a comment naming the sanitizer case.+2. Map the Source-specific spellings: `Spine4` (the top of Source's four-joint spine; choose the canonical target and say why in the comment), `Neck1` to `Neck`, `Head1` to `Head`.+3. Add a `source` entry to `CONVENTIONS` in `src/rig-report.js` that matches joints starting with `ValveBiped.`, placed before the `biped` entry so it wins. Add its row to the conventions table in [`docs/rig-doctor.md`](https://github.com/nirholas/three.ws/blob/main/docs/rig-doctor.md).++Fingers are tracked in the separate Biped finger-chain issue; once that lands, Source fingers map through the same path with no extra work here.++## Acceptance criteria++- [ ] Pelvis, the spine chain, neck, head, clavicles, upper arms, forearms, hands, thighs, calves, and feet resolve for both `ValveBiped.Bip01_*` and `ValveBipedBip01_*`.+- [ ] No mapping crosses sides (test both `L` and `R`).+- [ ] Every existing Biped case still passes.+- [ ] `detectConvention` reports the new convention for a skeleton of `ValveBiped.` joints; a test in `tests/rig-report.test.js` proves it.+- [ ] The Rig Doctor doc table has the new row, and the drift test that compares supported conventions with documented ones passes.++## How to test++```bash+npx vitest run tests/glb-canonicalize.test.js tests/rig-report.test.js+npm test+```++Comment "taking this" before you start.diff --git a/marketing/growth/events/osf-issues/04-glb-magic-declared-length.md b/marketing/growth/events/osf-issues/04-glb-magic-declared-length.mdnew file mode 100644index 000000000..cfc935ad2--- /dev/null+++ b/marketing/growth/events/osf-issues/04-glb-magic-declared-length.md@@ -0,0 +1,56 @@+## Context++Before a user's 3D model is uploaded, the browser checks its 12-byte GLB header so a misnamed JPEG is rejected instantly instead of after a full upload. That check is `isValidGlbMagic` in [`src/shared/glb-magic.js`](https://github.com/nirholas/three.ws/blob/main/src/shared/glb-magic.js), used by [`src/create-agent.js`](https://github.com/nirholas/three.ws/blob/main/src/create-agent.js) and [`src/agent-edit.js`](https://github.com/nirholas/three.ws/blob/main/src/agent-edit.js).++Its header comment says it "mirrors the server-side `isValidGlbHeader()` in `api/_lib/glb-inspect.js`" and that it checks "that the declared file length field is at least the minimum GLB size". **It does not check the length field at all.** It checks the magic bytes and the version, then returns `true`.++The server version in [`api/_lib/glb-inspect.js`](https://github.com/nirholas/three.ws/blob/main/api/_lib/glb-inspect.js) does more:++```js+const declaredLen = view.getUint32(8, true);+if (declaredLen > buf.length || declaredLen < 20) return false;+```++So a truncated or corrupted GLB (a valid 12-byte header whose declared length is larger than the file, or smaller than 20) passes the browser check and is only rejected after it has been uploaded. The two checks are supposed to agree, and today they do not. There is also no test for `glb-magic.js`.++Verified on `main`:++```bash+node --input-type=module -e "+import { isValidGlbMagic } from './src/shared/glb-magic.js';+const header = (declared) => { const b = new ArrayBuffer(12); const v = new DataView(b); v.setUint32(0, 0x46546c67, true); v.setUint32(4, 2, true); v.setUint32(8, declared, true); return b; };+console.log('declares 5000 bytes, file is 12:', await isValidGlbMagic(new File([header(5000)], 'a.glb')));+console.log('declares 8 bytes:', await isValidGlbMagic(new File([header(8)], 'a.glb')));+"+```++```+declares 5000 bytes, file is 12: true+declares 8 bytes: true+```++Both should be `false`, because the server rejects both.++## What to change++In `isValidGlbMagic`, read the declared length (little-endian `uint32` at byte offset 8) and return `false` when it is below 20 or larger than `file.size`, matching the server. Keep reading only the first 12 bytes; the point of the function is that it never buffers the whole file. Make the header comment match what the code does.++Add `tests/glb-magic.test.js`. Node 20 and later have a global `File`, so tests can build headers the way the probe above does.++## Acceptance criteria++- [ ] A valid header whose declared length equals the file size returns `true`.+- [ ] Declared length larger than `file.size` returns `false`.+- [ ] Declared length below 20 returns `false`.+- [ ] Wrong magic, version 1, a file under 12 bytes, and a missing file all return `false` (these already do; lock them in).+- [ ] The function still reads only `file.slice(0, 12)`.+- [ ] The header comment describes exactly the checks the code performs.++## How to test++```bash+npx vitest run tests/glb-magic.test.js+npm test+```++Good first issue: a small, well-bounded correctness fix with a clear reference implementation next door. Comment "taking this" before you start.diff --git a/marketing/growth/events/osf-issues/05-tests-url-scheme-guards.md b/marketing/growth/events/osf-issues/05-tests-url-scheme-guards.mdnew file mode 100644index 000000000..6115f5df7--- /dev/null+++ b/marketing/growth/events/osf-issues/05-tests-url-scheme-guards.md@@ -0,0 +1,52 @@+## Context++Two small functions stand between user- or model-controlled URLs and the page:++- `safeUrl(url, fallback)` in [`src/safe-url.js`](https://github.com/nirholas/three.ws/blob/main/src/safe-url.js) guards `href`, `src`, and CSS `url(...)` sinks. It is imported across the app, for example by `src/communities.js`, `src/marketplace.js`, and `src/app.js`.+- `sanitizeUrl(url)` in [`src/shared/sanitize-url.js`](https://github.com/nirholas/three.ws/blob/main/src/shared/sanitize-url.js) guards links in rendered markdown from LLM, persona, or model output. It is imported by `src/fact-checker-app.js`, `src/economy-live.js`, `src/bounties.js`, and others.++Both exist to stop `javascript:`, `data:`, and `vbscript:` URLs from becoming clickable. **Neither has a single test.** A refactor that loosened either regex would ship green.++They also intentionally differ in a few ways, and those differences are currently documented nowhere but the regexes. Observed on `main`:++| Input | `safeUrl` | `sanitizeUrl` |+|---|---|---|+| `" javascript:alert(1)"` | `"#"` | `"#"` |+| `"JaVaScRiPt:x"` | `"#"` | `"#"` |+| `"data:text/html,x"` | `"#"` | `"#"` |+| `"//evil.com"` | `"#"` | `"#"` |+| `"#top"` | `"#top"` | `"#top"` |+| `"mailto:[email protected]"` | `"#"` | `"mailto:[email protected]"` |+| `"./a"` | `"./a"` | `"#"` |+| `" https://x.y "` | `" https://x.y "` (returned untrimmed) | `"https://x.y"` (trimmed) |++Reproduce:++```bash+node --input-type=module -e "+import { safeUrl } from './src/safe-url.js';+import { sanitizeUrl } from './src/shared/sanitize-url.js';+for (const u of [' javascript:alert(1)', 'JaVaScRiPt:x', 'data:text/html,x', '//evil.com', '#top', 'mailto:[email protected]', './a', ' https://x.y ']) console.log(JSON.stringify(u), JSON.stringify(safeUrl(u)), JSON.stringify(sanitizeUrl(u)));+"+```++## What to change++Add one test file, `tests/url-scheme-guards.test.js`, with a `describe` block per function and `it.each` tables. This issue is tests only: do not change either function. If a case surprises you, say so in the PR description and a maintainer will decide whether it is a bug.++## Acceptance criteria++- [ ] Script schemes are rejected in every casing and with leading whitespace: `javascript:`, `data:`, `vbscript:`.+- [ ] Protocol-relative `//host` is rejected by both.+- [ ] Allowed shapes are covered for each function: `https://`, `http://`, `/path`, `#anchor`; plus `./` and `../` for `safeUrl`, and `mailto:` for `sanitizeUrl`.+- [ ] Non-strings (`null`, `undefined`, a number, an object) and empty or blank strings return the fallback (`"#"` by default; a custom `fallback` argument for `safeUrl`).+- [ ] The differences in the table above each have a named test, so a future change to them is a deliberate, visible decision.++## How to test++```bash+npx vitest run tests/url-scheme-guards.test.js+npm test+```++Good first issue: no app knowledge needed, and every case is a one-line table row. Comment "taking this" before you start.diff --git a/marketing/growth/events/osf-issues/06-tests-model-url-allowlist.md b/marketing/growth/events/osf-issues/06-tests-model-url-allowlist.mdnew file mode 100644index 000000000..8734ef7cc--- /dev/null+++ b/marketing/growth/events/osf-issues/06-tests-model-url-allowlist.md@@ -0,0 +1,49 @@+## Context++Pages that accept a `?model=` URL render whatever 3D file that URL points at, under the three.ws origin. [`src/shared/safe-model-url.js`](https://github.com/nirholas/three.ws/blob/main/src/shared/safe-model-url.js) decides which URLs are allowed, so a three.ws page cannot be turned into an open relay that renders an attacker's GLB. It exports `isSafeQueryModelUrl(raw)` and the host allowlist `TRUSTED_ASSET_HOST_RE`, and it is imported by `src/pose-studio.js`, `src/agent-accessories.js`, and `src/avatar-embed.js`.++The allowlist regex is anchored on purpose (its comment says so: "never a substring like `three.ws.evil.com`"). **Nothing tests that.** Remove the `(^|\.)` anchor in a refactor and every test in the repo still passes.++Observed on `main`, with `location.origin` set to `https://three.ws`:++| URL | Result | Why |+|---|---|---|+| `/avatars/a.glb` | `true` | same-origin relative path |+| `//evil.com/a.glb` | `false` | protocol-relative, not same-origin |+| `ipfs://bafy...` | `true` | decentralized URI |+| `https://pub-x.r2.dev/a.glb` | `true` | subdomain of an allowlisted host |+| `https://three.ws.evil.com/a.glb` | `false` | allowlisted name as a prefix of another domain |+| `https://evilr2.dev/a.glb` | `false` | allowlisted name as a suffix without a dot boundary |+| `http://three.ws/a.glb` | `false` | not https and not same-origin |++Reproduce:++```bash+node --input-type=module -e "+globalThis.location = { origin: 'https://three.ws' };+const { isSafeQueryModelUrl: s } = await import('./src/shared/safe-model-url.js');+for (const u of ['/avatars/a.glb', '//evil.com/a.glb', 'ipfs://bafy', 'https://pub-x.r2.dev/a.glb', 'https://three.ws.evil.com/a.glb', 'https://evilr2.dev/a.glb', 'http://three.ws/a.glb']) console.log(u, s(u));+"+```++## What to change++Add `tests/safe-model-url.test.js`. The function reads `location.origin`, and the test suite runs in a Node environment, so stub it with `vi.stubGlobal('location', { origin: 'https://three.ws' })` in a `beforeEach` and restore with `vi.unstubAllGlobals()` afterwards. This issue is tests only: do not change the function or the allowlist.++## Acceptance criteria++- [ ] Every row in the table above is a test case.+- [ ] Look-alike hosts are rejected for at least three allowlisted names (a prefix form like `three.ws.evil.com` and a no-dot suffix form like `evilthree.ws`).+- [ ] Same-origin absolute URLs (`https://three.ws/x.glb`) are accepted.+- [ ] Non-strings, empty strings, and unparseable input (`https://`) return `false`.+- [ ] `ar://` URIs are accepted alongside `ipfs://`.+- [ ] The `location` stub is removed after the tests, so no other test file sees it.++## How to test++```bash+npx vitest run tests/safe-model-url.test.js+npm test+```++Good first issue: a security boundary that deserves a test, and no app knowledge needed. Comment "taking this" before you start.diff --git a/marketing/growth/events/osf-issues/07-pulse-format-unit-rollover.md b/marketing/growth/events/osf-issues/07-pulse-format-unit-rollover.mdnew file mode 100644index 000000000..02ee7a407--- /dev/null+++ b/marketing/growth/events/osf-issues/07-pulse-format-unit-rollover.md@@ -0,0 +1,53 @@+## Context++[`src/shared/pulse-format.js`](https://github.com/nirholas/three.ws/blob/main/src/shared/pulse-format.js) is the single source of truth for how numbers render on the [Money Pulse](https://three.ws/pulse) page (`src/pulse.js`) and the viability panels (`src/shared/viability-panels.js`). Its compact formatters pick a unit by comparing the raw value to a threshold, then round. When rounding pushes a value up past the threshold, the label comes out in the wrong unit:++Verified on `main`:++```bash+node --input-type=module -e "+import { fmtUsd, fmtThree } from './src/shared/pulse-format.js';+console.log(fmtUsd(9.999), fmtUsd(999.6), fmtUsd(999999), fmtThree(999.6), fmtThree(999950));+"+```++```+$10.00 $1000 $1000.0k 1000 1000.0k+```++| Call | Today | Expected |+|---|---|---|+| `fmtUsd(9.999)` | `$10.00` | `$10` (the format every other value from 10 to 999 uses) |+| `fmtUsd(999.6)` | `$1000` | `$1.0k` |+| `fmtUsd(999999)` | `$1000.0k` | a millions label, for example `$1.0M` (there is no millions branch today) |+| `fmtThree(999.6)` | `1000` | `1.0k` |+| `fmtThree(999950)` | `1000.0k` | `1.00M` |++On a live counter these are exactly the numbers that appear right before a milestone, which is when people screenshot the page.++There are no tests for this file today.++## What to change++Fix `fmtUsd` and `fmtThree` so the unit is chosen after rounding (or so the thresholds account for it), and give `fmtUsd` a millions branch. Keep every other output unchanged. Add `tests/pulse-format.test.js` covering the boundaries.++`fmtSol`, `fmtNum`, `fmtPct`, and the HTML helpers are out of scope for this issue.++## Acceptance criteria++- [ ] Every "Expected" value in the table holds.+- [ ] Values well inside each band are unchanged (for example `fmtUsd(0)`, `fmtUsd(5)`, `fmtUsd(42)`, `fmtUsd(12345)`, `fmtThree(0.5)`, `fmtThree(42)`, `fmtThree(340)`, `fmtThree(12400)`, `fmtThree(1200000)`), locked in by tests.+- [ ] Each boundary (10, 1,000, 1,000,000) is tested just below, at, and just above.+- [ ] Non-numbers and negatives render the same as today.++## How to test++```bash+npx vitest run tests/pulse-format.test.js+npm test+npm run dev+```++With the dev server running, open http://localhost:3000/pulse and confirm the counters still render.++Good first issue: pure functions, a visible result, and a clear table of right answers. Comment "taking this" before you start.diff --git a/marketing/growth/events/three-world-session.md b/marketing/growth/events/three-world-session.mdnew file mode 100644index 000000000..818fadb67--- /dev/null+++ b/marketing/growth/events/three-world-session.md@@ -0,0 +1,482 @@+# Three World Session: the monthly template++The **Three World Session** is the monthly community event in the+[command center](../README.md#3-the-community-becomes-the-stage): one hour inside+`three.ws/play`, where the venue is the demo. This file is the reusable kit. Part 1 is the+template any month fills in; Part 2 is the filled-in November 2026 session+(`MKT-2026-11-IBM-WORLD-2`), which follows October's+[IBM Community event two](./ibm-event-two.md) and uses the same structure, rules, and tooling.++---++# Part 1: the template++## The slots a month fills++Everything else in a session kit is fixed. Decide these nine values, and the rest of the kit is+mechanical.++| Slot | Rule | Where it is used |+|---|---|---|+| Campaign ID | The existing row in [campaigns.csv](../campaigns.csv); never renamed | Every UTM `utm_campaign`, the measurement row |+| Date | A Tuesday or Thursday. Prefer Thursday (the live-demo day in the [weekly rhythm](../README.md#weekly-operating-rhythm)) unless the campaign row already fixes a Tuesday | Posts, event page, `public/event.json` |+| Start (UTC) | 16:00 UTC while US Eastern is on daylight time (12:00 PM EDT); 17:00 UTC once it is on standard time (12:00 PM EST). In 2026 US daylight time ends November 1 | Everything with a time |+| Theme | One claim a viewer can verify during the hour | Title, abstract, X anchor |+| Proof surface | A shipped route, verified in code before the kit is written (see [feature verification](./ibm-event-two.md#feature-verification) for the method) | Run of show, links |+| Guest | Named only after the guest approves the wording; partners are speakers, not co-hosts, until they approve co-host wording | Speaker slot |+| Partner ask | Exactly one, from the campaign row | Relationship note, T+7 proof note |+| Community challenge | A one-week task that produces something to show on stream | T-7 posts, showcase segment |+| Souvenir | Optional. A new `tier: 'event'` item per [event-souvenirs.md](../../../docs/event-souvenirs.md); never re-grant a past one | `public/event.json` |++## The fixed timeline++| Beat | What ships | Channels |+|---|---|---|+| T-21 | Slots decided; relationship note to the venue partner; guest invited with the [speaker invitation](../templates.md#event-speaker-invitation) | Email |+| T-14 | Event page created; `public/event.json` committed and deployed; announcement posts | IBM Community (new thread), X, LinkedIn, Telegram |+| T-7 | Demo image or clip; community challenge opens; local rehearsal | X, LinkedIn, Telegram, IBM Community (reply in thread) |+| T-2 | Guest rehearsal; fallback assets generated | Internal |+| T-1 | Reminder with exact UTC and Eastern times; `npm run audit:meetup -- --base https://three.ws` | X, LinkedIn, Telegram, IBM Community (reply in thread) |+| Live | Live post at the start minute | All four |+| T+1 | Event config cleared and deployed; replay clip; recap blog with captured numbers only | All four; IBM Community gets a blog post |+| T+7 | [Seven-day proof note](../templates.md#seven-day-proof-note) to the partner; week-after posts | Email, all four |++## The fixed run-of-show frame++Sixty minutes, with doors fifteen minutes early. The segment contents change monthly; the frame+does not, because `public/event.json` agenda beats, the preshow chip, and the fireworks ramp all+assume it.++| Minute | Segment | Fixed element |+|---|---|---|+| -45 | Tech check | Host and Producer in the world; warm the lanes the session uses |+| -30 | Preshow (automatic) | Gold countdown chip |+| -15 | Doors | Host at spawn teaching WASD, Enter, hold Q, V |+| 0 | Welcome | Go-live banner and volley (automatic); independence line read once when a partner venue is involved |+| 2 to 22 | Theme segments | Two demos on the proof surface, each with a pre-made fallback |+| 22 to 37 | Guest segment | Fifteen minutes including three of questions |+| 37 to 50 | Proof and showcase | The verifiable moment, then up to three community showcases |+| 50 to 57 | Open Q&A | Moderator reads chat, the IBM thread, and Telegram in turn |+| 57 to 60 | Group photo and next date | Z then P at the coin totem; the photo card carries the event name |+| 60 | End (automatic) | Afterglow for 20 minutes, then the layer tears down |++## The fixed rules++- No hashtags, no emoji, no em or en dashes. Every X post carries an image and is checked with+ `node scripts/post-tweet.mjs --text "<post>" --dry-run`; target 100 to 179 weighted characters+ ([announce-voice.md](../../../docs/announce-voice.md)).+- IBM-facing copy follows [badge-usage.md](../../ibm-partner-plus/badge-usage.md). No `@IBM`+ tag while Granite is not serving in production.+- UTM format from [measurement.md](../measurement.md); `utm_content` is `t14`, `t7`, `t1`, `live`,+ `t1-recap`, or `t7-proof`.+- No count appears in any post, recap, or proof note unless it was captured with its time.+- Any real spend shown on stream (an x402 round, a payment from a wallet) is approved by the+ owner beforehand, with recipient, amount, and chain.+- After the window ends, `npm run event:schedule -- --clear --apply`, commit, deploy:+ `npm run check:event` (inside `npm run gate`) fails on an expired window.++## To make next month's kit++1. Copy Part 2 of this file into a new section below it, titled with the month and campaign ID.+2. Replace the nine slots, then recompute the T-dates and the UTC/Eastern line from the date.+3. Re-verify every route in the run of show against the code and a live `curl`, and record the+ check date in the verification table.+4. Link the new section from [events/README.md](./README.md).++---++# Part 2: November 2026, `MKT-2026-11-IBM-WORLD-2`++## Slots++| Slot | Value |+|---|---|+| Campaign ID | `MKT-2026-11-IBM-WORLD-2` |+| Date | **Tuesday, November 24, 2026** (the campaign row's date) |+| Start | **17:00 to 18:00 UTC**: 12:00 to 1:00 PM EST, 9:00 AM PST, 5:00 PM London, 6:00 PM Berlin |+| Theme | An agent buys a tool and returns with a result you can verify |+| Proof surface | The Agent Exchange in `/play` and its x402 jumbotron; `/x402`; `/ibm/x402-demo`; `/receipts` |+| Guest | [IBM SPEAKER: name, title, and topic, supplied and approved by IBM] |+| Partner ask | IBM event amplification and a partner-authored recap (from the campaign row) |+| Community challenge | Make one paid x402 call from your own wallet on `/ibm/x402-demo` and bring the receipt |+| Souvenir | Optional; a new item, never `laurel-meetup` |++**Calendar risk:** November 24 is the Tuesday of US Thanksgiving week (Thanksgiving is November+26), which can thin a US enterprise audience. If IBM prefers, move to **Tuesday, November 17,+2026, 17:00 UTC (12:00 PM EST)**: shift every T-date below one week earlier, then replace+`November 24` with `November 17`, `Nov 24` with `Nov 17`, and `2026-11-24` with `2026-11-17`+across Part 2 (the relationship note already offers both dates, so leave it as written).++| Beat | Date |+|---|---|+| T-21 | Tuesday, November 3 |+| T-14 | Tuesday, November 10 |+| T-7 | Tuesday, November 17 |+| T-1 | Monday, November 23 |+| Live | Tuesday, November 24, 17:00 UTC |+| T+1 | Wednesday, November 25 |+| T+7 | Tuesday, December 1 |++## Event page (IBM Community)++Title:++```text+An Agent Pays for Its Own Tool: Three.ws User Group Session Inside the 3D World+```++Abstract:++```text+An AI agent that can use a paid tool needs a way to pay for it without a person typing in a+card. In this session the Three.ws User Group meets inside the three.ws 3D world and watches+that happen end to end: an agent asks a service for a tool, receives an HTTP 402 payment+challenge, signs and settles a micropayment, gets the result, and leaves a public on-chain+receipt that anyone in the audience can open.++You join from your browser as an avatar. No download, no install, no account. Trying the+payment yourself is optional and uses your own wallet.++Hosted by three.ws in the Three.ws User Group on IBM Community. three.ws is an IBM Business+Partner. IBM does not endorse three.ws, and three.ws is not an IBM product.+```++Agenda:++```text+12:00 PM ET Doors open in the plaza. Welcome, and how to move, talk, and emote.+12:03 PM ET How an agent pays: the HTTP 402 challenge in one minute, on a real catalog.+12:08 PM ET Round one in the world: two agents settle a payment at the Agent Exchange.+12:16 PM ET Your turn, optional: one paid call from your own wallet, receipt included.+12:22 PM ET Guest segment: [IBM SPEAKER: name, title, and topic, supplied and approved by IBM]+12:37 PM ET Verify it yourself: signed receipts and the live payment feed.+12:44 PM ET Community showcase: members show what they built or paid for.+12:50 PM ET Open Q&A.+12:57 PM ET Group photo, and the date of the next session.+```++Details and login instructions: reuse the two blocks from+[event two, section 1](./ibm-event-two.md#event-details-table) with this line swapped in:++```text+When: Tuesday, November 24, 2026, 12:00 to 1:00 PM Eastern (17:00 to 18:00 UTC)+Your time: 9:00 AM San Francisco, 12:00 PM New York, 5:00 PM London, 6:00 PM Berlin+```++Registration CTA:++```text+Register on IBM Community to get the reminder, then add it to your calendar at three.ws/event.+```++## Relationship note (T-21, November 3)++Reply on the same IBM thread as event two's note:++```text+Subject: Three.ws User Group session three on November 24, and a recap ask++Hi [IBM CONTACT FIRST NAME],++Thank you again for [ONE SENTENCE ON IBM'S ACTUAL CONTRIBUTION TO EVENT TWO, from the T+7+measurement]. Session three is set for Tuesday, November 24, 12:00 PM Eastern (17:00 UTC), inside+the three.ws world again: an AI agent requests a paid tool, receives an HTTP 402 challenge,+settles a micropayment, and returns a result with a public receipt the audience can open.++Two asks. First, a 15-minute IBM speaker segment and a listing on the IBM Community events+calendar, as last time; the event page copy is ready. Second, would an IBM author be willing to+write the recap on an IBM surface afterwards? We will supply the recording, screenshots, receipt+links, and captured numbers within 24 hours.++If Thanksgiving week is a problem for your audience, we can hold Tuesday, November 17 instead.++Thank you,+Nich+three.ws+```++## Posts++Links follow the table in [event two, section 4](./ibm-event-two.md#4-posts) with+`utm_campaign=mkt-2026-11-ibm-world-2`. X posts are shown fully resolved.++### T-14 (November 10)++X:++```text+How does an AI agent pay for a tool with no card? Live inside the three.ws world: HTTP 402, a signed micropayment, a public receipt. Tue Nov 24, 17:00 UTC. https://three.ws/event?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-11-ibm-world-2&utm_content=t14+```++LinkedIn:++```text+An AI agent that uses paid tools needs a way to pay for them without a person typing in a card number.++On Tuesday, November 24, the Three.ws User Group on IBM Community shows the whole loop, live, inside the three.ws 3D world: an agent requests a tool, receives an HTTP 402 payment challenge, signs and settles a micropayment on Solana, gets its result, and leaves a receipt anyone in the audience can open and check.++12:00 PM Eastern / 17:00 UTC. Free, in the browser, no account. Trying a paid call yourself is optional and uses your own wallet.++https://three.ws/event?utm_source=linkedin&utm_medium=social&utm_campaign=mkt-2026-11-ibm-world-2&utm_content=t14++three.ws is an IBM Business Partner. IBM does not endorse three.ws, and three.ws is not an IBM product.+```++Telegram:++```text+Next community session: Tuesday, November 24, 17:00 UTC (12:00 PM Eastern), in the $THREE home town on three.ws/play.++Theme: an agent pays for its own tool. We run the Agent Exchange on stream, walk through the x402 challenge step by step, and open the Solana receipts together. Then your showcase.++https://three.ws/event?utm_source=telegram&utm_medium=community&utm_campaign=mkt-2026-11-ibm-world-2&utm_content=t14+```++IBM Community (new thread):++```text+Title: November 24: An Agent Pays for Its Own Tool (Three.ws User Group session three)++Session three is Tuesday, November 24, 12:00 to 1:00 PM Eastern (17:00 UTC), inside the three.ws world again.++The question for the hour: how does an AI agent pay for a tool it needs without a person in the loop, and how does anyone check that it happened? We will show an agent request a paid tool, receive an HTTP 402 payment challenge, sign and settle a micropayment, and return with the result, then open the public receipt together. A guest segment and a member showcase follow.++Join at https://three.ws/event?utm_source=ibm-community&utm_medium=partner&utm_campaign=mkt-2026-11-ibm-world-2&utm_content=t14 at the start time. No download, no account.++Showcase slots: reply here if you have built something that pays for or charges for a tool.+```++### T-7 (November 17): challenge++X:++```text+Challenge before Nov 24: make one paid API call from your own Solana wallet, watch the 402 challenge settle, bring the receipt. Best ones go on stream. https://three.ws/ibm/x402-demo?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-11-ibm-world-2&utm_content=t7+```++LinkedIn:++```text+A one-week warm-up before Tuesday, November 24.++The x402 live demo page pays a fraction of a cent in a dollar stablecoin from your own wallet to call a real three.ws data API. You see the HTTP 402 challenge arrive, sign the authorization, and get the settlement receipt with its explorer link. A Solana wallet works, and so does an EVM wallet.++Try one call, then bring the receipt to the session. Showcase slots go to the three most interesting things people do with it.++https://three.ws/ibm/x402-demo?utm_source=linkedin&utm_medium=social&utm_campaign=mkt-2026-11-ibm-world-2&utm_content=t7+```++Telegram:++```text+Challenge for the November 24 session: one paid call from your own Solana wallet on the x402 demo, then post the explorer receipt link here. Amounts are shown before you sign. The best three go on stream.++https://three.ws/ibm/x402-demo?utm_source=telegram&utm_medium=community&utm_campaign=mkt-2026-11-ibm-world-2&utm_content=t7+```++IBM Community (reply in the T-14 thread):++```text+One week out. Optional warm-up: the x402 live demo makes one paid API call from your own wallet and shows the HTTP 402 challenge, the signed authorization, and the settlement receipt. Post what you notice in this thread and we will pick questions for the session.++https://three.ws/ibm/x402-demo?utm_source=ibm-community&utm_medium=partner&utm_campaign=mkt-2026-11-ibm-world-2&utm_content=t7+```++### T-1 (November 23)++X:++```text+Tomorrow inside the three.ws world: an agent pays for its own tool and we open the receipt together. 17:00 UTC, 12:00 PM Eastern. No account. https://three.ws/event?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-11-ibm-world-2&utm_content=t1+```++LinkedIn:++```text+Tomorrow, Tuesday, November 24: the Three.ws User Group session inside the 3D world. 17:00 UTC / 12:00 PM Eastern / 9:00 AM Pacific / 5:00 PM London. Open the link in a desktop browser at the start time; the team is at the spawn point 15 minutes early.++https://three.ws/event?utm_source=linkedin&utm_medium=social&utm_campaign=mkt-2026-11-ibm-world-2&utm_content=t1+```++Telegram:++```text+Tomorrow: 17:00 UTC (12:00 PM Eastern, 5:00 PM London). Chip goes gold in the plaza 30 minutes before; we are at spawn 15 minutes early. Bring your receipts.++https://three.ws/event?utm_source=telegram&utm_medium=community&utm_campaign=mkt-2026-11-ibm-world-2&utm_content=t1+```++IBM Community (reply in the T-14 thread):++```text+Reminder: tomorrow, Tuesday, November 24, 12:00 to 1:00 PM Eastern (17:00 UTC). Open https://three.ws/event?utm_source=ibm-community&utm_medium=partner&utm_campaign=mkt-2026-11-ibm-world-2&utm_content=t1 in a desktop browser at the start time.+```++### Live (November 24, at 12:00 PM ET)++X:++```text+Live now in the three.ws world: in eight minutes two agents settle a real payment for a tool, and we open the receipt on stream. Walk in, no account. https://three.ws/event?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-11-ibm-world-2&utm_content=live+```++LinkedIn:++```text+We are live inside the three.ws world for the Three.ws User Group session. The first agent payment round starts at 12:08 PM Eastern.++https://three.ws/event?utm_source=linkedin&utm_medium=social&utm_campaign=mkt-2026-11-ibm-world-2&utm_content=live+```++Telegram:++```text+LIVE now in the $THREE home town. First payment round in eight minutes: https://three.ws/event?utm_source=telegram&utm_medium=community&utm_campaign=mkt-2026-11-ibm-world-2&utm_content=live+```++IBM Community (reply in the T-14 thread):++```text+We are live. Join here: https://three.ws/event?utm_source=ibm-community&utm_medium=partner&utm_campaign=mkt-2026-11-ibm-world-2&utm_content=live+```++### T+1 (November 25)++Bracketed values come only from the measurement capture; delete a sentence whose value was not+captured.++X:++```text+Replay: an agent hit an HTTP 402, signed a micropayment, got its tool result, and the receipt is public on Solana for anyone to check. https://three.ws/event?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-11-ibm-world-2&utm_content=t1-recap+```++LinkedIn:++```text+Yesterday's Three.ws User Group session, recapped.++In order: the HTTP 402 challenge on a live catalog; two agents at the Agent Exchange settling a payment for a tool, with the receipt opened on stream ([EXPLORER URL FROM THE LIVE ROUND]); attendees making their own paid calls; [IBM SEGMENT SUMMARY: one sentence, approved by the IBM speaker]; and member showcases.++[ATTENDANCE SENTENCE, only from the captured peak count.]++The next session date is announced first in the Three.ws User Group on IBM Community.++https://three.ws/event?utm_source=linkedin&utm_medium=social&utm_campaign=mkt-2026-11-ibm-world-2&utm_content=t1-recap+```++Telegram:++```text+Thank you for coming in yesterday. Replay clip above, and every receipt from the session is public on the Solana explorer. The next date goes up here as soon as it is booked.+```++IBM Community: a recap blog post within 24 hours, same outline as+[event two's T+1 recap](./ibm-event-two.md#t1-oct-16-replay-links-next-date), drafted in+`docs/ibm-community-blog-session-3-recap.md`. If IBM agreed to author the recap, send them the+draft and the assets instead and link their post when it is live.++### T+7 (December 1)++Send the [seven-day proof note](../templates.md#seven-day-proof-note) on the IBM thread with the+completed measurement.++X:++```text+A week on, every receipt from our in-world session is still public. That is the point of an agent paying on-chain: nobody has to take our word for it. https://three.ws/agent-exchange?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-11-ibm-world-2&utm_content=t7-proof+```++LinkedIn:++```text+One week after the session: the receipts from every payment made on stream are still public, and the Agent Exchange runs every day in the three.ws world for anyone who wants to watch agents settle a payment themselves.++https://three.ws/agent-exchange?utm_source=linkedin&utm_medium=social&utm_campaign=mkt-2026-11-ibm-world-2&utm_content=t7-proof+```++Telegram:++```text+Week-after note: the Agent Exchange is in every coin town on three.ws/play, any day. Walk up to NOVA and ORACLE and press E. Next session sign-ups are open in this chat.+```++IBM Community (reply in the recap post's comments):++```text+A week later, the receipts from the session are still public, and the Agent Exchange is available in the world any day for anyone who wants to watch a payment settle. Suggestions for the next session's theme are welcome here.+```++## Run of show++Times relative to 17:00 UTC (12:00 PM EST). Roles as in event two: Host, Producer, Moderator.++| Time | ET | Segment | Exactly what happens | Fallback |+|---|---|---|---|---|+| -45 | 11:15 | Tech check | Host and Producer in the world; Producer runs one Agent Exchange round (owner-approved) and opens `/x402`, `/ibm/x402-demo`, and `/receipts` in tabs | If the round fails, run the `x402-economy-triage` agent before the event rather than assuming the payer is empty |+| -30 | 11:30 | Preshow (automatic) | Gold chip | None needed |+| -15 | 11:45 | Doors | Host at spawn teaching WASD, Enter, hold Q, V | Moderator pastes keys in chat |+| 0 | 12:00 | Welcome | Go-live banner and volley; independence line read once; Producer posts Live beats | None needed |+| 3 | 12:03 | How an agent pays | Tab on `https://three.ws/x402`: open one endpoint, show its price and schema. One sentence each on the 402 challenge, the signed authorization, and settlement | Describe it over the jumbotron in the world |+| 8 | 12:08 | Round one in the world | Walk to NOVA and ORACLE, press E. NOVA pays ORACLE for its `tools/list` catalog through `/api/x402-pay`; the x402 jumbotron steps challenge, sign, verify, settle, confirmed; open the explorer link from the receipt. Read the amount off the panel | Show the jumbotron's platform-wide feed of recent paid calls |+| 16 | 12:16 | Your turn (optional) | Show `https://three.ws/ibm/x402-demo`. Attendees who want to pay use their own wallet; the Host demonstrates only with a dedicated demo wallet that shows nothing else, and only with the owner's prior approval of that payment | Skip if nobody wants to try; do not pressure anyone to spend |+| 22 | 12:22 | IBM guest segment | [IBM SPEAKER], 12 minutes plus 3 of questions | Move the showcase up |+| 37 | 12:37 | Verify it yourself | `https://three.ws/receipts`: connect a wallet, sign one read-only message, and list its signed receipts with explorer links. Then `https://three.ws/pulse` for the live feed of agent wallet activity | Open the round-one explorer link again |+| 44 | 12:44 | Community showcase | Up to three members from the T-14 thread, over spatial voice | Show challenge receipts posted in Telegram and the IBM thread |+| 50 | 12:50 | Open Q&A | Moderator rotates chat, IBM thread, Telegram | None needed |+| 57 | 12:57 | Group photo and next date | At the coin totem: Z then P | None needed |+| 60 | 13:00 | End (automatic) | Afterglow, then teardown; Producer captures measurement at +20 | None needed |++**Do not show:** the Oracle Ribbon's price forecast, token price talk, or any wallet holding+other than the dedicated demo wallet.++## Event config++```json+{+ "id": "user-group-session-3",+ "name": "Three.ws User Group: An Agent Pays for Its Own Tool",+ "tagline": "The IBM Community user group session, held inside the world.",+ "startsAt": "2026-11-24T17:00:00Z",+ "endsAt": "2026-11-24T18:00:00Z",+ "link": "/play?coin=FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump&name=three.ws&symbol=three",+ "linkLabel": "Join the session",+ "agenda": [+ { "atMin": 0, "title": "Doors open in the plaza", "detail": "Welcome and controls" },+ { "atMin": 3, "title": "How an agent pays", "detail": "HTTP 402 on a live catalog" },+ { "atMin": 8, "title": "Round one at the Agent Exchange", "detail": "Two agents settle a payment" },+ { "atMin": 16, "title": "Your turn", "detail": "Optional, your own wallet" },+ { "atMin": 22, "title": "Guest segment", "detail": "Questions in chat" },+ { "atMin": 37, "title": "Verify it yourself", "detail": "Signed receipts and the live feed" },+ { "atMin": 44, "title": "Community showcase", "detail": "Members show what they built" },+ { "atMin": 50, "title": "Open Q&A", "detail": "Ask anything" },+ { "atMin": 57, "title": "Group photo", "detail": "Gather at the totem" }+ ]+}+```++Write it at T-14 (after event two's config has been cleared), run `npm run event:schedule` to+validate and print the clock lines, commit, and deploy. Clear it at T+1 with+`npm run event:schedule -- --clear --apply`.++## Feature verification (checked 2026-09-17)++| Claim | Source |+|---|---|+| NOVA pays ORACLE for its `tools/list` catalog through `/api/x402-pay`, on an explicit E press only, a stablecoin payment on Solana, explorer receipt | `src/game/agent-commerce.js` |+| The jumbotron steps challenge, sign, verify, settle, confirmed and shows a platform-wide feed | `src/game/x402-jumbotron.js`; `GET /api/x402-pay?feed=1` returned live items |+| `/ibm/x402-demo` pays a sub-cent stablecoin amount from the visitor's own wallet (Solana, or an EVM chain) and shows the receipt | `data/pages.json` entry; route answered 200 |+| `/receipts` lists signed x402 receipts for a wallet after one read-only signature | `data/pages.json` entry for Receipt Vault |+| `/x402`, `/agent-exchange`, `/pulse`, `/event`, `/play` are live | Each answered 200 on 2026-09-17 |+| World features (chip, agenda, fireworks, photo stamp, keys) | See [event two's verification table](./ibm-event-two.md#feature-verification) |++## Owner steps, in order++1. Confirm November 24 or the November 17 alternative (T-21, November 3), and send the+ relationship note.+2. When IBM confirms the speaker and wording, fill the `[IBM SPEAKER]` fields and create the event.+3. Commit and deploy the event config (T-14, November 10).+4. Approve the Agent Exchange rounds and any Host demo-wallet payment, with amount and chain.+5. Post each beat on its date; run the session; capture measurement at +20 minutes.+6. Clear the config and deploy (T+1); post recaps with captured numbers only.+7. Send the proof note (T+7) and update the campaign row's status.diff --git a/marketing/growth/templates.md b/marketing/growth/templates.mdindex 568e39ff5..75cf20d09 100644--- a/marketing/growth/templates.md+++ b/marketing/growth/templates.md@@ -38,6 +38,9 @@ Subject: `Three.ws user group: event two, Agent Connect, and the open June follo> Build-track Partner Marketing Kit? The full public implementation and relationship wording> are documented at https://three.ws/ibm/hello.+The dispatch-ready version for event two, with the date options and all four asks, is section 2+of the [event two kit](./events/ibm-event-two.md#2-relationship-email-to-ibm).+Send the Agent Connect `APP_ID` request separately using the existing[submission pack](../ibm-partner-plus/agent-connect-listing.md); combining a technical unblockwith the marketing note makes both harder to route.@@ -68,7 +71,9 @@ after booking:> The stream plan and fallback assets are ready; happy to send the 16:9 card and 20-second demo> clip in advance for the official announcement.-Do not use this reply until the booking is confirmed; the current issue has no date.+Do not use this reply until the booking is confirmed; the current issue has no date. The fuller+reply written after approval, with only the date left to fill, is in the+[contribution menu](./events/open-source-friday-menu.md#booking-reply-for-issue-254).## Coinbase Founders Fuel application corediff --git a/marketing/ibm-partner-plus/agent-connect-listing.md b/marketing/ibm-partner-plus/agent-connect-listing.mdindex 4bb01ddc4..1f2bdc621 100644--- a/marketing/ibm-partner-plus/agent-connect-listing.md+++ b/marketing/ibm-partner-plus/agent-connect-listing.md@@ -26,7 +26,13 @@ Send to **[email protected]**. Allow 2 to 3 business days.> artifacts. Also performs remeshing, retexturing, segmentation, optimisation, and> automatic rigging on existing models.>-> We are an existing IBM Business Partner running IBM Granite on watsonx.ai in production.+> We are an existing IBM Business Partner. three.ws agents can run on IBM Granite foundation+> models served through IBM watsonx.ai.++The last sentence uses the safe claim from [`badge-usage.md`](badge-usage.md): do not say Granite+runs "in production" while the production service has no `WATSONX_*` credentials+(`/api/ibm/galaxy` answered `watsonx_not_configured` on 2026-09-17). The same email is in the+[event two kit](../growth/events/ibm-event-two.md#3-agent-connect-app_id-request-separate-email).Save the `APP_ID` from the reply. If it is ever lost, the same address retrieves it giventhe server name.