Back to How it works
the console

Operational visibility & exception tracking

Every object across every pipeline, in one view — with exceptions surfaced the moment they happen and a signed attestation attached to each completed transfer.
Exceptions
☰ Show all 0 Failed executions — Stalled over limit 0 Authorization required — Overwrites detected

Transfer Explorer

Transfer IDObjectPipelineStartEndStatusEvidenceAttestation
26e0e720…c391patient001_study002_series05_img010.dcmGCP1 → AWS101:39:3701:48:19Completed◫ Available⚖ Attestation
a587c094…683fpatient001_study002_series05_img009.dcmGCP1 → AWS101:39:5101:48:02Completed◫ Available⚖ Attestation
c9566197…a45fpatient004_study008_series05_img040.dcmGCP1 → AWS101:39:5101:47:44Completed◫ Available⚖ Attestation
6f2f64f0…b492patient004_study008_series04_img039.dcmGCP1 → AWS101:39:3701:47:29Completed◫ Available⚖ Attestation
42a5f1e3…1f52patient002_study003_series03_img022.dcmGCP1 → AWS101:39:2201:47:08Completed◫ Available⚖ Attestation
175ae29b…4b21patient004_study007_series05_img035.dcmGCP1 → AWS101:40:04Encrypting◫ Available
443a6e27…9af3patient004_study008_series02_img037.dcmGCP1 → AWS101:39:24Queued for Transfer◫ Available
02877ec4…0484patient001_study002_series05_img011.dcmGCP1 → AWS101:39:12Queued for Transfer◫ Available
Showing pipeline tg-7c4f1e-gcp1-aws1 · last 24 hours. Completed objects carry a signed attestation; in-flight objects show “—” until they complete. The first row is fully traceable — open its object-level detail or its signed attestation.

Exception tracking

0
Failed executions
0
Authorization required
0
Integrity mismatches
0
Overwrites detected
A failed integrity check, a missing authorization, or an attempted overwrite halts the transfer and surfaces here — never as a silent gap. An object that completes without an attestation would appear as an exception, not as a blank.

Diagnostics

100%
Integrity verifications passed
1:1
Attestation per completed object
P-384
ECDSA / SHA-384 signing
AES-256
GCM · FIPS 140-2 L2