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.
# Dropbox Sign as a carrier for if.trace (if.bus preview one-pager)
**Audience:** preview cohort
**Reality gate:** no Dropbox Sign adapter is deployed on this host; this is a roadmap integration for `if.api` + `if.bus`.
---
## 1) What Dropbox Sign is (black/white)
- Dropbox Sign (HelloSign) is a hosted e-signature service with APIs for signature requests.
- It manages signing flows and audit events for documents.
- 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 signed document bytes.
- Dropbox Sign manages signature workflows; `if.trace` attests to the outputs you publish.
## 4) Non-overlap (important)
- Dropbox Sign does not provide receipt chains for your output artifacts.
- `if.trace` is not an e-signature workflow service.
## 5) Recommended pattern (carrier model)
1) Use Dropbox Sign for the signing workflow.
2) Produce an output pack (signed PDF, audit log export, summary).
3) Bind the outputs to `if.trace` receipts and link them alongside the signature request record.
## 6) What not to claim
- Do not claim "Dropbox Sign = receipt for output bytes".
- Do not claim "if.trace replaces Dropbox Sign workflows".
---
## References (one URL per line)
https://developers.hellosign.com/
https://developers.hellosign.com/api/reference/welcome/
https://infrafabric.io/if/trace/