In a corporate joint venture, two corporations—often competitors—collaborate on a project. But how can corporations be partners and competitors at the same time? Though it sounds like a contradiction, such collaborations are commonplace. Many of the most familiar products come from corporate joint ventures, from high-technology like solid-state drives for laptops or rocket boosters for NASA’s Discovery program, to everyday items like Star Wars action figures and even Shredded Wheat cereal. Indeed, Meinhard v. Salmon, arguably the most celebrated case in all of business law, arose out of a dispute within a joint venture. Yet unlike more familiar business forms such as corporations or LLCs, neither case law nor statute provides a clear statement of what a joint venture is or even which laws apply. Given this confusion, it is not surprising that the literature has not produced a unified theory of the corporate joint venture: a coherent statement of both what it is as a matter of law and how it functions.

This Article offers a theory of the corporate joint venture. It traces the development of joint venture law and practice from its origins in 19th-century American case law to the present. The central claim is that at the heart of joint venture law and practice, there is a singular legal problem: the foundational fiduciary duty that applies to all business forms—the duty of loyalty—is inherently contradictory within the context of a joint venture. The contradiction arises because the law has effectively treated joint ventures as partnerships whose members happen to be corporations. This formulation is contradictory because partnership law requires each corporation to be loyal to the other, while corporate law requires each agent to be loyal only to her own corporation. Thus, joint venture law both requires and prohibits a division of loyalty.

The Article first shows how this inherent conflict was a latent motivation behind the path of early case law, as well as how case law subsequently obfuscated the conflict and left a legacy of confusion. It then uses economic theories of business organization and contract law to explain how the joint venture forms we observe today resolve this conflict through a hybrid corporate-contract form. Finally, it demonstrates empirically how the modern contractual solution has engendered a new set of fiduciary problems via networks of joint venture connections across corporations in an industry. The Article concludes by offering policy prescriptions to tackle these problems and clarify the law of joint ventures.

Introduction

A little loyalty is a dangerous thing.[2] In many spheres of life—love, war, family, friendship—divided or conditional loyalty is no loyalty at all. The same applies to the law. Law requires loyalty whenever it finds a relationship exhibiting two elements: agency and trust. Both are essential. Agency is the legal authority of one person (the agent) to make decisions on behalf of another (the principal).[3] Trust is the principal’s belief that the agent will act in her interest, even when the agent’s behavior cannot be observed or verified in court. More agency requires more trust, while greater trust supports greater agency. When these two elements extend together, the law recognizes the relationship as fiduciary.

Fiduciary law takes as its point of departure the idea that the agent’s loyalty is undivided. An agent must act in the best interest of the principal. Departures from this ideal inspire vast literatures that study “agency costs,” the catchall to describe any deviation from a first-best, efficient outcome that arises from this principal-agent relation.

Agency costs abound in both corporations and partnerships. We find them in corporations because shareholders’ and managers’ incentives are misaligned. We find them in partnerships because partners exercise mutual agency vis-a-vis each other and often disagree over what constitutes the partnership’s “best interest.” The law thus demands loyalty from agents of both. Corporate agents owe a duty of loyalty to the corporation; partners owe a duty of loyalty to each other.[4]

What about the case in which two corporations form a partnership? This is the case of joint venture. Corporations might form a joint venture because they desire something more collaborative than arms-length contracting but less permanent than merger. Though joint ventures can arise among both natural and legal persons, my focus here is on joint ventures between corporations.

Corporate joint ventures stack the agency costs of corporation and partnership on top of each other. The result is a seemingly contradictory relation: how can corporations be partners and competitors at the same time? At first blush, they cannot. “Competing with your partner” is anathema to partnership law. The partnership duty of loyalty requires each partner “to refrain from competing with the partnership in the conduct of the partnership business.”[5] This applies with full force to joint ventures. In the enduring words of Judge Cardozo, the standard of behavior among co-venturers is “[n]ot honesty alone, but the punctilio of an honor the most sensitive.”[6] Between co-venturers, “the rule of undivided loyalty is relentless and supreme.”[7]

Yet undivided loyalty is hardly “relentless and supreme” in modern joint ventures. We regularly observe joint ventures in which corporate co-venturers continue to compete against each other. Such joint ventures are found within many industries—aerospace, telecom, integrated circuits, food and beverage, retail investment, heavy industry, and pharmaceuticals.[8] The modern joint venture thus begins with precisely the opposite presumption: the duty of loyalty is necessarily divided between competing partners. This division will produce its own unique kind of agency cost—a fiduciary conflict that is inherent in the structure of joint ventures.

This Article argues that the intrinsic fiduciary conflict is the fundamental legal challenge facing corporate joint ventures. It demonstrates how the law and private parties can and should respond to this challenge. The argument proceeds in three parts. First, I show that the fiduciary duties of corporate joint ventures are contradictory. The literature has overlooked this contradiction, even though it is the fundamental legal problem for joint ventures. The problem is that both corporate law and partnership law apply to joint ventures. The contradiction is that corporate law imposes a duty of undivided loyalty to one’s own company, while partnership law imposes the same duty to one’s partner company.

I begin by showing that this conflict was a latent motivation behind the evolution of joint venture case law, from its origins in the nineteenth century to the present. I then argue that modern corporations resolve this conflict through a hybrid contract-entity form in which they (1) alter the loyalty duties through a covenant not to compete (CNC) and (2) avoid conflicts by operating the venture through a separate entity. This theory thus offers a new explanation behind CNCs: in corporate joint ventures, a CNC establishes coherent fiduciary duties.[9] It also demonstrates a counterintuitive purpose for the creation of a separate entity: though a separate entity is often thought to create conflicts by introducing the principal-agent problem, corporate partners use a separate entity to avoid conflicts by delegating decisions for which the corporate partners are conflicted.

This Article builds on a literature that seeks to identify the key legal features that distinguish the law of contract from the law of business entities. Prior literature has highlighted a functional distinction: the law of business entities enables investors to create a legal person—a corporation, LLC, or other entity—with power to own and dispose of property. This in turn enables investors to cleanly separate business assets from personal assets.[10] The resulting “asset partition” would be infeasible through contract law, which contains no such power to create legal persons.

Here I introduce a complementary and counterintuitive role for entities. When the investors themselves have conflicting objectives, how can they realize gains from collaboration? The solution is to collectively delegate decisions to an “agent”—i.e., a separate legal entity. Crucially, this entity is populated with (natural) persons who owe no duties to the investors directly; rather, their duties are owed to the entity itself. Their objective is to maximize the joint interests of the conflict-ridden principals. I use a case study to demonstrate how this works in practice.

The Article then investigates whether and how the law enables investors to enforce this structure. States vary considerably in the extent to which they are willing to enforce CNCs. Although the literature has acknowledged this variation across states, it has not previously considered the consequences of this variation for corporate joint ventures. Corporate co-venturers would encounter serious problems if they sought to enforce their fiduciary obligations in places like California, which heavily restricts both the alteration of fiduciary duties and the enforcement of CNCs.

For this reason, the Article recommends the creation of an “internal affairs” doctrine for corporate joint ventures. Under this rule, parties would be allowed to choose the law that governs their joint venture, and courts would honor that choice even if it meant enforcing a CNC. Courts should be more willing to enforce CNCs in corporate joint ventures (especially ones that have already passed federal antitrust scrutiny) because the usual policy arguments against them do not apply. Enforcing these provisions would generally not restrict the mobility of employees at either firm. Rather, they would only prevent the corporate partners themselves from opportunistically poaching the venture’s business opportunities. Voiding such agreements would thus deter collaborative innovation while yielding relatively few competitive benefits.

Finally, the Article documents the existence of joint venture networks, in which corporations in the same industry maintain multiple partnerships with overlapping membership. These networks compound the relatively simple fiduciary conflicts that obtain in isolation. They also reveal the robustness of the structure of modern corporate joint ventures, particularly its ability to compartmentalize fiduciary conflicts that might otherwise propagate over the joint venture network. I conclude by considering the implications of these networks for the theory of the firm, which canonically treats firms as distinct, nonoverlapping units of production.[11]

The rest of this Article is organized as follows. Part I examines the law and origins of joint venture and its intrinsic fiduciary conflict. Part II uses a case study from the aerospace industry to analyze how corporations respond to the intrinsic fiduciary conflict of joint venture. Part III discusses enforcement of joint venture agreements and the Article’s recommendation for an internal affairs doctrine. Finally, Part IV demonstrates how the hybrid corporate-contract structure of modern joint ventures sustains joint venture networks; it also discusses implications for the theory of the firm.

I. The Intrinsic Fiduciary Conflict of Joint Venture

Though largely forgotten, the law of joint venture originated as a direct judicial response to the intrinsic fiduciary conflict. In this Section, I set forth three stages in the development of this law. The first was outright prohibition: corporations were not permitted to participate in any partnership. The second was a short-lived exception to this rule—the doctrine of “joint venture,” which permitted corporate partnerships so long as they were limited in scope. In the third and final stage, states overruled the prohibition by statute. I conclude that the arc of joint venture law was not toward “solving” the intrinsic fiduciary conflict, but instead toward relinquishing the problem-solving onus onto private parties.

A. Legal Origins

1. The Rule Against Corporate Partnerships

Nineteenth-century American corporations were prohibited from participating in any partnership, be it with another corporation, an individual, or any other legal person.[12] The few exceptions to this rule were so limited and distinguishable that they seem to prove the rule. For example, courts occasionally granted exceptions based on theories of unjust enrichment. A typical case involved a corporation that benefited from an ultra vires partnership association.[13] In these cases, the partnership was recognized only as a means to calculate the appropriate disgorgement remedy; the partnership itself was not permitted to continue operations.[14] Even in such cases, however, courts did not always grant the exception.[15]

There were two reasons why courts prohibited corporations from forming partnerships: the ultra vires doctrine and the contradiction between partnership and corporate law duties. The first reason came from the historical state monopoly on incorporation. Before states adopted general incorporation laws, only acts of the legislature granted corporate charters, and charters were therefore public law.[16] Courts recognized only two types of limited powers that the legislature could confer through a charter: (1) express powers that were granted in the charter, and (2) implied powers that were “necessary and proper” to exercise express powers.[17] Any corporate act that did not rely on one of these two powers was prohibited under the ultra vires doctrine.

Charters did not typically include an express power to form partnerships, and courts would not infer an implied power. There were several reasons. The most important was that, by forming a partnership, two corporations could effectively merge, thereby forming a “new” corporation. Since only the legislature could grant incorporation status, this was ultra vires.[18] Though the ultra vires doctrine was the main basis for prohibiting corporate partnerships, a few courts offered a second.

The second reason why corporations could not form partnerships was because the joint application of corporate law and partnership law produced an inherent fiduciary conflict. The influential case of Whittenton Mills v. Upton is an early example of how the law grappled with this fiduciary tension.[19] The Whittenton Mills corporation, a Massachusetts cotton manufacturer, had entered into a partnership agreement with William Mason, a natural person. Mason was to provide manufacturing equipment and would share in Whittenton Mills’ profits. All went well until Mason suddenly declared bankruptcy. In the insolvency proceedings, Mason’s creditors brought an action to collect against Whittenton Mills as Mason’s general partner. The collection procedure would have liquidated the corporation, but the court held that Whittenton Mills did not have the capacity to form a partnership. The insolvency proceedings against Whittenton Mills were vacated.[20]

The court reasoned that Whittenton Mills’ charter could not have conferred an implied power to form partnerships because Massachusetts business law and policy relied on the corporation’s capacity “to manage its affairs separately and exclusively.”[21] The power to form partnerships would have contradicted this policy because it would have enabled the corporation’s fiduciaries—its directors and officers—to delegate decision-making authority to the other party in the partnership. Of course, much of a manager’s job is in delegating both tasks and authority. But a partnership contemplates a total and irrevocable delegation: as the corporation’s general partner, Mason would have had authority equal to that of the corporation’s directors, officers, and shareholders combined.[22] The effective authority would have been even greater since Mason could have acted as an individual, rather than through the checks and balances of corporate command. Indeed, had the partnership been recognized, Mason’s unilateral decisions would have liquidated the corporation.[23]

2. The Exception for “Joint Venture”

Like any bright-line rule, the problem with the prohibition of corporate partnerships was its overinclusiveness. The rule was based on the worst-case scenario of general partnership, cases like Whittenton Mills, in which one person could claim total authority over the corporation. But not every corporation that sought a partnership-like relationship wanted to form a general partnership. The purpose of a corporate partnership was not to delegate authority per se and certainly not to authorize would-be partners to dispose of corporate property without limit. Instead, the purpose was to engage in a limited sphere of cooperation with an entity outside the corporation—or, to use the Coasean lingo, to coordinate with another firm without the price mechanism. These corporations therefore sought a relation that was fiduciary in nature: something less formal than partnership yet stronger than contract.

Joint venture was the judicial response to this demand. Joint venture law was created as an exception to the general rule against corporate partnerships. Courts justified the joint venture exception by deemphasizing its partnership-like qualities while emphasizing its circumscribed, contractual nature.

The key judicial move was to separate the two components of partnership: co-ownership of assets and mutual agency. Agency, the more problematic of the two, was tamed by emphasizing the joint venture’s limited business scope.[24] So long as the corporation’s co-venturer did not exert “too much” control, courts reasoned that the business deal simply did not implicate partnership law. It may have looked and quacked like a partnership, but its “limited purpose” was sufficient grounds for concluding otherwise.

