Build plan
Phases 0–8, owners and estimated weeks.
- 0
Decide and confirm
Leadership, backend lead, legal counsel · 1-2 wks · Wk 0–2Get Thales SDK terms in writing (free, no royalties, own AI allowed), confirm Windows 11 driver, start legal review of patents and MA privacy rules, set priorities.
- 1
Buy one CR5400 and bench test
Backend lead · 1-2 wks · Wk 2–4Install on the HP station, capture test cards under all three lights both sides, time scans, check USB stability.
- 2
Scanner integration service
Backend lead · 3-4 wks · Wk 4–8Wrap the Thales SDK, parse AAMVA PDF417 (DOB, expiry, state, ID number), local API for the register, clean fallback if unplugged/jammed.
- 3
Register UI
Frontend lead · 3-4 wks · Wk 6–10Scan ID prompt, checking state, pass/fake/under-21 screens, payment gate, logged manager override.
- 4
Barcode age check live
Backend + frontend leads · ~2 wks · Wk 10–1221+ from barcode, expiry, barcode vs front match.
- 5
Own AI forensic engine
Backend lead (AI), legal counsel for data · 12-16 wks, in parallel · Wk 4–20Legal data collection, MA template library, train UV/IR/template/microprint/ghost/barcode-vs-front/tamper checks, accuracy targets set by leadership, offline model on the station.
- 6
Hub side
Frontend + backend leads · 3-4 wks · Wk 8–12Verification log, settings, device health, add-on enablement per store.
- 7
AWS test, test store pilot, approval
Leadership sign-off · 4-6 wks · Wk 12–18Separate AWS test environment, pilot at the test store, leadership sign-off.
- 8
Rollout state by state
Leadership · ongoing · Wk 18–26+Massachusetts first, then add states as each state's model passes testing.
Decisions needed
All durations are planning estimates; leadership sets the real schedule.