PRITECT VEIL, SAMPLE DISCLOSURE BUNDLE

EVERY PERSON IN THIS BUNDLE IS INVENTED. Nothing here is a real access
request, a real employee, a real customer or a real organisation, and nothing
here is anonymised real material. Pritect Veil has no customers, so there is
no real case to publish and nothing has been de-identified to make this.

The people, addresses and identifiers come from Veil's own test corpus, and
they are unreal by construction rather than by assurance:

  - Names are invented.
  - Email addresses are under veil-corpus.example. The .example top level
    domain is reserved by RFC 2606 and cannot resolve.
  - Network addresses, where any appear, are RFC 5737 TEST-NET-1 (192.0.2.0/24).
  - National identifiers are generated to satisfy their own checksums. They
    belong to nobody.

WHAT THIS BUNDLE IS

It is the real output of a real run. The case was taken through the product's
own pipeline end to end: ingest, extraction, detection, entity resolution,
policy, render, an independent verification pass, packaging, the spot check,
and release through the same door an operator uses. The entity decisions were
confirmed by an operator journey and written to the audit log.

The redaction decisions were made by replaying model completions recorded from
mistral-large-latest, not by a script reading the answer key. So the
placeholders you see are where a real model actually found a person.

WHAT IS IN IT

  000_manifest.json        the machine readable index of the case
  000_MANIFEST.pdf         the same index, as a document
  000_QUALITY_REPORT.pdf   what the run did and what it could not clear
  001_*, 002_*             one output document per source document

The numbering carries the container structure. 001 is an uploaded zip archive,
001a and 001b are the documents inside it. 002 is an email and 002a is its
attachment. Each source document produced its own output, which is what makes
it possible to withhold one file without losing the rest of a bundle.

WHAT TO LOOK FOR

The data subject stays. Third parties become stable placeholders, and the same
person carries the same placeholder in every document, which is the point: one
decision, propagated. Every page carries the case reference, the document id
and the page number.

You will also find an over-redaction. A Norwegian greeting was read as part of
a name and redacted along with it. That is the system erring in the direction
it is designed to err in: what it cannot attribute to the data subject is
redacted and raised for a person, never disclosed on a guess. We would rather
you saw that in the sample than discovered it later.

THE ONE FILE THE PRODUCT DID NOT WRITE

This README. Everything else in this archive is exactly as the product emitted
it, unmodified. The bundle as released had the SHA-256:

  ece23fc1a0881fc35d02fa03179100b79d63597cce6b2fb15081e1c408c308e9

The manifest does not list this file, because the manifest lists documents and
this is not one.

Generated 17 Sep 2026.
