Contract analysis

I. Executive Summary This memorandum presents a detailed chronology of the cure notice and termination-for-cause sequence from January 18, 2024, through April 8, 2024, and demonstrates that Northgate Fiber Americas Inc. ("NFA" or the "Owner") strictly complied with the procedural requirements of Section 14.1 of the Master Construction Agreement dated March 15, 2020 (the "MCA") when it terminated Meridian Infrastructu

II. Contractual Framework — MCA § 14.1 and Related Provisions Before turning to the chronology itself, it is necessary to set forth the contractual provisions governing the termination-for-cause process. The MCA is a comprehensive construction agreement for the design and construction of a fiber optic network spanning multiple states along the eastern seaboard of the United States. The MCA was executed on March 15, 2

Section 14.1 of the MCA sets forth the exclusive mechanism by which the Owner may terminate the MCA for cause. In relevant part, it provides that the Owner may terminate the MCA if the Contractor commits a "material breach" of the Agreement that remains uncured for thirty (30) calendar days after the Owner provides the Contractor with written notice specifying the breach. The procedural requirements of Section 14.1 c

Section 14.5 of the MCA establishes the consequences that follow from a valid termination for cause under Section 14.1. These consequences are significant and include the following: (a) Forfeiture of termination fee. The Contractor forfeits any right to a termination fee that would otherwise be payable under MCA § 14.3 (governing termination for convenience). Under Section 14.3, a Contractor that is terminated for co

Section 14.3 of the MCA provides an alternative termination mechanism: termination for convenience. Under this provision, the Owner may terminate the MCA at any time for any reason (or no reason) upon sixty (60) days' prior written notice to the Contractor. If the Owner exercises this right, the Contractor is entitled to (i) payment for all work properly completed and accepted as of the termination date, and (ii) a t

Section 8.2 of the MCA establishes a detailed milestone schedule consisting of fourteen (14) defined milestones, organized across three phases of construction. The milestones serve as intermediate benchmarks for measuring the Contractor's progress, and the MCA requires the issuance of interim completion certificates for each phase. The three phases and their associated milestones are as follows: Phase 1: NY Metro & N

Section 9.1 of the MCA provides for liquidated damages for delay. Specifically, for each day of unexcused delay beyond a milestone's scheduled completion date, the Contractor is required to pay the Owner liquidated damages of $175,000 per day per milestone. These liquidated damages are subject to a cap of 10% of the applicable milestone value per milestone, and an aggregate cap of 5% of the total Contract Price, whic

Section 12.4 of the MCA requires that all work performed by the Contractor conform to the quality standards set forth in Northgate Technical Specification NS-FIBER-2020, as well as applicable industry standards including ANSI/TIA-568 (cabling standards) and BICSI guidelines for telecommunications distribution design. The MCA imposes an affirmative obligation on the Contractor to maintain quality assurance processes a

Section 16.1 of the MCA governs changes to the scope of work or the construction schedule. It requires that any change to the scope or schedule be formalized through a written Change Order signed by both parties. No change is effective or binding unless memorialized in a properly executed Change Order. This provision is relevant to the present analysis because, in its February 2, 2024 response to Cure Notice No. 1, M

III. Background — Pattern of Delays and Quality Deficiencies Pre-Dating Cure Notices The cure notice and termination sequence described in Section IV did not arise in a vacuum. Rather, it was the culmination of a years-long pattern of escalating schedule delays and persistent quality deficiencies that began during Phase 1 of the project and worsened markedly during Phase 2 and into Phase 3. This section sets forth th

IV. Detailed Chronology of Cure Notice and Termination Sequence This section sets forth the detailed chronology of the cure notice and termination sequence, beginning with Cure Notice No. 1 on January 18, 2024, and concluding with Meridian's demand on the Ironclad performance bond on April 15, 2024. Each event is presented with its full context, including the authorship, delivery, content, and legal significance of e

1. Author and Recipient. Cure Notice No. 1 was sent by Renata Voss, Vice President of US Network Infrastructure at Northgate Fiber Americas Inc., to Victor Sandoval, Managing Member and Chief Executive Officer of Meridian Infrastructure Partners LLC. Ms. Voss was the senior NFA executive with direct operational responsibility for the fiber network construction program and was the designated representative for purpose

2. Form and Delivery. Cure Notice No. 1 was issued as a formal written notice, as required by MCA § 14.1. The notice was transmitted via two independent delivery methods: (i) overnight courier service (Severin Partners LLC), addressed to Meridian's registered office, and (ii) electronic mail to Mr. Sandoval and Meridian's general counsel. Severin Partners LLC delivery was confirmed on January 19, 2024, establishing t

