Memory, coordination, and execution infrastructure for reliable AI agents.
Website: underpassai.com
Underpass AI builds the infrastructure layer around models: a coordination plane that runs auditable deliberations among councils of specialist agents, a memory plane that agents can navigate and audit, and an execution plane that governs how agents act on real systems.
We do not build foundation models. We build the operational substrate that makes them safer, more useful, and easier to inspect in production.
Memory plane — Underpass KMP — Kernel Memory Protocol
for temporal, multidimensional, auditable agent memory. Exposes an API-first
KernelMemoryService gRPC boundary for memory ingest, deterministic Wake/Ask,
temporal traversal, graph path tracing, and node inspection. Memory is scoped by
about, split into dimensions, connected by explicit relationships, and backed by
evidence and provenance.
KMP ships in two distributions that share the same protocol semantics:
- Infrastructure — typed gRPC server with Neo4j/Valkey/NATS adapters, Helm/Kubernetes deployment, full TLS/mTLS and observability. For teams running shared, auditable agent memory at scale.
- Local / embedded — the kernel in-process inside an MCP stdio binary: zero
infrastructure, per-project
.kernel/memory, fsync-durable, verified live in Claude Code and Codex. Same KMP tools with identical JSON by construction.
Coordination plane — MADE by Underpass — Multi-Agent Deliberation Engine runs structured deliberations (propose → peer-critique → revise → validate → score → winner) and longer declarative YAML ceremonies as explicit state machines. Enforces output contracts, can score with an LLM judge, and ships observability that shows why an answer won. Domain- and provider-agnostic. Kubernetes-first.
Execution plane — Underpass Runtime provides isolated workspaces, governed tool execution, policy checks, telemetry, and adaptive tool recommendations for tool-driven agents.
Together these three planes form infrastructure, not an application. Any domain that needs institutional memory plus governed action can be built on top.
Underpass is designed to run alongside existing infrastructure. Operational systems produce domain events. MADE convenes a council of specialist agents that investigate real systems, recover relevant memory through KMP, act through governed runtime tools, and record evidence back into memory.
Domain event fires
-> MADE convenes a specialist agent council
-> Agents investigate the real system
-> KMP restores scoped memory and navigable timelines
-> Runtime governs tool execution
-> Evidence is recorded
-> The next similar event starts with better memory
The common pattern:
domain event -> orchestration -> agent -> memory -> governed action -> evidence -> better memory
Reliable agents need memory they can navigate, not just context they can retrieve.
For real agentic work, it is not enough to ask which text chunk looks similar. The system also needs to answer:
- what was known at a given moment;
- which attempt failed;
- what changed later;
- which agent introduced a wrong assumption;
- why one answer replaced another;
- which evidence supports the final result.
Underpass KMP is built around that model: memory as a temporal, inspectable, multidimensional graph, not just raw transcript replay or vector search over chunks.
| Plane | Repository | Language | What it provides |
|---|---|---|---|
| Memory | kmp |
Rust | Underpass KMP: typed KernelMemoryService, deterministic memory retrieval, multidimensional memory, temporal traversal, trace/inspect, evidence-backed Ask, MCP adapter, Helm/Kubernetes deployment, embedded/local distribution |
| Coordination | made |
Rust | MADE: structured deliberation, YAML ceremonies, LLM-as-judge scoring, event-driven dispatch, output contracts, deliberation-native observability; use-case- and provider-agnostic; API-first |
| Execution | underpass-runtime |
Go | Isolated workspaces, governed tools, policy checks, adaptive tool recommendation, telemetry, mTLS, Kubernetes-oriented execution |
The rehydration-* names are historical repository and artifact names. The
public memory product name is Underpass KMP.
| Component | Ownership | Examples |
|---|---|---|
| Underpass KMP | Underpass | Memory protocol, temporal traversal, graph inspection, evidence model, embedded distribution |
| MADE by Underpass | Underpass | Council deliberation, YAML ceremonies, LLM-as-judge scoring, event-driven dispatch |
| Underpass Runtime | Underpass | Governed tools, execution isolation, policy checks |
| Integration adapter | Product/team using Underpass | Alert relay, CI/CD hooks, ERP connectors, domain event emitters |
| Application services | Product/team using Underpass | payments-api, order-svc, internal platforms |
| Observability and CI/CD | Product/team using Underpass | Prometheus, Grafana, PagerDuty, GitHub Actions, ArgoCD |
- API first: KMP behavior is defined by typed gRPC and domain contracts; MCP is an agent-facing adapter over the same memory semantics.
- Explicit scope: memory reads are scoped by current
about, selected abouts, or intentionally global reads. - Temporal traversal: callers can move through memory with
goto,near,rewind,forward,trace, andinspect. - Evidence and provenance: recovered memory carries refs, proof, relation metadata, and traceability.
- Fail-fast behavior: invalid scopes and unsafe fallbacks are rejected instead of silently widening a query.
- Observability: structured logs, metrics, traces, and relation-quality signals make memory behavior auditable.
- Infrastructure boundaries: TLS/mTLS, Kubernetes deployment, Helm tests, and adapter-based persistence roles.
Auditable multi-agent deliberation — ceremonies that turn a meeting of specialist agents into a first-class artifact: the winning contribution of each step returned over the API, the full debate replayable as a distributed trace in Grafana/Tempo, and the health of the decision process — judge discrimination, winner-score distribution, provider saturation, token cost — measured as Prometheus metrics.
Replayable operational memory for AI agents — a memory layer that lets people and LLMs inspect what happened, what each agent knew, where the process forked, which evidence mattered, and why the final resolution worked.
Current focus areas:
- KMP embedded distribution: zero-infrastructure, per-project memory verified in Claude Code and Codex;
- KMP discovery plugin for memory exploration by agents and humans;
- stronger MemoryArena, MemoryAgentBench, and LongMemEval evaluations;
- hybrid retrieval, reranking, and typed domain plugins;
- visual graph and timeline exploration for traversing agent memory;
- a small operator model trained to use KMP/MCP tools efficiently;
- MADE ceremony authoring and runtime observability runbooks.
- No queremos agentes que contesten. Queremos decisiones que se puedan auditar
- Operator: cuando responder no basta
- Building Kernel Memory Protocol: Navigable Memory for AI Agents
- Construyendo Kernel Memory Protocol: memoria navegable para agentes de IA
- What an event-driven agent pipeline looks like when you trace it end-to-end
- Why event-driven agents reduce scope, cost, and decision dispersion
Core infrastructure is deployed and validated on live Kubernetes clusters with TLS/mTLS-enabled boundaries. Underpass KMP includes typed gRPC memory APIs, temporal traversal, graph tracing, node inspection, scoped multidimensional memory, an MCP adapter over the same public API, and a local/embedded distribution verified in Claude Code and Codex.
MADE runs council deliberations and YAML ceremonies end-to-end against live
vLLM-served models on Kubernetes, with an optional LLM judge, the debate exported
as OpenTelemetry traces over mTLS, and a deliberation-specific Prometheus metrics
suite served at /metrics.
The project is active and evolving quickly. Public repositories are released under Apache-2.0 unless stated otherwise.
Underpass AI is a project created by Tirso Garcia Ibañez.