Oracle Publishes Agent Design That Keeps Credentials and Proof Outside the Model

Oracle has published guidance for production AI agents that separates reasoning from operational authority. Under its design, a model may propose an action, but the surrounding harness—not the model—holds credentials and confirms that the requested work occurred.

The distinction addresses a failure that can appear after an agent has done much of the underlying work. Oracle cites a replay of 16,758 coding-agent runs in which 60% to 69% of incorrect-answer runs in two tested systems had already found and edited the correct code. A completion claim therefore needs evidence from the system where the action took effect, rather than the model’s own account of the task.

A model proposes; the harness decides

Oracle defines an agent harness as the configured layer around a model that controls its context, permitted actions, action destinations, persistent state and proof of completion. Its five-layer architecture separates model, framework, harness, runtime and environment, assigning the harness authority, containment, continuity and proof.

That wrapper can also alter task results without changing the underlying model. Oracle cites a SWE-agent ablation across 300 SWE-bench Lite tasks where GPT-4 Turbo solved 18.0% with a purpose-built codebase interface and 11.0% with a plain shell. Harness-Bench found a 23.8-point gap between its best and worst configurable harnesses across 5,194 trajectories and 106 sandboxed tasks.

Performance gains do not identify the responsible control

The comparisons do not isolate which component produced each gain, because the tested adapters combine multiple mechanisms. Oracle also cites long-context Gemini 2.5 Pro reaching 50.8% on SWE-bench Verified with a fully observable environment and simple scaffolding. Oracle’s view is that scaffolding used to compensate for weaker reasoning may shrink as models improve, while identity and independent verification remain accountability controls.

The Oracle implementation is database-centered

Oracle presents an Enterprise Data Agent Harness workshop built around an approximately 300-line Python orchestration loop, database primitives and the SQLcl MCP Server. Its LangChain integration connects Oracle Database 26ai as a vector store, while its LangGraph integration adds OracleSaver checkpoints and OracleStore cross-thread memory. Oracle also describes a migration harness that moves a RAG corpus from MongoDB to Oracle AI Database 26ai through retrieved migration skills for sampling, schema translation, transfer, verification and reconciliation.