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

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

---

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

- DOI is a persistent identifier + metadata record (not an integrity system).
- DOI resolution is built on the Handle System; registrants can update metadata and targets.
- DOI does not prove that a specific PDF or file byte stream is authentic.

## 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 answer: "What is this thing, and how do I refer to it?"
- DOI is global naming; `if.trace` is byte-level integrity.

## 4) Non-overlap (important)

- DOI does not validate integrity.
- `if.trace` does not provide a global scholarly identifier.

## 5) Recommended pattern (carrier model)

1) Mint a DOI to a landing page.
2) The landing page links to the `if.trace` pack (HTML-first).
3) If a Registration Agency allows it, include the `if.trace` receipt link in DOI metadata.

## 6) What not to claim

- Do not claim "DOI = verified bytes".
- Do not claim "if.trace replaces DOI naming".

---

## References (one URL per line)

https://www.doi.org/
https://www.doi.org/the-identifier/what-is-a-doi/
https://www.doi.org/doi-handbook/HTML/basic-principle-integration-of.html
https://www.crossref.org/services/content-registration/
https://infrafabric.io/if/trace/