Use this page with AI

Copy this into your coding assistant and add your request.

Read https://openiap.dev/docs/foundation/whitepapers and https://openiap.dev/llms.txt. Follow the reading instructions, detailed reference, and linked guides relevant to my task before making changes.
Inspect my existing project and reuse its framework and conventions. Ask me for missing product decisions. Implement the requested behavior and run the applicable checks.
Show the working result, the commands and actual test results, and any remaining limitations. Keep your explanation brief.

My request: [describe what customers should be able to do]
See an example request →

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.