Lifecycle feature matrix

The canonical end-to-end map of a Kiosk-X vending machine's life — from the pallet to decommission — with every cell backed by an executable eval. Rows are lifecycle stages; manufacturer columns cover Reyeah (RK3288 board, com.ruiye.jd APK, /apk/* protocol) and ZHZN/CSM (T3568 board, Python agent, /zhzn/* gateway); channel coverage spans the vending APK, operator Android app, operator web console, the web emulator, and the Partner API. A USA-operability column tracks currency, language, tax, and compliance posture.

This is a living document: the eval-run ledger at the bottom records the latest execution against the live stack (api.kiosk-x.ai).

How the evals run

Cell IDs (LM-nn) appear in test names (test_lm05r_… = row 5, Reyeah column) so a matrix cell can always be traced to its eval and back.

Lifecycle at a glance

Status legend

• PASS — eval executed and green (evidence: suite/ledger row)
• FIXED→PASS — failed on first run; fixed in this repo, re-run green (commit in ledger)
• ROUTED — owned by another in-flight agent; verified state documented, not double-fixed
• BLOCKED-HW — needs the physical machine (RK3288 motor, Nayax reader tap, ZHZN test unit)
• BLOCKED-BIZ — needs business credentials (live Stripe keys, real Nayax merchant, DOOH network contracts)
• BLOCKED-CFG — code path exists and is tested in-process, but the live deployment doesn't enable it yet (env/secret)

The matrix

Channels key: API · Emulator · Vending APK · Operator APK · Web console

USA-readiness bottom line

Reyeah: USA-operable for cash + Nayax cashless vending today at the cloud level — USD on every money surface (catalog, goods, orders, reports, subscriptions), English console/docs, Tobacco-21 age gate enforced server-side, tax-inclusive pricing with per-machine tax-liability estimates. Server-side currency is now guaranteed (31b4ad7 forces $ in the equipment config regardless of fixture drift). Remaining gaps are device-side: the Chinese/vape-banner APK cleanup and the OTA rollout to the deployed demo unit are in flight (RCA/OTA agent), and motor/ID-scanner/Nayax-tap verification needs the physical machine.

ZHZN: cloud gateway fully implemented and tested (register / config / pending / report / heartbeat / upgrade, exactly-once settlement forwarding), USD/English by construction since the device runs our agent, enabled on the live deployment since 2026-08-12 (KIOSKX_ZHZN_DEVICE_SECRET CI-bootstrapped into kiosk-x-secrets and wired in the deployment — kube-infra b534dd65; live proof: lifecycle_flavors_live.py run 8657773248, existing-zhzn PASS), but never validated against a physical ZHZN unit (BLOCKED-HW). The one-APK universality question is settled per the zhzn repo's committed docs: a single shared APK across manufacturers is not feasible (incompatible boards and wire protocols) — ZHZN ships as our headless Python agent speaking /zhzn/*, which is exactly what this matrix's ZHZN column evaluates.

Migration runbook (deployed vendor-cloud machine → Kiosk-X)

Status: cloud path proven by eval (LM-25); device steps require a site visit.

1. Build: CI produces reyeah-vending-kioskx.apk with UrlConfigString.baseUrl patched to https://api.kiosk-x.ai (see apk-rollouts.md); hosted on the downloads page.
2. On the machine (manager PIN → Android settings): uninstall the vendor APK first — the kioskx build is signed with our key, so in-place update is refused. Install the kioskx APK.
3. First contact: the board calls getEquipment with its existing serial; the cloud auto-provisions it into the unclaimed pool and it boots to a working USD grid immediately (LM-25 verified).
4. Claim: operator registers the serial (console or POST /api/v1/machines/register); any vends taken before claiming follow the machine (LM-05r verified).
5. Nayax: bind the reader's real Device Number (POST /machines/{no}/nayax) so settlement webhooks resolve (LM-06). Binding wires up the record; it does not give us the reader. See step 6.
6. What breaks / does not carry over: vendor-cloud order history, ad configuration, and planogram do NOT migrate (the vendor cloud is opaque to us) — re-enter the planogram (LM-07) and restock counts. Everything from first contact onward is continuous. The Nayax terminal does not migrate either, and that half is not ours to finish: on a second-hand cabinet the VPOS usually stays in the previous operator's Nayax Core organisation, commissioned for their old machine type. Its MDB profile and its settlement destination can only be changed by that actor (or moved by Nayax support), so card can be dead — or paying someone else — on a board that is otherwise fully migrated. Scan & Pay (Stripe QR) has no such dependency and is the card path that migrates cleanly. Details + the four ways to close it: docs/payments-nayax.md → "What migration cannot move".
7. Verify: cash vend + card vend that produces a real Nayax transactionId in your own payout report (a Kiosk-X-side settlement label is not proof) + ordersUpdate reconcile, then enroll the machine in the current OTA rollout.

Routed items (other in-flight agents own these)

Blocked items and exactly what unblocks each

Eval-run ledger

Latest live run: 2026-08-11T21:07:42Z against https://api.kiosk-x.ai — BLOCKED-CFG 1, PASS 28