ADR 002: Session Notes Storage

Status: Accepted Date: 2026-07-05 Issue: #2630

Decision

Hybrid approach: narrative markdown in docs/sessions/YYYY-MM/ (git), structured metadata in dev_r_agent_sessions columns (Supabase).

Rationale

• Option A (git only): no SQL query capability, notes not linkable from Grafana
• Option B (separate repo): cross-repo search becomes investigation bottleneck
• Option C (hybrid, chosen): Supabase provides SQL/Grafana searchability; git provides history, diff, PR context

Consequences

• Local dev sessions (Path B) write notes to git only — session_note_path stays NULL in Supabase. Known limitation, documented.
• docs/sessions/ will grow; monthly subdirs keep navigation manageable.
• EU AI Act Art.12 (tamper-evident git commits), Art.13 (SQL-queryable decisions), Art.14 (risks->priorities.md escalation).