Constitutional Prompting: Reliable Agents Without the Iteration Tax

Introduction

Every team automating developer workflows with agents hits the same wall: the iteration tax. You ask the agent to review a PR, scaffold a feature, audit code — it does something almost right, you correct it, it overcorrects, you add guardrails, it gets confused. Four round-trips later you've spent more time than doing the work yourself. Constitutional prompting borrows from Anthropic's research: govern behaviour with a small, explicit set of principles, not an ever-growing list of "don't do that"s.

Why this matters

Long instruction lists drift; principles compose.
Debuggability comes from a small set of stable rules, not a sprawling prompt.
New edge cases derive from existing principles instead of bolting on a new rule each time.
Teams onboard faster onto a constitution than onto a 600-line system prompt.

Core concepts

What a constitution is

A short, ordered list of principles that govern behaviour, expressed at the level of values rather than rules. The agent applies them to specific situations.

Principles vs. rules

A rule says "always include unit tests." A principle says "the change must be safe to merge." Principles cover cases the author didn't anticipate.

Ordering and conflict resolution

When principles conflict, the order resolves it. "Be safe" before "be fast" before "be terse." Make the order explicit.

Constitution as living document

Edge cases that aren't covered become principle additions, not exception lists. The constitution evolves; it doesn't accumulate scar tissue.

Practical patterns

Five-to-ten principles, not fifty

Force yourself to compress. Anything you can't justify as a principle is probably a rule that belongs in tooling.

Examples per principle

For each principle, include a few concrete examples of how it resolves an ambiguous case.

Versioned constitution

Track changes; tie agent behaviour regressions to constitution diffs.

Constitutional eval suite

For each principle, an eval that checks the agent applies it correctly.

Pitfalls to avoid

A constitution full of motherhood statements ("be helpful") that don't resolve actual conflicts.
Letting the constitution grow into the rule list it was meant to replace.
No examples — principles without examples drift in interpretation.
Treating it as a system prompt afterthought rather than a living artefact.