Skip to content

design: define the persistent conversation and channel model #102

@ibourgeois

Description

@ibourgeois

Context

As a product and architecture team, we need a clear conversation and channel model so Katra can support collaborative chats with users, models, and agents without inheriting the disposable transcript patterns of current AI harnesses.

Acceptance Criteria

  • The issue defines how conversations are represented in the desktop MVP shell.
  • The navigation model supports group chats, chats with other users, chats with models, and chats with agents.
  • The direction is explicitly closer to Slack, Teams, or WebEx conversation organization than to one-thread-per-context-window AI interfaces.
  • The issue captures the principle that one persistent conversation with a given model or agent may be sufficient because Katra does not rely on full transcript replay as its primary context strategy.
  • The conversation model is compatible with graph-native relationships to tasks, artifacts, decisions, and future multi-user collaboration.
  • The resulting guidance is suitable for informing the MVP shell mockup without locking the app into chat-only assumptions.

Notes

This is a product-shaping issue, not just a visual design issue. It should help avoid reproducing current AI chat ergonomics that Katra is explicitly trying to move beyond.

Out of Scope

  • implementing full conversation persistence or collaboration behavior in the same issue
  • real-time multiplayer transport details

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions