data_dir defaults to ./pikopod-data and is set with the data_dir key or PIKOPOD_DATA_DIR. Recordings are redacted before they are written, so what is here is what you would be comfortable sharing, with one exception: the salt.
Layout
Scenario packs are also read from
./scenarios in the working directory, which is where committed packs live.
Back it up like state
Baselines represent days of learning, and losing them restarts every warmup window. The event log and recordings are what every open incident reproduces from. Putdata_dir on a persistent volume and give it to exactly one agent. See Deployment.
The salt
Tokenization is an HMAC keyed by.salt. It is what makes tokens correlatable within your install and meaningless outside it. pikopod refuses to start if the file is group- or world-readable. Deleting it regenerates it, and old tokens stop correlating with new ones, so baselines are effectively reset. Include it in backups and exclude it from anything you share. See Security.
Retention and rotation
Recordings and the event log rotate by size, keeping one previous generation. Withretention.max_age_hours set, a record is kept at least that long and deleted no later than roughly twice that age. Dedupe and acknowledgement state is never aged, so an acknowledged fingerprint stays quiet across restarts.
Resetting things
Inspecting what is stored
pikopod inspect prints stored records with tokenized fields visible, so you can confirm what was kept before you trust it. See Inspecting.