## Memorandum for BrightForge ### 1. Subject-Matter Jurisdiction, Fraudulent Joinder, and Removal BrightForge is a citizen of State A. Leo Martin is also a citizen of State A. If Leo is a real defendant, complete diversity does not exist, and the federal court lacks subject-matter jurisdiction. Nimbus Ledger LLC is a citizen of the states of its members, State C and State D, not merely its organization state. Orbit is a citizen of State C. Thus BrightForge is diverse from Nimbus and Orbit, but not from Leo. The defendants therefore had to show that Leo was fraudulently joined. That is a difficult standard: Leo is fraudulently joined only if there is no reasonable basis under State A law for a claim against him. Disputed facts must be resolved in BrightForge’s favor. BrightForge has a reasonable fraud claim against Leo. - Leo’s statement was factual, not puffery: Nimbus allegedly “operates active-active infrastructure in two independent regions,” so that production remains online even if an entire region fails. - The internal message says Leo knew, two days before signing, that region two was still dark and that activation was at least three months away. - The slide deck made a similar factual representation. - Leo allegedly concealed the dark region rather than merely describing future plans. - BrightForge plausibly relied on that representation in choosing the service. - The 32-hour outage and inability to fail over caused damages. The later merger clause and no-reliance clause do not automatically eliminate this claim. The stated governing law says such clauses are relevant but not conclusive when the defendant allegedly concealed a present fact peculiarly within its knowledge. That is exactly what the internal message suggests. The $8 million allegation is also enough for the amount-in-controversy requirement. Even if the contract cap is $240,000, the fraud claim is not obviously capped, and the face of the complaint seeks well over $75,000. **Likely outcome:** Leo is not fraudulently joined. Therefore complete diversity is destroyed, and the federal court must remand the case to State A under 28 U.S.C. § 1447(c). --- ### 2. Viability of Claims Against Leo BrightForge did not sue Leo for breach of contract, and Leo is not a party to the agreement. The viable claims against him are fraud and possibly the State A consumer-protection claim. Leo can be personally liable for fraud even if he acted as Nimbus’s agent or employee. A corporate agent is liable for his own torts, especially affirmative fraudulent misrepresentations. The facts support each fraud element: a false present statement, knowledge or reckless disregard, intent to induce reliance, reasonable reliance, and damages. The consumer-protection claim against Leo is also colorable if the statute allows individual liability and if the misleading “active-active” slide was used as a standardized presentation with at least twenty prospective customers. That is enough to allege public impact under the governing law, unlike a one-off private negotiation. --- ### 3. Personal Jurisdiction over Orbit Orbit is not subject to jurisdiction merely because it owns Nimbus. A parent-subsidiary relationship alone is insufficient. But BrightForge has alleged direct, purposeful contacts with State A: - Orbit engineers participated in sales calls with BrightForge. - Orbit approved the architecture that was described to BrightForge. - Orbit remotely managed the infrastructure serving BrightForge’s State A factory. - Orbit installed the network patch that caused the outage. The negligence claim against Orbit arises directly out of those contacts. It is reasonable to require Orbit to defend in State A for conduct purposefully directed into that state. So the personal-jurisdiction motion should fail if the negligence claim survives. Separately, even if the negligence claim is later dismissed under the economic-loss rule, Orbit may still be subject to jurisdiction for any surviving consumer-protection or fraud-related claim if BrightForge alleges Orbit participated in the misleading sales conduct. --- ### 4. The Arbitration Amendment The original agreement did not contain an arbitration clause. Nimbus later emailed updated terms adding arbitration. BrightForge did not click an acceptance button and merely continued using the service. Under the stated law, an emailed amendment does not create an arbitration agreement merely because the recipient continued using the service. The original agreement allowed Nimbus to update “operational policies” by posting notice. A mandatory arbitration clause is not an operational policy. It is a material change to dispute resolution. The original agreement did not clearly authorize unilateral amendments to dispute-resolution provisions. Even if Nimbus provided notice by email, BrightForge was not given a meaningful opportunity to reject the new term. Continued use is not assent under these facts. **Conclusion:** The motion to compel arbitration should be denied. --- ### 5. Forum-Selection Clause The original agreement contains a mandatory forum clause: > “All disputes arising out of or relating to this agreement shall be brought exclusively in the state or federal courts located in State C.” The fraud alleged here is fraud about Nimbus’s architecture, not fraud directed specifically at the forum-selection clause. Under the stated governing law, general fraud in the inducement does not invalidate a forum-selection clause. There is no showing that State C would deny BrightForge a meaningful day in court, and no strong public policy exception is apparent from the facts. The clause is therefore likely enforceable between BrightForge and Nimbus. The clause also likely applies to Leo and Orbit. - Leo was Nimbus’s salesperson, personally negotiated the transaction, and is sued for statements about the subject matter of the agreement. It was foreseeable that he would be covered. - Orbit is Nimbus’s parent and infrastructure provider. It participated in sales calls, approved the architecture, and managed the infrastructure at issue. The claims against it relate directly to the agreement’s subject matter. Application of the clause to Orbit was foreseeable. Thus, if the case remains in federal court, the court will likely transfer it to State C under the forum-selection clause. But if, as likely, the case is remanded for lack of complete diversity, the federal court should not decide the forum-selection motion. The State A court will address it on remand. BrightForge should not assume that remand solves the forum problem; the clause may still be enforced by the state court. --- ### 6. Likely Order of Decision in Federal Court The federal court should address the issues in this order: 1. **Subject-matter jurisdiction first.** If Leo is not fraudulently joined, the court lacks complete diversity and must remand. It should not decide arbitration or transfer. 2. **Arbitration next, if it retains jurisdiction.** Arbitration is a gateway issue. If a valid arbitration agreement existed, the court would stay or dismiss the case and not decide the forum-transfer motion. Here, because the arbitration amendment is invalid, the court would deny the arbitration motion. 3. **Forum-selection clause and transfer.** If arbitration is denied and jurisdiction exists, the court should enforce the mandatory forum clause and transfer to State C under 28 U.S.C. § 1404(a). It generally need not first decide Orbit’s personal jurisdiction in State A because the selected forum is State C and the clause applies. Because the likely outcome is remand, the federal court likely never reaches the arbitration or transfer motions. --- ### 7. Contract Claims and Contractual Limitations BrightForge’s breach-of-contract claim against Nimbus is straightforward: the 32-hour outage fell below the 99.9% availability target. However, the contract limits that claim sharply: - Service credits are the exclusive remedy for availability failures. - Liability is capped at six months of fees, or $240,000. - Consequential damages and lost production are excluded. - The agreement is integrated. - BrightForge disclaimed reliance on statements outside the agreement. Because the merger clause means the “active-active” sales statements were not contractual terms, BrightForge cannot recover for breach based on a promise of active-active infrastructure. The contract claim is therefore essentially an SLA claim. The exclusive-remedy clause likely bars cash damages for the outage itself, leaving BrightForge only the service credits described in the SLA. The $240,000 cap is a maximum, not an automatic award. Lost production and emergency expenses likely are excluded as consequential damages, although emergency expenses might be argued as direct mitigation costs. That argument is weak because the contract expressly makes service credits exclusive for availability failures. --- ### 8. Fraud, Merger Clause, and No-Reliance Clause The fraud claim is BrightForge’s best path around the contract limitations. The merger and no-reliance clauses do not automatically bar the fraud claim. Under the stated law, they are relevant to reliance but not conclusive when the defendant concealed a present fact peculiarly within its knowledge. Leo’s internal message — “Do not volunteer that region two is still dark” — supports concealment. Fraud can also avoid contractual limitations, depending on how BrightForge proceeds: - If BrightForge rescinds the contract, it can avoid the contract’s remedy limitations. - If BrightForge affirms the contract and sues in tort for fraud, the limitation-of-liability clauses are not necessarily binding. Courts are generally reluctant to allow a party to immunize itself from liability for intentional fraud unless the clause clearly covers that conduct. - The forum-selection clause is different. Fraud directed at the contract generally does not invalidate it; only fraud directed at the clause itself does. The no-reliance clause should not be ignored. It will be powerful evidence against reasonable reliance. But the alleged concealment of the dark region creates a factual dispute for the jury. --- ### 9. Negligence and the Economic-Loss Rule BrightForge’s negligence claim against Orbit is likely barred by the economic-loss rule. BrightForge seeks only economic losses: lost production and emergency expenses. There is no personal injury or property damage. Orbit is not in privity with BrightForge. The duty BrightForge alleges arises from Orbit’s role in providing the infrastructure and installing the patch — essentially the subject matter of the service contract. Under the stated governing law, a negligence claim seeking only contractual economic losses is barred unless the defendant violated an independent legal duty. The facts do not yet identify such an independent duty. Mere participation in sales calls, approval of architecture, and remote management are contacts, but they do not automatically create a tort duty of care for purely economic loss. BrightForge should consider pleading negligent misrepresentation against Orbit if the facts support it. Orbit’s engineers participated in sales calls and “approved” the architecture described to BrightForge. If BrightForge justifiably relied on Orbit’s information, negligent misrepresentation may be an independent-duty exception. But the claim as currently pleaded — ordinary negligence — is likely dismissible. --- ### 10. Consumer-Protection Claim The State A consumer-protection claim is more promising than the negligence claim. A private negotiation between sophisticated businesses is ordinarily not enough to show public impact. But here Nimbus used the same “active-active” slide with at least twenty prospective customers. That is a standardized course of deception directed at multiple customers, which satisfies the public-impact requirement under the stated rule. Against Leo, the claim is colorable because he personally used the sales presentation and allegedly concealed the dark region. Against Orbit, the claim is weaker unless BrightForge can show Orbit communicated or endorsed the misleading slide. Orbit’s mere parent-company role or infrastructure supply would not be enough. --- ### 11. BrightForge’s Likely Recoverable Damages If BrightForge recovers only on the contract claim, its recovery will be limited to service credits, not the full $8 million. The $240,000 cap is the outer limit, but the “exclusive remedy” language likely makes the SLA credit formula the actual ceiling. Lost production is excluded. If BrightForge proves fraud, the result could be different: - Fraud damages may include out-of-pocket losses, benefit-of-the-bargain losses, and consequential damages caused by the fraud. - The $8 million in lost production and emergency expenses could be recoverable if BrightForge proves they were proximately caused by the false active-active representation and are not speculative. - The “sole remedy” and cap clauses may not apply to intentional fraud. - Leo can be held personally liable for the same fraud damages. The $8 million figure is not guaranteed. BrightForge must prove the losses with reasonable certainty, particularly lost production. Juries and courts often scrutinize lost-profit calculations. Still, fraud is the only claim that can realistically reach the $8 million amount. --- ### 12. Procedural and Strategic Consequences **Remand to State A** This is BrightForge’s best result. Leo remains a defendant, complete diversity is destroyed, and the federal court cannot decide arbitration or transfer. The case proceeds in BrightForge’s chosen state forum. But remand does not eliminate the forum-selection clause. Nimbus, Leo, and possibly Orbit can still ask the State A court to dismiss or transfer the case to State C. BrightForge must be ready to fight that motion if it wants to stay in State A. **Arbitration** If the arbitration amendment were enforced, BrightForge would lose the court forum and likely face a more limited arbitration process. The amendment is invalid, so BrightForge should strongly oppose arbitration. **Transfer to State C** If the federal court retains jurisdiction and enforces the forum clause, the case will be transferred to State C. That favors the defendants. State C is Orbit’s home state, and Nimbus has contacts there. BrightForge would lose the home-forum advantage. **Remaining in Federal Court in State A** That happens only if the forum clause is not enforced or if the court finds Leo fraudulently joined and denies transfer. That is unlikely because the forum clause is broad and valid. Still, if it happens, BrightForge can litigate the fraud and consumer claims in federal court in State A, though Leo would be dismissed as fraudulently joined. --- ### 13. Strongest Course for BrightForge After Removal BrightForge’s strongest course is to: 1. **Move immediately to remand** under 28 U.S.C. § 1447(c). 2. **Make Leo the centerpiece.** Argue that the fraud claim against him is colorable because of the internal “do not volunteer” message, the darkness of region two, and the 32-hour outage caused by the absence of failover. 3. **Do not voluntarily dismiss Leo.** Dismissing Leo would create complete diversity and allow the case to remain in federal court. 4. **Oppose arbitration in the alternative.** Show that the emailed amendment was not accepted and was not authorized by the original agreement. 5. **If remand is denied, oppose transfer only on narrow grounds:** argue the forum clause does not reach Leo’s personal fraud, Orbit’s non-contractual conduct, or the consumer-protection claim if the facts allow. Also preserve the point that the federal court lacks jurisdiction and should not transfer. 6. **Seek leave to amend the negligence claim against Orbit** to add negligent misrepresentation, if the facts support it, before the economic-loss rule is used to dismiss it. The bottom line is that the case should be remanded because Leo is not fraudulently joined. BrightForge should therefore lead with the fraudulent-joinder argument, oppose arbitration, and prepare for a separate fight over the forum-selection clause in State A.