Contract analysis

I. Executive Summary This memorandum analyzes whether Vantage Mobility Systems Corp.'s ("VMS" or the "Company") Technology Errors & Omissions Policy provides coverage for losses arising from or related to the derivative works ownership dispute with Meridian Code Technologies, Inc. ("MeridianCode") under the Master Embedded Software License and Services Agreement dated June 21, 2022 (the "MESLSA"). The dispute centers

II. Background A. The MESLSA and Project Argonaut On June 21, 2022, VMS and MeridianCode entered into the MESLSA, pursuant to which MeridianCode licensed to VMS its proprietary ATLAS-RT™ embedded real-time operating system, Version 4.2 (subsequently updated to Version 4.2.3 through a series of maintenance releases during the first year of the agreement). The MESLSA is a comprehensive enterprise software licensing agr

III. Policy Overview A. Policy Identification and Basic Terms The insurance policy at issue is identified as follows: The policy is a claims-made and reported form, meaning that coverage is triggered when a claim is first made against the insured during the policy period (or any applicable extended reporting period) and the insured reports the claim to the insurer within the time frame specified in the policy. This s

IV. Coverage Analysis A. Trigger of Coverage — Is There a Covered "Claim"? The threshold question for any coverage analysis under a claims-made policy is whether a "Claim" has been made against the insured within the policy period. Current Status of the Dispute. As of the date of this memorandum, MeridianCode has asserted its position through its outside counsel, Redstone Whitaker LLP (Alan M. Briscoe, lead partner,

1. Arguments in Favor of Coverage Several features of the dispute support an argument that it falls within the insuring agreement of the Tech E&O policy: The Policy's IP Dispute Coverage Language. The policy description indicates coverage for "losses arising from third-party IP disputes related to embedded software." The derivative works dispute is precisely such a dispute: it concerns the ownership of three embedded

2. Arguments Against Coverage Commonwealth will likely advance several arguments against coverage, and we must candidly assess their strength: Contractual Origin of the Dispute. The derivative works dispute arises from a negotiated contractual provision — Section 7.2 of the MESLSA — rather than from a tort, wrongful act, or negligent omission by VMS. MeridianCode is not alleging that VMS infringed MeridianCode's copy

V. Notice Obligations and Timing A. Policy Notice Requirements Under the claims-made and reported form of Policy No. TEO-2022-7891, VMS is required to provide prompt written notice to Commonwealth of any claim or potential claim. The precise notice requirements are set forth in the policy's conditions section, which typically requires that the insured provide notice "as soon as practicable" or "promptly" after the in

1. Policy Identification. Policy Number TEO-2022-7891; Named Insured: Vantage Mobility Systems Corp.

2. Description of the Dispute. MeridianCode's assertion of joint ownership and perpetual royalty-free license-back rights to derivative works DW-001, DW-002, and DW-003 (approximately 47,000 lines of code) under Section 7.2 of the Master Embedded Software License and Services Agreement dated June 21, 2022 between VMS and MeridianCode.

3. Nature of the Claim. MeridianCode, through its counsel at Redstone Whitaker LLP (Alan M. Briscoe, lead partner, and Natasha C. Ferraro, senior associate), has communicated its position that the derivative works are jointly owned and that MeridianCode retains a perpetual, royalty-free license to commercialize the works independently. VMS disputes this position and asserts sole ownership of the derivative works.

4. Potential Financial Exposure. The estimated commercial value of the derivative works is $1,800,000 to $2,500,000 (based on the independent assessment by Hargrove Technical Consulting, LLC, Dr. Samuel Beecroft, Ph.D., lead consultant), plus defense costs in a potential binding arbitration before the Midwest Arbitration Institute (three-arbitrator panel for disputes exceeding $1,000,000).

5. VMS's Position. VMS contends that DW-001, DW-002, and DW-003 are VMS-originated works developed independently by VMS engineers and that they do not constitute "modifications, adaptations, or extensions to ATLAS-RT source code" within the meaning of Section 7.2.

6. Current Status. The dispute is in the pre-arbitration, counsel-to-counsel negotiation phase. VMS's outside counsel, Drummond & Fenwick LLP, and MeridianCode's outside counsel, Redstone Whitaker LLP, are engaged in discussions. No arbitration demand has been filed to date. The dispute is subject to binding arbitration under MAI rules if not resolved through negotiation.

7. Reservation of Rights. The notice should expressly reserve all of VMS's rights under the policy, including the right to seek defense costs, indemnification, and any other benefits to which VMS may be entitled. The notice should be sent to Commonwealth Surety & Insurance Co. at the address specified in the policy's notice provisions, by the method required under the policy (typically certified mail, overnight couri

VI. Impact on Pending Negotiations and Resolution Strategy A. Coordination with Ongoing MeridianCode Negotiations The insurance coverage analysis does not exist in a vacuum. VMS is simultaneously engaged in active negotiations with MeridianCode regarding the dormancy extension, fee restructuring, and resolution of the derivative works dispute. Our team has drafted and circulated several documents in connection with t