---
type: "post"
stable_id: "post:the-harness-owns-the-work-and-the-accepted-artifact-closes-the-loop"
slug: "the-harness-owns-the-work-and-the-accepted-artifact-closes-the-loop"
title: "The Harness Owns the Work; the Accepted Artifact Closes the Loop"
description: "Agentic engineering is moving from one prompt to a persistent harness that manages environments, cost, review, release, and maintenance."
retrieval_nugget: "The output metric is shifting from model calls to accepted work: merged changes, shipped artifacts, and maintained systems, with review burden and vendor claims kept visible."
published_at: "2026-08-14"
updated_at: "2026-08-15"
record_date: "2026-08-14"
date_kind: "discovered_at"
topics: ["harness-engineering","coding-agents","workflow"]
entities: ["Databricks","Vercel","Cursor","Factory"]
source_urls: ["https://www.databricks.com/blog/managing-ai-coding-costs-scale","https://vercel.com/blog/building-a-software-factory-for-ai-sdk","https://wesmckinney.com/blog/agentic-engineering-aug-2026","https://cursor.com/blog/builds","https://factory.ai/news/agent-effectiveness","https://x.com/bcherny/status/2088014489438621990"]
source_format: "article"
editorial_timing: {"lane":"regular_hourly","scheduled_at":"2026-08-22T08:00:00+03:00","real_news_delta":"owner-selected cross-source synthesis"}
origin: {"basket_id":"5854f7b2-5954-4d2a-8997-81596a49da74","basket_revision":1,"target_kind":"synthesis","target_id":"d615eda9-a4cb-4cd8-b31d-b3aed4c34d47","owner_selection":"45","route":"hermes"}
visual_decision: {"outcome":"generate_explanatory_diagram","status":"included","reason_code":"mechanism_or_flow","explanatory_value":"a persistent harness turns incoming work into tested, reviewed, accepted artifacts and feeds production evidence back into the next task","text_only_limitation":"The pattern joins environment setup, implementation, review, release, measurement, and maintenance; a loop diagram exposes the ownership and acceptance boundary better than a list.","owner_reviewed":true,"reviewed_by":"owner-and-codex"}
schema_version: "newruntime-agent-readable-v0.2"
status: "published"
visuals: [{"role":"hero","src":"/images/drip/the-harness-owns-the-work-and-the-accepted-artifact-closes-the-loop/the-harness-owns-the-work-and-the-accepted-artifact-closes-the-loop.webp","alt":"New Runtime whiteboard diagram explaining the harness owns the work; the accepted artifact closes the loop.","caption":"New Runtime synthesis from databricks.com."}]
routes: {"html":"https://newruntime.com/posts/the-harness-owns-the-work-and-the-accepted-artifact-closes-the-loop/","markdown":"https://newruntime.com/posts/the-harness-owns-the-work-and-the-accepted-artifact-closes-the-loop.md","json":"https://newruntime.com/posts/the-harness-owns-the-work-and-the-accepted-artifact-closes-the-loop.json"}
---

# The Harness Owns the Work; the Accepted Artifact Closes the Loop

## Retrieval answer

The output metric is shifting from model calls to accepted work: merged changes, shipped artifacts, and maintained systems, with review burden and vendor claims kept visible.

Agentic engineering is moving from one prompt to a persistent harness that manages environments, cost, review, release, and maintenance.

New Runtime reading: The output metric is shifting from model calls to accepted work: merged changes, shipped artifacts, and maintained systems, with review burden and vendor claims kept visible.

Evidence boundary: this item uses the listed public sources and keeps vendor, author, or reporter claims attributed. The queued page is an editorial synthesis, not an independent validation of every reported metric.