messages
messages.elonn.local is the open Messages service for Elonn. Production is messages.elonn.com.
Messages owns open one-to-one member communication outside Social context. It does not own Social DMs, Social replies, Social conversations, communities, events, identity, or runtime layout.
Owns
- open message threads
- exactly two thread participants
- message bodies
- inbox ordering
- unread/read state
- message-thread object sources
- Messages runtime panel payloads as compatibility presentation content
Does Not Own
- Social DMs initiated from Social context
- conversation or event replies
- communities, conversations, events, profiles, presence, activity, or notifications
- member identity records or member directory
- World object identity, placement, relationships, runtime routing, focus, or workspace composition
- runtime panels, rails, markers, lists, meshes, interaction, or rendering
Routes
GET /health
GET /ready
GET /messages
GET /messages/objects
POST /messages
GET /messages/{id}
POST /messages/{id}/messages
GET /runtime/panel/messagesRuntimes do not call Messages directly. World exposes /world/messages and /world/panels/messages, then relays to Messages with authenticated member context.
World consumes GET /messages/objects as the service-owned object source route. That route publishes message threads as domain objects with source, object_type, title, summary, state, domain_permissions, domain_actions, and relationships. It must not publish runtime layout or presentation primitives.
Product Rule
A message thread is one-to-one. If a member tries to add a third member or make a thread into a group, the product should guide them to create or use a Social community, conversation, or event instead.