What problem does it solve? Setting up the cloud PingOne Authorize trust framework for the AI-Demo banking project is error-prone because the PingOne API cannot create COMPARISON-type conditions directly, forcing manual console work and guesswork about policy IDs, attribute IDs, and decision endpoint wiring. ## Core Features & Use Cases - Snapshot-Based Import: Import the authoritative AI_Demo_Transaction_Authorization_P1AZ.snapshot.json file to recreate the full policy set, including attributes, condition definitions, statements, rules, and policies with preserved synthetic IDs. - Condition DSL Reference: Documents the snapshot condition format (and/or/not/comparison/reference operators) and effectSettings types so policies like RequiresStepUp, HasValidActorChain, and RequiresHitlConsent can be authored correctly. - Post-Import Wiring: Guides the manual steps that snapshots cannot encode, such as binding the decision endpoint to the AI Demo Policies policy set and adding the BFF actor client ID clause to HasValidActorChain. - Use Case: After spinning up a new PingOne environment, import the snapshot, fetch a worker token via client credentials, verify the decision endpoint points to the correct policy set, and confirm HITL and step-up statements map to the right BFF obligations. ## Quick Start Ask the assistant to import the PingOne Authorize snapshot and wire the decision endpoint to the AI Demo Policies policy set using the worker credentials from demo_api_server/.env.