The problem
Change intelligence has limited value when the people who own affected policies, procedures, controls, or evidence do not know that action is required.
What EKOS does
EKOS creates per-recipient alerts, resolves approved ownership and directory-group context where available, and falls back to tenant administrators when ownership cannot be resolved safely.
- Per-recipient tenant-scoped in-app feed
- Unread filtering and explicit read state
- Deep links for supported subjects
- Owner and team routing with administrator fallback
- Priority states for supported regulatory work
How it works
A supported event, such as an opened impact report or a reopened finding, creates a tenant-scoped alert.
EKOS resolves the recipient through an approved owned_by relationship first, then owner or author metadata that matches a person or team.
A team recipient fans out to the active members of a matching directory group.
When ownership cannot be resolved safely, the alert goes to tenant administrators instead of disappearing.
Recipients filter unread items, mark each one read explicitly, and follow deep links on supported subjects straight to the work.
Business outcome
Relevant work reaches responsible people while compliance teams retain a fallback when ownership data is incomplete.
Proof and human control
Each notification retains its tenant, recipient, subject, event context, read state, and supported route back to the work.
Example in practice
A policy revision opens an impact report for an owned procedure. EKOS alerts the resolved owner and links to the report so the owner can inspect what changed and why it matters.
Scope today
Current delivery is in app. Deep-link behavior depends on the notification subject and the product route currently available for it.