Version: v1.0 · Effective: 2026-09-24
Fulcrix changes often. This page says what kind of change you will see, how much notice you get, and how to tell which version of the product produced a number you are holding.
Every export the product makes (the board packet, the business-case one-pager, CSV files, the evidence pack, workspace and workflow files) carries two stamps: the application version and the engine version, printed as Fulcrix v2026.9.24 · Fulcrix Engine 2026.09.
- The application version is a date (
2026.9.24is the release of 2026-09-24) and moves with every release. - The engine version (
2026.09) moves only when a release can change a computed number for the same inputs. If two packets carry the same engine version, a difference between them comes from your inputs, not from us.
Exports made before 2026-09-24 carry Fulcrix v1.0.0 and no engine stamp.
Application updates are changes to screens, imports, documents, security and reliability. They cannot move a computed figure. They roll out in the background with no advance notice, and each one is listed in What changed with the date it shipped. The account menu shows a marker when there is a release you have not read.
Engine updates are changes to how figures are computed: the ripple engine, the roll-up, capacity, the revenue cycle, the sample data and calibration defaults. Because they can move a number you have already exported or presented:
- We announce them as far ahead as we can and normally at least 30 days before release. The announcement appears under Upcoming on What changed, as a banner in the application, and by email to every workspace administrator. On release day the same channels say it has shipped.
- Correction carve-out. When an engine update corrects a defect (a figure that was wrong), we release it as soon as it is verified rather than waiting 30 days, and give notice at release naming the affected figures. A wrong number left in place for a notice period helps nobody.
- Every engine entry names the figures that moved on the sample lab and how to compare your own.
- Read the stamp on the packet you hold: the engine version tells you which release computed it.
- Open Settings ▸ Version history and restore or view the last save before the engine release date; every save is kept (the newest 50 per workspace), and a restore writes forward, so nothing is lost.
- Export the same packet again on the current engine and compare the figures the release entry names. If a figure the entry does not name moved, tell us; that is a defect report we want.
Anything you may hold outside the product (an API key prefix, an export or import file format, a CSV column, an address) is retired only with a published sunset date, listed under Deprecated in What changed, and never with less than 90 days' notice. The old form keeps working until that date.
Changes to the Terms of Use follow their own process, not the release tracks: a material change is announced by email at least 30 days before it takes effect, and you confirm the updated Terms once on your next sign-in after that date. Minor edits move the Terms' "Last Updated" date and are listed in the release notes. The current text is always at Terms of Use.
- What changed: every release, newest first, with the Upcoming block for scheduled engine updates.
/changelog.json: the same content as a feed an IT team can poll.- Your workspace administrators receive the engine and Terms notices by email; application updates are never emailed.