What Changed

Current release: 2026.9.24 · Released: 2026-09-24

What changed in Fulcrix, release by release. Versions are dates: 2026.9.24 is the release cut on 2026-09-24; a second release on the same day carries a -2 suffix. Every export the product produces (Leadership Summary, board packet, evidence pack) carries the version that produced it, so a figure taken to a committee can be traced to the release it came from.

Every entry is tagged Application (screens, imports, documents, security, reliability — rolls out in the background) or Engine (can move a figure you have exported — normally announced under Upcoming 30 days before it ships, with the figures that move named; a correction to a wrong number ships as soon as it is verified, with notice at release). The full policy, including how to compare a packet across engine versions, is in How Fulcrix is updated. Anything being retired is listed under Deprecated with the date it stops working, never with less than 90 days' notice. IT teams can subscribe to the same feed at /changelog.json.

_No engine update is scheduled. When one is, it is listed here from the day notice is sent, at least 30 days before it ships, with the figures it will move._

• Application · A public "What changed" page at /support/changelog, a machine-readable /changelog.json,

an in-app "What's new" marker, and two version stamps on every export: the app version (2026.9.24) and the engine version (Fulcrix Engine 2026.09). Exports before this release carry 1.0.0 and no engine stamp.

• Application · "How Fulcrix is updated" at /support/updates: the two tracks, the 30-day norm for engine

updates and its correction carve-out, and how to compare a packet across engine versions.

• Application · Deprecation register. Anything a customer may hold (API key prefixes, import and export

formats, old addresses) is now retired only through a published sunset date. The first entries are the pre-rename bfk_ API key prefix and the benchforge.workflow import tag, both accepted until 2027-03-31.

• Application · Restore runbook and stated recovery objectives. What Fulcrix can recover, from which copy,

and how quickly, is written down and matches the security documents.

• Application · Terms of Use v1.7: an "Updates to the Service" clause states the two tracks, the 30-day

norm for engine updates and the correction carve-out, and where release notes live. Every user confirms the Terms once on next sign-in.

• Engine · The sample lab's data was corrected across this release and the previous one: the bring-up cost

is counted once; NGS runs are priced per million reads with run kits at contract price; the sequencer fleet is sized honestly. Your own lab's numbers are unaffected by the sample; they come from your inputs.

• Engine · The revenue-cycle view and every "what if this one thing changes" surface now agree with the

whole-lab re-solve on the binding constraint, the multi-year seam, the rate file and shared-pool insourcing.

• Engine · NGS realism: no NGS controls on qPCR assays, honest blood-draw funnels, tumour/normal pairs on

the same kit, deep 60× sequencing at a confirm share.

• Application · One tab pattern across the product, one icon set, one period suffix (/mo, /yr), a

board packet that prints with page breaks, and a builder that fits a phone.

• Application · The AI compute meter shows the same figure everywhere it appears.
• Application · The reel and the product walkthrough video were re-cut on the corrected sample numbers.

• Application · The AI kill-switch is now enforced in the database as admin-only, and the SOP attachment

bucket enforces its 10 MB and file-type limits at the storage layer (applied to production 2026-09-24).

Engineering: #952 #953 #955 #957 #958 #959 #960 #961, plus the release-standard, deploy-gate and runbook pull request (#968).

• Application · The product is now Fulcrix. BenchForge was renamed across the app, the documents, the mark

and the address (fulcrix.helixwrks.com; the old address redirects, so saved links keep working). Existing API keys and exported files keep working (see Deprecated).

• Engine · The sample lab's 2027 rate scenario now uses CMS's real preliminary CY2027 fee-schedule file

instead of a uniform 15% cut, so its rate-file triage moved. Your own rate file is unaffected.

• Engine · Cash flows are scheduled by year, the board's capital case and the decision register agree on

one A/R timing, and Monte-Carlo copy says what it measures.

• Engine · Per-payer collection lag is charged in the discounted cash flow.
• Engine · The multi-year Horizon switches to cost mode for cost-centre labs.
• Application · Terms of Use v1.6 and the security documents carry the new name; the security documents

now describe the anonymous-role posture exactly as enforced.

• Application · The director-facing Interpretation control (variant curation and sign-out) is in the

builder; the multi-year Horizon lives in the Decisions tab.

• Application · The splash and pricing pages read as early access, matching the door.
• Application · Text takes a text colour throughout (WCAG AA contrast is now a test); the locked builder

