Riven Docs
See GitLab proof

Resources

Architecture

The whole system in one view: what triggers Riven, the Orbit-backed analysis path in the middle, the risk contract it emits, and the GitLab and remediation surfaces downstream.

Riven architecture - Orbit-backed merge governance for GitLab

Open the full-screen view ->

The three paths

  • Graph path. Riven indexes the repository with Orbit Local, maps the MR diff to changed definitions, and traverses inbound static CALLS edges to find impacted callers.
  • Contract path. The analyzer turns that evidence into risk-contract.yaml, risk factors, verification guidance, and explicit limits.
  • Remediation path. Optional AI and MCP flows can draft proposals, validate candidate diffs, and verify them in a temporary worktree without changing the original gate.

Reusable as infrastructure

Riven is not just a CLI:

  • a GitLab CI scaffold turns it into a merge-request gate
  • an MCP server exposes the same workflow to external tools and agents
  • an AI Catalog agent packages the interface for GitLab Duo Agent Platform

See How Riven works for the analysis pipeline and GitLab gate for the enforcement path.