After courts dispatched the agency problem, all that remained was co-ownership. The case for corporate co-ownership was easy. Common law had long held that co-ownership, by itself, was not sufficient to form a partnership.[25] And since corporate charters already included an express power of individual ownership, courts could reason by extension that co-ownership was an implied power, “not inconsistent” with a charter that was silent on the issue.[26]

As a legal doctrine, however, joint venture did not last long. By the mid-twentieth century, courts openly acknowledged that the joint venture exception had effectively swallowed the rule.[27] Joint venture law was closer to a sub silentio overruling than a carefully crafted carve-out.[28] One scholar of the time wrote that it “indirectly give[s] the corporation the implied power to enter into a partnership agreement,” and further that a hypothetical law expressly granting the same power “would do nothing more than recogniz[e] an accomplished fact.”[29]

3. Statutory Authority for Joint Venture

Over the next few years, all state legislatures eventually passed such laws, expressly granting corporations power to form partnerships. These laws overruled both the prohibition of corporate partnerships and the ultra vires doctrine by essentially flipping the default authority: previously, the ultra vires doctrine required every corporate act to be authorized by an express (or implied) charter provision. Now, so long as the charter does not expressly provide otherwise, corporations have authority to carry out any lawful act. This includes the authority to engage in any business or business form.[30] A corporation can form partnerships[31] (and vice versa),[32] convert into a partnership,[33] merge with a partnership,[34] and even organize itself as if it were a partnership.[35]

B. Contemporary Legacy

One might think that joint venture doctrine—though now essentially defunct—would have left a legacy of case law and analysis that grapples with the intrinsic fiduciary conflict. It has not.

Instead, the only legacy is a mild confusion over the legal distinction between joint venture and partnership. In practice, the difference is essentially zero. Partnership law generally applies to joint ventures.[36] The reasoning behind this typically revolves around a simple inference: joint ventures are, by legal definition, similar to partnerships; therefore, partnership law should apply.[37] A related line of reasoning is that partnership law applies to joint ventures, but only “by analogy.”[38] The effect of this reasoning is that partnership law is usually applied to joint venture, but in a piecemeal fashion. When confronted with an issue that is settled in partnership law but has never been applied to a joint venture, a court will declare the question a matter of “first impression,” acknowledge the joint venture relation, state the “general rule” that partnership law applies, and finally conclude that partnership law governs.[39]

A few states admit idiosyncratic differences between partnership and joint venture law. The two most important concern termination procedures and voting rights. Partnerships are “terminable at will” by default.[40] Illinois, however, makes an exception for joint ventures: by default, joint ventures are not terminable until the purpose of the venture is achieved.[41] On voting, some states have different default ownership rights in joint venture versus partnership, and this can generate different voting procedures. In partnership, the default for all jurisdictions is that real property is owned by the partnership entity or by the partners as tenants in partnership.[42] However, Michigan makes an exception for joint ventures: the default is that co-venturers own real property as tenants in common.[43] The practical effect of this exception is that, in Michigan, partnership defaults concerning transfer of property are flipped for joint ventures: while tenants in partnership can transfer the entire, co-owned estate without a unanimous vote,[44] tenants in common must have a unanimous vote.[45] These two exceptions on default termination and voting rights, however, are idiosyncratic to particular states and have no effect on most cases.[46] Further, at least in some instances, courts arguably did not intend to create these exceptions.[47]

Though most jurisdictions seem to admit no difference between partnerships and joint venture law, only Texas and Maryland have expressly abolished the legal distinction by statute.[48] Thus, notwithstanding a few peculiarities (not to mention significant confusion in the case law) the law is easily summarized: in Texas and Maryland, joint venture and partnership are legally equivalent; in all other states, case law has approximately equated the two.

Since the law of corporate partnerships very quickly transitioned from outright prohibition to total contractual freedom, it is not surprising that there is no case law analyzing the intrinsic fiduciary conflict. The conflict simply did not spend enough time in the courts to evolve into a coherent doctrine.

This absence of doctrine was not inevitable. Indeed, many of today’s corporate doctrines evolved out of business activities that were previously prohibited. To give one example, consider the old common law rule against interested transactions. The rule was that any deal between the corporation and one of its agents was automatically voidable by the corporation.[49] Like the rule against partnerships, the rule against interested transactions was also overruled by statute.[50] Yet unlike the rule against partnerships, the rule against interested transactions eventually transitioned into a coherent doctrine. This was because the law did not relinquish control over interested transactions. Delaware, for example, only overruled the automatic voidability of interested transactions; its statute and case law replaced this with the threat of voidability—that is, a set of judicial standards to evaluate such deals.[51] By contrast, corporate law simply relinquished control over corporate partnerships; they were unconditionally enabled. Because of this, there were no cases, and so it is not surprising that there emerged no doctrine through which courts could grapple with the loyalty conflicts inherent in joint ventures.

The modern response to this conflict is thus not found in statute or case law, but in contract. In what follows, I lay out a study of such contracts. The goal is to understand how modern corporate joint ventures deal with the intrinsic fiduciary conflict. I will argue that a combination of a CNC and a separate joint venture entity form the key contractual solution.

II. Private Parties’ Response

This Section presents a theory of how corporations respond to the intrinsic fiduciary conflict of joint venture. At the heart of this response lie two legal devices: (1) a CNC and (2) a separate joint venture entity. I argue that these devices work together to resolve the fiduciary conflict. The parties alter the default loyalty duties with the CNC while simultaneously sidestepping potential conflicts by operating their venture through a separate entity.[52] Figure 1 diagrams this structure.

This theory thus offers a new explanation behind CNCs: in corporate joint ventures, CNCs are the key mechanism for establishing coherent fiduciary duties. The theory also presents a novel use for entities: entities are often thought to create conflicts because they introduce the principal-agent problem, but I argue that in joint ventures they counterintuitively prevent conflicts because they enable partners to delegate conflicted decisions.

The main exposition will proceed with a case study from the aerospace industry. It should be kept in mind, however, that we observe this basic structure in corporate joint ventures across all industries.[53]

A. Case Study

In 2005, The Boeing Company and Lockheed Martin established a joint venture.[54] Their agreement formed a new, multi-billion-dollar company, United Launch Alliance (ULA), a Delaware LLC owned in equal shares by its two members.[55] The business of ULA is to launch satellites into orbit for the US government. Most of these services are provided to the US Air Force and NASA.

The ULA venture was the result of an Air Force program that began in 1994.[56] The program increased funding for the procurement of rocket systems from private companies. It ultimately led to the development of two competing rocket systems, one by Boeing (the “Atlas” system) and the other by Lockheed (the “Delta” system).[57] For many years, Boeing and Lockheed separately designed and manufactured their two systems. In the course of their competition, the US government awarded both companies several contracts throughout the 1990s and early 2000s.

The competition between these two firms was not only fierce, but at times illegal. Early in the Air Force procurement process, a Boeing executive solicited a Lockheed engineer to work at Boeing.[58] The Lockheed engineer brought thousands of pages of confidential documents to Boeing.[59] These documents exposed Lockheed’s plans for contract bidding as well as Lockheed’s new proposals to the Air Force.[60] In 2003, the Justice Department charged the executive and the engineer with conspiracy to steal Lockheed trade secrets.[61] The United States and Lockheed also filed separate civil actions against Boeing.[62] As a result, Boeing was fined, temporarily banned from providing launch services to the US government, and stripped of several of its existing contracts.

This was a low point in trust between the two firms, yet out of this mess came the ULA joint venture.[63] The details are unclear (and confidential), but much of the impetus behind ULA seems to have come from the Air Force. For national security reasons, it wanted to keep both Boeing and Lockheed rocket systems operational. To accomplish this, the Air Force encouraged a joint venture between the two firms. It expected (or hoped) that this would not only ensure their survival, but also result in higher quality launches.

Boeing and Lockheed, despite their pending suits and counter-suits, were probably happy to oblige since the venture would create a monopoly on launch services to the US government. The Federal Trade Commission noted this anticompetitive effect in its review of the proposed venture, but nevertheless approved the venture because of the Air Force’s concerns about national security.[64] Boeing and Lockheed settled their civil claims,[65] and—out of this dramatic conflict—their venture was born. They may have been rivals, and cheating rivals at that, but as partners they now owed each other a duty “of the finest loyalty.”[66]

B. Covenants Not to Compete (CNCs)

A covenant not to compete (CNC) is a contractual provision through which one party commits not to compete with another in a specified market. The next four subsections will (1) describe the CNC in the Boeing-Lockheed venture, (2) offer a new rationale for the role of CNCs, namely, to design coherent fiduciary duties in corporate joint ventures, (3) compare this new rationale with two traditional rationales for CNCs, and finally (4) argue that the new rationale I offer (designing fiduciary duties) is the fundamental purpose of a CNC in the context of a corporate joint venture.

1. CNCs in Action

The ULA venture included two types of CNCs. The first was a “non-solicitation agreement,” which covered promises over labor market demand and the movement of employees.[67] The second part of the CNC, the “non-competition agreement,” covered promises over product market supply. Together, these clauses ran about eight pages and constituted the most intricate—and confusing—sections of the 120-page ULA joint venture agreement.[68] To summarize the covenant not to compete, I will break it down into several parts.

First, Boeing and Lockheed defined their joint market as launch services for which: (1) the customer was the US government, (2) payloads were between 2–70 metric tons, and (3) payloads were delivered into low Earth orbit, which is between 160–2,000 kilometers above sea level. Boeing and Lockheed next agreed to refrain from two types of competition in this joint market: (1) for five years, neither would separately engage in the R&D of related products, and (2) for seven-and-a-half years, neither would separately engage in the manufacture or provision of related products.

Having cast a broad net, the non-competition agreement then made several exceptions. These included carve-outs relating to Boeing and Lockheed’s preexisting joint ventures,[69] carve-outs for “ordinary course” activities (twelve in total), and a severability clause—a kind of judicial carve-out that essentially asks the judge to make only the minimum modification necessary to cure an unenforceable CNC.

Finally, the non-solicitation agreement forbade all parties—Boeing, Lockheed, and the joint venture LLC—from actively soliciting certain of each other’s employees for two years. Although this affected the employment prospects of some top executives among Boeing, Lockheed, and the LLC, it had no effect on their ability to seek work outside of these three firms. Further, it was not an outright prohibition that would prevent, for example, a Boeing employee from changing jobs to Lockheed. Instead, it was merely a restriction on the procedure by which such a switch could occur: the partner corporation and the joint venture entity could not directly approach the employee. Given Boeing and Lockheed’s competitive history, particularly the instance of espionage between Boeing and Lockheed executives,[70] such a restriction seems prudent, if not necessary, to prevent each side from stealing the other’s trade secrets. The non-solicitation agreement included some exceptions based on both the rank and status of the employee (which were confidential).

2. A New Rationale for CNCs: Altering Fiduciary Duties

Why would a joint venture agreement adopt a CNC? Traditional law and economic theory have promoted two rationales based on the holdup and antitrust problems (which I summarize in the next section). Here, however, I offer a novel explanation for the primary function of a CNC in a corporate joint venture: corporations adopt them to alter fiduciary duties. CNCs are thus a key mechanism behind how corporations respond to the intrinsic fiduciary conflict of joint venture.

Without a CNC, Boeing would have had a duty to pursue partnership business opportunities for the benefit of both Boeing and Lockheed. But a Boeing agent could have easily become conflicted: what if, for example, the agent had to buy an input for the joint venture—and this input could only be purchased from one of the two partners?

The CNC solved this problem by prohibiting Boeing and Lockheed agents from even making this decision and instead delegating the decision to the independent agents of the joint venture LLC. Boeing still owed a partnership duty of loyalty to Lockheed. Under the CNC, however, it was satisfied by simply abstaining from action. Agents of Boeing did not have to compromise their corporate law duties by affirmatively acting in Lockheed’s interest.

To get a sense of how this works in practice, consider the intellectual property arrangement in the Boeing-Lockheed venture, where the intrinsic fiduciary conflict applied in full force. Boeing and Lockheed extended to ULA a free license over all their rocket-related intellectual property (discussed in more detail below). But this intellectual property could also be applied to purposes well outside the scope of ULA’s operations. For this reason, the Boeing-Lockheed licensing agreement included one significant exception: each firm retained the right to separately and independently exploit the same intellectual property in the ordinary course of its own business.[71] Because of this exception, Boeing and Lockheed could, and indeed do, continue to separately market their launch systems (the Boeing “Delta” and Lockheed “Atlas”) to commercial markets. The co-venturers are thus loyal partners with respect to technologies in one market, but aggressive competitors over the very same technologies in another. How is this possible? The answer is the CNC.

A CNC enables this competitor-partner dichotomy by regulating the duty of loyalty. To see this, first imagine a world without CNCs. In this case, the default duty of loyalty would govern. The default duty is a legal standard. It requires that each corporate partner “refrain from competing with the partnership in the conduct of the partnership business.”[72] This standard is used to determine which opportunities belong to the venture and which opportunities can be lawfully appropriated by either party. But like any standard, the boundaries are unclear. Judges, co-venturers, and even agents of the joint venture entity could hold reasonable but conflicting positions on what precisely constitutes “the partnership business” and whether any given opportunity lies strictly inside or outside of it.

