Skip to content

The ultimate harness for coding agents and beyond. All your agents. All your machines. One command center. Start with code, then follow your curiosity and build across disciplines: CAD, circuits, robots, games and music.

Docs: point to PRODUCT.md and ENGINEERING.md; mark the September direction docs superseded (#2777)

0xken158d8401f190cd
diff --git a/AGENTS.md b/AGENTS.md
index bd7b72d90..43b72083a 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -1,5 +1,8 @@
# Development and release work
+Read [ENGINEERING.md](ENGINEERING.md) before changing code: every change meets its standards. What Harness must
+achieve, and the targets code is measured against, is in [PRODUCT.md](PRODUCT.md).
+
Follow [CONTRIBUTING.md](CONTRIBUTING.md) and the component's instructions. For
validation and shipping, use [docs/validation-and-release.md](docs/validation-and-release.md).
diff --git a/PRODUCT.md b/PRODUCT.md
index 8e028cca9..79953ed79 100644
--- a/PRODUCT.md
+++ b/PRODUCT.md
@@ -14,8 +14,8 @@ It describes the product we are heading for, not the product as it is today. How
**Harness runs a crew of agents from every lab, on the machines you own, directed by a Product Manager agent, with
work verified before it ships.**
-- **A person says what they want; the crew delivers verified work.** The Product Manager turns accepted requests into
- tasks. Engineers build, Reviewers and Testers check, and the result is a merged change that works.
+- **A person says what they want; the crew delivers verified work.** A crew of agents led by a Product Manager agent
+ builds and checks it, and delivers a merged change that works.
- **People give direction, taste and acceptance, from anywhere.** They answer questions and approve results at the desk,
in the browser, on the phone or on the Harness device. Agents do the execution.
- **Agents are the labs' real CLIs** (Claude Code, Codex, OpenCode and the rest) under each person's own login, so a
diff --git a/docs/ideal-users.md b/docs/ideal-users.md
index fd26a8b58..9280a7fb3 100644
--- a/docs/ideal-users.md
+++ b/docs/ideal-users.md
@@ -1,5 +1,8 @@
# Who we're building Harness for
+> **The audience here is superseded on 2026-11-03 by [PRODUCT.md](../PRODUCT.md#who-it-is-for).**
+> The voice and wording rules still apply.
+
Product and marketing direction, September 20, 2026. Validate this working audience through real
projects, repeat use, contributions, and device purchases.
diff --git a/docs/product-direction.md b/docs/product-direction.md
index 1cd421fdc..cba96ddad 100644
--- a/docs/product-direction.md
+++ b/docs/product-direction.md
@@ -1,5 +1,7 @@
# Harness: product thesis and roadmap
+> **Superseded on 2026-11-03 by [PRODUCT.md](../PRODUCT.md).** Kept as history.
+
Working product thesis, September 27, 2026. This records the framing developed with the
founder and the product bet it suggests. Roadmap stages remain proposals for the order of
learning and investment. See the [system diagram and ownership boundaries](architecture.md).
diff --git a/docs/strategy/2026-09-26-what-we-are-building.md b/docs/strategy/2026-09-26-what-we-are-building.md
index 4e4e8c6e1..ab2837d10 100644
--- a/docs/strategy/2026-09-26-what-we-are-building.md
+++ b/docs/strategy/2026-09-26-what-we-are-building.md
@@ -1,5 +1,7 @@
# What we're building
+> **Superseded on 2026-11-03 by [PRODUCT.md](../../PRODUCT.md).** Kept as history.
+
Strategy proposal, September 26, 2026. An opinion to argue with, not a decision. It builds on the
[terminal tools market research](../research/2026-09-26-terminal-tools-market.md) and
[who we're building for](../ideal-users.md).