# fixtures

## Purpose

Synthetic repeatable evaluation and acceptance inputs.

## Ownership

harness-activation, parity, quality and workflow-proof scenarios.

## Local Contracts

Fixtures contain no credentials, real conversation transcripts or private user stores. Keep schema/protocol expectations explicit.

## Work Guidance

Update fixtures only for intentional contract changes, not to hide an implementation failure.

## Verification

Run their owning Rust tests and quality/workflow examples when those scenarios change.

## Child DOX Index

None. This document owns the full subtree.