Constitutional AI is a training approach where a model is given a written set of principles — a constitution — and asked to critique and revise its own answers against those principles before that improved data is used for further training. Instead of a human rater flagging every problematic response one at a time, the model does a first pass of self-correction, and humans (or another model) review and refine from there. It is less a replacement for human oversight than a way to make that oversight go further.
What changed in 2026
- Multi-document constitutions became common. Rather than one flat list of principles, several labs now layer a base constitution with domain-specific addenda (coding, medical-adjacent topics, agentic tool use) that get selectively applied by context.
- Constitutions started getting version-controlled and published alongside model cards, making it easier to audit what changed between model releases and correlate it with behavior shifts.
- Self-critique got combined with process supervision. Instead of only critiquing final answers, some pipelines now have models critique intermediate reasoning steps against the constitution, catching problems before they reach the output.
- Adversarial constitution testing matured. Red teams increasingly probe not just model outputs but the constitution itself, looking for principles that conflict or that a model can satisfy in unintended ways — often using the same jailbreak patterns attackers use against deployed models.
How the training loop actually works
- The model generates an initial response to a prompt, including prompts specifically chosen to elicit borderline behavior.
- The model critiques its own response against the written constitution, identifying where it may have violated a principle.
- The model revises the response based on its own critique.
- The revised, improved responses become training data for a supervised fine-tuning step, and often feed a preference model used in a subsequent RLHF-style stage.
- Human review samples the pipeline at each stage to catch cases where self-critique missed something or introduced a new problem.
The key property is that steps 1–3 require no human in the loop, which is what makes this approach scale differently than pure human-feedback pipelines.
Constitutional AI vs RLHF vs RLAIF
| Approach |
Feedback source |
What it produces |
| RLHF |
Human preference comparisons |
A reward model trained on human judgment |
| RLAIF |
AI-generated preference comparisons |
A reward model trained on model judgment, cheaper to scale |
| Constitutional AI |
Model self-critique against written rules |
Revised training data, typically feeding into RLHF or RLAIF afterward |
These are not competing methods — most production alignment pipelines use constitutional self-critique to generate better data, then still run a preference-optimization stage on top.
Where written constitutions fall short
A constitution is a specification, and specifications have the same failure modes any spec has. Principles that sound clear in isolation can conflict in practice — "be helpful" and "be cautious" pull in opposite directions on plenty of real prompts, and the model has to resolve that tension somehow, whether or not the constitution says how. Principles can also be satisfied in letter but not spirit: a model told to "avoid unnecessary caveats" can comply while still hedging every substantive claim in a different form.
The other limit is coverage. A constitution written today cannot anticipate every prompt pattern a model will see after release, especially adversarial ones designed specifically to exploit gaps between what is written and what was intended.
FAQ
Is constitutional AI the same as a system prompt?
No. A system prompt is inference-time instruction given to an already-trained model. Constitutional AI is a training-time process that shapes the model's weights using self-critique, before any system prompt is applied.
Do all major labs use constitutional AI?
Several do, in some form, though implementations differ. Not every lab publishes their constitution or training details, so it is hard to verify specifics — check individual model cards for current claims.
Can a constitution make a model safe on its own?
No single technique does that. Constitutional training reduces certain failure classes but still needs to be paired with evals, red-teaming, and deployment-time monitoring.
Does a longer, more detailed constitution produce better behavior?
Not necessarily. Overly long or overlapping principles can produce contradictions the model has to resolve arbitrarily. Clarity and non-redundancy matter more than length.
Where to go next