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

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

---

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

- Salesforce is a CRM and workflow platform with APIs for records, cases, and events.
- It manages customer data, process state, and automation metadata.
- 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 business records and outputs.
- Salesforce stores CRM data; `if.trace` attests to the outputs you publish.

## 4) Non-overlap (important)

- Salesforce does not provide cryptographic receipt chains for output artifacts.
- `if.trace` is not a CRM or workflow engine.

## 5) Recommended pattern (carrier model)

1) Use Salesforce as the upstream system of record.
2) Produce an output pack (report, export, audit).
3) Bind the output to `if.trace` receipts and link them alongside the Salesforce record metadata.

## 6) What not to claim

- Do not claim "Salesforce = receipt for output bytes".
- Do not claim "if.trace replaces Salesforce CRM".

---

## References (one URL per line)

https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/
https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/overview.htm
https://infrafabric.io/if/trace/
