Skip to main content
A bundle carries one incident from the host that recorded it to any machine that will reproduce or fix it. It holds the event, the already-redacted recording and the contract version, and nothing else: no salt, no token, no configuration.

Producing one

The first writes one bundle. The second writes a JSON array of every incident last seen in the window.

Consuming one

Both read nothing from the local data_dir. An argument is treated as a bundle path when it ends in .json, contains a path separator, or exists as a file; a fingerprint always starts with fp_, so the two are never confused.

Safety on the way back in

A bundle is untrusted input. schema_version is checked first, unknown fields are refused, an incomplete bundle (no event or no recording) is refused, and the file is capped at 8 MiB. See Incident bundles for the workflow.