Evidence
Sealing
Sealing fixes an evidence package permanently: what it records, who may do it, what changes afterwards, and how a mistake is corrected.
Last revised
Sealing is the act that turns a package from a working document into a record. It computes the SHA-256 fingerprint of the manifest and of every asset, writes them with the time and the person who sealed, and closes the package to every further change. It is the artifact a brand may put in front of a marketplace or a court, and the only correction available afterwards is a second package that says the first was wrong.
Who may seal
Brand Admins only. It is the widest permission gap in the product outside arming enforcement, and it sits in the same place as activating a policy: the acts whose consequences reach a third party belong to the role that owns the workspace. A support session cannot seal.
Sealing a package
- Open the package from Compliance › Evidence. It must be Ready for review; the control is not shown in any other state.
- Read the summary — observed price, MAP, gap, seller and its standing at capture, policy version — and the manifest section.
- Optionally choose Verify integrity to confirm the stored bytes still match what was captured.
- Choose Seal this package. Sealing needs a fresh second factor — if yours is older than fifteen minutes you are asked for a code first — and the confirmation is explicit: sealing is permanent, and a sealed package cannot be edited.
What sealing records
| Field | Meaning |
|---|---|
| Manifest SHA-256 | The fingerprint of the canonical manifest bytes. |
| Asset SHA-256 | One per asset, from the bytes actually stored. |
| Sealed at · sealed by | The instant and the person. A person, always — no system identity may seal. |
| Sealing version | Which hashing rules were used, so a package sealed today verifies under today’s rules forever. |
After sealing
- Every read verifies the fingerprint. A mismatch is shown as Integrity failed, a first-class state, rather than the file being served quietly. See Hash verification.
- No field changes — not the manifest, not an asset, not even a later scan result on an attached file. A package that gained a file after sealing would no longer be the package that was attested, and the database refuses the insert.
- Only a sealed package can carry an enforcement notice. Evidence not sealed is one of the blockers the notice page shows. See Prepare a notice.
Correcting a sealed package
If a sealed package turns out to be wrong — the wrong observation, a listing matched to the wrong product — it is not edited or deleted. A new package is captured and sealed, and it references the one it supersedes. Both stay visible, with the reason, so anyone reading the record later sees the correction and the thing it corrected.