# S3 Landing, Replay, and Failure Storage

## Summary

Defines the generic S3 component for raw capture, load-ready artifacts, curated exports, and failure handling. This epic makes ingestion durable, replayable, and operationally understandable, and serves as the shared storage foundation for multiple jobs and integrations.

## Key Documents

- `source-task.md` - goal, scope, and current placeholders for this epic
- `s3-storage-proposal.md` - proposed shared S3 bucket strategy, prefix model, Athena partitioning, and generic storage contract
- `s3-storage-implementation-plan.md` - implementation plan for the generic ETL S3 service, project placement, DI, and Aspire configuration
- `s3-storage-streaming-implementation-plan.md` - implementation addendum for normal and streaming uploads, multipart strategy, and bounded-memory writes
- `s3-storage-e2e-test-plan.md` - end-to-end test coverage for live S3 writes, replay, multipart, and failed artifact scenarios
- `../../../../ETL.md` - feature-level ETL architecture