The problem
A small document revision can affect procedures, controls, evidence, and owners, but broad manual rereads create noise and still miss dependencies.
What EKOS does
EKOS aligns old and new passages, moves unchanged citations forward, marks changed dependencies stale, and traverses reviewed relationships to produce affected items with reasons and suggested actions.
- Passage-level version alignment
- Silent migration for unchanged citations
- Stale relationship and provenance states
- Graph-based blast radius with inclusion reasons
- Controlled report and item lifecycles
How it works
When a new version arrives, EKOS aligns the old and new documents at the passage and section level.
Evidence that still cites unchanged text is silently re-pointed to the new version, so no review work is created for it.
Relationships, provenance, and mappings supported by changed or removed passages are marked stale and routed back into focused analysis.
EKOS walks the reviewed graph to build the blast radius, recording why each affected item was included, its severity, and a suggested next action.
Items move through an open, acknowledged, and resolved or dismissed lifecycle, and a report cannot be resolved while unresolved work remains inside it.
Business outcome
Teams receive a focused and explainable worklist instead of rereading every related artifact after each revision.
Proof and human control
Each report records its trigger, affected items, severity, inclusion reason, suggested next action, and controlled item lifecycle.
Example in practice
A password policy changes its rotation interval. EKOS marks relationships supported by the changed clause as stale and opens a report for the implementing procedure and related evidence.
Scope today
The internal document-change path is available. External regulatory orchestration remains preview, and impact quality depends on the reviewed relationships and ownership data available to the analysis.