3. Content of Cure Notice No. 1. Cure Notice No. 1 identified the following as constituting a material breach of the MCA, thereby triggering the cure process under Section 14.1: (a) Failure to achieve Milestone 8 (Phase 2). The notice identified Meridian's failure to achieve Milestone 8 — the final milestone of Phase 2 — as a material breach of MCA § 8.2 (Milestone Schedule). As of the date of the notice, Milestone 8

4. Significance. Cure Notice No. 1 was the first formal invocation of MCA § 14.1's termination-for-cause mechanism. It is important to distinguish this from the prior liquidated damages assessments. NFA had previously assessed liquidated damages for milestone delays under MCA § 9.1 — beginning with the LD assessment letter of November 5, 2021, for Milestone 3, and continuing with subsequent assessments for Milestones

1. Author and Recipient. Meridian's response was transmitted by letter from Victor Sandoval, Managing Member and Chief Executive Officer of Meridian, to Renata Voss, Vice President of US Network Infrastructure at NFA.

2. Timing. The response was dated February 2, 2024 — fifteen (15) days after the issuance of Cure Notice No. 1 and within the 30-calendar-day cure period. The response was timely in the sense that it was submitted during the cure period; however, timeliness of response is distinct from the question of whether the response constituted an actual cure of the identified breaches. Cross-reference: Supporting document — Me

3. Content of Meridian's Response. Meridian's February 2, 2024 response disputed NFA's characterization of Meridian's performance as constituting material breach. The letter did not acknowledge any breach or undertake to cure any of the identified deficiencies. Instead, Meridian asserted three defenses: (a) Permitting Delays (MCA § 5.3). Meridian claimed that NFA failed to timely obtain municipal permits for certain

