Jake Winckowski joined the June cohort fireside to discuss AI-augmented customer experience work at HackerOne. The conversation covered how increased AI-driven activity has changed support ticket volume, and how Jake built an internal Slack-based workflow with Claude Code to pull in tickets, suggest responses from historical context, and let support agents approve, edit, escalate, or resolve them. The group also discussed keeping humans in the loop for trust, security, payment, mediation, and technical troubleshooting while the team improves confidence scoring, data access, reporting, and agent-assisted support workflows.
0xHunter joined the June cohort fireside to discuss AI-enabled consulting workflows, self-hosted software strategy, and context sharing across teams and clients. He described Datalist Consulting's work building custom software, training, integrations, and technical consulting for medium-sized businesses, with a thesis that cheaper custom software can let smaller companies own more of their infrastructure. The conversation also covered Hunter's Codex-heavy workflow, build-versus-open-source decisions for internal tools, frontend QA concerns, and the still-unsolved challenge of sharing scoped AI context without copying isolated agent chats by hand.
30 minute casual game jam focusing on games or DIY projects that fit into RaidGuild Forge ("Where makerspace and gaming meet."). See https://forge.raidguild.org/ to understand what fits.
There is no strict agenda. Just show up with a project or join a project. Collaborate with others, or feel free to work quietly the entire time.
Victor Ginelli joined the June cohort fireside to discuss how AI-assisted development is changing developer workflows and team collaboration. The conversation covered his move from skepticism to daily use of tools such as Codex, Claude, Cursor-style workflows, terminal tooling, and mobile prompting, with developers shifting toward specifying work, managing AI agents, reviewing output, and building CLIs or wrappers for repeatable tasks. The group also discussed limits around planning, infrastructure, deployment, maintenance, governance, and human review, plus how small teams may collaborate more through shared specs, internal tools, and agent-ready interfaces.
MoDev & RaidGuild was scheduled as a June 17, 2026 fireside conversation hosted on Google Meet. A same-day RaidGuild Discord message invited raiders to join a conversation with the founder of MoDev.com about agentic event platforms, using the same meeting link and 11:00am-12:00pm America/Los_Angeles time window.
June Cohort Fireside Chat with Justice Conder.
Calendar: RaidGuild
Created by: clerics@raidguild.org
Who: clerics@raidguild.org, justiceconder@gmail.com
Hosted by Dekan, Spencer Graham joins RaidGuild for a June Cohort Fireside on personal CRM systems, agentic coding workflows, and the future of coordination. The conversation connects Spencer's product and strategy background with his current experiments in self-hosted relationship software, AI-assisted development, context systems, UX verification, and open source security.
Guest background: Spencer's RaidGuild profile highlights product management, operational strategy, UX/technical trade-off thinking, game theory, and token economics.
Discussion themes:
- Self-hosted personal CRM and relationship-aware software
- Agent-assisted development workflows using doer/reviewer loops
- Context and verification as hard problems for AI agents
- UX QA automation for human-facing products
- The risk of AI workflows creating more atomized developers
- Why AI may strengthen, not kill, open source software
Notable guest quotes:
- "Context is changing still, and it came in an unsolved kind of lane."
- "It would be really bad if it happened that we lost so much of what makes working together on things fun."
- "The idea that open source is dead is just hilarious and so wrong."
Working session to define a Queen Raida user manual for RaidGuild members and map how members should leverage the tool to turn siloed conversations, channels, and communication streams into shared guild context.
We will also jam on Cohort and RaidGuild expansion: how cohorts are meant to operate, who the stewards/POCs are, what a cohort looks like from start to finish, and how to distinguish project-specific cohorts from more general cohorts.
Source message: https://discord.com/channels/684227450204323876/1496892348582596668/1512539243602509884
Cohort Demo Day is a session for raiders and cohort participants to share what they have been working on, show progress, and connect around next steps.
Monthly RaidGuild all-hands meeting to discuss what is happening across the guild and share what raiders are working on.
Fireside host script and process working notes:
Purpose: Run lightweight 30-60 minute fireside chats about how people are using AI in real work. Focus on useful tools, workflow changes, trust and limits, adoption barriers, and where each field is headed. Capture recordings and transcripts so each session can become notes, case studies, clips, posts, Portal articles, newsletters, or knowledge-base material.
Recording and transcript process: Before each session, create a Portal Session with the guest, host, topic, and prep notes. If the session happens in Discord, start the voice session and run /prism-recordvoice in the relevant Discord channel. Confirm consent at the beginning of the call for recording, transcript, research, and possible content reuse. After the call, attach the Prism recording summary, transcript, recording URL, and artifacts back to the Portal Session so Portal remains the source of record. For sessions outside Discord, collect the recording or transcript and add it to the Portal Session with enough context for follow-up content work.
Opening: Thanks for joining. The goal is to understand how people in different fields are actually using AI: what tools are useful, what has changed in your workflow, what still feels hard, and where you think this is headed. This is casual; we are looking for real examples, patterns, and stories.
Consent prompt: Are you comfortable with us recording this conversation for transcript and research purposes? The recording may be used to create internal notes, summaries, case studies, or public content. We can review anything before publishing and avoid using your name or company if you prefer.
Interview flow: Ask the guest to introduce themselves and describe their work, what a normal week looks like, and what used to be repetitive, slow, or frustrating before AI tools became common. Ask what AI tools they use now, how often they use them, their main AI-assisted tasks, and a recent concrete example where AI helped. Explore how their workflow has changed, what is faster, what they approach differently, and whether AI has changed the work they spend time on. Cover trust, quality, and limits: where they trust AI, where they avoid it, bad or risky outputs, and what still needs a human expert. Discuss adoption barriers in their field, including trust, training, cost, privacy, and workflow fit. Close with future expectations, advice for someone just starting, anything important we missed, and who else we should talk to.
Closing: Thanks again. We may turn this into notes, a short case study, or a broader piece about how AI is being adopted across different industries.
Kick off the How to RaidGuild cohort with a one-hour info session hosted by Dekan. We will get to know each other, orient around RaidGuild as a digital coworking space for builders, and talk through how the cohort helps people join sessions, find collaborators, build skills, and turn ideas into active guild work.
A working session to shape RaidGuild's upcoming Fireside format: Field Notes from the Edge, a series of conversations with members actively adapting across agency work, protocol development, AI tooling, operations, media, governance, infra, experiments, and indie products. Goal: define the interview format, session structure, content artifacts, and Portal publishing hierarchy for turning each Fireside into useful public content and durable guild knowledge. Agenda: reconfirm the live-adaptation frame; review candidate role tracks; refine the interview spine; define the artifact package; map the PortalCMS hierarchy; choose first guests/themes; decide what must exist before the first public session. Expected outputs: final format, artifact package draft, PortalCMS mapping, guest/topic shortlist, and production checklist.
Elco presents Bard School, a practical content system for DAOs and communities. The talk frames content as coordination infrastructure, using buckets, long-form seeds, awareness funnels, lightweight rituals, and a minimal publishing cadence to help RaidGuild produce consistent, useful public artifacts.
0xJustice-eth presented ClawBank, a platform that gives AI agents bank accounts, crypto wallets, and the ability to form LLCs, prompting discussion about onboarding, cleanup workflows, legal liability, and the broader implications of agent-run entities.
James Young explores Digital Twin Agents as AI representatives for DAO members and decentralized organizations. The session covers preference learning, coherence scores, recursive trust networks, delegated decision-making, multi-agent governance, and how alignment-focused agents could expand coordination beyond token-weighted voting.
Matt from Pinata walks through Pinata Agents and how the platform supports agent-oriented workflows. The session covers practical uses for hosted agent infrastructure, file and data handling, and how developers can connect Pinata's tooling into AI-enabled applications.
Dekan walks through Venice.ai as a private-by-default AI platform with hosted model access and token-based compute. The session covers anonymized model routing, open-source and commercial LLM access, daily compute credits, staking mechanics, and how Venice-style infrastructure can fit into agent workflows.
ECWireless breaks down the keys to running a successful RaidGuild project through three pillars: scope, team, and pace. The session focuses on defining realistic project boundaries, assembling and trusting the right contributors, setting role clarity, managing blockers, and keeping delivery momentum without losing client context.
This brown bag demos Droid as a coding-agent workflow for auditing documentation, planning fixes, and updating a repository from the terminal. The discussion focuses on practical developer ergonomics: readable agent responses, task breakdowns, repo inspection, documentation maintenance, and the overlap between Droid and other AI-assisted coding tools.
