QR Pairing Should Bind a Physical Device to a Backend Identity

Scanning a code is useful only if the backend can prove which unit and account the ceremony joins.

I reached QR Pairing Should Bind a Physical Device to a Backend Identity through a repeatable lab problem rather than a design slogan. The LOUP MVP plan uses QR pairing so the parent app can claim a specific device without typing long identifiers.

A pairing token should be short-lived, single-purpose and associated with a known factory device record. The app authenticates the human, the backend consumes the token, and the device transitions only after the backend confirms ownership. The QR image itself should not become a permanent device credential.

The useful debugging step was separating signal path, state and timing instead of modifying all three and then guessing which change mattered. Evidence marker: qr-pairing.

Pairing tokens are invitations, not identities. Durable trust should be established after the invitation is consumed. That distinction also makes regressions cheaper to isolate when hardware, firmware and infrastructure are changing in parallel.

Project evidence

LOUP engineering marker: qr-pairing. This note records the design or debugging lesson without publishing device credentials, private keys, customer data or manufacturing secrets.