How ART works

A file's journey

1. The user sends

   They pick the file and the destination and confirm with the operating system. The Agent keeps an encrypted copy.

2. The appliance collects

   On that side's turn the request is registered and the file passes into the appliance's custody. From here the sender has no control over it.

3. Assurance and approval

   Validation and inspection run and, where policy asks, approvers decide.

4. Delivery

   On the destination side's turn the file is placed at its fixed path and checked.

Waiting for the appliance's turn

The appliance takes turns between the two networks, and the user never controls the switch. “Waiting for Bardin Gate” is a normal state, and no percentage or time estimate is shown for it, because it would be invented. Between two turns the appliance is disconnected from both networks; a file waiting for the next turn is safely in its custody.

The Agent on the user's computer

The Agent is deliberately small: a file action, a compact Send window, a compact Activity window, and the system's own notifications. Your administrator installs it from a signed package.

The states of a transfer

Preparing, Waiting for Bardin Gate, Sending, Received, Under security review, Waiting for approval, Waiting for destination, Delivering, Delivered; or Rejected, Expired, Cancelled, and Failed: action required. Each is a plain, stable word; technical detail sits behind a Details control with a reference code. The user can cancel until the appliance gives its durable receipt. After that the file is in Bardin Gate's custody, and the Agent says so plainly.