Veloce-Engine: I Added a Reservation, Confirmed It, Then Hit Refresh — What the Demo Does and Doesn't Prove

Description and use

The Veloce-Engine demo is an interactive front‑end prototype with a four‑state reservation pipeline, but it lacks persistence and backend integration.

Problem

Determine whether the Veloce-Engine demo is a functional live instance or a static prototype before purchasing a $199.99 license.

Outcome

The demo is a genuine interactive front‑end prototype with a realistic four‑state reservation pipeline, staff roster, and shift planner, but it lacks persistence, concurrency, and backend integration.

Workflow

• Open the demo page and observe seeded reservations and staff status.
• Add a new reservation with guest details and confirm the counter increments and row appears.
• Change the reservation status through the four-state dropdown (Pending → Confirmed → Seated → Completed).
• Refresh the page and note that the new reservation is lost and counters revert to original values.

Evidence

The demo holds its state in memory. Nothing I did was written anywhere.

Source

I confirmed the same thing in the page source: no fetch(), no XMLHttpRequest, no localStorage, no indexedDB anywhere in the page.

Source

The interface is real and interactive. Add, status-change, and delete all work without a page reload.

Source

The demo holds its state in memory. Nothing I did was written anywhere.

Source