Skip to content
ContractSpec
Start here

reference

SupportOS case assignments

Revision-fenced claim, release, assignment, and governed steal semantics.

field.key.label
docs.customer-support.case-assignments
field.version.label
field.type.label
field.title.label
SupportOS case assignments
field.tags.label
supportos,assignment,collision,idempotency
field.owners.label
field.stability.label
public

Assignment mutations are scoped by authenticated tenant, workspace, and actor. Claim always derives the assignee from that actor. Release is limited to the current assignee or an administrator. Assign and steal require administrator authority, and steal also requires governed evidence. Every write is fenced by the case revision and a stable idempotency key. Durable authorities update the assignment projection and immutable case history atomically.

The steal decision is verified server-side and bound to scope, case, target, revision, and expiry. Exact receipt replay does not require a still-live decision; any new or changed mutation does.

An assign or steal mutation may bind a routing decision. Production authorities must revalidate the selected case, assignee, active team and membership, target queue, current policy revision, and live capacity, then consume that immutable decision exactly once in the assignment transaction. Authorities that cannot provide atomic decision consumption fail closed.