# Trusted Records integration guide
Status: PROPOSED — no released backend or production credentials.

1. Open Developer Center; choose paper/device, born-digital, acceptance, identity or billing workflow.
2. Download openapi-proposed.json/yaml. Both are generated from the same specification. OpenAPI 3.1.1, contract 1.1.0-proposed.
3. Inspect security/scopes and tenant/project binding. Browser SSO is not machine authorization.
4. Read Swagger Reference (local assets, Try-It disabled). For offline simulation use Explorer, whose inputs are validated with Ajv 2020 against the same request schemas.
5. Exercise synthetic success, 422, 403, 409 and 503. Mutate required fields, enums, hashes and timestamps to verify validation. Reuse an idempotency key with the same body, then change the body to observe 409.
6. Device RECEIVED means receipt only. Require execution/observed-location evidence before physical reconciliation. Unknown physical outcome requires a state query/manual check, never blind replay.
7. Payment confirmation must be authenticated and reconciled. Invoice state is separate and asynchronous. There is no payable QR or live issuer in this package.
8. Agree provider contract, endpoint, issuer/audience, quota, timing, retention windows, event signing and approved data before requesting sandbox access.
9. Run authorized backend contract tests, fault injection and business acceptance. Offline success does not satisfy these gates.

## Proposed event recovery
Verify raw-body signatures server-side under the agreed signing contract; enforce timestamp and replay policies, tenant/context and object version. Persist eventId before acknowledging. Duplicate delivery must not repeat side effects. Ordering is per agreed object/version, not assumed globally. Exhausted retries enter audited exception/reconciliation handling.

## Release requirements
Confirm all proposed domains and provider mappings; do not treat example .invalid servers as callable. Do not log secrets/record content. Policies remain unissued drafts. Live backend, Flow R sheet-control, RAR, SSO, NAPAS and Trusted Billing integration tests: NOT RUN, no authorized environment provided.