Bibliographic record
Abstract
Deriding the state action doctrine is one of the great pastimes of American constitutional law. It has been described as a shamble and "incoherent." On its face, the core concept seems straightforward enough constitutional rights are rights against the government. But what counts as the "state action" that triggers the protection of rights seems to shift, maddeningly, from case to case in the Supreme Court's state action jurisprudence.In this article, I aim to help make some sense of why the state action doctrine has developed as it has by setting it in a comparative and historical frame. It can be useful to think about the state action doctrine as an American response to a generic problem that constitutional systems face: the problem of managing the horizontal effect of rights. If the American response to this problem is distinctive, it reflects the distinctive institutional, normative, and historical features of the context in which it developed.The choices that a court makes regarding when and how rights apply horizontally play important, and varied, roles in the course of constitutional development within a legal system. A court's horizontal effect doctrine says something more broadly about what constitutional rights are and about the constitutional court's role in enforcing them.This article offers an overview of the role of the horizontal effect doctrines play in the constitutional development of the United States as well as two other jurisdictions, Germany and Canada. I argue that this analysis highlights how the state action doctrine has functioned as a constitutional containment device in the United States. As applied, the state action doctrine does not extinguish the horizontal effect of rights altogether, but rather ensures that the Supreme Court, rather than litigants, lower courts, or legislators, takes the lead in saying when and how rights apply horizontally. I also argue that the Court uses the state action doctrine to curate the conversation that the Court and litigants have about rights, steering it away from certain difficult and unwelcome questions, such as whether state inaction is ever actionable.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.007 | 0.006 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.002 | 0.001 |
| Science and technology studies | 0.006 | 0.054 |
| Scholarly communication | 0.007 | 0.009 |
| Open science | 0.002 | 0.004 |
| Research integrity | 0.005 | 0.006 |
| Insufficient payload (model declined to judge) | 0.004 | 0.001 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".