Product

From capture to recall: the Kiomon pipeline, explained

A walk through the capture, clean, connect, and remember pipeline, and how memory graphs organize agent context.

Turning unstructured real-world web content into reliable, high-precision context for AI agents is not a one-step operation. A raw web page or unformatted meeting transcript contains noise, broken scripts, navigation sidebars, and disorganized information that can confuse even the smartest reasoning model.

To make information truly useful for autonomous agents, Kiomon runs every piece of ingested knowledge through a structured 4-stage pipeline: Capture → Clean → Connect → Remember.

01 Capture • Browser Extension • Cloud Connectors • Agent Reflections • Ingest API 02 Clean • Reader Mode Strip • Entity Extraction • Claim Distillation • Memory Kind Tag 03 Connect • Auto-Linking Graph • Bidirectional Edges • Context Topology • Tenant Isolation 04 Remember • Hybrid Search • Grounded RAG • MCP Protocol • Ranked Recall

Stage 01: Capture

Information arrives from multiple disjointed touchpoints in a developer’s daily workflow:

  • Browser Extension: 1-click clipping of technical documentation, articles, and research papers.
  • Cloud Connectors: Continuous, chunked synchronization with team knowledge bases.
  • Agent Reflection: Working notes and architectural rules drafted by coding assistants during active sessions.
  • Direct Ingest API: Programmatic ingestion from CI/CD pipelines and webhooks.

Every incoming payload is normalized into standard UTF-8 text with metadata preserving its origin URL, timestamps, and workspace ownership.

Stage 02: Clean & Distill

Raw documents contain clutter: cookie banners, tracker scripts, duplicate headers, and navigation menus. Stage 02 extracts the signal from the noise:

  1. Reader Mode Filtering: Strips HTML boilerplates and generates clean markdown text.
  2. Entity & Claim Extraction: Identifies key architectural concepts, design patterns, and factual claims.
  3. Taxonomy Categorization: Tags the content into distinct cognitive kinds (Episodic, Semantic, Procedural, or Reference) to optimize how models query it later.
Raw HTML Payload ──> [ Reader Filter ] ──> Clean Markdown ──> [ Entity Extraction ] ──> Structured Record

Stage 03: Connect & Graph

Isolated documents become forgotten silos. Stage 03 integrates the new knowledge into your personal knowledge graph:

  • Semantic Auto-Linking: Measures conceptual similarity against existing notes and establishes bidirectional graph edges.
  • Topological Clustering: Forms topic neighborhoods, allowing agents to navigate related concepts across diverse sources.
  • Tenant Isolation: Guarantees that all graph connections remain strictly scoped to your private workspace.

Stage 04: Remember & Ground

When an agent needs context, Stage 04 surfaces high-precision evidence cards:

  • Hybrid Ranking (BM25 + Dense Vectors): Combines exact keyword matching with semantic vector retrieval.
  • Evidence Formatting: Serves concise, citeable memory snippets over MCP to keep prompt token counts minimal.
  • Grounded Verification: Provides direct citation URLs so agents can ground their assertions in original source material.

The Result: Continuous Working Context

By structuring ingestion into a 4-stage engine, raw information transforms into an organized, queryable second brain. Your AI agents gain immediate access to clean, connected, and verified context whenever you work.

All field notes

Kiomon Engineering

We build persistent context, knowledge, and memory infrastructure for AI agents over native MCP.

Give your AI agent a brain that remembers

Stream persistent context to Claude Code, Cursor, and any MCP agent with zero setup friction.

Get started free View docs