Validation-first layering

Validation runs at the earliest moment within its scope, before that scope's first effect. When every layer follows the rule, the first failure that surfaces is the outermost defect: the one closest to the author's mistake, reported in the author's terms, before any inner layer has acted on the malformed input.

The principle is a layering rule, not a call to validate more. Each scope validates what it owns, once, at its boundary. A file validates when it loads. A configuration validates when it finalizes. A statement validates when it compiles, and again when the process verifies it against its target. A request validates when it is parsed. An inner scope trusts what an outer scope has validated and validates only what it adds. The outermost defect surfaces first because the outermost scope ran first.

What early validation provides

Where the organization's code applies the rule

Keyboard shortcuts

Settings