# RFC 0003: MVP Architecture

## Status

Draft

## Goal

Prove that systems with evolving operational memory perform better over time
than stateless systems.

## MVP Features

- event ingestion
- candidate memory extraction
- confidence scoring
- structured retrieval
- validation and contradiction events
- memory decay
- historical timelines

## Preferred Stack

- PostgreSQL as the durable system of record
- simple HTTP APIs
- event-driven processing
- optional embeddings for recall expansion
- relational memory links
- deterministic scoring before complex model-driven scoring

## Core Services

Ingestion API:
Accepts events from agents, infrastructure systems, deployment tools, market
watchers, and human operators.

Extraction Worker:
Turns events and observations into candidate memories.

Memory Store:
Persists capsules, lifecycle events, relationships, permissions, and source
references.

Scoring Worker:
Updates confidence and freshness based on validation, contradiction, recall,
usefulness, source quality, and age.

Recall API:
Returns structured memories relevant to a task, environment, incident, or
decision.

Timeline API:
Exposes how a memory changed over time.

## Suggested API Surface

POST /events

POST /memories/candidates

GET /memories/search

GET /memories/{id}

POST /memories/{id}/validate

POST /memories/{id}/contradict

POST /memories/{id}/relationships

GET /memories/{id}/timeline

POST /recall

## MVP Measurement

Compare stateless and memory-backed agents across repeated operational tasks:

- time to diagnosis
- repeated error rate
- successful remediation rate
- recall precision
- recall usefulness rating
- contradiction detection rate
- stale memory suppression rate