28 lines
1.0 KiB
Markdown
28 lines
1.0 KiB
Markdown
|
---
|
||
|
|
id: "0003"
|
||
|
|
date: 2026-07-06
|
||
|
|
status: Accepted
|
||
|
|
supersedes:
|
||
|
|
superseded-by:
|
||
|
|
affected-paths: [lib/reportgen/delivery.rb, Rakefile]
|
||
|
|
affected-components: []
|
||
|
|
---
|
||
|
|
|
||
|
|
# 0003 — Client deliverables go to the client's SFTP drop, never email
|
||
|
|
|
||
|
|
## Context
|
||
|
|
|
||
|
|
Report packages contain client financial data. Email delivery (even to an internal distribution list) leaves copies sitting in inboxes and forwarding chains outside of our control, which is unacceptable for this class of data.
|
||
|
|
|
||
|
|
## Decision
|
||
|
|
|
||
|
|
Delivery must place packaged reports on the client's dedicated SFTP drop. Email must never be used as a delivery mechanism for client report packages, including delivery to internal ops addresses as an intermediate step.
|
||
|
|
|
||
|
|
## Consequences
|
||
|
|
|
||
|
|
Client data stays within an access-controlled, audited channel. Delivery code and any Rake tasks that trigger delivery must target the SFTP drop path, not a mail send.
|
||
|
|
|
||
|
|
## Alternatives rejected
|
||
|
|
|
||
|
|
A shared cloud storage link (e.g. emailed download link) was considered and rejected for the same inbox/forwarding exposure as direct email.
|