MARSOVIVS

Changelog

The signed record of every release.

Each release of Marsovius is signed by the house, dated, and reversible. The changelog is updated in markdown; one file per version. Subscribe via the RSS feed.

0.2.0

Workspace foundationshipped

Released 18 · V · MMXXVI · signed by The house

The first public-facing release of Marsovius. The platform's surface is rebranded, the module lexicon is in place across navigation, and the workspace abstraction is plumbed end-to-end. Marsovius v0.2 is the first release the house publishes by name. Earlier internal versions, under the working name ONTOS, are not catalogued here.

Added

  • Marsovius rebrand. The product is Marsovius. The chrome, the docs and the public surfaces are updated.
  • Greek and Latin module names applied to every navigation item — Hermes, Aqueduct, Bibliotheca, Codex, Lyceum, Forge, Eidolon, Vigil, Demos, Civitas — each paired with its English subtitle in the chrome.
  • App Rail (52px) — Palantir-style left rail. Modules grouped by layer; workspace switcher at the top, user menu at the bottom.
  • Workspaces (Demos). Backend table, WorkspaceProvider on the frontend, and the /w/{slug}/* URL structure. One installation, many tenants.
  • WorkspacePicker and WorkspaceHome — the picker for choosing a demos, the launcher for the apps inside it.
  • Stubs reserved for the modules whose implementation lands in later releases: Logos, Praxis, Atlas, Tabula, Pythia. The names are committed to the lexicon; the surfaces will follow.

Changed

  • Legacy top-level routes (/home, /clevel, …) redirect into /w/{current}/.... Existing links keep working; new code uses the workspace prefix.

Sovereignty

  • Apache 2.0 source remains the deployment story. No SaaS. No managed cloud. The customer hosts the platform; the house does not host customer data.

Known limitations

  • Logos, Praxis, Atlas, Tabula, Pythia are scaffolded but not yet functional. The roadmap commits each to a named release.
  • Pythia requires ANTHROPIC_API_KEY. Without it, the AIP endpoints return 503; every other module operates fine.
  • Multi-region deployments are not supported. Single-region only through v1.x.
  • Per-workspace physical data isolation — separate ontology folders, separate ClickHouse databases — is on the v0.5 roadmap. Today, the workspace boundary is a URL prefix and a column.

The next release is described in the platform's docs/ROADMAP.md. The changelog records what has shipped; the roadmap records what is next.

The house

V

A release is a contract. Once signed, it does not move. New versions extend the record; they do not rewrite it.