Case bundles
A case bundle is one .viokit file that holds a case so you can hand it to a colleague or archive it,
and so the receiver (or you, years later) can check that nothing in it has changed.
Exporting
Console: Export… in the case bar, or ⌘K then “Export case…”.
In the export dialog you can leave out the bytes of the saved source copies for a lighter file (the custody records still travel), carry the branches too, seal the file with a passphrase (see below), or count what would go in and estimate the size without building anything.
Always on: erased and withheld content stays out. The result says which saved copies were left out and why.
What is in the file
The file is a zip. It holds the case's history (notes, purpose declaration, decisions and erasure records), the saved source copies with their custody records (who obtained each, when, how), and a manifest. The manifest holds the case name, purpose and lawful basis, retention review date, who made it and when, the Viokit version, counts, a SHA-256 checksum of every file and a hash chain over the files. Unzip it with any tool to look, and check any file against the manifest by hand.
Integrity, and what it does not prove
- Any changed byte, changed log line, missing or extra file is caught on opening, and the whole file is refused.
- A saved copy is named by its own SHA-256, so it is checked against its name too.
- If the exporting machine has a signing key (set by whoever runs Viokit), the manifest is signed and the receiver sees the key's fingerprint. Compare it with the sender's by another route. An unsigned file proves it is unchanged since it was made, not who made it: anyone can unpack, edit and re-make an unsigned file with fresh hashes.
Passphrase
With a passphrase the whole file is encrypted with AES-256-GCM, the key derived with PBKDF2-SHA256 (600,000 iterations). The file starts with a plain header that says so. Viokit does not store the passphrase and cannot recover it: lose it and the file cannot be opened. This is file-at-rest protection, not a substitute for a managed key.
Opening
Console: Open file… or ⌘K then “Open a case file…”. You can also check a file without opening it, which verifies and reports without writing.
- Everything is verified in memory first: file digests, the chain, the log chains, each saved copy
against its name, the signature, path containment (no
.., absolute paths, backslashes, duplicate names), and size limits (entry count, per-file, total and expansion ratio). - If anything fails, nothing is written and the message names the file.
- Otherwise a new case is created (a case is never overwritten). Step, entity and saved-copy ids
are unchanged; branches return forked where they were. A note records "Imported from
on " with the bundle's fingerprint.
- The sender's purpose declaration is shown to you and withdrawn in the new case. Declare your own in the “Before you look up people” panel before any person lookup.
Console files are limited to 90 MB; larger ones can be opened by whoever runs your Viokit.
Erased content
Export reads the case as every other reader does, so an erased person's steps and content are already gone. Saved copies removed by an erasure are absent; redacted copies and restricted or sensitive dataset evidence are listed by id and reason, with no bytes or custody record. The erasure record itself travels, so the receiver can see that something was erased.