4. Analysis of Response. Meridian's February 2, 2024 response was defensive in nature but did not constitute a "cure" of the identified breaches in any sense of the term. A cure requires affirmative corrective action — the actual remediation of the breach — not merely a letter disputing the characterization of the breach. Even assuming arguendo that some of Meridian's defenses had merit (an assumption this memorandum

1. Author and Recipient. Cure Notice No. 2 was sent by Renata Voss, VP of US Network Infrastructure at NFA, to Victor Sandoval, Managing Member and CEO of Meridian.

2. Timing. Cure Notice No. 2 was sent on February 19, 2024 — two days after the expiration of the 30-calendar-day cure period from Cure Notice No. 1 (which expired on February 17, 2024). This timing is significant: as of February 17, 2024, NFA had the contractual right to issue a notice of termination, because the 30-day cure period had expired without cure. NFA chose not to exercise that right immediately. Instead,

3. Form and Delivery. Cure Notice No. 2 was issued as a formal written notice, consistent with Cure Notice No. 1. It was sent via overnight courier (Severin Partners LLC) and electronic mail. Delivery was confirmed. Cross-reference: Supporting document — Cure Notice No. 2 letter, Bates Nos. [to be assigned].

4. Content of Cure Notice No. 2. The content of Cure Notice No. 2 included the following: (a) A statement that Meridian had failed to cure the material breach identified in Cure Notice No. 1 within the 30-calendar-day cure period, which expired on February 17, 2024. (b) A rejection of Meridian's defenses (permitting delays, scope changes, and force majeure) as set forth in Meridian's February 2, 2024 response, charac

5. Significance. By issuing Cure Notice No. 2 with an additional 15-day window for a remediation plan, NFA went substantially beyond the contractual minimum required by MCA § 14.1. NFA could have terminated the MCA on or after February 17, 2024, when the initial 30-day cure period expired. Instead, NFA extended the process by issuing a second cure notice, inviting a remediation plan, and affording additional time for

1. Author and Recipient. The Corrective Action Plan was submitted by Bridget Yeung, Chief Operating Officer of Meridian, to Renata Voss (VP of US Network Infrastructure, NFA) and Sean Calloway (Director of Construction Management, NFA). The fact that the plan was submitted by Meridian's COO, rather than its CEO, is of some significance — it suggests that Meridian recognized the operational nature of the issues and as

2. Timing. The Corrective Action Plan was submitted on March 5, 2024 — one day before the 15-calendar-day deadline set in Cure Notice No. 2 (which ran from February 19, 2024, and expired on March 6, 2024). The plan was therefore timely submitted within the additional window provided by NFA. Cross-reference: Supporting document — Meridian Corrective Action Plan dated March 5, 2024, Bates Nos. [to be assigned].

3. Content of the Corrective Action Plan. Meridian's Corrective Action Plan contained the following principal elements: (a) Proposed accelerated construction schedule. The plan proposed an accelerated construction schedule, stating that Meridian would deploy additional construction crews to increase the pace of Phase 3 construction. The plan did not, however, specify the number of additional crews, their geographic d

4. Analysis. The Corrective Action Plan was materially deficient in several respects. Most fundamentally, it transformed Meridian's cure obligation into a demand for contract renegotiation. Rather than committing to cure the identified breaches within the existing contractual framework — by achieving delinquent milestones, accelerating Phase 3 construction, and remediating quality deficiencies — the plan conditioned

1. Author and Recipient. NFA's rejection of the Corrective Action Plan was communicated by letter from Renata Voss (VP of US Network Infrastructure, NFA) to Victor Sandoval (Managing Member and CEO, Meridian) and Bridget Yeung (COO, Meridian). Cross-reference: Supporting document — NFA Rejection Letter dated March 12, 2024, Bates Nos. [to be assigned].

2. Content. The rejection letter contained the following key points: (a) NFA rejected the Corrective Action Plan as inadequate and non-responsive to the breaches identified in Cure Notices No. 1 and No. 2. (b) NFA cited 12 additional critical NCRs that had been issued during February 2024 — that is, during the cure period and after the issuance of Cure Notice No. 2. These 12 new critical NCRs demonstrated that Meridi

3. Significance. This letter is important to the litigation record for two reasons. First, it establishes that NFA gave full and fair consideration to Meridian's proposed cure before concluding that it was inadequate. NFA did not summarily reject the Corrective Action Plan; the rejection came seven days after its receipt and was accompanied by a detailed explanation of the plan's deficiencies. Second, the citation of

1. Author and Recipient. The Notice of Termination for Cause was issued by Renata Voss on behalf of Northgate Fiber Americas Inc. to Victor Sandoval on behalf of Meridian Infrastructure Partners LLC.

2. Timing. The following timeline illustrates the deliberate pace at which NFA proceeded: • 73 calendar days after Cure Notice No. 1 (January 18, 2024 → April 1, 2024). • 41 calendar days after Cure Notice No. 2 (February 19, 2024 → April 1, 2024). • 27 calendar days after Meridian's Corrective Action Plan submission (March 5, 2024 → April 1, 2024). • 20 calendar days after NFA's rejection of the Corrective Action Pl

3. Form and Delivery. The Notice of Termination was issued as a formal written notice. To ensure conclusive proof of delivery, NFA transmitted the notice through three independent delivery methods: (i) overnight courier service (Severin Partners LLC); (ii) electronic mail; and (iii) certified mail, return receipt requested. Delivery was confirmed through all three channels. Cross-reference: Supporting document — Noti

4. Content. The Notice of Termination was a comprehensive document that recited the full factual and contractual basis for the termination. Its key provisions included: (a) Termination for cause under MCA § 14.1, effective immediately. The notice stated that the MCA was terminated for cause under Section 14.1, effective as of the date of the notice (April 1, 2024). (b) Recitation of grounds for termination. The notic

5. Significance. The termination notice was comprehensive and well-documented. It cross-referenced both cure notices and the rejected Corrective Action Plan, creating a clear documentary chain linking the cure notice process to the termination decision. The notice left no ambiguity about the grounds for termination or the contractual provisions on which it was based. Most significantly, NFA afforded Meridian 73 days

1. Author and Recipient. Meridian's contestation was communicated by letter from Victor Sandoval (Managing Member and CEO, Meridian) to Renata Voss (VP of US Network Infrastructure, NFA).

2. Timing. The letter was dated April 8, 2024 — seven (7) days after the Notice of Termination. This was the last pre-litigation correspondence between the parties on the termination issue. Cross-reference: Supporting document — Meridian Contestation Letter dated April 8, 2024, Bates Nos. [to be assigned].

3. Content. Meridian's April 8, 2024 letter contested the validity of the termination for cause and included the following: (a) Repetition of prior defenses. The letter repeated the three defenses previously asserted in Meridian's February 2, 2024 response — permitting delays, unformalized scope changes, and force majeure — without providing additional factual support or documentary evidence for any of them. (b) New

4. Significance. This letter is significant for several reasons. First, it marks the first articulation of the pretext theory that has become central to Meridian's case. The timing of the allegation — raised for the first time after the termination had already occurred — is relevant to evaluating its credibility; the pretext theory was not mentioned in Meridian's February 2, 2024 response to Cure Notice No. 1 or in t

V. Summary of Compliance with MCA § 14.1 Procedural Requirements This section provides a consolidated summary of NFA's compliance with each of the procedural requirements of MCA § 14.1 for termination for cause. A. Written Notice Requirement — Satisfied MCA § 14.1 requires the Owner to provide the Contractor with written notice specifying the breach. NFA provided not one but two written cure notices: • Cure Notice No

VI. Anticipated Meridian Counter-Arguments and Responses Based on the pleadings, Meridian's discovery responses, and deposition testimony to date, we anticipate that Meridian will raise the following counter-arguments in opposition to summary judgment and at trial. Each is addressed below. A. "Cure Period Was Insufficient" Meridian may argue that the 30-day cure period specified in MCA § 14.1 was insufficient to cure