Skip to main content

Prism / Queen Raida

Prism is RaidGuild’s organizational agent system. In Discord it commonly appears as Queen Raida. Its purpose is to help the Guild turn ongoing activity into durable memory, reusable workflows, and useful tools without flattening context or ignoring permissions.

What Prism Connects​

  • Knowledge sources — approved handbook pages, living documents, meeting notes, code, and other scoped sources.
  • Durable memory — summaries and structured records that preserve decisions, context, and open threads over time.
  • Shared workflows — repeatable content, operations, code, and research tasks.
  • Surfaces — Discord, chat, apps, and tools used by members and stewards.

Permissions Are Contextual​

Prism does not have one universal level of access.

  • A channel may expose only a read-only slice of the knowledge base.
  • A workflow may allow the agent to create or update a specific kind of record.
  • Steward categories may use agent profiles tailored to their responsibilities.
  • Future member profiles may have different sources and actions.

Always check the visible workflow and audience before sharing sensitive material or asking the agent to act. Agent output should preserve source references when it summarizes Guild knowledge.

Intended Uses​

  • preparing and organizing meeting notes;
  • retrieving Guild knowledge with references;
  • drafting content and operational artifacts;
  • supporting steward workflows and recurring coordination;
  • generating and reviewing code; and
  • helping turn activity into daily, weekly, and topic-level living documents.

Steward Agent Assistants​

Each steward or other accountable Hat wearer can have a dedicated Prism agent space and agent profile tailored to that role. This acts as the steward's agent assistant: it can work with the approved knowledge, recurring workflows, records, and tools relevant to the Hat while keeping that context separate from other roles.

The profile should inherit the permissions and boundaries of the steward workflow, not the full access of the person wearing the Hat. Changing the human wearer must include reviewing the agent space, sources, credentials, pending work, and handoff context. The named human remains accountable for the role and for any sensitive action taken with agent assistance.

Human Responsibility​

Prism supports judgment; it does not replace it. Members remain responsible for checking sensitive claims, governance proposals, client commitments, financial instructions, permissions, and anything that acts outside a reversible draft workflow.

Governance roles and sensitive infrastructure access must retain a named human owner. An agent may assist that person, but it should not become the ultimate holder of privileged authority. See the proposed accountability model in DAO Roles and Hats Governance.

Do not treat an agent response as ratified Guild policy. The handbook, final RIPs, onchain proposals, contracts, and decisions recorded by the responsible people remain the durable authorities for their respective domains.

Ask Raida