People and roles are Platform references without database keys

Context

User and role authority belongs to Platform, while CRM stores ownership and work-routing references. Local grammar does not establish that an actor can use the workspace.

Decision

The cited planning ruling asks for assignment eligibility validation, and the current persistence path still performs syntax-only checks. Role-only claims separately consult current role holding. The two checks must not be conflated.

Alternatives Considered

The structured alternatives describe concrete competing designs and their tradeoffs. Where the origin records an existing ruling, it remains the authority; an observed implementation does not establish Product’s rejection of every alternative.

Consequences

API-created routing can reference unavailable actors or roles. The pending assignment check remains an implementation requirement supported by its existing planning finding.