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

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

---

## 1) What Microsoft Teams is (black/white)

- Microsoft Teams is a collaboration and messaging platform with webhook connectors.
- It routes messages and workflow notifications across teams and channels.
- 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.
- Teams delivers notifications; `if.trace` attests to the outputs you publish.

## 4) Non-overlap (important)

- Teams 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 Microsoft Teams to deliver the notification or workflow outcome.
2) Bind the output to `if.trace` receipts.
3) Store or share the receipt links alongside the Teams message.

## 6) What not to claim

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

---

## References (one URL per line)

https://learn.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/what-are-webhooks-and-connectors
https://learn.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook
https://infrafabric.io/if/trace/