# Introduction

What Safeput intends to solve and how its file lifecycle works.

Safeput is developer infrastructure intended to simplify secure file uploads.
It is designed for applications that need to accept untrusted files without
assembling their own quarantine, asynchronous scanning, and temporary retrieval
pipeline.

> Safeput is not yet a production service. The architecture and interfaces in
> these docs are provisional until the first API release.

## The problem

Accepting a file is only the first step. A responsible pipeline also needs to
control access before scanning, process files asynchronously, distinguish clean
and rejected outcomes, handle failures, and remove expired content.

Safeput intends to place those concerns behind a focused API.

## Basic lifecycle

```text
upload → quarantine → scan → clean/rejected → retrieve
```

An uploaded file remains untrusted while it is quarantined and scanned. A clean
scan result permits temporary retrieval. A rejected result follows a separate
disposition path and is not released as clean.

Malware scanning reduces risk but does not guarantee that a file is harmless.