Validation rules
Validation rules are the standards every implementation is checked against. They are how you say "this is what good looks like here" once, instead of finding the same problem in review after review.
What you start with
Every project begins with a built-in, code-review-style rule set. You do not have to author anything to get value from validation — the defaults cover the kinds of problem a reviewer would raise anyway, and you add to them as your own standards emerge.
What a rule targets
A rule applies to feature implementation, the UI prototype, or both. That choice matters: a rule about accessible markup belongs on the prototype, a rule about error handling belongs on the implementation, and a rule about naming probably belongs on both.
Authoring a rule
Rules are written on their own page, not in a dialog. That is deliberate — a rule worth enforcing is usually worth a few paragraphs, and a dialog encourages one-liners that agents interpret loosely.
Write a rule the way you would explain it to a new reviewer: what the rule is, why it exists, and what a violation looks like. The prompt generation behind it knows the project's target stack and codebase, so you do not have to restate them.
When rules run
Validation runs as part of implementation, and the reviewer decides whether an Adjust update runs the rules again. Rules are grouped into shared-evidence agent calls rather than run one at a time — several rules that need the same evidence are checked together, which is why a validation pass costs less than the rule count suggests. A pass is capped at a configurable number of agent calls, so a large rule set cannot run away with your budget.
Validation agents run inside the project they are validating, against the real codebase rather than a summary of it.
Conflicts
Two rules that contradict each other are surfaced, not silently resolved. The platform will not pick a winner on your behalf: it reports the conflict and holds the affected work.
The Validation Rules page shows which jobs a conflict is holding paused. That is the place to look when an implementation seems stuck for no reason — a rule added last week can be the thing blocking it.
Rules in local development
If your developers implement locally with the Repave plugin, its code review checks the same validation rules, in grouped parallel agent calls, against the same project. A rule is a project standard, not a platform-pipeline standard.