Documentation

The operating manual for the boundary.

Everything your operators, installers, and reviewers need to run Laurel Secure. Full documentation ships with pilot onboarding; the public set below grows as the platform does.

01 · Core references

Start with the concepts that never change.

Concepts

How verification works

The on-device check, the three-outcome vocabulary, and the boundary between the reader and the platform.

Credentials

Supported mobile IDs

The ISO/IEC 18013-5 landscape, what the reader requests, and how jurisdiction coverage is confirmed.

Operations

Deployment guide

Postures, rollout stages, activation codes, network requirements, and MDM coexistence.

Data

The privacy boundary

What the platform stores, what it structurally cannot store, and how k-anonymity protects small report buckets.

02 · Outcome vocabulary

Three words your whole team will share.

Every Laurel surface — reader, portal, report — speaks the same closed vocabulary. Staff training starts and ends with what each answer requires of them.

Outcome What staff do

pass The credential proved the age threshold. Proceed.

fail The credential answered no. Decline the age-gated action.

unable_to_verify The check could not complete. Use your standard manual fallback.

03 · Pilot onboarding set

Delivered with your pilot, maintained for your rollout.

Pilot customers receive the full operating set: site-profile worksheets, installer runbooks for each reader posture, portal administration guides for every role, staff quick-reference cards for the three outcomes, and the security-review package — architecture overview, data-classification table, and the privacy-boundary specification.

API reference documentation for the typed platform contracts ships alongside integration scoping during qualification.

Get the full set with a pilot Request a specific document