Back to Library

    GOVERNANCE · 7 MIN READ

    What Is the Private Domain?

    This is where we start exploring what separates the public domain from the private domain: what belongs to government, and what people build for themselves through lawful agreement. Everything else on this site builds from here.

    The line every legal system draws.

    Walk into any functioning legal system and you'll find the same basic division. On one side sits the public domain: government, its agencies, and the entities it charters to carry out public functions, subject to public oversight because they exercise public power. On the other side sits everything people build for themselves, on their own initiative, answerable to the private agreements, contracts, and governing documents they create for themselves rather than to a regulator's constraints.

    The private domain is not a loophole. It is not a gray zone courts tolerate reluctantly, and it is not some realm only available to a select few. It is a body of doctrine the United States Supreme Court has protected, defined, and refined for well over a century, because the founders understood that a republic where every church, association, and family trust ultimately answers to the state is not a free one.

    This article is the starting point. Everything else in this library, on private membership associations, trusts, ministries, and 508(c)(1)(A) organizations, is a more detailed map of one region within this domain of jurisdiction.

    Three pillars, one principle.

    The private domain isn't a single legal doctrine. It's the name for a pattern that shows up across three distinct areas of law, each reinforcing the same idea from a different direction: people have the right to organize their own affairs, and courts will not run those affairs for them.

    1. The right to associate privately.

    NAACP v. Alabama, 357 U.S. 449 (1958), is the cornerstone here. Alabama tried to force the NAACP to hand over its membership lists. The Court said no: compelled disclosure of who belongs to a private association can chill the very right to associate, and the First Amendment protects against that chill. The case arrived in a civil rights context, but the principle it established has outlasted that context: a private association's membership, and its internal affairs, are not the government's to inspect on demand.

    Roberts v. United States Jaycees, 468 U.S. 609 (1984), sharpened the point by drawing a distinction that still matters: intimate associations (family, close personal relationships) get the strongest protection, while expressive associations (organizations formed around a shared belief or purpose) are protected against government action that would force them to change who they are or what they stand for. Boy Scouts of America v. Dale, 530 U.S. 640 (2000), applied that expressive-association protection concretely: an organization with a genuine expressive purpose has the right to decide who leads and represents it, even when a state anti-discrimination law says otherwise.

    Together, these cases establish the associational pillar of the private domain: you have the right to form a group, define its purpose, govern its own membership, and keep its internal affairs private. That right has independent constitutional weight, not merely the government's permission.

    2. The right of a religious body to govern itself.

    Watson v. Jones, 80 U.S. 679 (1871), is the foundational case in what's now called the church autonomy doctrine. The dispute was ordinary enough (a fight over who controlled a local church after a denominational split), but the Court's holding was not ordinary at all: civil courts have no authority to resolve questions of religious doctrine, polity, or internal discipline. Where a dispute is ecclesiastical in nature, the court's job ends and the religious body's own governing structure takes over.

    Kedroff v. Saint Nicholas Cathedral, 344 U.S. 94 (1952), applied that principle against a legislature, not just a court: a state law that transferred control of a church from one religious authority to another was unconstitutional, because the state has no power to decide which religious authority is the legitimate one. And Hosanna-Tabor Evangelical Lutheran Church v. EEOC, 565 U.S. 171 (2012), extended the doctrine into the modern employment-law era, recognizing a ministerial exception that shields a religious organization's choice of its own ministers from civil employment-discrimination claims.

    This is the private domain's second pillar, and its oldest: a religious body's governance, doctrine, and choice of who leads it belong to that body, not to a judge and not to a legislature.

    3. The right to hold property on your own terms.

    The private domain also has deep roots in trust law: the long-recognized right of a person or group to place property under a defined set of governing terms, a trust instrument, a charter, a set of bylaws, administered according to those terms rather than by default public rules. A trust is, in a real sense, a private government for a defined pool of assets and purposes: it has its own constitution (the trust instrument), its own officers (trustees), and its own beneficiaries. So long as it operates within the law, courts enforce its terms rather than rewriting them.

    This is what makes trusts, associations, and religious bodies structurally related, even though they serve different purposes: each is a form of private self-governance the law recognizes and protects, rather than a public function the law administers.

    What the private domain is not.

    The private domain does real legal work, which is exactly why it's worth being precise about its limits: precision is what gives it authority.

    The private domain is not a loophole around generally applicable law. It does not mean an organization is exempt from laws of general application simply because it calls itself private, and it is not a mechanism for avoiding legitimate obligations, contractual, criminal, or otherwise. What it does mean is narrower and, we'd argue, more durable: on matters of internal governance, doctrine, membership, and the terms on which private property is held, the government does not get to substitute its judgment for the judgment of the people who built the organization. That is a meaningful, court-protected line, and like every real legal line, it has an inside and an outside. Knowing exactly where that line runs, for your specific structure and your specific purpose, is what a real legal review is for.

    Why this matters for how you build.

    If you are forming a ministry, a private membership association, or a trust-based structure, you are not just picking a legal wrapper. You are deciding how much of your governance sits inside the private domain and how much sits outside it. A structure built with real attention to Watson, NAACP v. Alabama, and the trust-law tradition behind it will hold up differently than one built on the label alone. That distinction, between a structure with real doctrinal footing and one without it, is the difference this entire library exists to explain.

    The pieces that follow this one go deeper into each pillar: what a private membership association actually is and isn't, how the church autonomy doctrine applies in practice, and what a trust can and can't do for a ministry's long-term stability. This article is the map; those are the roads.

    Explore the full case record behind this article in the Lawful Precedent library, including Watson v. Jones, NAACP v. Alabama, Roberts v. United States Jaycees, Boy Scouts of America v. Dale, Kedroff v. Saint Nicholas Cathedral, Hosanna-Tabor v. EEOC, and Jones v. Wolf.

    BACK TO THE LIBRARY