TEST — non-authoritative fixture data

Test API keys (pk_test_*) return fixture-driven responses that are non-authoritative and never represent real customers or real determinations. Every TEST response displays TEST MODE, NON-AUTHORITATIVE, and NOT A PRODUCTION CREDENTIAL. Use test mode only during integration development.

PILOT — production-path code, internal data only

The platform ran in pilot mode during early operator onboarding. Pilot data records exist in the database but were never governed by production evidence policy. Pilot records are identifiable by their pre-V4 policy versions. Reliance receipts issued against pilot records carry the same ISSUANCE_NOT_AUTHORIZED marker as all current records.

PRODUCTION_DATA — live determination data, no authoritative issuance

Current system state. Determination and evidence records are real, the machine trust endpoint serves live data, and reliance receipts are durable. API keys with pk_live_* prefix authenticate against pv_api_keys. The machine trust response authority field always reflects issuance_authorized=false, signing_key_present depends on the DB query result (currently 0 active signing keys), and authoritative_state=NOT_AUTHORIZED.

AUTHORITATIVE_ISSUANCE — not activated

Authoritative credential issuance requires Phoenix (CEO) activation: production signing keys enrolled, dual independent approval configured, CUSTOS operational, revocation capability live, and the issuance_authorized flag set to true in the authority module. Until activation, credential.authoritative=false in all responses and integrity.credential_signature.state=NOT_APPLICABLE. This state has not been reached. Do not claim or imply authoritative issuance in any downstream system.