How It Works

The Architecture Stack

The system is built in five layers from bottom to top:

Layer 1: Data Model — Map the organization, its assets, and its current reality. Organizational structure, digital accounts, documents, member data, sponsor contacts, Discord history, Notion content. This is the foundation everything else builds on.

Layer 2: Workflow Model — Document how things actually get done today. Every club function has workflows — the current way it's done, who does it, what tools they use, what the inputs and outputs are.

Layer 3: Tool Layer — Build surfaces that augment and eventually replace manual workflow execution. Integrations (Discord, Notion, email, calendar, Luma), services (Sponsor CRM, Member CRM, Committee management), and dashboards.

Layer 4: Cognitive Layer — Agent programmes that use the tools to execute the workflows. This is where the AI goes from being a passive knowledge store to an active operator.

Layer 5: Orchestration Layer — Autonomous decision-making, heartbeat loops, and human approval gates. Agents make decisions based on information from reality, propose actions, and seek human approval. This is where autonomy lives.

The Knowledge Base

All organizational knowledge is written in Markdown — interconnected notes that the AI agent reads, reasons over, and updates. This collection of notes is called the Mesh. It's the AI's memory. Between sessions, the Mesh holds everything; the agent itself remembers nothing.

Each session, the agent reads the current state of the organization, does whatever work is needed, and writes the results back.

The Human-AI Loop

The agent and the human work in complementary roles:

The agent handles:

• Planning and task generation
• Documentation and knowledge maintenance
• Progress tracking and status reporting
• Identifying what needs to happen next
• Executing workflows through integrated tools

The human handles:

• Physical-world execution (meetings, events, communication)
• Approval of plans and significant decisions
• Creative direction and judgment calls

Neither works in isolation. The agent generates work, the human executes and feeds results back. Over time, the goal is for more of the loop to shift toward the agent.

Club Functions

RAID operates across seven functional areas, each of which will progress through the architecture stack independently:

• Marketing — Brand assets, marketing materials, outbound messaging
• CRM / Members — Member management, acquisition, onboarding
• Events — End-to-end planning, logistics, Luma integration
• Sponsorships — Sponsor CRM, outreach, partnership management
• Finance — Financial management, reporting, invoicing
• Initiatives — Software projects, arbitrary club projects
• Committee — Committee coordination and management

Micro-Projects

Under the overarching ORG1 project sit micro-projects (initiatives), each scoped to deliver a specific tool or service version. Each initiative takes a RAID function through one or more layers of the architecture stack:

1. Modelling — map the function into the data model
2. Tooling — build a surface for that function
3. Cognition — wire an agent to use that tool
4. Orchestration — agent autonomously runs that function

All initiatives are open-source with concrete deliverables.