Core concepts
Orbismo has a small vocabulary. Once these terms click, the rest of the product follows naturally.
The top-level container. A world is one self-contained universe — its own entities, lore, collaborators, and subscription. You can own several worlds, and each is independent of the others. Think of it the way you’d think of a single repository.
Entity
Section titled “Entity”The building block of a world. An entity is any element you want to track — a person, a place, an event, a group. Entities are the nodes of your world’s graph, and each one can carry custom properties and lore. See Entities and relationships.
Entity type
Section titled “Entity type”The category an entity belongs to — Person, Place, Event, and so on. Every world starts with a default set of entity types and can be extended with your own.
Relationship
Section titled “Relationship”A connection between two entities — “is a member of”, “lives at”, “led to”. Relationships are the edges of the graph; they’re what let you ask connected questions like “everyone in this group who attended that event.” See Entities and relationships.
Long-form prose attached to an entity — its history, description, and detail. Lore is indexed for semantic search, so you can find things by meaning, not just by exact wording. See Lore.
A label from a shared vocabulary you apply across entities (for example, “coastal” or “noble house”). Tags keep your world consistent by preventing near-duplicates like “swordsmanship” vs. “sword fighting.”
Default schema
Section titled “Default schema”Every world is created with the same default schema — a general-purpose set of entity types (Person, Place, Event, Group, Project, Interest, Item) and the relationship types that connect them. There’s no template to pick; you adapt the one schema to whatever you’re building by extending it and setting a world prompt. See the Data model.
Collaborators and roles
Section titled “Collaborators and roles”Other people you invite into a world. Each collaborator has a role:
- Owner — the person who created the world. Full control, including billing, invitations, and roles. Every world has exactly one owner.
- Editor — can read and write entities, lore, and relationships, but can’t manage billing or invite people.
- Viewer — read-only access.
See Collaborators and permissions.
AI integration (MCP)
Section titled “AI integration (MCP)”Every world is reachable over the Model Context Protocol (MCP), so AI tools can read and edit it alongside your team. Access is governed by API keys you control: read-only keys can query, read-write keys can change the canon. See Connect an AI tool.
Looking for a quick lookup instead? The Glossary collects these terms in one place.