Verification stops at its boundary.
Runtime code, implementation references and active delegation are distinct claims.
Bind code to state
A runtime hash belongs to a specific address and state. Source verification must bind the claimed code to that runtime. A familiar contract name, explorer badge or repository is not a substitute for an exact verification result.
Resolve the proxy without guessing
A recorded implementation slot supports a reference at the captured state. Active delegation, beacon routing and implementation behavior require their own evidence. A zero slot does not exclude custom proxy routing. The view distinguishes observed references from proven execution paths.
Coverage is not an audit
Verification can make code inspectable without proving the absence of vulnerabilities or future upgrades. The Code view retains mismatch, missing source, unresolved routing and administrative coverage as separate limits.