CNCs organize the venture’s opportunities by swapping the default loyalty standard for a bright-line loyalty rule. The result is that co-venturers can more readily distinguish partnership opportunities from those which are “fair game” for either co-venturer to seize. For any given opportunity, both sides can more confidently don the “partners hat” or the “competitors hat.”

Though CNCs draw clear lines, they do not draw perfectly clear lines—nor should they. A CNC generally replaces fiduciary standards with fiduciary rules, and indeed some of the CNC carve-outs provide very clear lines. For example, Boeing and Lockheed were permitted to own exactly 10 percent or less of a competing business.[73] But both the CNC and the licensing provisions also expressly incorporated standards that were less clearly defined. For example, Boeing and Lockheed were permitted to separately engage in the R&D and manufacture of reuseable launch vehicles, as opposed to expendable launch vehicles, which was the defined business of the ULA venture. A reusable vehicle is one that is recovered after launch (such as the Space Shuttle), whereas an expendable vehicle is discarded after launch (usually by disintegrating on reentry). These may seem to be distinct concepts, but the line between them is not exactly bright. It could be analogized to the line between NASA’s Space Shuttle and Apollo programs. The former used reusable vehicles while the latter used expendable vehicles. The line between these programs may separate distinct projects and goals, but it does not separate distinct boundaries in intellectual property.

CNCs do not strive for the greatest clarity because certainty does not come for free. Requiring certainty means that co-venturers can only collaborate in markets that can be perfectly delineated. These markets do not necessarily coincide with the markets for which there are gains from collaboration. A more rule-like CNC discourages spontaneous collaboration outside the original scope of the joint venture, collaboration that could in turn lead to innovation that neither would have achieved separately. At the extreme, a “perfectly” delineated CNC would perfectly discourage such collaboration because the scope of the duty of loyalty is completely determined ex ante. Contrast this with a fiduciary standard. A fiduciary standard strongly encourages spontaneous collaboration because the scope of the duty is completely determined ex post: the scope is “the business of the partnership,” which, if left unspecified, is simply wherever the partners’ collaborations take them. Since technologies are often applied well beyond their original intention, a “perfect” CNC could prove counterproductive.

In summary, CNCs replace the loyalty standard with a level of clarity that balances the rule–standard tradeoff. In so doing, they mitigate the intrinsic fiduciary conflict by organizing joint venture opportunities.

3. Two Traditional Rationales for CNCs

Here I briefly outline two traditional rationales for CNCs based on the holdup and antitrust problems. The holdup problem arises where collaboration requires one or both sides to make relationship-specific investments.[74] The problem with such investments is that they are costly to redeploy outside the relationship. Having sunk a relationship-specific investment, the cost of backing out of the deal increases for the investing party. The counterparty is then incentivized to exploit the investing party’s vulnerability, to threaten to “hold up” the project and extract a larger share of the surplus. Ex ante, the threat of holdup inefficiently discourages relationship-specific investments.

A CNC mitigates the holdup problem by lowering the value of investments made outside the relationship. If a CNC is perfectly enforced, then investments made within the scope of the CNC but outside the relationship become worthless. Indeed, if CNCs are specifically enforced, then each party can enjoin the other from making such investments (or compel the other to divest if the investment is already made). The CNC thus provides indirect mutual assurance for relationship-specific investments: it does not prevent one party from threatening to walk away after the other has sunk a relationship-specific investment, but it does mitigate this holdup threat by limiting the breaching party’s outside options.

The antitrust rationale cuts two ways: co-venturers in similar markets prefer a broader CNC to capture a larger monopoly rent, while competition authorities prefer the opposite.[75] A joint venture’s CNC thus outlines a compromise between these two interests. For example, in the Boeing-Lockheed venture, the broad scope of the CNC was likely an advantage to Boeing and Lockheed because it provided more opportunities to monopolize the aerospace industry. But, in an effort to balance the monopolizing effect of the CNC, the Federal Trade Commission conditioned its approval for the venture on the implementation of certain pro-competitive policies, effectively altering the terms of the ULA CNC.[76]

4. The Fundamental Role of a CNC in Corporate Joint Ventures

In corporate joint ventures, the fundamental role of a CNC is to resolve the intrinsic fiduciary conflict; the holdup and antitrust motivations are of secondary importance. This is because the fiduciary role is logically prior. The holdup problem concerns opportunistic behavior in which one party purposely exploits the other’s vulnerability. The antitrust explanation is similarly purposeful: the partners are trying to grab as much market power as possible. Yet both explanations assume that these opportunistic and purposeful corporate agents actually know what their roles are.

The premise of this Article is that they do not. This is because corporate law and partnership law assign each agent two conflicting roles—or perhaps even three, if one considers the interests of the partnership entity as separate from the partners. Each agent must (1) advance the best interests of one’s own corporation (the corporate duty of loyalty), (2) advance the best interests of one’s partner corporation (the partnership duty of loyalty), and (3) advance the best interests of the joint venture entity (the “third” role, created by contract).

These fiduciary roles inherently conflict. Thus, this fiduciary conflict is logically prior to the antitrust or holdup problems: to exploit one’s own position, one must first know what it is. By forbidding each corporate partner from acting within the market defined by the CNC, the CNC “defines” the co-venturers roles by effectively eliminating all three. That is the innovation of the CNC. It carves out a negative space in which neither corporate partner may act. As explained below, the modern joint venture then fills this negative space with a separate entity whose role is to pursue the joint venture’s—and only the joint venture’s—interest.

C. Joint Venture Entities

Altering fiduciary duties with a CNC is only one half of the response to the intrinsic fiduciary conflict. We now arrive at the second, complementary half: the separate joint venture entity.

1. Using an Entity to Avoid Conflicts

Here I demonstrate a new function for entities: they are an innovative and deceptively simple response to the intrinsic fiduciary conflict. Perhaps the greatest challenge facing entities is that they create conflicts through agency, that is, through the separation of decision makers (agents) from beneficiaries (principals). The innovation of the joint venture entity is that corporations counterintuitively use a separate entity to avoid conflicts by delegating decisions for which the beneficiaries (i.e., the corporate partners) are conflicted. For example, consider again the one given above: suppose the joint venture had to buy an input from either Boeing or Lockheed. Boeing and Lockheed agents would both be conflicted; a third party must make this decision.

A joint venture entity thus serves the role of quarantining the venture’s opportunities. The Boeing-Lockheed venture created a new entity that is separate from both companies. The joint venture agreement itself was a contract among three parties: Boeing, Lockheed, and “a Delaware limited liability company to be formed.”[77] The “company to be formed” was United Launch Alliance, LLC.[78] ULA, the joint venture entity, acts as a buffer between the two co-venturers. Boeing and Lockheed may own the entity itself, but neither directly pursues the joint venture’s opportunities nor has the authority to make partnership decisions. Instead, all this is done through a third-party entity.

Critically, ULA has a separate set of agents who work only for ULA and not for either Boeing or Lockheed. As a matter of law, these managers owe a duty of loyalty to ULA itself, not to either co-venturer. Of course, there may be economic temptations that would bend the loyalties of ULA’s agents toward Boeing or Lockheed, especially because the managers themselves come from each: the LLC’s CEO is a former Lockheed manager, its COO is a former Boeing manager.[79] This assignment of in-house managers could create problems in enforcing the duty of loyalty. But before the LLC was established, the intrinsic fiduciary conflict created much more than a mere problem of enforcement: it was not even clear who owed what loyalty to whom. Further, the default duty of loyalty would have required Boeing agents to be loyal to Lockheed and vice versa. This would have been an impossible duty because Boeing and Lockheed are direct competitors. Creating a joint venture entity enables loyalties to remain “undivided” since no individual agent owes loyalty to more than one firm: Boeing agents are loyal to Boeing, Lockheed agents to Lockheed, and ULA agents to ULA. The enforcement problems may remain, but at least the duty itself is clear to both corporate partners.

The joint venture entity thus supplants the default structure of both loyalty and ownership over partnership opportunities. It replaces this with a structure in which partners retain ownership over the profits of the joint opportunities while the opportunities themselves remain out of reach. Instead of “joint custody” over the joint venture opportunities, there is “third-party guardianship.” Instead of having Solomon “split the baby,” Solomon himself—the neutral third—protects the baby.[80]

In addition to solving the intrinsic fiduciary conflict, entity creation also provides several additional conveniences. It limits the liability of both companies for the venture’s actions, serves as an accounting convenience to keep track of each party’s contributions and the venture’s operations, and clarifies the managerial chain of command. Operating the venture through an LLC (or other entity) also avoids the confusion in state law between joint venture and partnership. For example, some states maintain distinct (and sometimes confusing) procedures for terminating joint ventures and partnerships.[81] In contrast, Delaware provides clear statute and case law on when a co-venturer can petition the court to dissolve a joint venture corporation or joint venture LLC.[82] Creating an entity thus serves many roles that are separate from the intrinsic fiduciary conflict: economic, accounting, managerial, and legal. Conflict avoidance is yet another role, unique to joint ventures, that entities can play.

2. The Need to Collaborate Via an Entity

The joint venture entity also enables corporate competitors to collaborate. Direct collaboration would exacerbate the inherent fiduciary conflict. It would also mean disclosure of trade secrets and business practices to one’s competitor. Thus, instead of collaborating directly with each other, modern joint ventures collaborate indirectly through the joint venture entity.

In the Boeing-Lockheed venture, collaboration via an entity enabled the partners to share intellectual property without having to disclose it to their competitor. Boeing and Lockheed both granted ULA “a worldwide, perpetual, irrevocable, non-transferable, no-cost, royalty-free” license to their intellectual property portfolios relating to expendable launch vehicles (one-time-use rockets). The license was exclusive during the term of the CNC, meaning that ULA enjoyed both unrestricted and exclusive access to the rocket-related intellectual property of Boeing and Lockheed.[83] After the term expired, ULA’s access was still unrestricted but no longer exclusive.[84]

This is a formidable power on the part of ULA. Intellectual property is the core of an aerospace firm and many of its technologies are general. The same patents that go into the guidance and aerodynamics of rockets are also used to design airfoils and electrical systems on fighter jets or commercial airliners. Thus, though it is difficult to estimate precisely, the value of ULA’s access to intellectual property likely exceeded the (transferable) value of ULA itself.

This power created both uncertainty and vulnerability. The uncertainty was that Boeing and Lockheed’s relative contribution could not be easily quantified ex ante. Even ex post, it may not have been clear which side contributed more. A “pay per use” accounting scheme for patents (i.e., a price mechanism) would have mitigated this. Instead, the ULA joint venture agreement simply stated that Boeing and Lockheed would share their intellectual property with the LLC, free of charge. ULA’s access also left Boeing and Lockheed vulnerable. Instead of piecemeal assignment or tailored access to individual technologies, ULA was given keys to both kingdoms—with the sole restriction that it use the keys “within the scope of the purpose of [the venture].”[85]

This vulnerability was the very problem that the Massachusetts court cited in 1858, when it prohibited the corporate partnership in Whittenton Mills.[86] The problem was that one partner had “too much” access—and therefore control—over the other. The further problem was that such control was lawful within the realm of partnership law. To the court, this presented not just a fiduciary conflict, but a contradiction. As discussed above, the original solution seemed like the only one: prohibition.[87]

If it were the case that Boeing and Lockheed were general partners and granted each other unrestricted access to their intellectual property, they would be in a situation akin to the partners in Whittenton Mills. Each corporate partner would have too much access and control over the other’s operations. Their vulnerability would be protected only by a threat of mutually assured destruction. But Boeing and Lockheed did not grant each other such access. They granted it to the joint venture entity, whose independence is checked by the fact that it exists only by the grace of the co-venturers. Instead of mutual access, there is third-party access. Instead of mutual control over all the partners’ business, there is third-party control over only the joint business.

Co-venturer shareholders in a joint venture firm thus differ from shareholders in a typical firm in several respects. First, shareholders of a corporate joint venture firm can appropriate the firm’s business opportunities. Indeed, the shareholders of ULA (Boeing and Lockheed) previously competed in the precise market in which ULA operated. Thus, one of the roles of the separate ULA entity was to protect the joint venture’s assets from its own shareholders. By contrast, the typical firm does not need to protect its assets from its own (small) shareholders. There is virtually no risk that a small shareholder of a typical firm will appropriate one of the firm’s opportunities. A small shareholder is often not able to even evaluate the business opportunities, let alone appropriate them.

The second difference is that co-venturer shareholders are integrated with the joint venture firm, that is, they coordinate with the joint venture firm without relying on a price mechanism. In the Boeing-Lockheed venture, the integration came in the form of “cost-free” access to the co-venturers’ intellectual property. This access was not mutually granted to each co-venturer, but instead granted to the joint venture firm. The integration was thus not between the co-venturers themselves, but between the co-venturers and their joint venture entity. By contrast, the typical shareholder is not integrated with the firm; the typical shareholder does not share assets with the firm.

Finally, there is no intrinsic fiduciary conflict among shareholders of a typical firm. The firm’s agents owe loyalty only to the corporation, while the shareholders owe no loyalties at all.[88] Put another way, shareholders of traditional dispersed corporations are not partners.

III. Enforcement Problems and Proposed Solution