palette reads as locked rather than faded.

• Application · The HelixWrks master brand guide v2.0 is applied to the app shell.
• Application · Automatic fetching of the CMS fee-schedule file is paused pending a legal review of the

file's licence terms; uploading a rate file yourself is unchanged.

• Application · Imports: a year column, a quarter column or an annual figure no longer imports as one

month; the workflow CSV survives Excel; per-sample hours, minutes, truncated rows and EU decimals import correctly.

• Engine · Insourcing no longer credits captured reimbursement on top of the send-out fee saving.
• Engine · The P&L card and its three twins apply the per-resource derate.
• Engine · A capital swap applied to some of the assays sharing an instrument no longer keeps the old

instrument on the books; one shared instrument's capital is charged once across the assays it serves.

• Engine · The sample trio exome no longer ships an eight-day P90 from a stale wait.
• Engine · A lab that declares fee-for-service is treated as one; a roster the director typed is theirs.
• Engine · A decision is no longer graded against its own bring-up period.
• Application · The 2027-rates door reads as current (the file is out); the demo banner no longer pushes

the page down; the executive-summary label fits.

• Application · Conflict reload keeps your edit and names the field that was replaced; the derate is

labelled where it is applied; the board has one bottom line.

• Application · One title per route, share cards on every page, the share door, and a password floor of

8 characters.

• Application · Every table privilege was taken away from the anonymous role and only the one the product

uses was re-granted (applied to production 2026-09-23).

• Application · The LIMS connector credential can no longer leak through an error path; compute-block

grants can no longer over-revoke.

• Application · API keys with the bfk_ prefix and workflow files tagged benchforge.workflow keep

working until 2027-03-31. New keys are fxk_; new exports are tagged fulcrix.workflow.

Engineering: #895 #896 #897 #898 #899 #900 #901 #902 #903 #904 #905 #906 #907 #908 #909 #910 #911 #912 #913 #914 #915 #916 #917 #918 #919 #920 #921 #922 #923 #924 #925 #926 #927 #928 #929 #930 #931 #932 #934 #935 #936 #937 #938 #939 #940 #941 #942 #943 #944 #945 #946 #947 #948 #949 #950 #951 #954

• Engine · Money-to-lab solve: enter a budget and the model finds the lab that fits it, with the

constraint-migration ladder wired to it.

• Engine · Lab-wide bottleneck cascade: one change ripples across the whole lab, not just its own assay.
• Engine · A full per-item consumables catalog; consumable prices ripple through every assay that uses

them.

• Engine · Device fleet live-link: a shared instrument's specification ripples to every workflow that

shares it.

• Engine · Collection lag (days sales outstanding) is folded into the discounted cash flow.
• Engine · Interpretation (variant curation and sign-out) as a cost and throughput driver.
• Engine · A multi-year trajectory engine (snapshot per year) behind the Horizon view.

• Application · Access is by application (early access). The open self-serve door from 2026-09-18 is

closed while the product is renamed; approved labs are invited.

• Application · The CMS fee-schedule watchdog can read CMS's own ZIP/CSV files.

• Engine · Shared device-fleet capital is counted once per fleet.
• Engine · The payer blend cannot leak a NaN or overstate below a 1.0 factor.

• Application · A LIMS credential could surface in an error message; it no longer can. Compute-block

revocation is scoped correctly.

Engineering: #879 #880 #881 #882 #883 #884 #885 #886 #887 #888 #889 #890 #891 #892 #894

• Application · Terms of Use v1.5: the modeling engine is a trade secret; scraping or deriving it is

prohibited.

• Application · Trade-secret hardening of the shipped code (licence, headers, browser source maps never

shipped).

Engineering: #877 #878

• Application · The product's public story leads with the cost-centre problem a molecular lab actually

has; the earlier "gaps between your systems" framing is retired.

Engineering: #876

• Application · Founding Labs programme and the request path for it.
• Application · Board: a per-assay cost chart on the fully-loaded basis, matching the all-in band.
• Application · Dual-modality (IVD and genomics) launch gates.

• Application · Fulcrix opened to self-serve paid access with a free trial (reversed on 2026-09-22; see

that release).

• Application · Billing copy and positioning tightened; the multi-site tier was withdrawn from public

pages.

• Application · Clearer failure messages on the payment path.

• Application · A free-tier compute cap and a database-level gate on raising the AI budget before billing

is live.

Engineering: #869 #870 #871 #872 #873 #874 #875