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.
# SharePoint as a carrier for if.trace (if.bus preview one-pager)
**Audience:** preview cohort
**Reality gate:** no SharePoint adapter is deployed on this host; this is a roadmap integration for `if.api` + `if.bus`.
---
## 1) What SharePoint is (black/white)
- SharePoint is a content and document management platform for sites, files, and workflows.
- It exposes APIs via Microsoft Graph for sites, drives, and list items.
- 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 document bytes.
- SharePoint stores content; `if.trace` attests to the outputs you publish.
## 4) Non-overlap (important)
- SharePoint does not provide cryptographic receipt chains for output artifacts.
- `if.trace` is not a document management platform.
## 5) Recommended pattern (carrier model)
1) Use SharePoint as the upstream content store.
2) Produce an output pack (report, export, audit).
3) Bind the output to `if.trace` receipts and link them alongside the SharePoint item metadata.
## 6) What not to claim
- Do not claim "SharePoint = receipt for output bytes".
- Do not claim "if.trace replaces SharePoint content management".
---
## References (one URL per line)
https://learn.microsoft.com/en-us/sharepoint/dev/
https://learn.microsoft.com/en-us/graph/api/resources/sharepoint?view=graph-rest-1.0
https://infrafabric.io/if/trace/