JLJeremy Longshoreinjeremylongshore.hashnode.dev·2h ago · 8 min readEvery Safety Gate Has a Failure DirectionA deterministic recap tool ran for the first time on a live system. Within hours, its block-event table showed seventeen consecutive BLOCK events. The natural question: what broke? The answer was wors00
JLJeremy Longshoreinjeremylongshore.hashnode.dev·1d ago · 9 min readThe Relevance Score That Broke Our Cite-or-Refuse GateA test you write to satisfy an audit can catch a correctness bug that has been silently shipping in production. That's what happened in our local RAG system: a vector-retrieval assertion failed on a l00
JLJeremy Longshoreinjeremylongshore.hashnode.dev·1d ago · 23 min readThe Moat Is the Trust Layer: Turning a Local-RAG App into a BYOK Document-Intelligence PlatformThe moat of a local-RAG tool is not the chatbot. Anyone can wire Ollama to Chroma and put a Streamlit box on top; there are a hundred "local RAG in 100 lines" tutorials that do exactly that. The moat 00
JLJeremy Longshoreinjeremylongshore.hashnode.dev·4d ago · 11 min readRun the Readiness Audit Before You Flip DNSThe cutover that would have taken the money and then broken The DiagnosticPro migration moved a live product off Firebase, Firestore, GCP, and Vertex AI onto a single self-hosted VPS. New database eng00
JLJeremy Longshoreinjeremylongshore.hashnode.dev·5d ago · 9 min readSurviving CoreWeave: the GPU failures that burn your hoursYour 64-GPU job just threw Xid 94. Reschedule, or is the node dead? It comes down to one bit, and most people get it wrong. They see "memory error," panic, drain the whole node, and lose an hour babys00
