iPhone sysdiagnose-style set, version 1.0
==========================================

Every file here was written by generate.py from a fixed seed (20261106). No file comes from a device.
App names, bundle identifiers, network names, hardware addresses, process numbers, run times and the
device model (iPhone99,1) are invented. The build (SYNTH26A1) is invented too.

What is in it
  cases/<case id>/sysdiagnose_...{tz}_iPhone-OS_iPhone_SYNTH26A1/   one reduced sysdiagnose-style folder per case
      SystemVersion/SystemVersion.plist                 device model, OS and build (invented)
      logs/MobileInstallation/mobile_installation.log.0 install and removal lines, device-local time
      WiFi/com.apple.wifi.known-networks.plist          known networks, XML property list, UTC dates
      crashes_and_spins/<App>-<date>.ips                crash reports (JSON form), time with UTC offset
      system_logs_excerpt/unified_log_excerpt.txt       TEXT excerpt in the style of `log show` (not a tracev3 archive)
  reference_answers.json    the reference answers, one record per case
  reference_answers.csv     one row per scripted action
  generator/generate.py     the script that wrote all of this (MIT)
  LICENCE.txt               licences

34 cases in 7 categories: full_script (6), shuffled_order (6), subset (6), reinstall (4), log_window (4), timezone_offset (4), trace_missing (4).

Each case is a short script of known actions on an invented phone: install an app, join a Wi-Fi network,
turn airplane mode on, turn it off, crash the app, remove the app. The reference answers give the true
time of every action and where its traces are in the folder. Some cases change the order, drop actions,
reinstall the app, start the log after the install, shift the device clock away from UTC, or remove one
trace file.

A model, not a copy. File names and line shapes follow what the public iLEAPP source and the Lab Technical
Reports describe. Where they do not describe a detail (the wording of the unified-log lines for an install
or a crash, the AddReason value in the Wi-Fi plist, the folder that holds each file), the detail is invented
here. A reader that passes on this set has passed on the model, not on a phone. The unified log is plain text
here; a real sysdiagnose holds a tracev3 archive, which this set does not reproduce.

The reference answers are not inside the case folders, so you can run a tool blind and compare after.

Check files with SHA256SUMS.txt or manifest.json (next to this archive).
Licence: data CC BY 4.0, generator MIT.
