Customer keys, trust and update integration
Current inspected release: beta17, private Premium preview. Read the current workflow and acceptance limits. Earlier beta references describe the retained feature history, not a newer public/stable stamp.
Customers open My Licenses after a confirmed purchase or explicit complimentary grant. For a supported customer board, approve the exact independent issuer after checking its fingerprint, then enter the matching product key. A prefix is not ownership proof and a key never approves its own signer.
An unknown/wrong-scope/disabled/tampered/expired key must be refused. Suspending or revoking vendor access removes key retrieval/update access, but copied offline signatures remain subject to the original signature/expiry and customer-core rules.
Historical156x Updates builds had confirmed wire mismatches with actual LMP; use the current integration-kit and acceptance guides for newer source and fixture evidence. A real separate vendor/customer paid/complimentary/theme/free installation journey is still required. No automatic machine activation endpoint/domain proof is claimed here; customer site records are self-declared registrations.
