TCN future action options
Purpose: suggested next actions after documenting the true current TCN machine state.
Lane 1 — rebrand machines to Ballbox highest priority
- Investigate and standardize Ballbox branding changes in
v3Skins, Text, local assets, and visible machine UI surfaces.
- Replace or hide Chinese/vendor-facing branding where safe.
- Prioritize the parts needed for clean machine delivery first: logos, welcome screens, product visuals, visible labels, and language cleanup.
- Define a repeatable Ballbox-branded delivery pack per machine.
- Keep proof of what changed on each delivered machine.
Why first: needed for clean delivery of the machines.
Lane 2 — operate current stack better now
- Create a Ballbox machine registry with TCN Machine ID, venue, EasyCoin device, BillWallet account, OurVend reference, QR status, and legal QR status.
- Create commissioning and maintenance checklists.
- Track proof of real test vend per machine.
- Store exports, logs, SQLite dumps, and ad packs as machine artifacts.
- Track stock reconciliation and incident notes.
Why now: biggest immediate operational value after delivery readiness.
Lane 3 — integrate around EasyCoin next
- Obtain and document EasyCoin API details.
- Test whether Ballbox can trigger remote vend or benefit redemption through EasyCoin.
- Explore memberships, sponsor benefits, and promo flows that use EasyCoin as the release bridge.
- Unify sales/ops visibility in Ballbox without pretending Ballbox owns the whole payment rail.
Why: this is the most realistic software leverage path around the current payment reality.
Lane 4 — improve machine-side branding/content control next
- Document and standardize asset-pack generation for
TCNFolder.
- Investigate
ImageGoods, Text, and v3Skins.
- Aim for better Ballbox branding, better product images, and cleaner language control.
- Prefer truth-preserving local asset control over fake cloud autonomy claims.
Lane 5 — long-term autonomy research risky / later
- Investigate OurVend TCP behavior at
qrc.ourvend.com:4150.
- Inspect FTP/ad/update mechanisms.
- Map what Ballbox could eventually replace: metrics, catalog, stock sync, branding, remote content.
- Do not mix this lane into short-term delivery plans unless evidence becomes much stronger.
Recommended sequencing
- Ballbox rebranding for clean machine delivery.
- Ops registry and checklists.
- EasyCoin API/documentation and practical bridge experiments.
- Further branding/content control depth.
- Protocol replacement research.
Guardrail
Do not reopen machine-native Mercado Pago adapter work unless new evidence shows TCN truly supports it.