1.7 KiB
1.7 KiB
Project Positioning
One-line Positioning
XQKqueue is a lightweight multi-project queueing and call-management system for scenic-area operations.
Primary Goal
The project exists to let visitors take and track tickets, let staff call contiguous queue batches safely, let administrators operate and audit projects, and show public queue status on browser and Android large-screen clients.
Target Users / Consumers
- Scenic-area visitors taking or checking tickets.
- Front-line staff issuing tickets and calling queue batches.
- Administrators configuring projects, users, history, and operational status.
- On-site public displays consuming privacy-safe queue snapshots.
Non-goals
- The Android display is not a general-purpose browser or an administrative client.
- Public display and visitor APIs must not expose private ticket fields.
- Client-side button state, polling, or audio is not an authority for queue writes.
Core Constraints
- The Go service and PostgreSQL database are the sole write authority.
- Ticket creation and call-next correctness is enforced at the service transaction boundary; retryable write endpoints use their documented idempotency and revision contracts.
- Public screens must tolerate intermittent connectivity and disclose only allowlisted data.
- The dedicated Android display must work without System WebView or a device TTS engine.
Quality Bar
A good solution preserves FIFO and privacy invariants under concurrency, has observable loading/offline/error behavior, remains usable on the target 1920x1080 landscape display, and is covered by server, web, Android, and device-level acceptance checks proportionate to the change.
Last Reviewed
2026-08-12