Clari Offline Contract Development Loop

Overview

Make offline development the default and live provider calls an explicit integration stage. Model the provider’s authentication headers, job transitions, pagination, error objects, and schema drift without storing secrets or production records.

Prerequisites

• Chosen Clari surface and pinned contract version or fingerprint
• Synthetic fixtures covering success, empty, partial, and failure responses
• Local secret scanning and test-data classification rules

Instructions

Step 1: Define the contract boundary

List endpoints, headers, request fields, response fields, job states, and pagination semantics used by the integration.

Step 2: Build synthetic fixtures