Hi everyone!
I’m currently working on a personal archiving project where I’m trying to document the “born-digital” interactions within mobile gaming environments. I want to ensure that the logic and telemetry data generated during these sessions are preserved in a way that meets basic digital continuity standards.
I’ve been using a delta exec tool to handle the live execution of scripts on my mobile device, which generates a significant amount of real-time metadata and activity logs. My main challenge is that the delta exec tool produces data in a proprietary or transient format that seems to change frequently. I’m worried that if I don’t find a way to “freeze” these logs or convert them into a stable XML or JSON schema, the historical context of how these scripts interacted with the game world will be lost to software obsolescence.
Has anyone here dealt with the long-term preservation of logs generated by background executors or a delta exec tool? I’m specifically looking for advice on how to maintain the “fixity” of these files when they are being updated so rapidly. Should I be looking into a containerized approach for the executor’s output, or is there a standard metadata profile you’d recommend for capturing the provenance of automated mobile scripts? I want to make sure these digital records remain readable and “audit-friendly” for future researchers who might look back at mobile automation trends!
