BREAKING: Your next Obermind release isn’t 4.9.9 — it’s 2026.10.1

BREAKING — from 25 October 2026. The number on a new Obermind build is no longer 4.9.9. It is an Obermind Platform version: year, month, and which release we cut in that month. The first one is 2026.10.1.

Nothing on a running 4.9.8 deployment is renamed. Strategies and algos do not need a rebuild. What changes is the story the next build tells you — when it shipped, and whether the contract your code binds to actually moved.

Why we changed the numbers

Obermind is a multi-deployment product. Licensees do not all take a release on the same day. Some stay on last month’s build. Others take every cut. We ship one or two releases a week today, and that cadence will rise as we add deployments.

The old 4.x.y numbers were being asked to do two jobs at once:

• Tell operators which build is on a server
• Tell developers whether existing strategies still load

Those jobs pulled in opposite directions. A weekly ship wants the first number to move often. A strategy compiled against the core library wants the second number to stay still. We were rolling 4.8.9 into 4.9.0 because the last digit ran out of room — not because anything broke.

So we split the story.

Two names. Two numbers.

In public we now talk about two things.

Obermind Platform

Obermind Platform is every app you deploy together: Obermind Stream, ObermindDB, Obermind Web, the jobs, the mobile shell, the trading terminal. One Platform version. One deployment.

The Platform version is a calendar number: year.month.release.

• Year — 2026
• Month — 10 for October (no leading zero)
• Release — the 1st, 2nd, 3rd cut in that month, starting at 1

The last digit is not the day. 25 October is still 2026.10.1 if that is the first new-scheme cut in October. A second cut the same month is 2026.10.2. November starts again at 2026.11.1.

We do not use the calendar day (2026.10.25) because two releases on the 25th would collide, and the next one would look like the 26th.

Obermind Framework

Obermind Framework is the core library only — OberMind.dll. Obermind Stream, ObermindDB, Obermind Web, every trading venue adapter, Obermind Quant, and customer strategies and algos all compile against it.

That assembly version stays 4.9.8.0 until we make a change that existing code or existing data cannot read. Then it becomes 5.0.0.0, and we say so in the release notes. Strategies are rebuilt. Every app in the deployment moves together.

A bug fix inside a method, a new instrument type appended at the end of a list, a new field behind a version gate — those change the Framework source, not the Framework identity. They ship in a normal Platform cut.

What you will see on each app

After the first calendar cut, a deployment on 2026.10.1 looks like this:

• Obermind Stream console: ObermindStream Version 2026.10.1.0
• ObermindDB console: 2026.10.1.0
• The same consoles, file version of OberMind.dll: 2026.10.1.0 — that is the Platform build, not a Framework jump
• Obermind Web, Downloads, cache-busting URLs: v2026.10.1
• Obermind Framework assembly version (what algos bind to): still 4.9.8.0

Stream prints the file version of the library so you can see which Platform build produced that file. The frozen 4.9.8.0 is the strong name. Existing strategies keep loading.

You will not see Stream 5.0.0 unless we publish a breaking Framework change. You will not see 4.9.9.

Deployments already on 4.9.8

They stay on 4.9.8. We do not rewrite history.

A mixed fleet is the point of this change:

• Licensee A stays on 4.9.8 until they choose a new build
• Licensee B takes the next cut → 2026.10.1 (even on 25 October)
• Licensee C takes a later October cut → 2026.10.3

Update checks treat 2026.10.1 as newer than 4.9.8. That is correct.

Do not mix apps. Obermind Stream 2026.10.2 and Obermind Web 4.9.8 are not a supported pair. Take a Platform version as a set. You may skip Platform cuts freely while the Framework major is still 4. You may not skip a Framework major without rebuilding strategies.

When “BREAKING” actually means rebuild

The word on this article — and on the 4.9.8 public changelog — is for operators: read this, the published numbers look different.

It is not a Framework break. It is not a rebuild. Running 4.9.8 does not stop.

A Framework break is a different sentence. We use it when:

• a public type, member or signature is removed or changed
• a constant, id or enum value moves
• new code cannot read existing books, instruments or portfolios
• customer strategies have to be rebuilt

Then the Obermind Framework identity moves (4.9.8.0 → 5.0.0.0), the public notes say so, and every app in the deployment is upgraded together.

HTTP API compatibility is a third axis. User API v1 does not become v2 because the Platform number changed.

4.9.8 already said this

Obermind Platform 4.9.8, released 25 October 2026, is the last 4.x number. Its public changelog opens with that BREAKING line so every licensee sees the scheme before they take 2026.10.1.

From that date, a normal bump after a commit increments the Platform version only. A public release still gets operator notes. A Framework change still has to be called compatible or breaking — we do not let a silent edit to OberMind.dll ship without that decision.

Who this is for

• Operators who run more than one Obermind deployment and need to know which build is where
• Quant and algo teams who need the library identity to stay still across weekly Platform cuts
• White-label firms who will take releases more often as we add tenants

If you already run Obermind, you do not have to move today. When you do, you take 2026.10.1 (or later) as a set, and your strategies keep loading on Framework 4.9.8.0.

Get started

Read the 4.9.8 changelog on your deployment, then talk to us about the next Platform cut. If you have custom strategies, confirm they were built against Framework 4.9.8.0 — they will be, if they already run on 4.9.8.