The platform
Five layers. One contract.
Marsovius is a stack of five layers — pipelines, ontology, workflows, agents, surfaces — that share one semantic contract and operate as a single system of truth. From a single online shop to a sovereign government, the architecture does not change.
Architecture
The five layers
- — V —
Surfaces
The operator-facing applications. Workspaces, case files, operational HUDs, storefront surfaces. Built on the ontology so that every interaction is bound to a contract.
- — IV —
Agents
Assisted and autonomous decision agents. They cannot operate outside the ontology — every action is typed, traced, and revocable.
- — III —
Workflows
Long-running, versioned business processes. Each step transition is signed. Each branch is replayable. Each rule is reviewable in court.
- — II —
Ontology
The semantic core. Objects, relationships, allowed actions. The shared contract that a thousand workers — or a single shopkeeper — agree to when they say "patient", "order", "asset".
- — I —
Pipelines
Source-of-truth ingestion and transformation. Lineage from the raw source to the leaf field. Every transformation auditable, every dataset attributable.
The four capabilities
Ontology
The contract of meaning.
A versioned, typed semantic model of every object the institution cares about — subject, order, asset, branch, outcome — and the actions allowed on them. Every dashboard, every workflow, every agent acts through this contract.
- · versioned types
- · typed actions
- · lineage-aware
- · reviewable as code
Digital twin
A live shadow of the operation.
Marsovius keeps a continuous digital replica of the physical world: a warehouse, a fleet, a hospital floor, a population. The twin is queried like data, simulated like a model, and synchronised in both directions in real time.
- · bidirectional sync
- · scenario simulation
- · what-if branches
- · event-time replay
Predictions
Forecasts bound by the ontology.
Demand, risk, capacity, throughput, mortality, congestion. Forecasts are first-class objects in the ontology — their inputs are traceable, their confidence is published, and the action they trigger is signed.
- · traceable inputs
- · published confidence
- · human-in-the-loop
- · signed actions
Agents
Bounded by the ontology.
Assisted and autonomous agents that cannot operate outside the ontology. Every tool call is typed. Every action is signed. Every capability is scoped by policy and revocable by the institution at any moment.
- · typed tools
- · capability scopes
- · signed actions
- · revocable in one call
The modules
The platform is composed of small, focused apps — named for the Greek and Roman concepts they enact. The names are signposts, not stories.
Status reflects what ships in the current release (v0.4, 2026-05-20).live = shipped and in production for at least one workspace. partial = shipped, narrow capability set. stub = scaffolded, route reserved, implementation on the roadmap.
| Layer | Module | Purpose | Status |
|---|---|---|---|
| Connect | Hermes | Connectors — ingest from any source | live |
| Transform | Aqueduct | Pipelines — SQL · Python · dbt · webhook steps | live |
| Transform | Bibliotheca | Catalog — datasets, lineage, search | live |
| Model | Codex | Ontology — types, links, actions | live |
| Model | Lyceum | Object Explorer — walk the objects | live |
| Logic | Logos | Function Studio — typed computed properties | live |
| Logic | Praxis | Workflows — triggers, actions, branches | live |
| Build | Forge | Workshop — dashboards and app builder | live |
| Build | Atlas | Map — geospatial visualization | live |
| Build | Tabula | Pinboards — published, read-only views | live |
| Operate | Eidolon | Digital Twin — scenarios, snapshots, what-if | live |
| Operate | Vigil | Notifications — alerts on conditions | live |
| Intelligence | Pythia | AI Assistant — grounded on the ontology | stub |
| Admin | Demos | Workspaces — tenants and isolation | partial |
| Admin | Civitas | Users — roles and access | live |
Etymology and the full lexicon live in the platform repository under docs/MODULES.md.
Technical stack
A modern, well-understood stack. No proprietary runtime, no hidden telemetry, no licensed wrapper around an open-source core.
— VI —
The code is open. The architecture is built. The house is open to those who know how to request audience.