Elonn Docs Platform Documentation

object

spatial canonical authority: varies — always qualified by service

Object

A renderable entity within a block, originating from a service. Objects are the data primitives the surface system presents.

Examples by provider:

  • place (maps.elonn.local)
  • member (api.elonn.local)
  • gathering (social.elonn.local)
  • message (messages.elonn.local)
  • social-dm (social.elonn.local)
  • route (maps.elonn.local)
  • calendar item (time.elonn.local)
  • notification (social.elonn.local)

Sub-concepts:

  • object provider — the service responsible for producing the object
  • object state — current live state of an object (online, active, busy, joined, saved, muted)

Allowed:

  • [name] object (e.g., place object, member object)
  • object provider
  • object state

Forbidden:

  • item (too generic; use the domain noun where possible)
  • entity (database term; not a product noun)
  • record (implies a database row)

Notes:

  • "Object" in the surface system means a renderable data entity within a block. This is distinct from the informal use of "object" elsewhere (carry object, field object, world object) where it is a generic noun, not a system term.
  • Always prefer the domain noun (place, member, message) over bare "object" when referring to a specific type.
  • Objects may expose actions. Cards are the visual presentation of objects.

Related:

  • card (object's visual presentation)
  • block (object's container)
  • action (object may expose actions)
  • finding (objects may be findings)