The Veloce-Engine Demo Still Says "Coming Soon" — So I Tested the Demo That is Already Live

Description and use

The Veloce-Engine demo demonstrates a functional reservation manager with a relational data model and graceful handling of missing references, yet it lacks persistence, network calls, and backend integration.

Problem

The demo page displays a stale "coming soon" message while a live interactive reservation manager is present, causing buyer confusion.

Outcome

The demo demonstrates a relational data model with graceful handling of missing references, counters, and CRUD operations, but lacks persistence, network calls, and backend integration.

Workflow

• Open demo URL
• Observe functional dashboard
• Note stale "coming soon" block
• Interact with reservations, staff, and shifts
• Test data model by deleting staff referenced by a shift
• Verify graceful handling of orphaned references

Evidence

The demo isn’t a flat list of rows. It’s relational — and that’s the interesting part.

Source

I removed a staff member from the roster while a shift still pointed at them, then re-rendered the shift list.

Source

It didn’t crash. The render guards it: <span>${s ? s.name : 'Unknown'}</span>

Source

No persistence. There is no localStorage, no sessionStorage, no indexedDB in the page.

Source