What changed. Why. For whom.
A Codex session may draft proposals; a named person approves publication, contract impact and effective date.
The status column in the table is the outcome; this is the gate in front of it
The table below shows a status per change, but not what it takes to get from one state to the next. That is in the publication rule, as one sentence with eight items inside it. Here that sentence stands as a gate, with the states from the table underneath and with the way back that does not exist today.
| Date | Version | Change | Impact | Status |
|---|---|---|---|---|
| 25 August 2026 | RATE.0.4 | price label corrected from the Dutch consumer price including Dutch VAT to the consumer price including tax: a digital service to a private consumer is taxed where that consumer lives, so the amount stays the same in every country and only the tax share inside it moves. Sources Belastingdienst and European Commission, checked 25 August 2026 | price and legal | applied |
| 25 August 2026 | LEG.1.0 | Jarvis consumer terms adopted at version 1.0; the right to cancel survives the first fourteen days even with both boxes ticked, and we do not rely on it having lapsed | legal | applied |
| 11 August 2026 | RATE.0.3 | Brain Start entry plan added at 9 euro per month, the Dutch consumer price including Dutch VAT; Solo, Team and Business unchanged in price and capacity | price | review required |
| 28 July 2026 | J.0.3 | direction 1 chosen; knowledge network from direction 3 added | visual and product | accepted |
| 28 July 2026 | RATE.0.2 | Solo 29 euro, Team 99 euro, Business 249 euro as a validation proposal | price | review required |
| 28 July 2026 | TRUST.0.2 | trust centre and legal registers added | legal | legal review |
| 28 July 2026 | AUTO.0.1 | weekly maintenance session with approval gates designed | operations | draft, not approved |
Publication rule
Every material change records its primary source, owner, review date, proposed text, code impact, customer impact, effective date and communication route. There is no version archive yet from which you can request an older approved version; as long as there is not, we cannot point you back to an earlier version. The data processing agreement says the same. Prices, contracts, retention periods, models, data flows and security boundaries never change quietly on the back of behavioural telemetry.
Where the legal versions live
This register tracks product and pricing decisions. The version history of a legal document sits on the document itself: terms, privacy statement, data processing agreement and sub-processors each have a chapter of their own about changes. Which set of those texts applies when you take out Jarvis is set out at the product terms for Jarvis. Where this register differs from the document, the document applies.