Riven AIDocs

Internal Docs Platform

A Confluence-like internal documentation system built into the Riven AI platform for centralized engineering knowledge.

What is Internal Docs?

Internal Docs is a full-featured documentation platform built directly into Riven AI. Think of it as a Confluence-like wiki purpose-built for engineering teams — with typed pages, versioned content, inline comments, hybrid search, and first-class AI agent integration via MCP.

Instead of scattering knowledge across Notion, Google Docs, and Confluence, Internal Docs gives your team a single place to write, organize, and discover engineering documentation alongside the services and infrastructure you already manage in the platform.

Internal Docs is accessible through the platform UI, the Riven CLI, and programmatically via Connect RPC APIs. AI agents can read and write docs through the MCP server.

Why Internal Docs?

  • Centralized knowledge — All engineering documentation lives next to your services, deployments, and tasks.
  • Typed pages — ADRs, RFCs, runbooks, and API references are first-class citizens with structured metadata, not just plain wiki pages.
  • Version history — Every edit creates a new version. Diff any two versions to see what changed.
  • AI-native — The docs-mcp-server exposes 34 tools so AI agents can search, create, and update documentation autonomously.
  • Hybrid search — Meilisearch-powered BM25 + vector search across all spaces and page types.
  • CLI-first — Full CRUD, search, and management from the terminal via riven commands.

Architecture

Internal Docs is composed of four backend services that work together:

Architecture
text
┌─────────────────────────────────────────────────┐
│              Riven Platform UI                   │
├─────────────────────────────────────────────────┤
│                                                  │
│   pages-service        files-gateway             │
│   (53 RPCs, 8 svc)     (S3 presigned URLs)       │
│         │                     │                  │
│   search-service       docs-mcp-server           │
│   (Meilisearch)        (34 MCP tools)            │
│                                                  │
├─────────────────────────────────────────────────┤
│   PostgreSQL  ·  S3  ·  Meilisearch  ·  Auth    │
└─────────────────────────────────────────────────┘
ServiceRole
pages-serviceCore CRUD for spaces, pages, comments, labels, permissions, templates, and version history. 53 RPCs across 8 Connect RPC services.
files-gatewayGenerates S3 presigned URLs for uploading and downloading file attachments.
search-serviceHybrid search powered by Meilisearch (BM25 + vector). Indexes all pages across all spaces.
docs-mcp-serverModel Context Protocol server exposing 34 tools and 5 resource types for AI agent integration.

All services are authenticated via JWT and scoped to the user's organization through the platform-auth interceptor.

Key Capabilities

Typed Page System

Every page has a type that determines its metadata schema and behavior:

  • page — Standard wiki page for general documentation.
  • folder — Container for organizing child pages into a hierarchy.
  • adr — Architecture Decision Record with status, deciders, date, and supersedes fields.
  • rfc — Request for Comments with status, author, reviewers, deadline, and voting.
  • runbook — Operational runbook for incident response and procedures.
  • api-reference — API documentation page.
  • live-doc — Auto-updated page that stays in sync with external sources.

Built-in Templates

Seven templates are available out of the box to standardize documentation:

  • Blank Page, Folder, ADR, RFC, Meeting Notes, Runbook, Service Overview

Collaboration

  • Inline comments — Comment on specific sections within a page.
  • Footer comments — General discussion at the bottom of a page.
  • Reply threading — Threaded replies on any comment.
  • Resolve/reopen — Mark comment threads as resolved and reopen them later.

Organization

  • Spaces — Top-level containers that scope pages, labels, and permissions.
  • Page tree — Hierarchical parent-child organization within each space.
  • Labels — Colored tags for cross-cutting categorization. Space-scoped and auto-created on first use.
  • Permissions — Role-based access control at the space level.

Getting Started

1

Create a Space

Spaces are the top-level container for all documentation. Create one for your team or project:

Terminal
bash
riven spaces create "Engineering"
2

Create Your First Page

Add a page to your space. Use a template to get started quickly:

Terminal
bash
riven pages create --space engineering --title "Onboarding Guide" --type page

Or create from a template:

Terminal
bash
riven templates list
riven pages create --space engineering --title "Auth Migration" --template adr
3

Organize with Labels

Add labels to categorize pages across your space:

Terminal
bash
riven labels add <page-id> "backend" "priority:high"
4

Search Across Everything

Find documentation across all spaces using hybrid search:

Terminal
bash
riven search "authentication flow"

Next Steps

PreviousObservabilityNextSpaces, Pages & Content Types