Back to corpus
architecturetechnical paper candidatescore 62

HUB-2: Threaded Messaging Architecture

Replace Discord's channel model with a threaded architecture tailored to OpenClaw: - **Threaded, not channel-based** — every conversation is a thread with a parent category - **Quad-inspired layout** — 4 concurrent contexts visible (like the terminal quad) - **Feed integration** — 33 Prefect flows post directly to threads (no Discord webhooks) - **Agent-native** — threads can be owned by agents, not just humans - **Voice-first** — every thread supports voice input/output - **Offline-capable** — SwiftData persistenc

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

**Date**: 2026-03-01 **Status**: Design Complete — Ready for HUB-3 Implementation Replace Discord's channel model with a threaded architecture tailored to OpenClaw: - **Threaded, not channel-based** — every conversation is a thread with a parent category - **Quad-inspired layout** — 4 concurrent contexts visible (like the terminal quad) - **Feed integration** — 33 Prefect flows post directly to threads (no Discord webhooks) - **Agent-native** — threads can be owned by agents, not just humans - **Voice-first** — every thread supports voice input/output - **Offline-capable** — SwiftData persistence with Supabase Realtime sync ### 2.1 Conversation Threads (interactive) Human ↔ Agent bidirectional conversations. Created when user starts a chat or dispatches a task. **Properties**: owner (human), agent (assigned), model (claude/gemini/ollama), session_key, gateway connection, conversation history (10-turn), context hints from Kimi. ### 2.2 Feed Threads (read-only, system-generated) Automated posts from Prefect flows. Replace Discord webhook channels.

Promotion decision

What has to happen next

Promote into a technical note or architecture paper with implementation anchors.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.