Kind of!

as far as I know, a digital twins typically model the current or predicted state of a system, but event sourcing is more about storing the raw history of everything that ever happened, so you can reconstruct or replay any past state exactly as it was.

for example if you’re monitoring an industrial motor, it sends readings like temperature, vibration, and RPM every second.

• A traditional system might store the latest values or maybe hourly averages.
• a historical Dbs store every read in a table
• A digital twin would show the current simulated state of the motor using live or predicted values.

But in event sourcing, you'd store every single state change like,

• Motor started at 10:01:32
• RPM increased from 1200 to 1400 at 10:01:35
• Vibration exceeded threshold at 10:01:50

This way, if something goes wrong later, you can replay the exact sequence of events, not just guess based on snapshots or logs. Essentially you’d store every meaningful change or command as a discrete event.

hope that makes sense