Capabilities
What Selira does, grouped by what you get.
Eight things the platform gives you. All of them come from one model and one engine — there is a single thing to deploy, not eight.
Model your world
Declare the things your operation actually has — parts, aircraft, people, sites, work, materials — and the relationships between them, in configuration rather than code. Your words, not ours: if your operation calls it a rotable, the model calls it a rotable.
Know when it was true
Every statement carries when it held and when you knew it. Ask as of any moment — past or planned — and get the answer in that moment’s terms. Read a decision against what was held when it was taken.
Know where it is
Places nest — a bin in a store at a station, an aircraft on a stand in a hangar — and where a thing sits is a statement like any other, with its time and its source. Ask for everything inside a place, at any level.
Know whose word it is
Claims rather than fields. Each statement keeps who made it and on what authority — a plan, a reading, a signature. Competing claims live side by side, never merged, and an answer says which one it used.
Know which source said it
Each source — a system, a spreadsheet, a document — keeps its own record and its own origin. Where records describe the same real thing they are bound: by key where the systems share one, and with a confidence you supply where they don’t. Each question sets the floor it will accept, and nothing is merged away.
Take it in
Records arrive from the systems you run through an API and import jobs — back-dated where they should be — each keeping its origin and when it was known. A spreadsheet comes in as a spreadsheet, formulas intact. Live connectors are where it is going.
Run the work
Procedures declared once and run exactly as written, resuming where they stopped if anything fails. Rules that refuse a breaking write, and name the rule: in build. Where it is going: agents that prepare the options and record what they read, and as of when — with release and disposition always a named person’s call.
Trace it
Every answer names the claims and records it rests on, the authority each stands under and the moment it was asked as of — back to the system each came from. Quantities carry their units and their kind, so one kind is never compared against another.
A note on breadth
Eight capabilities, one thing to operate
A long list of capabilities usually means a lot of services to run. Not here: these eight are one engine seen from eight sides, not eight components wired together.
There is one model, one query path, one deployment. Time, space, truth and source are not subsystems you buy one at a time — they are held in the same model, which is exactly why a single question can cross them.
It is also why they come together, as one platform. Truth without time could not tell you what you believed when you decided.
Pick the capability you need first.
The rest of the platform comes with it. Bring the question that hurts most.