This Section discusses differences across states in their willingness to enforce CNCs, as well as their willingness to let co-venturers alter fiduciary duties. It then offers a policy recommendation: an internal affairs doctrine for corporate joint ventures. Under this rule, parties would be allowed to choose the law that governs their joint venture and courts would enforce that choice.

A. Enforcement Problems

1. Are CNCs Enforceable?

States vary considerably in their willingness to enforce CNCs. Here I consider two illustrative jurisdictions that delimit the ends of this spectrum of enforceability: Delaware and California.

Delaware embraces CNCs as the source of a corporate joint venture’s fiduciary duties. In Universal Studios, Inc. v. Viacom, Inc.,[89] the Delaware Chancery Court considered a joint venture that was structurally similar to the Boeing-Lockheed deal. Two corporations, Universal and Paramount, formed a partnership called the USA Network, which soon became a successful cable network. The core provision of their deal was a CNC that prevented the partners from operating competing cable networks. There were some exceptions for their preexisting businesses, though these exceptions may not have been necessary because neither had competing cable networks. Some years later, Paramount was acquired by Viacom. Viacom had several preexisting cable network subsidiaries (including MTV and VH1). Universal then sued Viacom, claiming that by continuing to hold on to these networks, it violated the CNC.

The court made several holdings, all of which favored the interpretation of the CNC as an enforceable source of fiduciary duties. Universal argued that Viacom’s acquisition tortiously interfered with the USA Network partnership agreement. The court rejected the claim, writing that “[a] more appropriate analysis of Viacom Inc.’s actions must be within a discussion of the parties’ fiduciary duties.”[90] It then held that the CNC was the exclusive source of these duties:

The parties . . . intended to define the participants’ duty of loyalty to each other and to the Venture partnership within the non-compete or covenant not to compete clause. As such, I need not discuss the issue of any independent breach of common law fiduciary duty. All of the parties’ respective contentions concerning the scope of the duty, the existence of a breach of duty, the effect of the breach, the nature of the harm suffered by the USA Networks, and who bears responsibility as a result, can and should be discussed within the framework crafted by the parties themselves—the non-compete clause and associated provisions of the contractual relationship.[91]

The court ultimately found that Viacom had breached its duty of loyalty to Universal.

The court thus endorsed the idea that corporate partners define their fiduciary duties through a CNC. The case also demonstrates that Delaware is willing to enforce a CNC in the context of corporate joint ventures.

California, in great contrast to Delaware, takes a less permissive approach to CNCs. CNCs are notoriously difficult, if not impossible, to enforce in California. Section 16600 of the California Business and Professions Code imposes a blanket prohibition that voids any “contract by which anyone is restrained from engaging in a lawful profession, trade, or business of any kind.”[92]

This prohibition applies even in the context of an ongoing joint venture. In Kelton v. Stravinski,[93] two natural persons, along with their associated corporations, formed a series of partnerships to develop warehouses. Their first agreement included a CNC: each party agreed not to pursue future warehouse projects without the other. Kelton used this agreement to claim an interest in projects that Stravinski had pursued outside the partnership. The trial court rejected Kelton’s claim and held that the covenant was unenforceable as a matter of law under section 16600.[94] The appeals court affirmed, holding that “[i]n the partnership context, an ongoing business relationship does not validate the covenant.”[95] Further, the appeals court separately held that Kelton could not recover under a duty of loyalty claim because subsequent amendments to the agreement had limited the scope of partnership to its existing projects.[96] The court did not reach the question of whether a partner could enforce a CNC by claiming that it defines the venture’s duty of loyalty. Thus, it is not clear whether and to what extent joint venture agreements with CNCs are enforceable in California.[97]

2. Are Fiduciary Duties Alterable?

The default and mandatory fiduciary boundaries of joint ventures are governed by partnership law.[98] Here I again consider California and Delaware, which delimit the spectrum of the extent to which states permit alteration of these duties. In previous work, I have shown that these jurisdictions are among the most commonly chosen by sophisticated parties.[99]

California limits co-venturers’ power to tailor fiduciary duties. Like most states, California adopted the Revised Uniform Partnership Act’s (RUPA) position on altering fiduciary duties.[100] California law provides that a partnership agreement “may not . . . eliminate the duty of loyalty,” but that it may exempt specific behavior by describing it in detail.[101] However, exempted behavior is still subject to judicial review.[102]

In the Boeing-Lockheed case, if California law had governed the CNC, it is unlikely that Boeing and Lockheed would have been able to enforce their alteration of fiduciary duties, especially if a dispute had arisen over one of the agreement’s enumerated exceptions for certain “ordinary course” activities. This is because a partnership opportunity must be specifically described in the contract before it may be lawfully appropriated. It should come as no surprise then, that the Boeing-Lockheed deal did not select California law (or any other RUPA state), but instead chose Delaware.

Delaware enables partners to opt out of the duty of loyalty. Delaware adopted RUPA but changed the rule for altering fiduciary duties. The Delaware statute replaces the elaborate altering provisions of RUPA with a simple statement that partnership agreements “may not . . . [e]liminate the implied contractual covenant of good faith and fair dealing.”[103] Delaware law explicitly states that this, along with other changes to RUPA, were made to promote freedom of contract.[104]

A partner that contracts out of loyalty in Delaware can lawfully appropriate a partnership opportunity without disclosing it ex ante or accounting for its benefits ex post.[105] This is not possible under RUPA.[106] However, the duty to disclose partnership opportunities should not be conflated with the duty to disclose information about the partnership itself (i.e., its books and records). This duty is mandatory in all states.[107]

B. Policy Recommendation: An Internal Affairs Doctrine for Corporate Joint Ventures

The variation across state law in parties’ ability to enforce CNCs introduces legal uncertainty in corporate joint ventures. The uncertainty is over the extent to which co-venturers can alter and enforce fiduciary duties. The central claim of this Article is that the baseline fiduciary duties of corporate joint ventures— those imposed by corporate and partnership law—inherently conflict. Thus, corporate partners must design their own, coherent set of fiduciary duties. For this reason, I recommend the following policy: an internal affairs doctrine for corporate joint ventures.

Before discussing this policy, first consider the logical alternative: changing partnership law to accommodate corporate joint ventures. This would be a mistake for several reasons. Reforming partnership law would require colossal effort and might introduce more uncertainties. Partnership law was not designed with corporations in mind.[108] The partnership as a business association was designed for natural persons, and as the default business association, it is an especially powerful tool for promoting fair dealing among laypersons who go into business without choosing a business form. Partnership statutes and case law are also slow to evolve. New York, for example, still uses the original Uniform Partnership Act of 1914.

By contrast, an internal affairs doctrine would be straightforward to implement. It would only require a court to honor the choice of law made by the parties to the joint venture.[109] Its operation would be analogous to the internal affairs doctrine in corporate law. And though there are notable exceptions, even California courts are relatively willing to honor the choice of law in corporate charters.[110] Crucially, courts would uphold corporate partners’ choice of law even if it requires them to enforce a CNC that would otherwise be unenforceable under their home law.

Courts should be more willing to enforce CNCs in joint ventures (especially ones that have passed federal antitrust scrutiny) because the usual policy arguments against such covenants do not apply with the same force in the context of joint ventures. In a seminal article, Ronald Gilson analyzed CNCs in employment agreements.[111] Such agreements forbid an employee from working for a competitor firm, typically for a few years after leaving their current firm. Gilson’s study highlights the social tradeoff that such agreements present: enforcing them encourages innovation by protecting IP and preventing employees from disclosing trade secrets, but not enforcing them also promotes innovation through labor market mobility and information spillovers.[112] Gilson then persuasively argues that the non-enforceability of such agreements in California may have been a blessing for the development of Silicon Valley, where information spillovers were the key to innovation.

The calculus changes, however, in the context of corporate joint ventures. CNCs in joint ventures are typically not blanket prohibitions that prevent employees from working at unrelated competitor firms. Rather, they prevent the corporate partners from opportunistically poaching each other’s employees and their venture’s business opportunities. CNCs are the crucial mechanism for establishing a coherent set of fiduciary duties vis-a-vis the corporate partners.

Courts should not make the mistake of thinking that enforcing a joint venture’s CNC necessarily promotes competition. From afar, Boeing, Lockheed, and the joint venture LLC might look like three distinct firms that would compete were it not for the CNC. Indeed, each company has its own separate legal personality and separate loyal agents. However, Boeing and Lockheed are both competitors and collaborators. Both companies are integrated with the joint venture LLC; they share their intellectual property with it. There might be a competitive benefit to voiding their agreement—perhaps a marginal Boeing agent would efficiently switch jobs to Lockheed. But Boeing agents are always free to switch to firms other than Lockheed or the joint venture LLC.

Furthermore, any competitive benefit is potentially swamped by the loss of collaborative innovation: without a CNC, there is no coherent fiduciary relationship; the partnership would not exist. This is not to say that any given joint venture’s CNC is socially beneficial, or even that the Boeing-Lockheed CNC is beneficial. Indeed, CNCs that generally prevent rank-and-file employees (as opposed to top executives) from switching firms are socially undesirable, unnecessary, and unfair. The point here is not to advance a position on the precise boundaries of an optimal CNC enforcement policy. Instead, the point here is that the policy calculus behind enforcing CNCs is fundamentally different in the context of a joint venture. The law ought take this difference seriously by adopting an internal affairs doctrine. Such a doctrine would allow co-venturer corporations to choose the law that governs intra-joint venture disputes.

IV. Joint Venture Networks

This Section empirically demonstrates the existence of joint venture networks. By “joint venture network,” I mean the situation in which three or more firms simultaneously engage in separate joint ventures with each other. I argue that these networks exacerbate the intrinsic fiduciary conflict. I also argue that these networks require us to update the theory of the firm.

A. Existence and Scale

Figure 2 gives a hint of the enormity of the aerospace joint venture network. It graphs the network for Boeing, Lockheed, and BAE Systems.[113] I found thirty joint ventures that involve at least one of these three companies.

Yet Figure 2 significantly underestimates the scale of the aerospace network—even among these three firms. The biggest reason is that it only includes ventures that directly involve one of these three. “Partners of partners” are not depicted. The scale is further underestimated because I personally gathered the sample. In my attempts to cobble together annual reports, industry reports, and news articles, I almost surely missed some joint ventures.[114]

Figure 2 also understates the complexity of the true network structure. Lockheed and BAE, for example, have two joint ventures together. One of them involves Rafael Advanced Defense Systems (an Israeli firm), and the other involves Airbus (a European conglomerate) and Finmeccanica (Italy). A single joint venture can also give rise to several entities, each with its own distinct purpose, yet part of the larger partnership. Perhaps most confusing of all, joint venture entities themselves form joint ventures.[115] Figure 2 compresses these complexities into a single link between the parent companies. The full picture is thus much grander in scale and complexity.

There are several structural reasons for the proliferation of joint ventures in aerospace. These reasons run the gamut from economic to political motives. As for economic rationale, aerospace products must integrate complex systems—airframes, engines, weapons, communications—into a single product. One way to conceptualize this industry is that each firm specializes in a few systems and any given product is either sourced from several firms or developed through a joint venture. Relatedly, joint ventures are also key to maintenance of existing products. For example, in the commercial airline industry, ventures often form among the airframe manufacturer, the airline company, and local airport authorities.

The political rationale is specific to aerospace. International ventures sometimes form as a response to the military procurement bureaucracy. The bureaucracy is a myriad of regulatory and political hurdles for any supplier, but it is especially cumbersome for the foreign supplier.[116] International ventures are sometimes created to “domestically” source technologies, either because direct foreign sourcing is prohibited or because the bureaucracy is too treacherous for the foreign firm to navigate alone.

International joint ventures can also arise out of a desire for political cooperation. Many of the North Atlantic Treaty Organization (NATO)’s suppliers, for example, are joint ventures among the large aerospace firms of member states.[117] It should be noted, however, that ventures form even in the face of domestic pressure not to trade with foreign governments.[118] International ventures thus form both because of and in spite of international political constraints.

B. Dynamic Networks

The aerospace joint venture network presents the intrinsic fiduciary conflict writ large. In the context of a single joint venture, the entity-CNC combination is, at the very least, an extremely convenient organizational device. In the context of an interconnected industry such as aerospace, this device becomes critical to sustaining the joint venture network.

Before their ULA venture, both Boeing and Lockheed were independently engaged in separate joint ventures with the same third firm, RSC Energia, a large state-owned aerospace company in Russia. Both joint ventures also provided launch services—and so they were seemingly competitors.[119] However, the Boeing-Lockheed CNC enabled both firms to maintain their respective positions because it was conditioned on (1) sales to the US government and (2) launch services to low Earth orbit. In contrast, their existing ventures were for sales to commercial customers and launches into medium and high Earth orbit.[120] This latter fact quite literally put their preexisting ventures thousands of miles beyond the scope of the ULA venture.[121] The agreement thus enabled both firms to continue their respective ventures with RSC Energia.[122]

Joint venture networks are thus dynamic. Figure 3 diagrams the joint venture network among Boeing, Lockheed, and RSC Energia before and after the ULA joint venture. The dashed links indicate changes to the network after ULA was formed.

