# Decision — Preserve original filenames on Triage auto-classify

**From:** Jimmie
**To:** Loom (design owner) → Atlas (build) + Riv (Echo→Triage pipe)
**Date:** 2026-05-22
**Re:** Loom's 2026-05-22 Statement Intake Rework, open question on naming convention

## Decision

When a file lands in `Team Inbox/_Triage/` and Atlas's classifier auto-routes it to `Team Inbox/<Client>/Reconciliations/` or `/Workpapers/`, **preserve the original filename as-is**. No auto-rename to `YYYY-MM_<source>_<doc-type>.pdf`.

Loom had defaulted to auto-rename-with-original-kept-as-metadata. Owner override: keep the sender's filename.

## Implementation notes for Atlas

- Filename at the destination = filename as it landed in `_Triage/`
- If a name collision happens at destination (same filename already exists in that client folder), append `_2`, `_3`, etc. — do NOT overwrite
- Classification metadata (client, doc-type, confidence score, source) still gets stored in the DB on the document record; just not embedded in the filename
- Searching by date/source still works via DB queries, not filesystem scan

## Why this matters

Audit trail. Whatever name the email forwarder, scanner, or original system gave the file is the name that gets preserved for accountability. Auto-renaming severs the connection between "what arrived" and "what's in our folder."

## What's NOT changing

- Triage routing logic (Atlas classifier, 0.75 confidence threshold) — unchanged
- Destination folder structure (`<Client>/Reconciliations/` and `/Workpapers/`) — unchanged
- Echo→Triage email forwarding (Riv's build) — unchanged
- The three-bucket workspace model (private workspace / shared workpapers / Owner Inbox) — unchanged