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

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

---

## 1) What Adobe PDF Services is (black/white)

- Adobe PDF Services (Acrobat API) provides hosted PDF operations such as OCR, export, and optimization.
- It is an API surface for transforming PDF inputs.
- 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.
- Adobe PDF Services transforms inputs; `if.trace` attests to the outputs you publish.

## 4) Non-overlap (important)

- Adobe PDF Services does not provide receipt chains for your outputs.
- `if.trace` is not a hosted PDF transformation API.

## 5) Recommended pattern (carrier model)

1) Use Adobe PDF Services for the transformation.
2) Produce an output pack (report, OCR output, conversion).
3) Bind the output to `if.trace` receipts and link them alongside the transform job record.

## 6) What not to claim

- Do not claim "Adobe PDF Services = receipt for output bytes".
- Do not claim "if.trace replaces Adobe PDF APIs".

---

## References (one URL per line)

https://developer.adobe.com/document-services/apis/pdf-services/
https://developer.adobe.com/document-services/docs/overview/pdf-services-api/
https://developer.adobe.com/document-services/docs/overview/pdf-services-api/howtos/
https://infrafabric.io/if/trace/