Rule 11.4

Chapter 11, Targets and the oracle Test

An emit golden is a reviewed artifact: a change to examples/__emit-goldens__/ must be read as a diff and must not be re-baked as a rubber stamp.

The rule text and the parts under it are the compiler's own English, as the design document writes them.

Rationale

a byte-identical change is what the goldens gate, and a semantic change must also pass the oracle parity gate and the compile gate.

AGENTS.md (“emit changes come in two kinds”).

Checked by a test. A test, a gate script or a CI workflow names this rule, and the traceability check fails when a file listed below stops naming it.

Where the rule says the compiler enforces it:

examples/emit-goldens.test.ts and examples/shade-examples.test.ts; the review is a person’s.

The files that verify it at commit 26de7be8, each at the first line that names the rule:

The rule at commit 26de7be8: