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.
# ORCID as a carrier for if.trace (if.bus preview one-pager)
**Audience:** preview cohort
**Reality gate:** no ORCID adapter is deployed on this host; this is a roadmap integration for `if.api` + `if.bus`.
---
## 1) What ORCID is (black/white)
- ORCID is a persistent identifier for researchers and contributors.
- It links people to works and affiliations via a registry.
- 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 are identity references for scholarly outputs.
- ORCID names people; `if.trace` attests to artifacts you publish.
## 4) Non-overlap (important)
- ORCID does not describe your transformation or receipt chain.
- `if.trace` does not serve as a contributor identity registry.
## 5) Recommended pattern (carrier model)
1) Use ORCID as the upstream contributor identity.
2) Produce an output pack (report, audit, decision).
3) Bind the output to `if.trace` receipts and link them alongside the ORCID IDs.
## 6) What not to claim
- Do not claim "ORCID = receipt for output bytes".
- Do not claim "if.trace replaces ORCID identities".
---
## References (one URL per line)
https://orcid.org/
https://info.orcid.org/documentation/
https://info.orcid.org/documentation/api-tutorials/
https://infrafabric.io/if/trace/