Evidence-linked trend hypothesis
Harness architecture outlives model choice
Rules, tools, permissions, memory, evaluation, execution, and recovery are becoming a stable runtime layer while models remain replaceable components.
Current thesis
- For production agents, the harness is becoming a more durable product boundary than the identity of the model running inside it.
- Confidence: high.
- Supported by 6 normalized raw signals.
Source ledger
Publishable sources attached to this record.
| # | Source | Role | Public status |
|---|---|---|---|
| 1 | opencode.aisource | primary receipt | source_urls |
| 2 | github.comrepo | supporting receipt | source_urls |
| 3 | github.comrepo | supporting receipt | source_urls |
| 4 | github.comrepo | supporting receipt | source_urls |
| 5 | docs.inference.netdocs | supporting receipt | source_urls |
What is stabilizing
Agent products repeatedly need the same non-model capabilities: project rules, tools, permissions, execution isolation, memory, context compaction, subagents, traces, evaluation, and recovery. OpenCode makes providers swappable inside one developer experience. Hermes combines a model endpoint with skills and tools. Deep Agents and agentOS package orchestration and execution as reusable runtime components.
The model still matters, but it is no longer the whole system.
Supporting evidence
- OpenCode preserves rules, skills, sessions, and commands across model providers.
- An inference gateway gives applications a stable access contract while routing policy changes behind it.
- Deep Agents packages planning, files, memory, middleware, and subagents as a reusable harness.
- agentOS treats isolation, durable workflows, limits, and host-side secrets as runtime responsibilities.
Operational consequence
Teams should version the harness contract separately from model configuration. That means portable task fixtures, explicit tool schemas, provider-independent traces, and a regression suite that runs whenever either the model or runtime changes.