Audiences are resolved when a person reads

Context

A handover changes the people who should see work without changing the underlying condition.

Decision

Store audience references and the provider’s scope chain, then resolve people from current responsibility and role holdings at read time.

Alternatives Considered

Expand audiences into people when publishing: Cover and membership changes would require rewriting stored audiences.

Reconstruct every provider hierarchy in Platform: Each application would need to duplicate its hierarchy semantics in Platform.

Consequences

Effective holding changes apply to subsequent reads. Repeated area-and-scope combinations are resolved once per read. A future fan-out cache would require measured justification; none is established here.