Skip to content
Procurement • Tool

# Attachment bundle export (offline).

Prepare the three auditor attachments with procurement‑grade naming and a ticket comment template — without uploads and without network calls. This tool generates a bundle manifest with file hashes for replay.

No uploads No network Deterministic naming Bundle manifest (SHA‑256)
Back to procurement Naming spec Offline verifiers

### What this prepares

- Audit summary (PDF) — print from a verifier and save using the suggested filename.
- Countersigned approval receipt (JSON) — download from a verifier (ticket‑bound; org threshold evaluated).
- Kit supply‑chain verification receipt (JSON) — download from /verify‑airgap‑kit (kit SHA‑256 + keyring snapshot + commitments/headchain).

This tool does not certify compliance and does not grant any patent rights. Outputs are non‑binding unless incorporated into a signed agreement.

## Inputs

Drag & drop your attachments here, or select files below.

Supported: PDF (audit summary), JSON receipts.

Audit summary (PDF) — optional

Tip: generate via /verify‑diligence, /verify‑assurance, /verify‑trust, or /verify‑airgap‑kit.

Countersigned approval receipt (JSON)
Kit supply‑chain verification receipt (JSON)
Ticket system (optional)
Ticket ID (optional)

If the countersigned receipt already includes a ticket binding, this will auto‑fill.

—
Advanced: bundle manifest
The bundle manifest records hashes and filenames for replay. It does not alter signed receipts.

## Outputs

Approval short code
`—`
Primary approval id
`—`
Ticket binding
`—`
Bundle manifest hash
`—`
Suggested filenames

    —

Bundle manifest

    —

If receipts contain different internal approval ids, this tool will warn but still allow a bundle. The manifest captures all ids and hashes for reconciliation.