← Latest Update

Agent plumbing, RAG fixes, and inference control for outcome engineers

Understanding the risks of OpenClaw. The piece frames OpenClaw as orchestration plumbing, not a standalone cloud, and details how its value and risks hinge on external models, APIs, and distributed trust boundaries. Outcome engineers must treat orchestration layers as fragile trust planes—design explicit provenance, least-privilege interfaces, and governance controls (Principles 09,10).

The laptop return that broke a RAG pipeline — and how to fix it with hybrid search. The story shows a RAG pipeline failing when stale or mis-scoped documents slip through and demonstrates hybrid search (vector similarity plus SQL predicates) as a practical fix. Outcome engineers should add predicate-based filtering and permission-aware retrieval to RAG pipelines to preserve ground truth and scoped context (Principles 02,06).

We replaced RAG with a virtual filesystem for our AI documentation assistant. The team replaces RAG with a virtual filesystem so agents can grep, ls, and cat docs instantly, cutting boot time to ~100ms and cost to near zero. That pattern treats documentation as first-class agent artifacts and points outcome engineers toward building agent-native interfaces and fast local ops instead of brittle retrieval layers (Principles 06,07).

Karpathy shares ‘LLM Knowledge Base’ architecture that bypasses RAG with an evolving markdown library maintained by AI. Karpathy proposes an LLM-maintained Markdown knowledge base that compiles, lints, links, and supplants RAG for mid-sized datasets. Outcome engineers can use self-maintaining knowledge artifacts to improve determinism, auditability, and operational documentation workflows (Principles 02,13).

Google adds Flex and Priority inference tiers to Gemini API for enterprise cost and reliability control. Google introduces Flex and Priority tiers so teams can trade cost for latency and reliability for agentic workloads. Outcome engineers should map inference tiers to SLAs, orchestrate tiered fallbacks, and codify cost-reliability tradeoffs into deployment pipelines to keep agents predictable in production (Principles 12,16).