Server Architecture Integration — Aura

Aura currently has a flat thread model: `HubThread` objects live in `hub_threads`, categorized by `ThreadCategory` and `ThreadType`, with no parent container. The Discord ecosystem, however, operates on three distinct architectural patterns — each representing an evolution in how the Clawdbot gateway handles task dispatch and message delivery. This document describes those three patterns in abstract form and specifies how they integrate into Aura as a **secluded feature** that does not interfere with the existing thread hierarchy. **Abstract model:** A stateless request-response loop. The client sends a named command with arguments. The server executes a direct database query, formats the result, and returns it immediately. No task queue, no progress streaming, no persistent connection. **Characteristics:** - Commands are a fixed set: each maps to exactly one query/action - No model routing — the server IS the executor - No progress updates — result arrives in one shot - Stateless — each command is independent, no session continuity - Response format: plain text, chunked if exceeding size limits **Data requirements:** - Command registry (name → handler function) - Direct database access (reads from domain-specific tables) - No task table, no thread table, no message history **When to use:** Domain-specific dashboards where you need instant answers from structured data. Sales pipeline queries, inventory lookups, metric summaries.