Mindtickle Contract-Fixture Development Loop

Overview

Make adapter development deterministic by separating domain behavior from the tenant transport and exercising only sanitized, versioned fixtures locally.

Prerequisites

• An authorized tenant contract digest and sanitized success and failure examples
• A product-specific adapter boundary from mindtickle-sdk-patterns
• A secret scanner and repository policy for generated or confidential artifacts

Tool Discipline

Use Read, Glob, and Grep to inspect code and fixtures, WebFetch only to refresh approved contract sources, and Write or Edit for local adapters, fixtures, tests, and documentation.

Current Contract

Public Mindtickle pages establish API families but not a public emulator or universal SDK. Local mode must therefore emulate the frozen customer contract, identify synthetic values clearly, and fail closed when an unrecorded operation appears.