02 - U_legacy Uniform End-State Recheck

Verdict

U_LEGACY_UNIFORM_ENDSTATE_NEEDS_FIX

Accepted: one sealed set, no DO_NOT_TOUCH/class subtraction, one object end-state, syntax-only relkind/prokind, and fail-closed collisions.

Blocking defect: the blueprint defines U_legacy = closure(#11, roots=#20 protected_target rows) as PG object identities, then requires both-EXCEPT equality against a denominator that unions:

1. PG object identities from reverse closure;
2. effective-EXECUTE principals;
3. trigger/event-trigger/scheduler/DOT entry-vector writers.

Those are different identity types. A principal or DOT/vector record cannot be an object member and cannot satisfy owner/definition/#21 object-state predicates. Known frozen DOTs make this more than a theoretical type error.

Required T1 fix:

• Keep U_legacy_object strictly as a typed PG-object identity set from sealed #20 roots plus exact #11/#22/analyzer object closure.
• Compare it both-EXCEPT only with a denominator of the same PG-object identity shape.
• Define a separate sealed principal universe used only to expand/check effective privilege for each object.
• Define a separate entry-vector/bypass coverage relation proving every vector targets a U_legacy_object member or is independently blocked; vectors are not members of U_legacy_object.
• Define protected-boundary collision as typed object-identity intersection; non-PG DOT/scheduler boundaries use the separate vector guard.
• Unknown, unresolved, uncovered vector, or type mismatch fails closed.