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.
Snax walks through PizzaDAO automation experiments from a hack day, including tools for project status, admin workflows, and proof-of-pizza style submissions. The session shows how lightweight automation and AI-assisted workflows can support community operations around PizzaDAO.
Dekan demos Daily Dust, an in-game, spatially aware newspaper for DUST. The walkthrough shows article creation, IPFS image selection, local discovery by player position, classified-style posts, curated front pages, and future uses such as lore, quests, walking tours, announcements, and world-based communication.
Sassquatch discusses non-technical roles in RaidGuild and web3 work, focusing on how contributors can create value beyond writing code. The session highlights operations, project coordination, client communication, community work, and the practical paths for non-developers to participate in technical ecosystems.
Spencer introduces Hats and its approach to roles, permissions, and organizational structure. The session explores how programmable role systems can support DAO operations, clarify responsibilities, and encode access or authority in ways that are composable with onchain coordination.
TheKerp makes the case for why RaidGuild matters as a model for the future of work. The session reflects on decentralized collaboration, guild-based opportunity, autonomy, reputation, and how RaidGuild's structure creates a different path from conventional employment.
GoldenLady leads a discussion on network states, digital communities, and the relationship between online coordination and real-world institutions. The session explores how communities can develop shared identity, governance, territory, legitimacy, and practical systems that bridge internet-native organization with political and social reality.
Nukemandan introduces zero knowledge and verifiable computation, moving from basic ZK concepts into zkVMs, RISC Zero, offchain execution, onchain verification, Bonsai, and practical developer workflows. The session also touches on privacy, healthcare use cases, fully homomorphic encryption, and advanced cryptography communities.
Sky explains why decentralization matters beyond slogans, grounding the discussion in resilience, agency, governance, trust, and the risks of centralized control. The session explores decentralization as both a technical and social design choice for communities, protocols, and institutions.
Jschiarizzi reflects on the builder mindset and what it means to create inside RaidGuild and web3 communities. The session focuses on agency, craft, experimentation, collaboration, and the habits that help builders move from ideas to shipped work.
0xRowdy presents The Juice in the context of product development. The session discusses how to shape product ideas, evaluate what is useful, and move from concept toward practical execution while keeping users, workflows, and delivery constraints in view.
Christina and BorrowLucid lead a story-focused session about content, attention, and narrative practice. The brown bag includes a writing exercise and discussion about how to tell stories from perspective, use sensory detail, and think about audience without polluting the internet with low-signal content.
