index.md

HTML wrapper for HTML-only fetchers; content is shown verbatim.

Raw file

Links (extracted)

Clickable list for reviewers; avoids copy/paste line-wrap issues.
# AWS S3 as a carrier for if.trace (if.bus preview one-pager)

**Audience:** preview cohort  
**Reality gate:** no AWS S3 adapter is deployed on this host; this is a roadmap integration for `if.api` + `if.bus`.

---

## 1) What AWS S3 is (black/white)

- AWS S3 is an object storage service with APIs for buckets and objects.
- It manages storage, metadata, and access policies for files and archives.
- It does not, by itself, provide a receipt for your output bytes.

## 2) What if.trace is (black/white)

- `if.trace` binds bytes to hashes with receipts (signatures only when present and verifiable).
- `if.trace` proves integrity of specific output bytes, not correctness or truth.

## 3) Overlap (small)

- Both touch the same stored bytes.
- S3 stores objects; `if.trace` attests to the outputs you publish.

## 4) Non-overlap (important)

- S3 does not provide cryptographic receipt chains for output artifacts.
- `if.trace` is not a storage or access-control platform.

## 5) Recommended pattern (carrier model)

1) Use S3 as the upstream storage location.
2) Produce an output pack (report, export, audit).
3) Bind the output to `if.trace` receipts and link them alongside the S3 object metadata.

## 6) What not to claim

- Do not claim "S3 = receipt for output bytes".
- Do not claim "if.trace replaces S3 storage".

---

## References (one URL per line)

https://docs.aws.amazon.com/AmazonS3/latest/userguide/Welcome.html
https://docs.aws.amazon.com/AmazonS3/latest/API/Welcome.html
https://infrafabric.io/if/trace/