docs(storage): clarify that S3 means the S3 API, not AWS (#136)

The architecture doc previously said "AWS S3 — current default for object storage" and pointed at a "provider-abstraction roadmap" for escaping AWS, framing it as a future improvement. That's misleading: boto3 already speaks the S3 API against any compatible backend today. Operators standing up the project outside AWS don't need to wait for a filesystem provider — they need to set AWS_ENDPOINT_URL_S3 to MinIO, Garage, Cloudflare R2, Backblaze B2, Wasabi, etc. Two narrow doc edits to reflect that: * architecture.md (Infrastructure section): rename the bullet to "S3-compatible object storage" and list the realistic options with links. Pointer to the new self-host guide for the full setup. Floci description rephrased as "S3-compatible emulator" rather than "AWS emulator" — same fact, less misleading. * src/services/storage_service.py module docstring: same clarification at the source-of-truth layer so readers of the code reach the same conclusion as readers of the docs. No code change. Concrete step toward the project's "maintained openly for any organisation" pitch landing for non-AWS operators. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Blake Bertuccelli-Booth committed on May 15, 2026, 06:47 PM

Showing 2 changed files +13 additions -3 deletions

M docs/explanation/architecture.md +2 -2

M src/services/storage_service.py +11 -1