F.15:2 - Problem frame

Unification work fails when composition is claimed before local meaning, exact object recovery, and continuity are checked:

1. Locality leak. Same spelling is treated as one meaning without comparing exact <ReferenceScheme, LocalSenseClaim> projections.
2. Row sprawl. F.17 rows or F.18 NameCards multiply although an existing governed value and admitted naming use already suffice.
3. System-role or status inflation. Adjectival, temporal, or source-label variants become new system-role kinds or status values without recovery through the pattern that defines them.
4. Silent rewrite. An edition or rename changes claim content while a stable id is treated as continuity proof.
5. Bridge hardening. A description, Card, CL, or earlier relation claim is later used as equivalence or use authority without a current obtaining occurrence and separate bounded-use claim.
6. Check collapse. Scope, rule, application/work, result claim, witness/evidence path, record episteme, publication, and currentness are treated as one object.
7. Register split. Tech and Plain designation expressions drift away from the exact current F.18 NameCard, governed value, or local sense.

F.15 catches these failures before the finite slice is used for naming reuse, cross-local comparison, assurance input, or another downstream claim.