Engineering Investigations
I investigate how AI systems fail, how to measure them, and how to make them trustworthy. The Code Archaeology series reads real code to find where design, implementation, and runtime diverge.
Featured Investigation
Code Archaeology · Part 10
"Code Archaeology Part 10 — The Abstraction That Earned Its Keep: after nine investigations into declared-but-unexecuted features, I went looking for one more — a single-implementation strategy ABC that looked like speculative abstraction. The evidence said otherwise: the interface lives in the domain layer with zero framework dependencies, every consumer depends on the facade, the injection point exists, and the second implementation is not a fantasy — CoVe and NLI are real, active research. This is the investigation where the pattern broke: the abstraction was right."
Finding
"A single-implementation strategy ABC turned out to be a correct dependency-inversion boundary — the series' first positive finding."
Code Archaeology
Forensic investigations into AI system failures — where architecture, implementation, and runtime diverge.
Code Archaeology · Part 9
HIGH
"The handover doc said the Review Agent wasn't wired to grounding — it was wired from the start, but to the wrong embedding model."
Code Archaeology
Grounding
Evidence
Review
Embedding
Engineering
"2026-08-02" · "15 min"Read more
Code Archaeology · Part 8
CRITICAL
"The knowledge base was indexed in 1024 dimensions; API queries ran in 1536 — two vector spaces in one system, and search could never work coherently."
Code Archaeology
Embedding
Vector Search
RAG
PGVector
Engineering
"2026-08-02" · "15 min"Read more
Code Archaeology · Part 7
CRITICAL
"POST /articles returned 201 Created, GET returned 404 — the entire API write path had zero commit() calls, and every 'successful' write vanished on session close."
Code Archaeology
Persistence
Transactions
FastAPI
SQLAlchemy
Engineering
"2026-08-02" · "15 min"Read more
Code Archaeology · Part 6
HIGH
"Sixteen typed event types fire into an empty listener list — the WebSocket endpoint has no clients, and the promised audit log is never written."
Code Archaeology
Events
WebSocket
Real-time
Observability
Engineering
"2026-08-01" · "15 min"Read more
Code Archaeology · Part 5
CRITICAL
"PostgreSQL trace stores exist with zero callers; the audit record lives in a Python list that evaporates on restart."
Code Archaeology
Observability
Audit
Trace
Engineering
"2026-07-20" · "15 min"Read more
Code Archaeology · Part 4
MEDIUM
"The three-way approval decision survives only in the enum — the frontend renders two buttons, the API can't carry modifications."
Code Archaeology
HITL
Approval
Engineering
Agents
"2026-07-12" · "15 min"Read more
Code Archaeology · Part 3
HIGH
"A complete hybrid retrieval subsystem (RRF + keyword + reranker) has zero production callers; the README claims BM25 that doesn't exist."
Code Archaeology
RAG
Hybrid Search
BM25
Engineering
"2026-07-05" · "15 min"Read more
Code Archaeology · Part 2
HIGH
"Edge.condition is defined and documented but never evaluated — the DAG executes every node unconditionally."
Code Archaeology
AI Agents
Workflow
DAG
Engineering
"2026-06-27" · "15 min"Read more
Code Archaeology · Part 1
CRITICAL
"The Evidence Agent emitted citations pointing at document_id='evidence_source' — a hardcoded string, not a real source."
Code Archaeology
AI Agents
Evidence
Engineering
RAG
"2026-06-20" · "15 min"Read more