Overview
Use the standard ContextResolver contract to resolve entities, relationships, timelines, permissions, presentation and actions.
Problem
Other applications need EngagementHub context through a trusted contract that preserves the canonical business runtime.
Solution
EngagementHub implements the eight ContextResolver operations over its canonical runtime and resource authorization.
How it works
A trusted application resolves an EngagementHub entity, loads relationships and timeline, asks for presentation and permissions, lists available actions, and executes an allowed action through the same operation layer used by direct calls.
Who is this for
Expected outcomes
- Fifteen explicit EngagementHub context entity types
- Relationship and timeline projections
- Available actions execute through canonical authorization
Key metrics
Resolved context entities restricted to declared types
0 %
100 %
Context actions routed through canonical operations
0 %
100 %
Secret/credential fields removed from context output
0 %
100 %
Gallery
Security impact
- Resolved engagement entities, relationships, timeline events, presentation fields and permissions · PII: Resolved entities can include workspace user/customer identifiers already present in authorized business records
Compliance
- Workspace-scoped application permissions and trusted execution context
- Operation/resource authorization for application calls
- Auditable workflow, queue, event or interaction records for this use case