Power and position
A charging position within reach of the checkpoint. The handheld posture assumes staff hold the device rather than asking patrons to lean over a fixed reader.
Deployment
From a portal record to a working checkpoint.
Deployment is deliberately unremarkable: create the device, activate it once, let it pull its configuration, and watch it appear in Fleet Health.
01 · The sequence
Five steps, in this order.
-
Create the device
In the portal, bound to one organization and one location. Nothing has touched hardware yet, so a mistake here costs nothing.
-
Distribute the application
Through your established MDM, device-management, kiosk-management, or CMS/content-management workflow. Exact hardware and platform compatibility is confirmed during consultation.
Signing Every release is signed with the permanent LaurelID certificate. A build that is not is not a LaurelID release, whatever it is called.
-
Activate once
The installer enters a single-use code. The device receives an encrypted credential stored under the Android Keystore, using StrongBox where the hardware provides it.
-
Retrieve configuration
The verifier pulls its configuration and policy version, and begins sending heartbeats. Configuration convergence is visible per device in the portal.
-
Verify a real credential
The deployment is not finished when the device appears online. It is finished when a real mobile ID has produced a real outcome at the real counter.
02 · Site requirements
What a location actually needs.
Outbound HTTPS
For activation, configuration, heartbeats, and queue drain. Verification itself does not need it, which is why an outage is survivable.
A named fallback
Your existing manual age-check procedure, written down, so
unable_to_verify has an obvious next action instead of a
hesitation at the door.
03 · Rollback
Agreed before it is needed.
A rollback plan that is invented during an incident is not a plan. Ours is constrained on purpose: rolling back requires the exact permanent signer, explicit approval, a compatible active policy, lease and location binding that still match, and either an empty outbox or an approved drain plan.
Rollback is never a way to bypass suspension, quarantine, revocation, lease expiry, a minimum-version floor, or a location mismatch.
Precondition Required
signer Exact permanent certificate
approval Explicit, recorded
policy and lease Compatible and active
outbox Zero depth, or an approved drain plan
credential rotation No unresolved overlap
Plan a deployment against your real floor.
Site profiling, installer runbooks, and staff training are part of the pilot, not an add-on.