Libranis documentation · concept

Orbitals

Focused experiences over one core — ScanThis, Casaeris, Nodivis, Firminis — and how an orbital differs from a separate product.

Canonical identifier
https://libranis.com/docs/orbitals/
Last updated

Definition

An orbital is a focused Libranis experience over the shared Libranis core: one lens on a person's world, shaped for one job. Orbitals are surfaces, not products. They read and write the same entities, the same relationships, and the same permissions, and they are all included in the one Libranis subscription.

Purpose

To let a person meet Libranis through the job they actually have — a physical thing, a household, money, a business — without splitting their world into applications that cannot reference each other.

What problem it solves

The usual answer to "this product does too many things" is to ship several products. That answer creates the fracture the product exists to remove: the same house, the same vehicle, the same person and the same document end up duplicated across applications with no relationship between the copies, and the seams become the user's problem.

An orbital gives focus without giving up the shared graph. Two orbitals looking at the same house are looking at the same house.

What it is not

  • Not a separate application. Orbitals live inside the one Libranis application. Installing Libranis and unlocking an orbital does not add an icon to a phone.
  • Not separately purchasable. One subscription covers every orbital, including ones that have not shipped yet.
  • Not a data silo. An orbital does not own its entities. It is a view and a set of tools over entities that belong to the person.
  • Not a marketing division. Orbital sites — scanthis.today and its siblings — explain and route. They do not sell. Purchases happen only at get.libranis.com.

The orbitals

OrbitalFocusStatus
ScanThisPhysical and informational things: scan or tap a thing to reach its living record and ask it questions.In beta today
CasaerisThe remembered home: routines, records, repairs, people, and projects kept where a household can ask.Planned
NodivisMoney held in stewardship, for households, businesses, non-profits, and the places they overlap.Planned
FirminisThe whole arc of a business: launch, operations, growth, acquisition, succession, and handoff.Planned

Only ScanThis is available. The others are described because the shape of the product is the point, not because they can be used today. New orbitals join the same application and the same subscription over time.

Orbital, primitive, hub

Three words name three different things and are routinely confused.

TermWhat it isExample
OrbitalAn experience over the core, shaped for one job.ScanThis
PrimitiveA way of interacting — a modality over an entity.Chat, Voice, Meet
HubA place or collection a person keeps.A home, a business

An orbital answers which part of my world. A primitive answers how am I interacting with it. A hub answers where am I. All three point at the same underlying entities.

Entity types

Orbitals introduce no entity types of their own. They present the shared types — objects, places, organizations, people, documents, work, conversations — with the emphasis and the tools their job requires.

Relationships

An orbital does not hold relationships. The person holds them, and the orbital renders the ones relevant to its job. This is why data relates across orbitals without an integration step: there is nothing to integrate, because there was never a second copy.

Capabilities

  • Present the subset of a person's graph relevant to one job, with tools shaped for that job.
  • Add entities and relationships that any other orbital can then see.
  • Bind Ari to the entity in view, so that questions asked inside an orbital carry that orbital's context.

Authority model

Identical to the rest of Libranis. An orbital grants nothing on its own; every read and every action is authorized by the person's identity, credentials, tethers, and — where relevant — entitlements. An orbital is not a permission.

Identical to the rest of Libranis. Moving between orbitals does not lower a consent requirement; the requirement belongs to the action, not to the surface it was taken from.

Privacy boundary

An orbital does not widen visibility. A record that is private in one orbital is private in all of them, because there is one record and one boundary. An orbital showing a thing does not publish it.

Examples

One house, three lenses. ScanThis holds the water heater, the softener, and the generator as things with service histories. Casaeris, when it ships, will hold the household's routines and responsibilities around the same house. Nodivis, when it ships, will hold what the house costs. Three lenses, one house, one set of records.

One business, two lenses. A plumbing company's trucks and equipment are ScanThis entities its technicians scan in the field. The same company's operating knowledge and succession planning are Firminis's job. Both work over the same organization and the same people.

What is live today

ScanThis, in beta, on iOS. Its scanning and claiming paths also work on the web without an application. No other orbital is released.

Machine interfaces

PurposeAddress
Orbital descriptions, for modelshttps://libranis.com/llms.txt
MCP serverhttps://mcp.libranis.com/mcp
Public read-only HTTP APIhttps://libranis.com/api/v1
OpenAPI descriptionhttps://libranis.com/openapi.json

Each orbital's public site also runs a read-only MCP instance at mcp.<orbital-domain> carrying that orbital's description and pointing back to Libranis. mcp.libranis.com is the one to start from.

Libranis · ScanThis · Primitives · Ari · Security and consent

All Libranis documentation