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.
# Google Cloud Storage as a carrier for if.trace (if.bus preview one-pager)
**Audience:** preview cohort
**Reality gate:** no GCS adapter is deployed on this host; this is a roadmap integration for `if.api` + `if.bus`.
---
## 1) What Google Cloud Storage is (black/white)
- Google Cloud Storage (GCS) is an object storage service with buckets and objects.
- It manages storage classes, object metadata, and access policies.
- 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.
- GCS stores objects; `if.trace` attests to the outputs you publish.
## 4) Non-overlap (important)
- GCS 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 GCS 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 GCS object metadata.
## 6) What not to claim
- Do not claim "GCS = receipt for output bytes".
- Do not claim "if.trace replaces GCS storage".
---
## References (one URL per line)
https://cloud.google.com/storage
https://cloud.google.com/storage/docs/json_api/
https://infrafabric.io/if/trace/