all

wiki/concepts/harness.md

@@ -16,6 +16,8 @@ The harness is the de-facto unit of agentic work in 2026. A good one has: a **sh
 
 **The business-facing formula.** An anonymous Russian business short ([[2026-07-22-ai-is-stupid]]) independently restates the concept for non-engineers: the harness is an "engineering wrapper" — what the model must verify, which tools to trust, how to shape the answer, what is forbidden — and **strong model + your business context + harness = employee-level answer**. Remove any component and you get "smart but generic," "specific but undisciplined," or "stupid AI." Useful as webinar language: it names what the audience already feels (generic answers) without requiring the engineering vocabulary.
 
+**A second reference harness: [[amp]].** Where [[claude-code]] is local-first and user-extended, AMP is sandbox-first and vendor-curated ([[2026-07-28-agentic-engineering-10x-developer]]): a PWA install, a low/medium/high/ultra dial that maps each level to a model *and* a sub-agent set, named sub-agents (**Oracle** the reviewer, **Painter** the image generator), a meta-agent (**Puck**) that spawns and messages other agents, and **orbs** — remote sandboxes where one URL carries thread + agent + computation + diff (see [[async-by-default]]). Two things it demonstrates about the concept: the harness is now the *product* (AMP's most-asked customer question is "what's the meta — what model, what prompt?", i.e. customers pay for research decisions), and a harness can be strong with **no user-authored skills layer at all** — the structure exists, but the vendor supplies it. That is the design axis [[hermes]] and Claude Code put in the user's hands.
+
 **The governance fault line:** [[eugene]] argues every developer should **build their own** harness (deep knowledge → more effective). [[sebastian]] counters that "bring your own harness" cannot survive enterprise compliance — it must be a company-managed resource, and *that gap is the business*. See [[enterprise-ai-reality]].
 
 ## Evidence
@@ -26,16 +28,18 @@ The harness is the de-facto unit of agentic work in 2026. A good one has: a **sh
 - Claude Code as the reference harness across surfaces — [[2026-07-14-gap-between-ai-users-irreversible]].
 - Consolidated multi-project workspace, inter-agent messaging, completion signals, "before and after" claim — [[2026-07-21-larysa-interview]].
 - Harness as "engineering wrapper"; model + context + harness formula; "stupid AI" as the harness-less default — [[2026-07-22-ai-is-stupid]].
+- AMP's dial/sub-agents/meta-agent/orbs; "what's the meta?" as the customers' recurring question — [[2026-07-28-agentic-engineering-10x-developer]].
 
 ## Related Pages
 
-- Tools: [[claude-code]], [[hermes]]
-- Concepts: [[skills-as-memory]], [[agentic-loops]], [[evolution-of-agent-tooling]], [[context-as-scarce-resource]], [[enterprise-ai-reality]], [[personal-ai-operating-system]], [[leave-less-room-for-imagination]]
-- Entities: [[eugene]], [[sebastian]], [[konstantin]], [[larysa]]
+- Tools: [[claude-code]], [[hermes]], [[amp]]
+- Concepts: [[skills-as-memory]], [[agentic-loops]], [[evolution-of-agent-tooling]], [[context-as-scarce-resource]], [[enterprise-ai-reality]], [[personal-ai-operating-system]], [[leave-less-room-for-imagination]], [[async-by-default]], [[shedding-weight]]
+- Entities: [[eugene]], [[sebastian]], [[konstantin]], [[larysa]], [[thorsten-ball]]
 
 ## Contradictions / Uncertainty
 
-- Personal vs company-managed harness is an unresolved tension (Eugene vs Sebastian), not a settled answer.
+- Personal vs company-managed harness is an unresolved tension (Eugene vs Sebastian), not a settled answer. [[amp]] adds a third option neither of them argues for: a **vendor-managed** harness, where the research decisions are the purchase and the user tunes almost nothing.
+- **Local vs remote.** Eugene's consolidation pitch assumes one place *on your machine*; Thorsten predicts local dev disappears into remote sandboxes. Compatible only if the thing being consolidated is the interface rather than the compute. Status: tentative.
 - The "life split into before and after" consolidation payoff is self-reported by its builder and never measured; Larysa, the practitioner it was pitched to, does not yet run one. Status: tentative.
 
 ## Next Questions