# Cloud exports

Kind

tutorial

For

operator · governance

Verified against

Veritio Cloud public claims · 2026-08-09 · @veritio/core@0.4.7 · vevb-1

A completed Cloud job means the download surface is ready; it is not an integrity verdict. The downloaded bundle uses the public `vevb-1` format, so verify it with OSS code outside the producing service.

## Request the right scope

[Section titled “Request the right scope”](#request-the-right-scope)

In the Cloud console, open Exports, select the intended project and available filters, and submit the request. Record the export ID, requester, project, selected filters, and request time in your operational ticket.

The bundle’s manifest—not the ticket or filename—is authoritative for what the file claims:

-   `full`: chain starts at sequence 1 and is gapless for its declared scope;
-   `windowed`: a contiguous partial window with boundary semantics;
-   `filtered`: content was intentionally excluded and filters are declared.

Do not describe a valid filtered export as proof that no omitted event exists.

## Wait for a terminal job state

[Section titled “Wait for a terminal job state”](#wait-for-a-terminal-job-state)

Refresh or follow the console status until it reaches a terminal success or failure. A failed job should remain an explicit failure; do not substitute an older bundle without recording that decision.

Download the completed bundle to a restricted directory. Preserve the original bytes and compute an external file digest if your evidence-handling procedure requires custody tracking.

## Verify outside Cloud

[Section titled “Verify outside Cloud”](#verify-outside-cloud)

The repository fixture builds, serializes, parses, verifies, and tampers with the same public format. Its checked result is:

offline verifier output

```json
{
  "bundleVersion": "vevb-1",
  "files": [
    "records/audit-events.jsonl",
    "records/evidence-edges.jsonl",
    "records/commits.jsonl",
    "verification.json"
  ],
  "valid": {
    "valid": true,
    "checks": {
      "structure": true,
      "integrity": true,
      "chains": true,
      "signature": "absent"
    },
    "chainScope": "full",
    "issues": []
  },
  "tampered": {
    "valid": false,
    "integrity": false,
    "issueCount": 3
  }
}
```

Use `parseExportBundle(downloadedText)` followed by `verifyExportBundle(bundle, options)`. Read the whole report:

Gate

Required meaning

`structure`

Manifest and file set map exactly; required files exist

`integrity`

Per-file digests, counts, and root hash recompute

`chains`

Event, edge, and commit chains match their declared scope

`signature`

Valid, absent, or explicitly skipped according to your policy

`chainScope`

Full, windowed, or filtered proof boundary

An unsigned bundle can be structurally and cryptographically valid with `signature: "absent"`. If your policy requires producer authentication, call the verifier with `requireSignature: true` and the trusted public key; otherwise absence must not be described as a valid signature.

## Retain the evidence package

[Section titled “Retain the evidence package”](#retain-the-evidence-package)

Store together:

1.  the original downloaded container;
2.  its external custody digest if used;
3.  the complete verifier report;
4.  the export request scope and requester record;
5.  the verifier package version and trusted signing-key identity, when applicable.

Any `valid: false` result blocks use of the bundle as verified evidence. Retain the failure report and request a new export only after diagnosing whether the issue is download corruption, scope mismatch, a chain failure, or signature policy.

Read the complete [export format](/docs/reference/export-format/) and [verifier reference](/docs/reference/verifier/) for programmatic use.

[Edit page](https://github.com/getveritio/veritio-website/edit/main/src/content/docs/docs/cloud/exports.mdx)

Last updated: Aug 23, 2026

[Previous  
Getting started](/docs/cloud/getting-started/)[Next  
Event schema](/docs/reference/event-schema/)

Veritio provides evidence support, not legal advice or automatic compliance.

This site uses cookieless, anonymous analytics (Umami) by default. With your consent, we also enable Google Analytics, which sets cookies and sends usage data to Google. [Privacy Policy](/legal/privacy/)