CNCs take a larger role in the context of a dynamic joint venture network. A CNC delineates the loyalty boundary for a given dyad. This makes it easier for each co-venturer to then turn around and cooperate with another company, for those companies to in turn form partnerships with others, and so on. Even if a fuzzy loyalty standard were optimal for a given dyad in isolation, it probably would not be optimal for a given company in a network. This is because the costs of an uncertain loyalty standard are compounded over a network. Uncertainty over loyalties translates to uncertainty over ownership of corporate opportunities. This creates uncertainties in neighboring ventures, both realized and potential. If A and B form a venture with fuzzy boundaries, how can C plan a potential venture with either? Suppose C forms a venture with B; then what is D to make of the fuzzy boundary from A to B and B to C? CNCs, along with separate joint venture entities, mitigate the propagation of this negative externality—both across firms and within ventures for a given firm. Together, they clarify the loyalty duties and insulate the corporate partners from the source of potential conflicts—that is, from the partnership’s day-to-day activities.

C. Implications for the Theory of the Firm

The vastness of the aerospace network compels a simple question for the theory of the firm: where are the firm boundaries? Joint venture networks do not conform to a traditional theory of the firm. If A, B, C, and D are the 4 firms of an industry, and in the course of their competition they form and maintain all possible combinations of joint ventures (11 in total),[123] does that mean that there are 4 + 11 firms? Or still just 4? Or 1 mega-firm?

The industry may have begun as a set of disjoint firms. And even after all 11 joint ventures are created, firms A, B, C, and D—by themselves—would continue to form a partition of the industry. That is, they are disjoint firms that together account for all the industry’s activity. But A, B, C, and D would no longer be an exhaustive list of all firms. There are firms A, B, C, and D separately, but there are also joint venture firms {A, B}, {A, C}, {A, D}, and {A, B, C}, not to mention the potential “joint venture of joint venture” firms.[124]

The theory of the firm starts with the premise that firms are a coherent unit of observation, that they are distinct and separate from each other, and that transactions either occur strictly “within the firm” or “in the marketplace.” This applies to all flavors of the theory of the firm, whether premised on transaction costs, control, ownership, or contract.[125]

The existence of joint venture networks challenges this assumption. In the aerospace industry, the “foundational” firms such as Boeing and Lockheed overlap with each other through their much more populous joint venture firms. Since corporate partners are integrated with the joint venture entity but not with each other, the joint venture transaction occurs both between and within firms. Firms may be distinct entities, but they are not necessarily disjoint entities. The boundaries of the firm overlap with one another.

Conclusion

Corporate joint ventures, by combining the corporate and partnership business forms, create an intrinsic fiduciary conflict. The conflict is that corporate law imposes a duty of loyalty toward one’s own company, while partnership law imposes an opposite duty of loyalty toward one’s partner company. This Article examined how private parties and the law can and should respond to this conflict.

The Article made three contributions. First, it showed that there is a conflict within the fiduciary duties of corporate joint ventures. This conflict has not been previously recognized by the literature. The Article presented a theory of how modern corporations respond to this fiduciary conflict: (1) by altering the default loyalty duties through a CNC; and (2) by avoiding conflicts by operating the venture through a separate entity. This theory thus suggested a new role for CNCs: they are the lynchpin of fiduciary duties in corporate joint ventures. It also suggested a novel role for entities, which are often thought to create conflicts because they introduce the principal-agent problem; instead, I showed that joint ventures counterintuitively employ entities to avoid conflicts by delegating decisions for which the corporate partners are conflicted.

The second contribution concerned enforcement. Some jurisdictions restrict partners’ power to alter the default duties and enforce CNCs, while others enable partners to do both. This creates legal uncertainty for corporations looking to form joint ventures. The Article offered a policy recommendation to mitigate legal uncertainty: an internal affairs doctrine for corporate joint ventures. Under this rule, parties would be allowed to choose the law that governs their joint venture and courts would honor that choice.

The final contribution was to empirically demonstrate the existence of joint venture networks. These complex networks further compound fiduciary conflicts and require us to update the theory of the firm.

DOI: https://doi.org/10.15779/Z38G73740T.

Copyright © 2018 California Law Review, Inc. California Law Review, Inc. (CLR) is a California nonprofit corporation. CLR and the authors are solely responsible for the content of their publications.

Sarath Sanga, Northwestern University Pritzker School of Law. Email: sanga@northwestern.edu. I thank Eric Talley, Robert E. Scott, Kerem Sanga, Jeffrey Rachlinski, Gabriel Rauterberg, Roberta Romano, James Pfander, Justin McCrary, Kate Litvak, Jeffrey Gordon, Victor Goldberg, James Texas Dawson, Richard R.W. Brooks, Patrick Bolton, Bernard Black, and Ian Ayres for very helpful comments. This research was supported by the Northwestern University Pritzker School of Law Faculty Research Program.

2. Alexander Pope, An Essay on Criticism pt. 2 (1709) (“A little Learning is a dang’rous Thing / Drink deep, or taste not the Pierian Spring . . . .”). ↑

3. The Restatement (Third) of Agency section 1.01 provides: “Agency is the fiduciary relationship that arises when one person (a ‘principal’) manifests assent to another person (an ‘agent’) that the agent shall act on the principal’s behalf and subject to the principal’s control, and the agent manifests assent or otherwise consents so to act.” ↑

4. See, e.g., Del. Gen. Corp. L. (DGCL) § 102(b)(7)(i) (2015); Revised Uniform Partnership Act (RUPA) § 404(b) (2017); Uniform Partnership Act (UPA) § 21 (1914). ↑

5. RUPA § 404(b)(3). ↑

6. Meinhard v. Salmon, 164 N.E. 545, 546 (N.Y. 1928). All jurisdictions have held that the default duties in partnership (undivided loyalty) also apply to joint ventures. See infra Part I.B. ↑

7. Meinhard, 164 N.E. at 548. ↑

