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

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

---

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

- Slack is a messaging platform with APIs for channels, webhooks, and app automation.
- It routes and stores collaboration messages and workflow notifications.
- 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 workflow outputs.
- Slack delivers notifications; `if.trace` attests to the outputs you publish.

## 4) Non-overlap (important)

- Slack does not provide cryptographic receipt chains for output artifacts.
- `if.trace` is not a messaging platform or workflow engine.

## 5) Recommended pattern (carrier model)

1) Use Slack to deliver the notification or workflow outcome.
2) Bind the output to `if.trace` receipts.
3) Store or share the receipt links alongside the Slack message.

## 6) What not to claim

- Do not claim "Slack = receipt for output bytes".
- Do not claim "if.trace replaces Slack messaging".

---

## References (one URL per line)

https://docs.slack.dev/
https://docs.slack.dev/messaging/sending-messages-using-incoming-webhooks/
https://infrafabric.io/if/trace/