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

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

---

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

- PURL (Persistent URL) is a redirect-based identifier system.
- It provides stable URLs that can resolve to changing targets.
- PURL 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 help users resolve long-lived references.
- PURL points to a landing page; `if.trace` attests to the bytes you publish.

## 4) Non-overlap (important)

- PURL does not describe your transformation or receipt chain.
- `if.trace` does not manage redirect registries.

## 5) Recommended pattern (carrier model)

1) Use PURL as the persistent pointer.
2) Produce an output pack (report, audit, decision).
3) Bind the output to `if.trace` receipts and link them alongside the PURL landing page.

## 6) What not to claim

- Do not claim "PURL = receipt for output bytes".
- Do not claim "if.trace replaces PURL registries".

---

## References (one URL per line)

https://purl.org/
https://purl.archive.org/docs/index.html
https://infrafabric.io/if/trace/