READ THE IMPLEMENTATION STATUS WITH THE EXPLANATION
A developer-documented function is supported by a current Fenix description, configuration article or V3 release record. That establishes the advertised scope. A supplied Airbus manual can explain the associated mechanism in more detail, but does not prove that every component, failure path or software-standard option has been implemented. These two evidence layers are kept distinct throughout the Pro chapters. [82, V3 avionics and systems release record]
Where an exact interface or failure detail remains unverified, the text identifies the boundary. Unverified means it has not been established by the available evidence or a live test in this work; it does not mean the aircraft definitely lacks that function. A reference-standard example can be studied for its geometry or logic without turning it into an instruction to select an undocumented option in V3. [66, Identified FMS software standard; page-dependent applicability]
Source dates also matter inside V3. A release note identifies a change at a particular build, and a known-issue record identifies an observation at a particular date. Neither is a permanent description of every subsequent installation. Confirm the installed build and current vendor information when investigating a discrepancy. [122, 22 October 2026 hotfix announcement]