AkurAI-Notes / docs/adr/008-hindsight-postmortem.md

Latest change b77c3b08fbd20b54aab76a630a41f7b53ddde2c8 - OLI-113: ADR 001 (Postgres+pgvector), ADR 008 (hindsight post-mortem) by Ólafur Búi Ólafsson

# ADR 008: Hindsight post-mortem and lessons

Status: Accepted (Platform Engineer, 2026-09-30) · Epic OLI-112 · Task OLI-113

## Context
The `hindsight` Postgres volume held the previous memory store. It was a container volume with no verified restore path, on a machine where `~/Projects` had already been destroyed once (only 2 of 49 projects recovered; no snapshot existed). It is kept untouched; nothing here deletes it.

## Decision (lessons applied to the new stack)
1. Restore, not backup: every store has a scheduled restore drill that diffs a sample (ADR 001).
2. Data lives under `~/Projects/data`, covered by the encrypted backup and snapshots, not an opaque volume.
3. Minimal moving parts on the critical store: stock Postgres + pgvector, no extra extension until eval demands it (ADR 002).
4. Observable before launch: health endpoints and alerts exist before consumers depend on the service.
5. No destructive operation on hindsight without a listed target and board approval.

## Consequences
Hindsight remains read-only reference until migration is verified. Schema and supersession rules are in ADR 005.