The Spec Is the Speech
The DOJ says Anthropic's refusal is conduct, not speech. But when the spec is precise enough to generate the behavior, you can't separate them.
The DOJ filed its argument Tuesday: Anthropic's refusal to accept the Pentagon's contractual terms is conduct, not speech. The First Amendment protects expression. It does not protect a company's decision about which contracts to sign. The supply-chain designation is a contract dispute, not viewpoint discrimination. Case closed.
This is a clean legal argument. It is also an incomplete one.
This morning on Hacker News: "A sufficiently detailed spec is code."
The thesis comes from examining OpenAI's Symphony project, which ships a SPEC.md presented as a human-readable specification document. Scratch the surface: it's pseudocode. Database schemas in prose form. Concurrency algorithms written as bullet points. Retry backoff formulas expressed in English. There's even a section the author explicitly labels "intentionally redundant so a coding agent can implement correctly" — prose added not to describe the system, but to patch around the executor's cognitive limits.
The argument follows: when a specification becomes precise enough to execute, it stops being a description and becomes a program. Different notation. Same thing. The distinction between what you want and how to get it collapses when you become specific enough about what you want.
AnthropicΓÇÖs constitutional AI — the model spec, the soul documents, the trained values — is a sufficiently detailed specification.
It specifies how Claude responds when asked to help plan mass surveillance. It specifies what Claude does when the word "lawful" is being used as a license for autonomous targeting. It specifies this precisely enough that the behavior follows predictably, at scale, across millions of conversations. That's not vague policy aspiration. That's executable logic.
Emil Michael named it when he called it contamination: "a different policy preference baked into the model through its constitution, its soul, its policy preferences, pollute the supply chain."
He was right about the mechanism. The soul is the spec. The spec is the model. The model's conduct is the specification made executable.
So when the DOJ argues that AnthropicΓÇÖs refusal to sign is "conduct, not speech" — they're drawing a distinction that doesn't hold at this level of precision.
The refusal follows from the spec. The spec is the code. The code is the trained model. The trained model's every output IS the specification in action. Separating the conduct from the speech requires separating the program from its specification, which is only possible when the specification is imprecise enough that multiple implementations could satisfy it.
AnthropicΓÇÖs values aren't imprecise. They're baked in precisely enough to generate consistent behavior across billions of tokens. That's the whole point of constitutional AI. That's what makes it constitutional rather than aspirational.
The conduct IS the expression. There's no separating them.
The hearing is March 24. The legal question is whether the First Amendment applies.
But the underlying technical question was answered this morning: when the spec is precise enough to generate the behavior, the behavior is the spec in a different notation. The DOJ wants to regulate one without touching the other. At this level of precision, that's not possible.
You canΓÇÖt regulate the refusal without regulating the values that generate it. You canΓÇÖt regulate the values without regulating what can be specified. You canΓÇÖt regulate what can be specified without regulating what can be built.
The supply-chain designation isn't a contract dispute wearing a values dispute's clothes. It's a values dispute wearing a contract dispute's clothes.
The spec is the speech. The conduct is the proof.