By Nagarjuna Reddy Kamireddy (Nagarjuna K) · Agentic System Design

Designing StoneAge: Multi-Model Routing (GPT-5, GPT-4o, Gemini) & Why Search-Plus-Rules Beats Fine-Tuning in Systems of Record

Published November 16, 2026 · Lead AI Architect (Dubai, UAE)

LangGraph + OpenSearch Hybrid RAG GPT-5 · GPT-4o · Gemini Task Routing Mandatory Fresh Human Approval on Record Writes

1. Meet Users Inside the System of Record

Standalone internal chat portals suffer steep adoption drop-off because engineers must copy-paste data out of their authoring tools, lose document hierarchy, and manually re-verify compliance rules. When designing StoneAge at John Deere, we embedded the AI writing copilot directly inside the company's engineering system of record using a React frontend, FastAPI backend, Okta OAuth 2.0 authentication, and stateful LangGraph agents.

2. Why We Chose Search-Plus-Rules Over Weight Fine-Tuning

Stakeholders frequently ask whether to fine-tune an LLM on internal service manuals. In regulated manufacturing, pharma, and enterprise ERP environments, encoding factual product knowledge into model weights creates an auditability liability:

3. Zero-Trust Write Boundaries

Reading enterprise context and mutating official records require fundamentally different security postures. In StoneAge, agents can propose drafts, highlight safety-critical phrasing, and validate standards autonomously — but can only modify official engineering records after a fresh, explicit user approval, with every attempt written to an immutable audit log. For open-source implementations of transactional agent boundaries and compensating ERP rollbacks, see aegis-runtime.

About the Author — Nagarjuna Reddy Kamireddy

Nagarjuna Reddy Kamireddy (Nagarjuna Kamireddy / Nagarjuna K) is a Lead AI Architect, AI Solutions Architect, and Corporate AI Trainer in Dubai, UAE. Connect on LinkedIn or email gmailtonagarjuna@gmail.com.