A released bundle you can open.
This is the whole output of one case, run through the product end to end and released the way an operator releases one. Download it, open the manifest, read the documents. Everybody in it is invented, and the archive says so in its own first file.
ZIP, 134 kB, 5 documents, 5 pages. No sign-up.
SHA-256 468e86fe3357f89f446ec0c6af05b183a79ac2c931fd3229940536906996460d
What you are downloading
- The real output of a real run. Ingest, extraction, detection, entity resolution, policy, render, an independent verification pass, packaging, a spot check, and release through the same door an operator uses.
- Redaction decisions made by a real model, replayed from recorded completions rather than derived from an answer key.
- One output document per source document, numbered so the containers are visible: an uploaded archive and the two documents inside it, an email and its attachment.
- The manifest, as machine readable JSON and as a document, and the quality report.
What it is not
- Not a customer case. Veil has no customers, so there is no real disclosure to publish.
- Not anonymised real material. There was nothing real to anonymise: the people are invented, the email domain is reserved and cannot resolve, and the identifiers are generated to satisfy their own checksums.
- Not a scan. The one component this run could not replay from a real model is optical character recognition, so the case deliberately contains no scanned document.
Five source documents, five outputs.
Read out of the archive's own manifest. Case reference VC-2026-0001, detector 1.11.0, verifier 1.5.0, redactions found by mistral-large-latest.
| No | Source | How it arrived | Output |
|---|---|---|---|
| 001 | c009_archive.zip | upload | 001_c009-archive.pdf |
| 001a | c009_policy.docx | archive entry | 001a_c009-policy.pdf |
| 001b | c009_log.txt | archive entry | 001b_c009-log.pdf |
| 002 | c009_mail.eml | upload | 002_c009-mail.pdf |
| 002a | c009_report.pdf | email attachment | 002a_c009-report.pdf |
The archive also carries the manifest as JSON and as a document, the quality report, and 000_README_SYNTHETIC.txt, which is the one file the product did not write. It names everybody in the bundle as invented and states the digest the bundle had before that file was added.
What to look for when you open it.
The subject stays
The person the request is about is named in full, in the documents and in the email header. Nothing about them is removed, including what somebody else wrote about them.
One decision, every document
The same third party carries the same placeholder in the archive's text file and in the email, because it was one decision about one person rather than two decisions about two mentions.
An over-redaction, and which way it points
In the email body, a Norwegian greeting was read as part of a name and redacted with it. That is the system erring the way it is built to err: what it cannot attribute to the data subject is redacted and raised for a person, never disclosed on a guess.
Every page is traceable
Each page carries the case reference, the document id and the page number, so a page detached from the bundle can still be placed in it.
What is not in the archive
There is no decision log here. Every entity decision, every download and every state change is written to an append-only audit record, and a customer exports that alongside their bundles rather than receiving it inside one. The audit record holds identifiers, counts and dates and never a document excerpt, which is what makes it something we can hand over rather than something we would have to redact first.
Your next access request does not have to eat a week.
Open a case, declare the subject, drop the documents in. Veil redacts, raises what it is not sure of, and shows you its working.