The problem
The relationships among requirements, policies, procedures, controls, and evidence often live in fragile crosswalks that lose their supporting context.
What EKOS does
EKOS proposes and records typed document relationships, attaches evidence and provenance to each edge, and supports depth-controlled exploration across trusted connections.
- Typed document relationship categories
- Candidate, deterministic, and entity-rollup paths
- Edge-level excerpts and provenance
- Depth-controlled interactive exploration
- One reviewed graph shared across EKOS workflows
How it works
As documents finish indexing, EKOS discovers plausible neighbors and proposes typed connections such as implements, supports, maps_to, evidences, supersedes, and conflicts_with.
Every edge carries source and target excerpts, confidence, extraction method, model context, and review state.
Trusted views focus on approved and policy-auto-accepted relationships rather than presenting every unreviewed suggestion as fact.
The explorer expands one to three relationship hops from any document and can re-center on a neighbor.
Impact analysis, requirement coverage, evidence assembly, and MCP graph tools read this same reviewed graph, so one relationship has one meaning everywhere.
Business outcome
Teams can follow a consistent proof trail across the same reviewed relationships used by impact, compliance, evidence, retrieval, and agent workflows.
Proof and human control
Each edge exposes source and target excerpts, confidence, extraction method, model context, and review state rather than appearing as an unexplained line.
Example in practice
An auditor opens an access-control policy and follows reviewed relationships to its implementing procedure and evidence, inspecting the reason each connection was accepted.
Scope today
Trusted views focus on approved and policy-auto-accepted relationships. Graph coverage depends on the available source material and reviewed connections.