Engine
Not a picture of your attraction. A working one.
A digital twin mirrors something that already exists. The Ghostlight Engine runs yours before it does.
One moment, opened up
At 14:10 on a rehearsed afternoon, a transformer fails and the coaster goes dark. Here is that one moment, seven layers down.
01Physics
Every device is computed.
Load, heat, wear and failure come from equations in real units. Nothing is played back.
Drag the load past 100% and watch insulation life burn faster.
02The wire
It answers in the real protocol.
The engine builds the actual frame for every device: header, byte order and checksum, byte for byte.
Pick any field. Change the load and the checksum changes with it.
03Power and network
Failures travel.
Power is solved as it is wired, down every cable, and the network beside it. Fail one thing and everything beneath it goes dark, then restarts in order.
Click any line to fail it, and again to repair it.
04The day
The whole day runs.
Weather, guests and crew are modelled hour by hour, so the fault lands on a real afternoon: a queue to clear and a technician to send.
Move across the chart to look at any hour.
05The record
Every effect has a cause on record.
Each event carries an ID that ties it to what caused it, and rules are checked across the entire run.
Pick an event to trace it back to the root.
06The source
Every number knows where it came from.
Each fact in the model points to the document, sheet and revision it was read from, or is marked as an assumption. The first findings appear here, before anything runs.
Pick a fact to see its source.
07The repeat
Same seed, same day.
Every rehearsal is seeded. Run it again and the day replays exactly, down to the bytes. Change the seed and it is a different day.
Change the second run's seed.
Start with what you have.
No site, no hardware, no connection to your network.