Case 01 · poisoned pipeline
Find every artifact descended from the bad source.
A corrupted sensor batch contains impossible readings, duplicate rows, and a payload hidden in a text field. The immediate gate matters, but so does the blast radius after the batch has already moved.
The evidence path
-
Origin
The collector signs the exact source batch and source claims at acquisition.
-
Normalization
The next statement binds the raw batch and predecessor envelope before producing cleaned bytes.
-
Aggregation
Downstream outputs append their own statements instead of editing the earlier history.
-
Receiver gate
A required profile rejects the forbidden record or field, while predecessor links identify every affected descendant.
What the scenario proves
| Useful result |
A deterministic deny with the failing profile path, plus a graph that supports impact analysis. |
| It does not prove |
That every hidden copy participates, that the source was truthful, or that a signature alone makes the batch safe. |
Concrete handoff
| Input | customers.raw.json plus its signed origin statement. |
|---|
| Steps | Normalize the records, then create the public-safe output; each statement binds the prior payload and exact input artifact. |
|---|
| Mutation | Change one byte in the final artifact after the handoff is signed. |
|---|
| Expected result | The receiver denies with E_ARTIFACT_DIGEST while the unchanged signed metadata remains inspectable. |
|---|
Open the exact denial report · Inspect the source bytes
Reproduce the denial
The complete fixture mutates final data and expects an artifact-digest failure.