Production checklist

The Talent API serves the fictional sandbox and three live account/license reads. Start with the quickstart for the supported test check, generation and receipt journey. There is no hosted conformance runner. This checklist records the requirements for a future live integration. Work through it with the people who own each area as those capabilities become available. Case IDs refer to the proposed conformance cases, not tests currently run by Reflections. Signing off this list does not enable live checks or output submission, or authorize real talent use.

Keys and access

Requirement	Guide	Case
Secret keys live only on your servers, in a secret manager, never in a client or a repository.	Security
Each service uses a restricted key with only the scopes it needs.	Security
You can rotate a key without downtime, and you have done it once.	Security
`Reflections-Account` is set from your own record of which licensee a user acts for, never from user input.	Security
You handle `connection.revoked` by stopping checks for that licensee.	Connection revoked

Checks

Requirement	Guide	Case
Every request that names a talent, matches the name index, or sends a reference or voice sample is checked before it is generated.	Resolve talent	CT-CHK-01
The check carries the request the model receives: system text, rewritten prompt, references, model.	Bind the request	CT-CHK-01
A changed request gets a new check.	Bind the request	CT-CHK-08
`end_user.id` is an opaque platform ID, never an email or a name.	Privacy modes	CT-CHK-01
On `deny`, nothing is generated and the user sees `reasons[].sentence` as written.	Decisions	CT-CHK-02, CT-CHK-03
A `license_request` remedy is offered only where your product supports requesting licenses.	Request a license
Requests naming several talent are decided for all of them.	Multi-talent requests	CT-CHK-09
Disambiguation sends `talent` or `exclude_talent` only after the user answers.	Resolve talent

Escalations

Requirement	Guide	Case
`escalate` shows a pending state and generates nothing.	Handle escalations	CT-CHK-04
`check.resolved` is handled for `allow`, `deny` and expiry.	Handle escalations	CT-CHK-04, CT-CHK-05
Polling, if used, is no faster than every 5 seconds.	Handle escalations	CT-CHK-04
Checks the user abandons are cancelled.	Handle escalations	CT-CHK-07
Every interactive surface sends `on_escalate: "deny"`.	Handle escalations	CT-CHK-06

Outputs

Requirement	Guide	Case
Every output is submitted as a generation, or the sampled share when the obligation says `sampled`.	Submit outputs	CT-GEN-01
Nothing is delivered until the generation’s decision is `allow`.	Submit outputs	CT-GEN-02, CT-GEN-03
Held outputs stay private; previews carry the draft mark when `draft_watermark` applies.	Handle escalations	CT-HLD-01
`generation.released`, `generation.denied` and `generation.expired` are handled.	Handle escalations	CT-HLD-01, CT-HLD-02, CT-HLD-03
Every `generation_instructions` entry reaches the model.	Obligations

Provenance

Requirement	Guide	Case
The `ai.reflections.license` assertion is embedded unchanged, signed by your platform’s C2PA certificate.	Embed provenance	CT-PRV-01
The manifest declares `trainedAlgorithmicMedia` in a `c2pa.actions` entry.	Embed provenance	CT-PRV-02
The disclosure text is shown as written, where its `placement` says.	Embed provenance
The bytes submitted are the bytes delivered, apart from the manifest.	Submit outputs	CT-PRV-01

Sessions

Skip this area if you do not run live voice or video.

Requirement	Guide	Case
Tokens are renewed every `renew_every`, and output stops when renewal returns `session_not_active`.	Real-time sessions	CT-SES-01
Samples are sent at the `sampling` rate.	Real-time sessions	CT-SES-01
Output stops within 1 second of a `deny` sample or `session.terminated`, including queued audio.	Real-time sessions	CT-SES-02, CT-SES-03
Output never continues past the current token’s `expires_at`.	Real-time sessions
The disclosure is shown for the whole session.	Embed provenance

Revocations

Requirement	Guide	Case
`revocation.created` is verified, deduplicated and queued within 10 seconds.	Handle revocations	CT-RVK-01
The revocation feed is read with `after` at least every 60 seconds if you cache decisions.	Handle revocations	CT-RVK-02
Cached checks, authorizations and reuse windows are purged.	Handle revocations	CT-RVK-01
Provider copies are deleted and listed in the acknowledgement.	Handle revocations	CT-RVK-03
`post_revocation` is applied to released outputs.	Handle revocations	CT-RVK-04
Every revocation is acknowledged before `acknowledge_by`, and someone is alerted when one is not.	Monitoring	CT-RVK-01

Webhooks

Requirement	Guide	Case
Signatures are verified on the raw body, against every `v1` entry, with a 5-minute tolerance.	Handle revocations	CT-WHK-01 to CT-WHK-04
Duplicate deliveries are ignored by event ID, and older `sequence` values are ignored.	Webhooks	CT-WHK-05
The endpoint answers within 10 seconds and does slow work in a queue.	Webhooks	CT-WHK-01
A secret rotation has been rehearsed.	Security	CT-WHK-04

Usage

Requirement	Guide	Case
Usage is reported in the units and within the time each `usage_report` obligation names.	Report usage
Rejected records are logged and corrected with `correction_of`.	Report usage
Session usage is reported after each session ends.	Real-time sessions

Resilience

Requirement	Guide	Case
Every retry reuses its `Idempotency-Key`.	Caching and outages	CT-IDM-01, CT-IDM-02
`503` and timeouts fail closed for any request that names a talent, matches the name index, or carries a reference or voice sample.	Caching and outages	CT-IDM-03
`429` waits for `Retry-After`.	Caching and outages	CT-IDM-04
The JWKS is cached and refetched once on an unknown `kid`.	Security

Privacy

Requirement	Guide	Case
A prompt mode is chosen on purpose for each surface: `full`, `redacted` or `withheld`.	Privacy modes
`metadata` carries no personal data.	Privacy modes
Your privacy notice describes what you send to Reflections.	Privacy

Operations

Requirement	Guide	Case
Request IDs are logged with every call.	Monitoring
Alerts exist for webhook failures, overdue revocations and `503` rates.	Monitoring
Your on-call runbook links to status.reflections.ai and records the monitoring coverage you have confirmed.	Monitoring
Your team knows how to reach support and what to send.	Support

Sign-off

Area	Owner	Date
Keys and access
Checks and escalations
Outputs and provenance
Sessions
Revocations and webhooks
Usage
Resilience, privacy and operations

Keep the sign-off with your integration’s evidence. The hosted conformance suite is not available yet. Live keys are created separately in the dashboard and support only account and license reads. Use the sandbox to test the supported check and output endpoints.

Get started

Quickstarts

Concepts

Integration guides

Build

Go to production

Keys and access

Checks

Escalations

Outputs

Provenance

Sessions

Revocations

Webhooks

Usage

Resilience

Privacy

Operations

Sign-off

​Keys and access

​Checks

​Escalations

​Outputs

​Provenance

​Sessions

​Revocations

​Webhooks

​Usage

​Resilience

​Privacy

​Operations

​Sign-off

Keys and access

Checks

Escalations

Outputs

Provenance

Sessions

Revocations

Webhooks

Usage

Resilience

Privacy

Operations

Sign-off