Elonn Docs Platform Documentation

world

world.elonn.local is the aggregation and composition layer for Elonn. Production is world.elonn.com.

World assembles identity, maps, social, messages, and time data into the platform-neutral runtime contract. Web is the first adapter proving that contract, not its architectural target.

World composes Surface runtime state into /world/session. See world-contract.md and Current State for the implemented end-to-end flow.

Owns

  • runtime contract (the composed session payload)
  • carry and field layout composition
  • world session
  • relay and rewrite of service endpoints for runtime adapters
  • relay and composition of Surface runtime state

Role in the stack

World sits between the web runtime and all domain services. The web runtime calls world for runtime data and actions; world proxies and rewrites routes from social, time, maps, and surface. World does not own authored field data — it consumes from maps.elonn.local. World does not own surface persistence — it consumes from surface.elonn.local.

Routes

World exposes the runtime contract endpoint, /ready, and relayed service routes. Runtime adapters do not call social, messages, maps, or time directly.

Key configuration

Key Purpose
ELONN_API_BASE_URL Identity validation
ELONN_SOCIAL_BASE_URL Social data source
ELONN_MAPS_BASE_URL Field and marker data
ELONN_TIME_BASE_URL Calendar data

Readiness

World exposes GET /ready as its readiness check. It verifies the dependent platform services that World composes into /world/session, including API identity, Maps, Social, Time, Find, and Surface.

Verification

World has a local smoke test suite:

bash world.elonn.local/test.sh

The smoke tests verify that /world/session preserves the Surface runtime contract:

  • surface_runtime includes normalized surface and stack fields
  • object-valued Surface runtime fields stay JSON objects, not empty arrays
  • Surface runtime command URLs point to World relay routes
  • Surface runtime command URLs do not expose member_id or direct Surface service URLs to runtimes

World still derives trusted member context internally when it relays focus, reorder, and placement writes to Surface.

Canonical terms

  • world — the composition service and product noun
  • contract — the runtime payload world produces
  • carry — user-following layer world composes
  • field — spatial layer sourced from maps
  • runtime — the environment that consumes the contract