# EM-LND-06 provider comparison

Both independent studies converge on **COMPLETE RESERVED MODEL** for existing `vr.vercy.plmm`, preserving `0.1.0-legacy` byte-identical and non-installable, creating no new identifier and no second `SoftwareProduct`. Both keep product internals in AISMM and keep WM-XCT-039 outside the required base while held.

Claude supplied the eleven-layer boundary, non-destructive lifecycle, explicit traversal inputs, provenance holds and the finding that the frozen AISMM tree is four commits past tag `v3.1.0`. Grok sharpened reference-record identity, immutable endpoint pins, derived qualified-path handling, coverage classes and explicit successor migration.

Two provider differences required local decisions. Membership identity excludes AISMM digest so overlapping pins become a conflict rather than duplicate products. AISMM is optional per membership with an explicit absence reason because a real product may lack an AISMM context. Per-membership exact pins and access-ceiling semantics are local reconciliation additions and are not attributed to either provider.

The single frozen audit confirmed the decision and required structural remediation. Candidate revision 3 applies that checklist once without a second audit. No installability, compatibility or publication-readiness claim is made.