Join and Follow the Conversation (problems with the current Commentary System)

Introduction

Seed Hypermedia is structured through Knowledge Communities. We want to experiment with interfaces for community engagement with AI. We are starting with the idea of Multiplayer Agent Chat Sesions/Threads.

The hardest dispute we are having is understanding the relationship between our Threads and the Agent Chat. Let's brute-force the dispute by launching prototypes and experiments.

Agent Chat gives us the opportunity to experiment at the same time with a few proposition values:

Agents.

Multiplayer Agent Chat Sessions.

Privacy.

Immediacy.

Slack-style interaction.

Once we crack the UX and develop Hypermedia Schemas, we need to integrate Agents into the core protocol.

Definitions

Space Agents

A Set of Agents that a site owner has enabled in a space.

Agent Session

A sequential log of user messages, agent messages, and tool calls.

Contains context about a specific task, a single thread of work.

Thread

The difference between a Session and a Thread is still to be defined.

Session without the tool/computation stuff. The permanent data that will get stored.

Agent threads are conversations attached to a target document.

An agent session can be turned on or off, and keep the Thread.

Target Document

In code, the field is targetDocumentId—the identifier of the target document. It is optional. There might

Target brings permissions.

Target brings archival.

Participants can be inherited from the Target Document.

When the conversation is finished, it is archived as a backlink to the target document, preserving the discussion in its context.

When there is no Target Document, I believe the session becomes ephemeral. Ephemeral in the sense that there is no Collective Memory.

Members (or Participants or People)

Writers need a clear understanding who are the recipients. Writers need privacy to discuss their findings.

Notification

Backlinks

All the links included in the Session/Thread.

Agent Chat Panel

The conversation remains active while users navigate to other documents, so the thread does not need to occupy the main content view.

On mobile, the existing comment system can largely be reused. The main exception is that starting an agent thread should open the chat panel rather than the standard comment panel.

User Stories

As a Writer, I want to create a new Chat Session with my personal assistant

As a Writer, I want to create a new Chat Session with my personal assistant that is not connected to any particular document. The current way

As a Writer, I want to create a new Chat Session/Thread

As a Writer, I want to create a new Chat Session/Thread with a certain document as context and with members. Right now, the way to do this is the following:

As a Writer, I want to create a new Chat Session/Thread with a certain document as context and members.

As a Writer, I want to find a Session.

As a Writer, I want to find a Session used from a certain document.

Disputes

Difference between current Threads and Agent Chats.

Data Model.

How to open Panels?

As a Writer, I want to create a new Chat Session with my personal assistant, which is not connected to any document in particular.