Version History & Release Notes
Executive Summary
Key Takeaways
- ✓ This page tracks ENGINE_VERSION, the identifier stamped onto every audit's provenance and used throughout this Technical Documentation library — currently 2.1.0.
- ✓ A second version identifier exists in the codebase, tracking product releases, and is not fully synchronized with ENGINE_VERSION as of this writing; this page states that honestly rather than presenting a single, unified version number that does not actually exist.
- ✓ The most substantively documented engine change on record is the R015 rule redesign, a genuine, dated calibration event with a full before-and-after account, published as its own Research Library case study.
- ✓ This is a living document, updated with every future engine change, per this library's own standing practice of re-verifying documentation against source at every revision.
Scope of This Page¶
This page tracks FMAE's engine version using ENGINE_VERSION, the specific identifier defined in the
engine's own version module and stamped onto every audit's provenance record — the same identifier this
entire Technical Documentation library references throughout as "as of engine version X.X.X." As of this
writing, ENGINE_VERSION is 2.1.0.
An Honest Note on a Second Identifier¶
A second version identifier exists elsewhere in the codebase, tracking product releases rather than the
engine specifically, and is not fully synchronized with ENGINE_VERSION as of this writing. Rather than
present a single, unified version number that does not actually exist in the codebase, this page states
the discrepancy plainly and scopes itself explicitly to ENGINE_VERSION — the identifier that is
consistently stamped onto every audit's own provenance record and therefore the one most directly relevant
to a reader asking "what engine version produced this specific audit."
The Most Significant Documented Change: The R015 Redesign¶
The most substantively documented change in the engine's history is the redesign of rule R015 (Explicit Aggregation Review), previously named "Addition Chain Risk." Following empirical review of the rule's own findings against a real institutional model, its minimum trigger threshold was raised, non-contiguous addition chains were excluded from evaluation entirely, its severity was lowered, and its scoring weight was reduced proportionally. This is documented in full, with the specific before-and-after parameters, as its own Research Library case study: RP-005: Evidence-Driven Rule Calibration — The R015 Case Study. It is the clearest example in the engine's history of a rule's calibration being revised in direct response to evidence from its own accumulated findings, rather than left static once deployed.
Other Documented Engine-Layer Changes¶
Beyond the R015 redesign, the engine's internal change history includes a body of report-layer refinements — corrections to report rendering, evidence-table grouping, and narrative language — which sit in the Report Generation layer rather than affecting rule detection logic, scoring, or the dependency graph. This page does not itemize every such report-layer change individually; it exists to track engine-level version identity and the rule and methodology changes (like R015's) most relevant to how an audit's findings and score are produced.
A Living Document¶
This page is maintained as a living document, intended to be updated with every future engine-level change — a new rule, a scoring-basis revision, a further rule recalibration — rather than left to go stale. Consistent with the standing practice across this Technical Documentation library, any future update to this page is re-verified directly against source at the time of the update, not carried forward from a prior version's assumptions.
Related Reading¶
- RP-005: Evidence-Driven Rule Calibration — The R015 Case Study — the full account of the engine's most significant documented calibration event.
- FMAE Audit Engine — Architecture Overview — the pipeline this version identifier is stamped across, via every audit's provenance record.
- Evidence & Provenance — where
ENGINE_VERSIONis recorded on every individual audit.
How OXXON tests thisRun a free structural check with FMAE
Frequently Asked Questions
What version is the FMAE engine currently on?
ENGINE_VERSION, defined in the engine's own version module and stamped onto every audit's provenance record, is currently 2.1.0. This is the identifier this entire Technical Documentation library tracks and references as "as of engine version 2.1.0."
Is there only one version number associated with FMAE?
No, and this page states that honestly rather than presenting a false single number. A second identifier in the codebase tracks product releases rather than the engine specifically, and is not fully synchronized with ENGINE_VERSION as of this writing. This page scopes itself explicitly to ENGINE_VERSION.
What is the most significant documented engine change?
The R015 rule redesign — a genuine, dated calibration event in which a structural rule's threshold, contiguity handling, severity, and weight were all revised together following empirical review of the rule's own findings. It is documented in full as its own Research Library case study.
How often is this page updated?
This is a living document, intended to be updated with every future engine change, consistent with the standing practice this Technical Documentation library follows of re-verifying every page against source rather than letting documentation drift out of sync with the codebase.
Related Articles
FMAE Audit Engine — Architecture Overview
The FMAE audit engine processes a workbook through five stages executed in a fixed order — parsing and workbook ingestion, dependency graph construction, rule engine execution, risk scoring, and report generation. Each stage consumes the previous stage's output and exposes nothing about how any later stage will use it, so the stages can be documented, tested, and read about independently. This page is the map; the detail behind each stage lives on its own Technical Documentation page as those pages are published.
RP-005: Evidence-Driven Rule Calibration — The R015 Case Study
This paper documents a single, real calibration event in the FMAE rule engine's history as a case study in evidence-driven rule design. R015, then named "Addition Chain Risk," originally fired on any formula joining five or more cell references by addition, at high severity. A review of that rule's findings against a real institutional model found the overwhelming majority — both non-contiguous addition chains (representing deliberate, named component selection) and contiguous ones (representing fixed, named business subtotals) — to be legitimate modelling practice rather than structural defects. The rule was redesigned in response — the minimum chain length was raised, non-contiguous references were excluded entirely, severity was lowered, and its weight was reduced proportionally. This paper treats that redesign as a case study in what evidence-driven calibration of a deterministic rule looks like in practice.