#Requirements Engineering
Hybrid Databases Were the Wrong Fix for Requirements RAG
A negative infrastructure result from a requirements RAG lab: Postgres, ParadeDB, and OpenSearch could host useful pieces, but none replaced the current retrieval stack without losing ranking quality or evidence bundles.
Read Post
The RAG Verifier Learned to Say No. It Still Missed a Hard Requirement Failure.
A held-out requirements RAG experiment: claim-level verification reduced harmful published answers from 35.7% selective risk to 4.0%, but strict human audit still found semantic completeness failures.
Read Post
Citations Were Not Enough for Safety-Critical Requirements RAG
A negative result from a requirements RAG lab: even with structured records, cited JSON answers, and deterministic guards, the answerer failed the abstention gate when evidence was insufficient.
Read Post
I Flattened 13,244 Requirements Into Chunks. 97% Lost Their Meaning.
A practical retrieval study over structured automotive requirements: why flatten-and-chunk failed, where ordinary top-k search stopped being the right tool, and how query routing improved both quality and latency.
Read Post
The Boring Part of Requirements Review Is Now Automated
How a lightweight AI agent eliminates the context-gathering overhead in safety-critical requirements review — so the architect can focus on judgment, not tool-switching.
Read Post