# SWHID as a carrier for if.trace (if.bus preview one-pager)

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

---

## 1) What SWHID is (black/white)

- SWHID is a persistent identifier for software artifacts in the Software Heritage archive.
- It is content-addressed (hash-based) and identifies specific objects (e.g., revision, directory).
- SWHID 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 identifiers for artifacts.
- SWHID names archived software objects; `if.trace` attests to bytes you publish.

## 4) Non-overlap (important)

- SWHID does not describe your output transformation or receipt chain.
- `if.trace` does not act as a global software archive identifier.

## 5) Recommended pattern (carrier model)

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

## 6) What not to claim

- Do not claim "SWHID = receipt for output bytes".
- Do not claim "if.trace replaces SWHID archive naming".

---

## References (one URL per line)

https://www.softwareheritage.org/
https://docs.softwareheritage.org/devel/swh-model/persistent-identifiers.html
https://archive.softwareheritage.org/
https://infrafabric.io/if/trace/
