Whitepapers

Longer-form documents that explain the reasoning behind OpenIAP’s design, published as PDFs so they can be read and cited outside the repository. Each states its own scope and what it does not establish. The specification remains authoritative for normative wording.

Why the Commerce Protocol Draws Its Boundaries Where It Does#

Version 1.1 · 7 September 2026 · read the PDF · Markdown source

A design paper connecting purchase verification, account ownership, lifecycle state, and current access. It explains the trust boundaries, then develops a provider architecture, persistence model, processing and recovery paths, and an implementation acceptance plan.

Design rationale and a non-normative implementation blueprint for server engineers. Protocol 1.0 remains unchanged. No empirical performance result or independent interoperability claim is made; this paper has not been peer reviewed.

The studies these documents draw on, and the engineering backlog derived from them, are catalogued under Research Foundations.