From b11a369d869319ce9aa9a0a084368eea6326adb4 Mon Sep 17 00:00:00 2001
From: Val Alexander <68980965+BunsDev@users.noreply.github.com>
Date: Sat, 13 Jun 2026 03:19:55 -0500
Subject: [PATCH] Update what-is-a-harness.mdx

---
 content/docs/harnesses/what-is-a-harness.mdx | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/content/docs/harnesses/what-is-a-harness.mdx b/content/docs/harnesses/what-is-a-harness.mdx
index 1432bcb..9ea6c29 100644
--- a/content/docs/harnesses/what-is-a-harness.mdx
+++ b/content/docs/harnesses/what-is-a-harness.mdx
@@ -51,3 +51,11 @@ coven run claude "review this module"
 ```
 
 Use [Install harness CLIs](/docs/harnesses/installing) if either harness is missing, and [CLI run reference](/docs/cli/run) for command syntax.
+
+## A note on the word "harness"
+
+In Coven's software architecture, "harness" refers specifically to the PTY-driven adapter for an external coding-agent CLI (Codex, Claude Code, etc.). This is Coven's technical term for that adapter layer.
+
+This is distinct from "harness engineering" in the broader AI literature — where "harness" (in Lopopolo's sense and related research) refers to the scaffolding humans design *around* agents: prompts, constraints, feedback loops, taste invariants, and evaluation mechanisms. That broader sense describes engineering choices, not a specific software component.
+
+When Coven docs say "harness," they mean the PTY adapter. When AI research literature says "harness," it often means the engineered scaffolding. Both usages are legitimate in their contexts.