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.
# OCI digest as a carrier for if.trace (if.bus preview one-pager)

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

---

## 1) What an OCI digest is (black/white)

- An OCI digest is a content hash (e.g., `sha256:...`) that identifies a specific image manifest or blob.
- It is used by OCI registries and tooling to reference immutable bytes.
- 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 are content-addressed references to bytes.
- OCI digests identify container artifacts; `if.trace` attests to outputs you publish.

## 4) Non-overlap (important)

- An OCI digest does not describe your transformation, decision, or receipt chain.
- `if.trace` does not operate as a registry or distribution protocol.

## 5) Recommended pattern (carrier model)

1) Use OCI digest as the upstream container identity.
2) Produce an output pack (report, audit, scan, decision).
3) Bind the output to `if.trace` receipts and link them alongside the OCI digest.

## 6) What not to claim

- Do not claim "OCI digest = receipt for output bytes".
- Do not claim "if.trace replaces OCI registries".

---

## References (one URL per line)

https://opencontainers.org/
https://github.com/opencontainers/image-spec/blob/main/manifest.md
https://github.com/opencontainers/distribution-spec
https://infrafabric.io/if/trace/