What schemas and tool actions could a complaint environment expose?

A generated environment could expose case fields such as `case_id`, `owner_role`, `status`, `ack_due_at`, `investigation_due_at`, `policy_ref` and `record_version`. Related tables can hold evidence requests, acknowledgements and escalation decisions using stable foreign keys.

Tool actions could include `acknowledge_case`, `request_evidence`, `record_finding`, `propose_escalation` and `accept_handover`. Each action needs a documented input schema, permission check and state effect. Accepting a handover could require a receiving role and an open referral; proposing one should not automatically replace the current owner.

Mutation requests can carry `expected_version` to detect concurrent changes and an `idempotency_key` to prevent duplicate actions after a retry. A rejected mutation should return a structured reason without partially changing the case.

JSONL can hold initial records and action traces, while JSON Schema can describe accepted payloads. A reset operation can restore a named starting snapshot. Evaluation hooks can capture rejected actions, successful transitions and final state. Together, these contracts let a lab distinguish a model that describes the right process from one that can execute it through tools.