lens-serve

The Lens — serve: query the verified library via API + MCP.

The Lens is a neutral, reusable "lab-in-a-box" for systems discovery: you launch a lab (a systems observatory) that reads a system's artifacts, stages candidate findings, has a human verify them, and serves a verified knowledge library.

lens-serve is the serve module — the read side. It exposes the verified library for query: a read API plus an MCP interface, so people and agents can ask it questions. It is read-only over verified.

Where it sits

The shared database shape (candidates → decisions → verified, plus lineage and oversight) is defined in lens-core. This module reads it over an injected connection (LENS_DB_URL) — never hardcoded.

Related MCP server: kb-mcp-server

Launch (stub)

pip install lens-serve        # once published
lens-serve --help

Connection is injected (LENS_DB_URL in your environment) — never hardcoded. See .env.example.

Identity

This repo has a CHARTER.md — its core directive and its boundary within The Lens. Read it first. Precedent (how PROVES/Tapestry did it before) is guidance, not this repo's identity.

Status

Scaffold, 2026-09-26. Neutral/open. No proprietary source data.

The Lens — related repositories

Part of The Lens — a modular, nearly-decomposable kit for systems discovery. Each repo stands on its own; together they compose a lab (a systems observatory).

• lens-core — main lab repo: shared standard + composition + launcher + the decomposition method

• lens-ingest — intake: source material into staged candidate records

• lens-review — review: human accept/reject/edit; promote to the verified library

• lens-serve — serve: query the verified library (API + MCP) (this repo)

• lens-observe — observe: signals over activity (active / orphaned / degrading / blind)