Elonn Docs Platform Documentation

social

social.elonn.local is the social object service for Elonn. Production is social.elonn.com.

Social owns social truth and publishes JSON contracts for world.elonn.local and web.elonn.local to consume. It does not own login UI or platform rendering.

Open platform Messages are a separate bounded context documented in messages-contract.md. Social DMs are Social-owned private one-to-one communication initiated from Social context.

Web does not call Social directly for visible runtime actions. Web calls World; World relays to Social, rewrites links and actions back through /world/..., and returns runtime JSON to Web.

Key model

Social is built around circles and discovery. A member's social world starts with people who share a private community with them, then expands to the people those people privately share communities with.

The current implementation exposes circle depth names:

Depth Name Meaning
1 Inner People who share a private community with the member directly.
2 Trusted People who are Inner to the member's Inner circle.
3 Extended People who are Inner to the member's Trusted circle.

Circles are not followers, friends, or manual lists. Public communities and public events are visible because they are public; they do not create circle bonds.

Owns

  • conversations and replies
  • communities
  • events (social events — not calendar events)
  • profiles
  • presence
  • activity feed
  • notifications
  • relationships (block records)
  • circles (derived from private community co-membership)
  • discovery graph
  • Social DMs

Role in the stack

Social is the authority for conversations, communities, social events, Social DMs, and related social graph objects. Time ingests social events as calendar mirrors via syncSocialEventToTime; social remains the source of event truth. World relays social endpoints to the web runtime.

Visible Social surfaces and panels are produced by /runtime/panel/social?format=json and /social/objects. Social DM endpoints are Social-owned and should appear only in Social context. World consumes Social endpoints and composes service-owned content into surfaces and service navigation panels. Social owns conversation, community, event, and Social DM data; it does not own runtime layout, surface identity, or rail presentation.

Routes (selected)

GET  /social/events
POST /social/events
GET  /social/events/{id}
POST /social/events/{id}/rsvp
GET  /social/conversations
POST /social/conversations
POST /social/conversations/{id}/messages
GET  /social/communities
GET  /social/presence
POST /social/presence
GET  /social/discovery/graph
GET  /social/activity
GET  /social/objects
GET  /runtime/panel/social
GET  /runtime/panel/social-dms
GET  /social/dms
POST /social/dms
GET  /social/dms/{id}
POST /social/dms/{id}/messages

Key configuration

Key Purpose
ELONN_API_BASE_URL Identity validation
ELONN_TIME_BASE_URL Event sync target

Canonical terms

  • event — social gathering with RSVP (not a calendar event)
  • conversation — titled group discussion
  • message — open one-to-one communication outside Social context
  • social-dm — private one-to-one communication inside Social context
  • reply — posted into a conversation or event
  • circle — derived from private community co-membership
  • discovery — circle-depth traversal for Social visibility and reach