← Back to all work GitHub AI and developer tools
RecallOps An incident-memory assistant that retrieves relevant resolved precedents and shows the evidence for operator review.
THE PROBLEM
What it sets out to solve. Past incident resolutions lose value when recommendations cannot be traced to service-specific history and observed outcomes.
THE APPROACH
How it comes together. FastAPI writes incidents and separate symptom, resolution, and outcome memories atomically. Retrieval admits only qualifying resolved incidents for the same service. Optional Bedrock reasoning summarizes the evidence and a read-only Managed MCP adapter audits the top recalled trail.
UNDER THE HOOD
Explore the architecture. Trace the components. Select a node for its role in the system.
Incident evidence and resolved-only memory recall8 COMPONENTS
INTERACTIVE 3DRecallOps
Python FastAPI SQLAlchemy
RecallOps / architecture
Operator console → FastAPI orchestration FastAPI orchestration → Configured embedder: embed memories FastAPI orchestration → Incident and memory store: transaction Incident and memory store → Resolved-only recall FastAPI orchestration → Resolved-only recall: investigate Resolved-only recall → Managed MCP audit: top precedent Resolved-only recall → Evidence summary: evidence Managed MCP audit → Evidence summary: audit receipt Evidence summary → Operator review Operator console → FastAPI orchestration FastAPI orchestration → Configured embedder: embed memories FastAPI orchestration → Incident and memory store: transaction Incident and memory store → Resolved-only recall FastAPI orchestration → Resolved-only recall: investigate Resolved-only recall → Managed MCP audit: top precedent Resolved-only recall → Evidence summary: evidence Managed MCP audit → Evidence summary: audit receipt Evidence summary → Operator review 01 Layer 1 Operator console Explore ↗
02 Layer 2 FastAPI orchestration Explore ↗
03 Layer 3 Incident and memory store Explore ↗
04 Layer 2 Configured embedder Explore ↗
05 Layer 2 Resolved-only recall Explore ↗
06 Layer 3 Managed MCP audit Explore ↗
07 Layer 3 Evidence summary Explore ↗
08 Layer 4 Operator review Explore ↗
Move to tilt · Drag to rotate · Arrow keys Drag to rotate · Tap a component 8 components · 9 connections
Ⅱ Pause motion↺ Reset view
▤ View in 2D2D diagram ◇ Return to 3D
01 Operator console Explore component + 02 FastAPI orchestration Explore component + 03 Incident and memory store Explore component + 04 Configured embedder Explore component + 05 Resolved-only recall Explore component + 06 Managed MCP audit Explore component + 07 Evidence summary Explore component + 08 Operator review Explore component + Trace connections 9 relationships Operator console → FastAPI orchestration FastAPI orchestration → Configured embedder embed memories FastAPI orchestration → Incident and memory store transaction Incident and memory store → Resolved-only recall FastAPI orchestration → Resolved-only recall investigate Resolved-only recall → Managed MCP audit top precedent Resolved-only recall → Evidence summary evidence Managed MCP audit → Evidence summary audit receipt Evidence summary → Operator review + Select a component to see how it fits into the system.
CAPABILITIES
What’s inside. 01 Atomic incident creation and resolution with provenance-rich memory events
02 Same-service resolved-only recall, relevance threshold, and five-result cap
03 CockroachDB VECTOR(512) cosine search and a local SQLite mode
04 Optional Titan embeddings, Nova Lite reasoning, and allowlisted MCP audit
05 Request tracing, readiness checks, and visible evidence IDs
TECHNOLOGY & BUILDING BLOCKS
Python FastAPI SQLAlchemy SQLite CockroachDB Amazon Bedrock MCP Docker
SCOPE & CURRENT STATE
Local workflow and integration code implemented and tested; no verified public cloud deployment is claimed.
CockroachDB Cloud, Bedrock, Managed MCP, and AWS hosting require live credential-based verification.
SQLite similarity is a local approximation, not numerically identical to cloud vector search.
Recorded outcomes are operator observations; the application does not independently verify them.
The system never executes remediation; append-only memory is enforced by API scope rather than a database immutability policy.