I/O Mesh

Product docs — docs as mesh products

PRDs and runbooks scatter across Notion and Confluence. Ingest doc changes as governed products under department tenancy. Knowledge mesh stays Beta — not GA. Private evals on your facts. Create a workspace when ready.

Who it's for

Product manager or product ops lead — PRDs, specs, and runbooks spread across Notion or Confluence.

The problem

PRDs and runbooks scatter across Notion and Confluence. Agents cite stale doc chunks disconnected from live incidents and shipping work.

Outcome

Docs as mesh products — ingest doc changes as governed products under department tenancy. Knowledge mesh stays Beta — not GA. Private evals on your facts.

Workflow map (2026)

Knowledge agents underperform when docs are RAG islands. 2026 buyers want doc events on the same fabric as incidents and shipping work (knowledge mesh Beta — not GA).

Product opsTechnical writerEng manager

Build

Notion/Confluence (Beta) page events as knowledge products with contracts.

Steer

compose_knowledge_mesh ties runbooks to live ops evidence.

Compound

Citation accuracy evals — incident→runbook match on your corpus.

Learning loop

PRDs, runbooks, and wiki changes compound as dept.* knowledge products. Knowledge mesh stays Beta — not GA.

Questions agents answer

  • Which runbook matches the live PagerDuty incident?
  • What changed in the PRD since last sprint?
  • Cite the spec section that governs this API behavior.

How it works on I/O Mesh

  1. Step 1

    Ingest doc platform webhooks

    Connect Notion or Confluence — page updates publish to dept.product.events.docs.* with department routing and audit.

  2. Step 2

    Catalog contracts

    Self-serve data product catalog surfaces subject patterns, freshness SLOs, and lineage for evaluators.

  3. Step 3

    Cross-link to ops evidence

    Compose knowledge products with operational incidents and PRs — agents cite the runbook that matches live engineering context.

  4. Step 4

    Governed recall

    MCP compose_knowledge_mesh retrieves doc products without ad-hoc exports or company-wide search indexes.

Departments

  • Product
  • Engineering
Knowledge meshOperational mesh

dept.* stream patterns

  • dept.product.events.docs.notion
  • dept.product.events.docs.confluence
  • dept.engineering.events.github
Browse data product catalog →

What ships today

  • Notion + Confluence connectors (Beta) — real webhook path
  • Google Drive + SharePoint connectors (Beta) — real webhook path; multi-tenant installs may lag
  • Knowledge mesh compose via MCP catalog discovery
  • Cross-layer lineage from connector through enrich to memory
  • FAIR metadata and contract enforcement opt-in

Governed MCP tools

  • list_catalog_data_products
  • compose_knowledge_mesh
  • get_catalog_contract
Typical company stage
scaleup
Evaluation path
Ingest doc changes as governed products under department tenancy. Knowledge mesh stays Beta — not GA. Private evals on your facts. Create a workspace when ready.
Pricing
Estimate usage meters and add-ons

Outcome metrics

Leading indicator
Doc products with cross-linked ops evidence
Lagging indicator
Incident→runbook citation accuracy

Recommended connectors

  • Notion

Each live connector bills as a usage meter — install from Integrations after signup.

Related solutions

B2B SaaS

PLG-to-enterprise learning loops across engineering, product, sales, CS, and support — governed dept.* products agents can consume, not a company-wide vector dump.

Platform engineering and SRE

AI-SRE-ready context plane for incidents, deploys, and on-call evidence as governed dept.* products — agents investigate with lineage, not another alert chat box.

Start compounding this workflow — create a workspace with the use case pre-selected.

Create a workspace Explore platform Browse all use cases