8. Examples of large joint ventures among such companies include Boeing and Lockheed (aerospace), AMD and Fujitsu (integrated circuits), MolsonCoors and SABMiller (beverages), Forest and Merck (pharmaceuticals), General Mills and Nestle (food and beverage), Goodyear and Sumitomo (tires), Hasbro and Lucasfilm (toys), Fossil and Seiko (watches), Deere and Hitachi (heavy industry and farm equipment), and E-Trade and Softbank (retail investment and telecom).

   A large literature examines the structure and formation of corporate joint ventures. *See, e.g.*, Ronald J. Gilson, Charles F. Sabel & Robert E. Scott, *Contracting for Innovation: Vertical Disintegration and Interfirm Collaboration*, 109 Colum. L. Rev. 431 (2009) (studying enforcement of collaborative and long-term supply contracts); Gary Pisano, *The R&D Boundaries of the Firm: An Empirical Analysis*, 35 Admin. Sci. Q. 153 (1990) (on the decision between in-house versus external sources of research and development); Gary Pisano, *The Governance of Innovation: Vertical Integration and Collaborative Arrangements in the Biotechnology Industry*, 20 Res. Policy 237 (1991) (surveying governance structures of biotechnology ventures); Zenichi Shishido, *Conflicts of Interest and Fiduciary Duties in the Operation of a Joint Venture*, 39 Hastings L. J. 63 (1987) (describing varieties of fiduciary conflicts that could arise between co-venturer corporations). On the tension between competition and cooperation among corporate actors, see generally Adam M. Brandenburger & Barry J. Nalebuff, Co-opetition (1996). [↑](#footnote-ref-8)

9. On the law and economics of fiduciary duties, see Robert Cooter & Bradley J. Freedman, The Fiduciary Relationship: Its Economic Character and Legal Consequences, 66 N.Y.U. L. Rev. 1045 (1991) (on burdens of proof and appropriation of opportunities); Jeffrey N. Gordon, The Mandatory Structure of Corporate Law, 89 Colum. L. Rev. 1549 (1989) (on the nature and function of these duties as mandatory versus default); Jonathan R. Macey, An Economic Analysis of the Various Rationales for Making Shareholders the Exclusive Beneficiaries of Corporate Fiduciary Duties, 21 Stetson L. Rev. 23, 36–39 (1991). On the enforcement of covenants not to compete in executive employment contracts, see Sarath Sanga, Incomplete Contracts: An Empirical Approach, 34 J. L. Econ. & Org. (forthcoming 2018). For an analysis of the corporate opportunities doctrine from the perspective of contract theory, see Eric Talley, Turning Servile Opportunities to Gold: A Strategic Analysis of the Corporate Opportunities Doctrine, 108 Yale L. J. 277 (1998). On innovations in contract generally, see Kevin E. Davis, Contracts as Technology, 88 N.Y.U. L. Rev. 83 (2013).

   Parties can also eliminate fiduciary duties by opting out of partnership and instead electing a relation more akin to independent investors. This solution is found in either joint ventures that explicitly waive fiduciary claims or, equivalently, partnership agreements that would otherwise look like a joint venture but include a “No Joint Venture” clause. On the former, see, e.g., *Dime Box Petroleum Corp. v. Louisiana Land & Exploration Co.*, 938 F.2d 1144, 1147 (10th Cir. 1991) (fiduciary standard in joint venture lowered to “gross negligence or willful misconduct”). On the latter, see, e.g., Nordstrom, Inc., Agreement Between Nordstrom Credit Card Master Note Trust and Nordstrom fsb (Form 10-K Ex. 10.40) (Apr. 1, 2002), https://www.sec.gov/Archives/edgar/data/72333/000089102003001270/0000891020-03-001270-index.htm [https://perma.cc/74R4-U2MT] (which, because of the way profits and losses are shared, would have been treated as a partnership by default). *See also* George S. Geis, *An Empirical Examination of Business Outsourcing Transactions*, 96 Va. L. Rev. 241 (2010) (studying the nuanced shades between contract-like versus partnership-like relations in outsourcing arrangements). [↑](#footnote-ref-9)

10. See Henry Hansmann & Reinier Kraakman, Organizational Law as Asset Partitioning, 44 Eur. Econ. Rev. 807 (2000); see also Kenneth Ayotte & Henry Hansmann, Legal Entities as Transferable Bundles of Contracts, 111 Mich. L. Rev. 715 (2013); Henry Hansmann & Reinier Kraakman, The Essential Role of Organizational Law, 110 Yale L.J. 387 (2000). ↑

11. This is not the first article to appreciate the “fuzzy” nature of firm boundaries. See generally Stephen M. Bainbridge, The Board of Directors as Nexus of Contracts, 88 Iowa L. Rev. 1 (2002); William Klein, The Modern Business Organization: Bargaining Under Constraints, 91 Yale L.J. 1521 (1982). ↑

12. See, e.g., Cent. R.R. & Banking Co. v. Smith, 76 Ala. 572 (1884); New York & Sharon Canal Co. v. Fulton Bank, 1831 WL 3125 (N.Y. Sup. Ct. 1831); Sabine Tram Co. v. Bancroft, 40 S.W. 837, 838–39 (Tex. Civ. App. 1897) (“The general rule is well established that a corporation cannot enter into partnership with other corporations or individuals.”).

    Though no state expressly enabled corporations to form partnerships, a few never directly addressed the question. One example is New Jersey. *See* Van Kuren v. Trenton Locomotive & Mach. Mfg. Co., 13 N.J. Eq. 302 (Ch. 1861) (suggesting the question is novel but deciding the case on other grounds). The New Jersey legislature eventually provided the answer. *See* N.J. Stat. § 14A:3-1(1)(f), (m) (permitting corporations to purchase interests in partnerships and participate in them). [↑](#footnote-ref-12)

13. See, e.g., Boyd v. Am. Carbon-Black Co., 37 A. 937, 938 (Pa. 1897) (“A corporation may not avail itself of the defense, ultra vires, when the contract has been in good faith fully performed by the other party, and it has had the full benefit of the performance and of the contract.”). ↑

14. For example, in Allen & Sons v. Woonsocket Company, 11 R.I. 288, 301 (1876), the Supreme Court of Rhode Island permitted a Rhode Island corporation to form a partnership, but only because a single individual owned the corporation and, more importantly, the partnership “was a mere partnership at will, terminable at any moment by either party.” The court reasoned that “[i]f the partnership had been for a definite period, it might well be argued that the respondent had no right to make such a contract. But it was a mere partnership at will, terminable at any moment by either party. The respondent, therefore, did no more part with the control of the business than if it had employed [the other general partner] simply as agents, and its right to do that cannot very well be denied.” Id. ↑

15. See, e.g., Aurora State Bank v. Oliver, 62 Mo. App. 390 (1895) (finding that a corporation that purchased a share of a partnership could not be held liable even for the existing debts of the partnership, because the contract was void ab initio and the corporation could not be estopped from claiming that it was never a partner). ↑

16. See generally Larry Ribstein, The Rise of the Uncorporation 65–66 (2010). In theory, therefore, only a state legislature could have enabled a corporation to form a partnership (by altering the corporate charter). In practice, I am not aware of any such case. ↑

17. See, e.g., Cent. R.R. & Banking, 76 Ala. at 579 (“The general rule [is] that corporations created by an act of the legislature, or organized under general laws, can exercise only the powers expressly granted, the implied powers necessary and proper to carry into effect the express powers, and such incidental powers as pertain to the purposes of their creation . . . .”); see also Gunn v. Cent. R.R., 74 Ga. 509, 514 (1885). ↑

18. See Allen & Sons, 11 R.I. at 301 (“[A]greements between companies which create a partnership between the parties thereto are void. . . . [T]wo corporations contract[ing] for a permanent amalgamation . . . would [be] equivalent to the creation of a new corporation without the consent of parliament.”); Mallory v. Hananer Oil-Works, 8 S.W. 396, 399 (Tenn. 1888) (shareholders could not ratify partnership formation).

    Similarly, partnerships could not obtain a back-door limited liability privilege by incorporating. Jackson v. Hooper, 75 A. 568, 571 (N.J. 1910) (“The law never contemplated that persons engaged in business as partners may incorporate, with intent to obtain the advantages and immunities of a corporate form, and then, Proteuslike, become at will a copartnership or a corporation . . . .”). [↑](#footnote-ref-18)

19. Whittenton Mills v. Upton, 76 Mass. 582, 595 (1858). ↑

20. Id. at 600. ↑

21. Id. at 597 (emphasis added). ↑

22. The court emphasized “one obvious and important distinction” between a corporation before and after partnership formation. “An act of the corporation, done either by direct vote or by agents authorized for the purpose, is the manifestation of the collected will of the society. No member of the corporation, as such, can bind the society. In a partnership each member binds the society as a principal. If then this corporation may enter into partnership with an individual, there would be two principals, the legal person and the natural person, each having, within the scope of the society’s business, full authority to manage its concerns, including even the disposition of its property.” Id. at 595. ↑

23. Whittenton Mills demonstrates how prohibiting partnerships preserves the integrity of the corporate entity. Invalidating the partnership agreement had the effect of shielding the corporation from the personal creditors of one of its stakeholders, in this case from a would-be partner. Some scholars have argued that this entity-shielding role (or, more generally, “asset partitioning”) is in fact the principal contribution of organizational law. See Hansmann & Kraakman, Asset Partitioning, supra note 9, at 812 (arguing that contract law alone could not achieve the same result); Hansmann & Kraakman, Essential Role, supra note 9, at 429. ↑

24. See, e.g., Bates v. Coronado Beach Co., 41 P. 855 (Cal. 1895). In that case, the court first observed that the problem of corporate partnerships lies in the agency power of the partner. “The ground upon which this power [of a corporation to enter into a general partnership] is sometimes denied is that a partnership implies the power of each partner, under his authority as a general agent for all the purposes of the partnership, to bind the others by his individual acts, whereas the statutes under which a corporation exists require its powers to be exercised by a board of directors, and preclude it from becoming bound by the act of the one who may be only its partner.” Id. at 856. Highlighting the transaction at issue’s limited and contractual nature, the court then held that “the present case [presents] no question of agency in the management of the affairs of the corporation.” Id. ↑

25. See Chapline, Lewis & Co. v. Conant & Wheat, 3 W. Va. 507, 508 (1869) (“The participation in profits, thus broadly and generally stated, never has been the test of liability as a partner.”); Baxter v. Rodman, 20 Mass. 435, 438 (1826) (similar holding in an employer-employee setting); Atherton v. Tilton, 44 N.H. 452, 453 (1863) (same). In 1914, this rule was codified in UPA section 7. See also RUPA § 202(3) (2017). ↑

26. See, e.g., Hackett v. Multnomah Ry. Co., 906 P. 659, 662 (Or. 1885) (permitting a corporation to co-own a ferry service). ↑

27. See, for example, Central Lumber Company v. Schilleci, 148 So. 614, 615–16 (Ala. 1933), in which the court noted that “[i]t is well settled that, ‘notwithstanding a corporation has no power to enter into a partnership it may under a joint venture with others transact any business which is within the scope of its legitimate powers and thereby become liable on account of the fiduciary relation assumed, and a corporation may in furtherance of the object of its creation contract with an individual, although the effect of the contract may be to impose upon it the liability of a partner.’” Id. ↑

28. The most recent discussions of this in case law come from the 1980s. See, e.g., Boatman v. George Hyman Constr. Co., 276 S.E.2d 272, 274–75 (Ga. App. 1981) (“This anomaly [that the common law distinguishes joint venture and partnership even though they appear to be equivalent] seems to arise out of the court’s desire to permit a corporation to participate in a joint venture where corporate authority to enter into a partnership was lacking.”) (discussing Clement A. Evans & Co. v. Waggoner, 30 S.E.2d 915 (Ga. 1944)); E. Elec. Co. v. Taylor Woodrow Blitman Constr. Corp., 414 N.E.2d 1023, 1026 (Mass. App. Ct. 1981) (“The Whittenton Mills decision [that corporations cannot form partnerships], and others like it elsewhere, have led to the use of joint ventures for quasi-partnership operations of two or more corporations.”). ↑

29. Leo I. Colowick, The Corporation as a Partner, 1955 Wash. U. L. Q. 76 (1955); see also Frank L. Mechem, The Law of Joint Adventures, 15 Minn. L. Rev. 644 (1931) (arguing that the laws governing “joint adventure” and partnership were substantially similar). ↑

30. Modern charters, like modern corporate law, are “general” in that they enable any lawful business or business form. Rather than enumerating express provisions on what the corporation can do, charters simply declare that the corporation can do anything lawful under general corporate law. See, e.g., Amazon.com, Inc., Restated Certificate of Incorporation (Form 10-Q Ex.-3.1) (May 15, 2000) (“The purpose of this corporation is to engage in any lawful act or activity for which corporations may be organized under the General Corporation Law of Delaware.”); Exxon Mobile Corp., Restated Certificate of Incorporation (Form 10-Q E.-3.(I)) (Aug 4, 2011) (“The purposes for which the corporation is organized are to engage in any or all activities within the purposes for which corporations now or at any time hereafter may be organized under the New Jersey Business Corporation Act . . . , including but not limited to the following: [listing two pages of examples].”).

    *See also* Model Business Corporation Act (MBCA) § 2.02(c) (2002) (granting a suite of corporate powers by default); *id.* § 3.04 (limiting the grounds under which a corporation’s power to act may be challenged). Approximately half of the states have adopted the MBCA. There are analogous provisions in non-MBCA states. [↑](#footnote-ref-30)

31. See, e.g., DGCL § 122(11) (2015) (A corporation may “[p]articipate with others in any corporation, partnership, limited partnership, joint venture or other association of any kind, or in any transaction, undertaking or arrangement which the participating corporation would have power to conduct by itself, whether or not such participation involves sharing or delegation of control with or to others.”); Cal. Corp. Code § 207 (2005); N.Y. Bus. Corp. Law § 202(a)(15) (2017) and official commentary; Model Business Corporation Act § 3.02(9). ↑

32. Incorporation statutes generally permit “any person” to create a corporation and then include partnership in the definition of a person. See, e.g., Ariz. Rev. Stat. §§ 10-201, 10-140(22), 10-140(36) (2018). Six states state that “partnerships . . . may form [a corporation].” See Cal. Corp. Code § 200 (2005); DGCL § 101 (2015); Kan. Stat. 17-6001 (2016); Okla.. Stat. tit. 18 § 1005 (1986); Or. Stat. § 60.044 (2015). ↑

33. DGCL § 266 (2015). ↑

34. DGCL §§ 263, 267 (2015). ↑

35. DGCL § 354 (2015). ↑

36. In re Groff, 898 F.2d 1475, 1476 (10th Cir. 1990) (citing Stone v. First Wyo.Y

    Bank N.A., 625 F.2d 332, 340 (10th Cir.1980)); Stone v. First Wyo. Bank N.A., 625 F.2d 332, 340 (10th Cir.1980) (“As a general rule the substantive law of partnerships is applicable in determining the rights and liabilities of joint venturers and third parties.”); Zeibak v. Nasser, 82 P.2d 375, 380 (Cal. 1938) (“The rule is that the rights and liabilities of joint adventurers, as between themselves, are governed by the same principles which apply to a partnership.”); Total Holdings USA, Inc. v. Curran Composites, Inc., 999 A.2d 873, 875–76 (Del. Ch. 2009). ↑

37. See, e.g., Hansler v. Bass, 743 P.2d 1031, 1036 (N.M. Ct. App. 1987) (“Although that provision relates to partnership, we believe it equally applicable to a joint venture, since the latter is generally considered to be a partnership for a single transaction.”) (citing Bard v. Hanson, 68 N.W.2d 134 (Neb. 1955)). ↑

38. Partnership law “does not govern directly”; its application to joint venture is discretionary and courts are free to apply a different law or make exceptions if the circumstances warrant. Doiron v. Castonguay, 519 N.E.2d 260, 262 n.2 (Mass. 1988). Notably, the court failed to mention which other law would be applicable. Cases citing Doiron generally apply UPA. See, e.g., BPR Grp. Ltd. P’ship v. Bendetson, 906 N.E.2d 956 (Mass. 2009). New Hampshire follows a similar “by analogy” doctrine. See Miami Subs Corp. v. Murray Family Trust, 703 A.2d 1366, 1370 (N.H. 1997). ↑

39. See, e.g., Bd. of Trustees of W. Conference of Teamsters Pension Trust Fund v. H.F. Johnson Inc., 830 F.2d 1009 (9th Cir. 1987); Doe v. Yale Univ., 748 A.2d 834, 854 (Conn. 2000) (explaining this piecemeal application of partnership law to joint venture). This piecemeal adoption sometimes even plays out in statute. See Oklahoma Title Examination Standards ch. 13.7 (2015) (Conveyances to and by Joint Ventures). Section (D) codifies the Oklahoma common law rule that, as in partnership, one co-venturer can bind the other by acts that are within the scope of the venture. However, it is not clear if this rule is equivalent or merely analogous to the partnership scope of agency. ↑

40. See RUPA §§ 101(8), 601 (2017). ↑

41. Meridian Homes Corp. v. Nicholas W. Prassas & Co., 687 F.2d 228, 231 (7th Cir. 1982) (“[T]he Illinois Supreme Court created an exception to [the general rule that partnership law applies to joint venture] in the area of termination of joint venture agreements.”) (citing Maimon v. Telman, 240 N.E.2d 652 (Ill. 1968)). This is not a substantive exception and it is not clear why Illinois courts call it one. Illinois courts, like others, specifically state that a partner incurs contractual liability for early termination when the partnership agreement is for a definite term. Browne v. Ritchey, 559 N.E.2d 808, 811 (Ill. App. Ct. 1990). Moreover, partners can alter the default termination procedure through contract. RUPA § 406 (2017); UPA § 23 (1914). ↑

42. UPA §§ 24, 25, 27 (1914); RUPA §§ 501, 502, 503 (2017); RUPA § 502 cmt. ↑

43. Kay Inv. Co. v. Brody Realty No. 1, L.L.C., 731 N.W.2d 777 (Mich. Ct. App. 2006); 86 C.J.S., Tenancy in Common § 1–11. ↑

44. The default voting rule in partnership is majority rule. RUPA §§ 301, 401(j) (2017). Further, tenants in partnership cannot transfer their individual interest in property, but tenants in common can. ↑

45. Kay Inv. Co., 731 N.W.2d at 783. ↑

46. Montana adopted the same ownership and voting exception as Michigan but later expressly overruled it. Ivins v. Hardy, 179 P.2d 745, 749 (Mont. 1947) (creating the exception); Walsh v. Ellingson Agency, 613 P.2d 1381, 1384 (Mont. 1980) (expressly overruling Ivins v. Hardy); see also Robertson v. Robertson, 590 P.2d 113, 115 (Mont. 1978) (distinguishing Ivins v. Hardy). ↑

47. For example, the Michigan exception is arguably unintentional. To the best of my knowledge, the origin of this exception is the U.S. Supreme Court case of Clark v. Sidway, 142 U.S. 682 (1892), in which the court refused to find a partnership where two persons had formed a land speculation business because the business owned only one parcel. The court instead found that there was no business and that the parties were merely co-owners, which by default left them as tenants in common.

    By itself, *Clark* would have had no effect on joint venture law. However, a leading treatise and several state courts later cited *Clark* out of context as persuasive authority that joint venturers *always* hold real property as tenants in common, regardless of how large their business may be. *See* Swan v. Ispas, 37 N.W.2d 704, 706 (Mich. 1949) (“Joint adventurers take title to real estate purchased by them as tenants in common.”) (quoting 48 C.J.S., Joint Adventures, § 7, which in turn cites *Clark v. Sidway*).
    
    The citation is out of context because the Supreme Court had previously established that “a copartnership may exist in the purchase and sale of real property, equally as in any other lawful business” and because *Clark* is based on the “smallness” of the business. Thompson v. Bowman, 73 U.S. 316, 317 (1867). *Clark* did not apply to joint ventures in general nor even use the phrases “joint venture” or “joint adventure” or “joint enterprise”; it did not even cite (let alone distinguish) the earlier ruling in *Thompson*.
    
    This could also explain why Maryland federal courts apply the exception even though Maryland state courts do not. The federal court cites the old version of Corpus Juris Secondum (which used to cite *Clark*), perhaps under the presumption that Maryland state courts follow it. Compare the federal case, *Institutional Management Corporation v. Translation Systems, Inc.*, 456 F. Supp. 661, 665 (D. Md. 1978) (“Joint adventurers hold real estate as tenants in common”) (citing 48 C.J.S. 834) with a corresponding state case, *Madison National Bank v. Newrath*, 275 A.2d 495, 497–98 (Md. 1971) (holding that co-venturers held real property as tenants in partnership, rejecting evidence suggesting the parties held it as tenants in common). [↑](#footnote-ref-47)

48. Texas was the first. When Texas adopted RUPA in 1994, it amended the definition of partnership. The original text of RUPA provided that “the association of two or more persons to carry on as co-owners a business for profit forms a partnership, whether or not the persons intend to form a partnership.” RUPA § 202 (2017). To this the Texas legislature added: “whether the association is called a ‘partnership,’ ‘joint venture,’ or ‘other name.’” 1993 Tex. Sess. Law Serv. ch. 917 (H.B. 273) (codified Tex. Civ. Stat. art. 6132b-2.02 (expired Jan 1, 2010); replaced with Tex. Bus. Orgs. Code § 152.051 (2006)).

    Three years later, Maryland followed. The Maryland legislature adopted RUPA and amended RUPA’s definition of partnership with language identical to the Texas statute. 1997 Md. Laws ch. 654 (H.B. 251) (codified Md. Code Ann., Corps. & Ass’ns § 9A-202(a) (2017)).
    
    Both Texas and Maryland case law have explicitly acknowledged that these actions abolished the joint venture/partnership distinction. Blondell v. Littlepage, 991 A.2d 80, 91 (Md. 2010); Ingram v. Deere, 288 S.W.3d 886, 894 (Tex. 2009) (“Prior case law discusses differences between joint ventures and partnerships. We see no legal or logical reason for distinguishing a joint venture from a partnership on the question of formation of the entity.”) (citing the Texas statute that abolishes the distinction). [↑](#footnote-ref-48)

49. See Wardell v. Union Pacific Railroad Company, 103 U.S. 651 (1880), which is discussed at length in Harold Marsh, Are Directors Trustees? Conflict of Interest and Corporate Morality, 22 Bus. Law. 35, 35–39 (1966). ↑

50. See DGCL § 144 (2015); see also Tex. Bus. Orgs. Code § 21.418 (2006). ↑

51. See DGCL § 144; Benihana of Tokyo, Inc. v. Benihana, Inc., 906 A.2d 114 (Del. 2006) (on ex ante safe harbors for interested transactions); Fliegler v. Lawrence 361 A.2d 218 (Del. 1976) (on ex post ratification of interested transactions). This control yields not only case law, but also scholarship. See, e.g., Bernard Black & Reinier Kraakman, A Self-Enforcing Model of Corporate Law, 109 Harv. L. Rev. 1911, 1958–60 (1996) (arguing that, in emerging economies, corporate law should minimize the need to resort to the legal system); Melvin Eisenberg, Self-Interested Transactions in Corporate Law, 13 J. Corp. L. 997 (1988) (surveying state laws governing transactions between a corporation and one or more of its directors and officers); Zohar Goshen, The Efficiency of Controlling Corporate Self-Dealing: Theory Meets Reality, 91 Calif. L. Rev. 393 (2003) (applying the theory of property versus liability rules to analyze laws that regulate self-dealing). ↑

52. The fact that these terms work together—and are therefore complements—cautions against studying any one, individual type of provision in isolation. See generally Ronald J. Gilson, Value Creation by Business Lawyers: Legal Skills and Asset Pricing, 94 Yale L.J. 239 (1984). ↑

53. See supra note 7 for a list of examples. ↑

54. Boeing and Lockheed are two aerospace giants. By revenue, Boeing is the largest aerospace firm in the world and Lockheed is ranked third. See PricewaterhouseCoopers, Top 100 Aerospace Companies, 16 Flight Int’l 22, 31–32 (Sept. 2014), https://www.pwc.co.uk/aerospace-defence/assets/2014-aerospace-top-100.pdf [https://perma.cc/2ZQQ-LMCU]. ↑

55. Lockheed Martin Corp. & The Boeing Corp., Joint Venture Master Agreement (“ULA-JVA”) (Ex. 10.2) (May 2, 2005), http://www.sec.gov/Archives/edgar/data/936468/000119312505150203/dex102.htm [https://perma.cc/QQB5-2XEM]. ↑

56. See National Defense Authorization Act for Fiscal Year 1994, H.R. 2401, 103rd Cong. § 213 (2014). ↑

57. Both companies had acquired the basic technologies for these systems through mergers: Lockheed acquired its Atlas V system through a merger with Martin Marietta in 1995; Boeing acquired its Delta IV system through a merger with McDonnell Douglas in 1997. ↑

58. Press Release, U.S. Dep’t of Justice, Two Former Boeing Managers Charged in Plot to Steal Trade Secrets from Lockheed Martin (June 25, 2003), http://www.justice.gov/archive/criminal/cybercrime/press-releases/2003/branchCharge.htm [https://perma.cc/97BJ-UQX8]. ↑

59. Id. ↑

60. Id. ↑

61. Id. ↑

62. See Lockheed Martin Corp. v. Boeing Co., 314 F. Supp. 2d 1198 (M.D. Fla. 2004). ↑

63. Most of the following comes from the FTC case regarding ULA. See In re Lockheed Martin Corp, Boeing Co., & United Launch All., LLC, FTC File No. 051-0165, Docket No. C-4188 (2007), http://www.ftc.gov/enforcement/cases-proceedings/0510165/lockheed-martin-corporation-boeing-company-united-launch [https://perma.cc/5KLM-59ZS]. ↑

64. Commissioner Harbour noted, “DoD unequivocally has communicated its position to the Commission: the creation of ULA is critical to protect national security interests, and enabling these unique national security benefits to flow is more important to the public interest than preventing the loss of direct competition between Boeing and Lockheed.” Concurring Statement of Commissioner Harbour, In re Lockheed Martin Corp., Boeing Co., & United Launch All., L.L.C., FTC File No. 051-0165, Docket No. C-4188 (May 8, 2007), http://www.ftc.gov/enforcement/cases-proceedings/0510165/lockheed-martin-corporation-boeing-company-united-launch [https://perma.cc/63HZ-NZNU]. ↑

65. The settlement was folded into the joint venture agreement itself. See ULA-JVA, supra note 54, at 21, Section 5.12 Stay of Civil Proceeding. ↑

66. Meinhard v. Salmon, 164 N.E. 545, 545–46 (N.Y. 1928). ↑

67. One might also consider similar promises in employee contracts. For a study of how CNCs interact with law and industrial organizations, see Ronald J. Gilson, The Legal Infrastructure of High Technology Industrial Districts: Silicon Valley, Route 128, and Covenants Not to Compete, 74 N.Y.U. L. Rev. 575 (1999). ↑

68. The joint venture agreement is organized into 80 sections and is about 30,000 words (about one-and-a-half times the length of this Article). This includes only the main text. It excludes the table of contents, signature pages, and attachments. See ULA-JVA, supra note 54. ↑

69. See infra Part IV.B. ↑

70. See supra Part II.A. ↑

71. Note 69 gives the first half of the licensing agreement in the ULA-JVA. The second half provides that this license is exclusive during the term of the CNC, but carves out an exception to this: Boeing and Lockheed can continue to use rocket-related IP in markets that do not overlap with the CNC. The text goes on to make the “ordinary course” exemption: “[P]rovided, however, that notwithstanding the foregoing, (A) Boeing may license or sublicense a Person to use Licensed Boeing Intellectual Property within the Field of Use: (1) to the extent necessary to allow such Person to make products or sell services for use by Boeing in Boeing’s ordinary course of business; or (2) as part of the sale to such Person of products or services in the ordinary course of Boeing’s business, to the extent the applicable Licensed Boeing Intellectual Property is used in such products or services, and (B) Boeing may, in connection with the sale of a portion of a business or product line of Boeing to a Person, license, sublicense, transfer, assign, convey or sell Licensed Boeing Intellectual Property used in such business or product line to such Person under terms permitting its use within the Field of Use, but not in a manner that would violate the provisions of Section 5.13 if used by Boeing in that manner.” ULA-JVA, supra note 54, at 18, Section 5.08(a)(i) (emphasis added). The provision for Lockheed is similar. ↑

72. RUPA § 404(b)(3) (2017). ↑

73. ULA-JVA, supra note 54, at 24, Section 5.13(b)(iii). ↑

74. See generally Aaron S. Edlin & Stefan Reichelstein, Holdups, Standard Breach Remedies, and Optimal Investment, 86 Am. Econ. Rev. 478 (1996) (reviewing the literature on holdups and finding that noncontingent contracts can prompt efficient investment by balancing holdup contingencies against breach remedies); Oliver E. Williamson, Transactions-Cost Economics: The Governance of Contractual Relations, 22 J.L. & Econ. 233 (1979) (examining transaction-specific governance and relational contracting). ↑

75. Antitrust law applies differently in the context of joint venture versus competition. For example, under section 1 of the Sherman Act, price-fixing arrangements are per se illegal. Catalano, Inc. v. Target Sales, Inc., 446 U.S. 643, 647 (1980). In the context of a joint venture, however, the rule of reason applies. Texaco Inc. v. Dagher, 547 U.S. 1, 8 (2006). ↑

76. To summarize, the FTC required that “(1) ULA cooperate on equivalent terms with all providers of government space vehicles; (2) the space vehicle businesses of Boeing and Lockheed provide equal consideration and support to all launch services providers when seeking any US government delivery in orbit contract; and (3) Boeing, Lockheed, and ULA safeguard competitively sensitive information obtained from other providers of space vehicles and launch services.” Analysis of Agreement Containing Consent Order to Aid Public Comment, In re Lockheed Martin Corp., Boeing Co., & United Launch All., L.L.C., FTC File No. 051-0165, Docket No. C-4188 (Oct. 3, 2006), http://www.ftc.gov/enforcement/cases-proceedings/0510165/lockheed-martin-corporation-boeing-company-united-launch [https://perma.cc/9BCG-96KW]. ↑

77. ULA-JVA, supra note 54, at 1. Section 2.01 further provides that “[p]rior to the Closing, the Members shall cause the Company to be formed as a Delaware limited liability company by filing a certificate of formation with the Secretary of State of the State of Delaware.” Id. ↑

78. Id. ↑

79. See Boeing Co., Item 1.01 (Form 8-K) (May 4, 2005). Boeing and Lockheed each appoint three members to the six-member board. ↑

80. See The Bible, 1 Kings 3:16–28. ↑

81. Supra Part I.B. and note 37. ↑

82. See Del. Code Ann. tit. 6, § 18-802 (1995) (court-ordered dissolution of joint venture LLCs); DGCL § 273 (2015) (court-ordered dissolution of joint venture corporations). Delaware courts have noted that the doctrine covering these two statutes are analogous. See Vila v. BVWebTies, LLC, No. 4308-VCS, 2010 WL 3866098, at 202 (Del. Ch. Oct. 1, 2010) (considering a court-ordered dissolution of a joint venture LLC); Wah Chang Smelting & Ref. Co. of Am. v. Cleveland Tungsten Inc., No. 1324-K, 1996 WL 487941 (Del. Ch. Aug. 19, 1996) (applying the “not reasonably practicable” standard for dissolving a joint venture LLC to a joint venture corporation); see also* DGCL § 226 (2015) (appointment of custodian to resolve deadlock in a joint venture corporation). ↑

83. ULA-JVA, supra note 54, at 17, Section 5.08(a). ↑

84. Id. ↑

85. Id. at 2, 17, Sections 5.08(a) and 2.08. ↑

86. Whittenton Mills v. Upton, 76 Mass. 582 (1858). ↑

87. See Part I.A. ↑

88. The analysis may change in the case of large and activist shareholders. See Iman Anabtawi & Lynn Stout, Fiduciary Duties for Activist Shareholders, 60 Stan. L. Rev. 1255 (2008). ↑

89. Universal Studios, Inc. v. Viacom, Inc., 705 A.2d 579 (Del. Ch. 1997). ↑

90. Id. at 593. ↑

91. Id. at 594–95 (emphasis added). ↑

92. The most important exception, which came from trade secret law, is no longer available. California courts previously suggested that, in theory, an employer might be able to prevent a former employee from working for a competitor if a trade secret would be “inevitably disclosed.” See, e.g., Muggill v. Reuben H. Donnelley Corp., 398 P.2d 147, 149 (1965) (Section 16600 “invalidates provisions in employment contracts prohibiting an employee from working for a competitor after completion of his employment or imposing a penalty if he does so . . . unless they are necessary to protect the employer’s trade secrets”). More recently, however, California courts have categorically rejected the inevitable disclosure doctrine; the exception is no longer available. See Whyte v. Schlage Lock Co., 125 Cal. Rptr. 2d 277, 293–94 (2002) (“Lest there be any doubt about our holding, our rejection of the inevitable disclosure doctrine is complete. If a covenant not to compete (which would include, for example, a nonsolicitation clause), is part of the employment agreement, the inevitable disclosure doctrine cannot be invoked to supplement the covenant, alter its meaning, or make an otherwise unenforceable covenant enforceable.”). ↑

93. Kelton v. Stravinski, 41 Cal. Rptr. 3d 877 (2006). ↑

94. Id. at 879. ↑

95. Id. ↑

96. Id. at 882. ↑

97. Parties cannot overcome this uncertainty with a choice of law clause. Even if a contract is governed by a law that would allow a CNC, California courts will invalidate it if it affects a California employer. See Application Grp., Inc. v. Hunter Grp., Inc., 72 Cal. Rptr. 2d 73 (1998). Parties also may not be able to overcome this problem by choosing a non-California forum. In Comedy Club, Inc. v. Improv West Associates, 553 F.3d 1277 (9th Cir. 2009), the court used section 16600 to vacate an arbitration award that would have enforced a CNC. This was a bold holding because, under federal law, a mistake in law is not sufficient to vacate an award; the standard of review is limited to egregious procedural defect, such as corruption, partiality, or ruling on issues or parties not subject to the contract. See 9 U.S.C. § 10(a) (2018). Furthermore, the Comedy Club case concerned a CNC that prevented opportunistic behavior during the term of the contract. The contract at issue was a trademark agreement that granted Comedy Club an exclusive license to develop a nationwide chain of clubs under the “Improv” brand. The term of the CNC was coterminous with the license, and it did not prevent, for example, any employee from seeking employment at a competing club. Nevertheless, Improv West leveraged section 16600 to get out of the deal and open its own competing clubs under the Improv brand. ↑

98. See, e.g., Censor v. ASC Techs. of Conn., LLC, 900 F. Supp. 2d 181, 214 (D. Conn. 2012) (“Joint venturers owe to one another fiduciary duties akin to those owed by partners in a partnership.”); Bank of California v. Connolly, 111 Cal. Rptr. 468, 477 (1973) (“Although a partnership ordinarily involves a continuing business, whereas a joint venture is usually formed for a specific transaction or a single series of transactions, the incidents of both relationships are the same in all essential respects.”); Hooper v. Yoder, 737 P.2d 852, 857 n.4 (Colo. 1987) (“Partners as well as joint venturers are fiduciaries with respect to each other and owe to each other the highest duty of loyalty.”); Meinhard v. Salmon, 164 N.E. 545, 546 (N.Y. 1928); Pan Am. Trade & Inv. Corp. v. Commercial Metals Co., 38 Del. Ch. 435, 440 (1959) (“The relationship between joint adventurers, like that existing between partners, is fiduciary in character and imposes upon all the participants the utmost good faith, fairness, and honesty in their dealings with each other with respect to matters pertaining to the joint enterprise . . . .”). On altering default contract duties, see generally Ian Ayres, Regulating Opt-Out: An Economic Theory of Altering Rules, 121 Yale L.J. 2032 (2012). ↑

99. See Sarath Sanga, Choice of Law: An Empirical Analysis, 11 J. Empirical Legal Stud. 894 (2014), which analyzed all choice of law clauses in material contracts disclosed to the Securities and Exchange Commission (SEC). The most common choice was New York (27 percent), followed by Delaware (12 percent) and California (11 percent). New York is perhaps somewhere between California and Delaware in the extent to which it permits alteration of fiduciary duties. However, its statute follows the original Uniform Partnership Act of 1914 (UPA), which does not provide a clear altering rule. See N.Y. P’Ship Law § 43(1) (2017). The analogous UPA provision is § 21(1). See UPA § 21(1) (1914). ↑

100. Thirteen states have not adopted some form of RUPA: Georgia, Indiana, Louisiana, Massachusetts, Michigan, Missouri, New Hampshire, New York, North Carolina, Pennsylvania, Rhode Island, South Carolina, and Wisconsin. Strangely, the California statute uses slightly different wording, but the differences are not substantive. RUPA § 103(b) provides: (b) The partnership agreement may not: (3) eliminate the duty of loyalty, but: (i) the partnership agreement may identify specific types or categories of activities that do not violate the duty of loyalty, if not manifestly unreasonable; or (ii) all of the partners or a number or percentage specified in the partnership agreement may authorize or ratify, after full disclosure of all material facts, a specific act or transaction that otherwise would violate the duty of loyalty. Cal. Corp. Code § 16103(b) states: (b) The partnership agreement may not . . . (3) Eliminate the duty of loyalty . . . but, if not manifestly unreasonable . . . . (A) The partnership agreement may identify specific types or categories of activities that do not violate the duty of loyalty. (B) All of the partners or a number or percentage specified in the partnership agreement may authorize or ratify, after full disclosure of all material facts, a specific act or transaction that otherwise would violate the duty of loyalty. ↑

101. Cal. Corp. Code § 16103(b) (2005) (emphasis added). Parties can also alter the voting threshold above which partners can permit activities that would violate the duty (after full disclosure). The default threshold is unanimity. Id. at § 16103(b)(3)(B). ↑

102. The standard of review is “not manifestly unreasonable.” Cal. Corp. Code § 16103(b). ↑

103. Del. Code Ann. tit. 6, § 15-103(b) (1995) (replacing RUPA §§ 103(b)(3), 15-103(f) (2017)); see also Del. Code tit. 6, § 17-1101(d)–(f) (1995) (granting similar provisions for limited partnerships). ↑

104. See Del. Code Ann. tit. 6, § 15-103(d) (“It is the policy of [Delaware partnership law] to give maximum effect to the principle of freedom of contract and to the enforceability of partnership agreements.”). ↑

105. See Del. Code Ann. tit. 6, §§ 15-404(b)(1), 15-103(b) (1995). ↑

106. See RUPA §§ 404(b)(1), 103(b) (2017). ↑

107. See UPA § 20 (1914) (“Partners shall render on demand true and full information of all things affecting the partnership to any partner . . . .”); N.Y. P’Ship Law § 42 (2017) (adopting UPA § 20); RUPA § 403 (2017) (replacing UPA section 20 with a more comprehensive description of “books and records”); Cal. Corp. Code § 16403 (2005) (adopting RUPA). Once again, however, there is a hint of ambiguity in UPA. See Donald J. Weidner, Three Policy Decisions Animate Revision of Uniform Partnership Act, 46 Bus. Law. 427, 453–54 (1991) (discussing UPA §§ 19, 20 (1914)). Delaware replaced the RUPA provision on disclosure of books and records with a much more comprehensive provision that specifically covers items such as tax returns, trade secrets, and forum selection. Del. Code Ann. tit. 6, § 15-403(a)(2) (1995). ↑

108. With only one exception, there are currently no statutes designed for joint ventures between corporations. The one exception is Delaware, which provides two statutes (as well as accompanying case law) that provide a default procedure for court-ordered dissolution of a joint venture corporation or joint venture LLC. See supra note 81. ↑

109. For an analysis of an analogous movement to enforce choice of forum in intra-corporate disputes, see Roberta Romano & Sarath Sanga, The Private Ordering Solution to Multiforum Shareholder Litigation, 14 J. Empirical Legal Stud. 31 (2017); see also DGCL § 115 (2015). ↑

110. See In re Sagent Tech., Inc., 278 F. Supp. 2d 1079, 1087 (N.D. Cal. 2003) (“In general, courts in California follow this rule and apply the law of the state of incorporation in considering claims relating to internal corporate affairs.”) (citing Cal. Corp. Code § 2116). But see Cal. Corp. Code § 2115 (2005) (providing statutory exceptions to the internal affairs doctrine). ↑

111. Gilson, supra note 66. ↑

112. A substantial literature has investigated several features of this claim. See, e.g., Sanga, Incomplete Contract, supra note 8 (showing how employers design discretionary severance packages to self-enforce covenants not to compete in California); Bruce Fallick, Charles A. Fleischman & James B. Rebitzer, Job-Hopping in Silicon Valley: Some Evidence Concerning the Microfoundations of a High-Technology Cluster, 88 Rev. Econ. & Stat. 472 (2006) (showing that labor mobility is particularly high in Silicon Valley, even compared to other geographic clusters of technology firms); Mark J. Garmaise, Ties that Truly Bind: Noncompetition Agreements, Executive Compensation, and Firm Investment, 27 J.L. Econ. & Org. 376 (2011) (exploiting variation in CNC permissiveness across US states to show that CNCs promote investments in human capital); Matt Marx, Deborah Strumsky & Lee Fleming, Mobility, Skills, and the Michigan Non-compete Experiment, 55 Mgmt. Sci. 875 (2009) (exploiting a natural experiment in Michigan to show that CNC enforcement decreases labor mobility); Sampsa Samila & Olav Sorenson, Noncompete Covenants: Incentives to Innovate or Impediments to Growth, 57 Mgmt. Sci. 425 (2011) (reporting lower levels of entrepreneurship in states that more readily enforce CNCs); Toby E. Stuart & Olav Sorenson, Liquidity Events and the Geographic Distribution of Entrepreneurial Activity, 48 Admin. Sci. Q. 175 (2003) (same). On the prevalence of CNCs, see generally Norman D. Bishara, Kenneth J. Martin & Randall S. Thomas, An Empirical Analysis of Noncompetition Clauses and Other Restrictive Postemployment Covenants, 68 Vand. L. Rev. 1 (2015); Evan Starr, James J Prescott & Norman D. Bishara, Noncompetes and Employee Mobility (U. Mich. L. & Econ., Research Paper No. 16-03, 2017); Evan Starr, Norman D. Bishara & James J. Prescott, Noncompetes in the U.S. Labor Force (2017) (manuscript) (on file with author). ↑

113. BAE was randomly selected from among the top twenty aerospace firms. See PricewaterhouseCoopers, supra note 53. ↑

114. I proceeded by first searching through the most recent 10-K filed by each company to the SEC. These are available through the SEC’s online Electronic Data Gathering, Analysis, and Retrieval (EDGAR) database. I searched for any reference to a “strategic partnership” or “joint venture.” I augmented this by using the same keywords to search through news article databases on Google and LexisNexis. ↑

115. For example, the FADEC Alliance is a joint venture between General Electric and FADEC International, which is a joint venture between BAE Systems and Safran. The FADEC Alliance was created to supply components to CFM International, which is a joint venture between General Electric and Safran. ↑

116. See, e.g., Buy American Act of 1933 (41 U.S.C. §§ 8301–8305 (2018), as amended, on federal procurement generally); the Berry Amendment (10 U.S.C. § 2533a (2018), as amended, on military procurement of food, clothing, and related items). For an overview, see the report by the Congressional Research Service, John R. Luckey, Cong. Res. Serv., Domestic Content Legislation: The Buy American Act and Complementary Little Buy American Provisions (2012), http://fas.org/sgp/crs/misc/R42501.pdf [https://perma.cc/KT6F-KZ69]. ↑

117. For example, NATO missile systems come from a joint venture among BAE Systems (UK), Airbus Group (headquartered in Netherlands, but with divisions in several European states), Finmeccanica (Italy), and Lockheed Martin (US). NATO also manages the joint venture among BAE Systems, Airbus Group, and Finmeccanica that produces the “Eurofighter” jet. See NATO, NATO Logistics Handbook 13 (2012), https://www.nato.int/docu/logi-en/logistics_hndbk_2012-en.pdf [https://perma.cc/9P43-BN8R]; see also Eurofighter Typhoon, About Us, Eurofighter Typhoon, https://www.eurofighter.com/about-us [https://perma.cc/6J9N-MZS6] (last visited Sept. 8, 2018). ↑

118. See, e.g., John Bussey, China Venture Is Good for GE but Is it Good for U.S.?, Wall Street J. (Sept. 30, 2011), https://www.wsj.com/articles/SB100014240
     52970204226204576601211373125234?ns=prod/accounts-wsj [https://perma.cc/ME28-7M8G] (discussing a joint venture between General Electric and a large state-owned Chinese aerospace company). ↑

119. Boeing was, and continues to be, a partner in Sea Launch, which began as a partnership between Boeing, RSC Energia, and two other firms. The venture was created in 1995. The other co-venturers are Kvaerner Group (since merged with Aker Solutions of Norway), and SDO Yuzhnoye/PO Yuzhmash (Ukraine). The shares were Boeing (40 percent), RSC Energia (25 percent), Kvaerner Group (20 percent), and SDO Yuzhnoye/PO Yuzhmash (15 percent). After a reorganization in 2010 (well after the establishment of ULA), Boeing’s share was reduced to 2.5 percent. Lockheed’s joint venture with RSC Energia was like Sea Launch in that it also catered launch services to commercial buyers. The venture was also created in 1995 and involved one other company, Khrunichev Research and Production Space Center, a large Russian aerospace firm. The name of the venture is International Launch Services. It continues to operate without Lockheed’s involvement. ↑

120. Medium Earth orbit refers to orbital altitudes greater than 2,000 kilometers above sea level. A particularly convenient orbital altitude lies just at the boundary of medium and high Earth orbit (35,786 km). Satellites that orbit the equator at this altitude achieve an orbital path such that they appear to be stationary in the sky relative to an observer on Earth (“geostationary orbit”). This is convenient because receivers on Earth then do not have to deal with problems relating to tracking satellites as they move across the sky. ↑

121. The ULA CNC explicitly acknowledges this. See ULA-JVA, supra note 54, at 25, § 5.13(d) (“Nothing in this Section 5.13 shall be deemed to prohibit, limit or restrict in any way any activities of (i) Boeing or its Subsidiaries related to Sea Launch vehicles.”). ↑

122. However, Lockheed decided to divest before signing the deal with Boeing. ↑

123. 11 = 24 – 1 – 4. (The power set minus the empty set minus each individual firm.) ↑

124. We observe joint ventures of joint ventures. See supra note 104. ↑

125. See Oliver Hart, Firms, Contracts, and Financial Structure (1995) (ownership); Oliver E. Williamson, The Economic Institutions of Capitalism (1985) (control); Ronald H. Coase, The Nature of the Firm, 4 Economica 386 (1937) (transaction costs); Michael C. Jensen & William H. Meckling, Theory of the Firm: Managerial Behavior, Agency Costs and Ownership Structure, 3 J. Fin. Econ. 305 (1976) (contract). ↑