Explainer

Loop Engineering vs Harness Engineering

Harness engineering designs the runtime around a model. Loop engineering compiles the known path for unattended work. Enterprise programmes need both — they fail in different places.

Nimbus Research

Loop engineering and harness engineering are two disciplines enterprise AI programmes confuse at their peril. Harness engineering designs the runtime around a model — tools, hooks, stops, eval sensors. Loop engineering compiles the known path for unattended work — triggers, recipes, skips, run pages. You need both. They are not interchangeable.

LangChain states Agent = Model + Harness. That equation is harness engineering’s centre of gravity. Loop engineering deliberately stays off that equation for the happy path: if the steps are known, compile them; do not pay tokens to re-derive them. Anthropic’s guidance on building effective agents makes the same architectural point: do not wrap a problem in agentic machinery when a fixed pipeline will complete the job.

Before the comparison lands, three nouns:

Eval loop — sensor that grades a run. See eval loops for enterprise agent harnesses.
Standing-order loop — job on a workstream that admits a run. See what is a standing-order loop.
Agentic workflow — interactive reasoning when the route is not fully known. See what is an agentic workflow.

An eval loop is not a standing order. A standing order is not an agent. Harness engineering owns the model path; loop engineering owns the compiled path. Mixing the words is how a programme buys sensors and still starts work from Slack.

Loop engineering vs harness engineering

Question	Loop engineering	Harness engineering
Unit of design	Compiled recipe on a workstream	Runtime around a model call
Happy path uses a model?	No	Yes
Primary failure mode	Silent drift, unrecorded skips	Tool misuse, prompt drift, false “done”
Primary artefact	Run page with outputs and skips	Hooks, sensors, versioned guides
Operator starts from	Form on a workstream	Chat or task inside a harness
Verification	Input sensors, skip rules, diff vs baseline	Eval loops, schema checks, human gates
Best reference	What is loop engineering	What is harness engineering

Loop engineering asks: can this job run the same way without anyone re-describing it? Harness engineering asks: when the model acts, what can it reach, and what independently verifies the claim?

Thoughtworks’ operating system for enterprise AI maps organisational layers — model, builder harness, user harness, organisational harness. Loop engineering sits closest to user harness for deterministic segments: feed-forward rules, deterministic feedback. Harness engineering owns the probabilistic segments and the hooks that refuse bad tool calls.

Neither replaces the other. A programme that only buys harness tooling will agent-wrap every checklist. A programme that only compiles loops will stall the first time someone says “it depends.”

Words you’ll hear

Compile. Turn a known checklist into a replayable recipe. Loop engineering’s verb.
Harness. Constrain a model: tools, stops, sensors. Harness engineering’s noun.
Happy path. The route that should not need judgement. Keep the model off it.
Exception class. A named kind of skip you might later attach to an agentic workflow.
Eval sensor. Grades a run. Does not admit a run. See eval loops for enterprise agent harnesses.
Hook. A refuse-or-allow gate around a tool call. Harness vocabulary.
Skip. A recorded halt on the compiled path. Loop vocabulary.
Guide / playbook. Feed-forward context. In coding harnesses, a file; in enterprise work, a wiki section on the workstream.

If a meeting uses “loop” for both a cron job and an eval sensor, stop and rename. You cannot staff a discipline you cannot point at.

When loop engineering leads

Choose loop engineering when:

the job already has a written checklist two people can follow
inputs are structured (APIs, sheets, exports), not scanned documents of unknown layout
the output is a table, list, or draft — not a novel strategy
runs should happen on a schedule or trigger without a human starting chat
cost and audit favour no model on the happy path

Examples: weekly pipeline exception lists, inventory threshold reports, connector health summaries, accrual mismatch passes, licence true-ups against a source of truth.

Loop vs RPA: prefer API reads and explicit skips over screen replay. Loop vs workflow vs agent: compile the segment that is stable; leave agentic workflow for the branch that is not.

Stanford HAI’s AI Index tracks capability rising faster than operational discipline. Loop engineering is discipline for work you already know how to do. Capability is not the bottleneck on a Monday exception table.

When harness engineering leads

Choose harness engineering when:

the step requires language generation with judgement (customer-facing prose, legal first draft)
tool selection is dynamic (which system depends on the case)
the environment changes faster than you can compile (greenfield code exploration)
verification must include inferential sensors (rubric-based quality) in addition to deterministic gates
you are wrapping an agent harness or enterprise agent harness

Examples: drafting a renewal brief from scattered notes, proposing a code patch with tests, summarising an incident with citations, negotiating which connector to query based on the question.

Eval loops for enterprise agent harnesses are harness engineering’s feedback layer. They do not admit runs; they grade them.

Böckeler on harness engineering and Thoughtworks on agent feedback sensors are the coding-native vocabulary — guides in, sensors back. The enterprise translation is wiki playbooks in, quoted writes and graph exports back. See write-back governance.

Harness engineering is not “add a model.” It is “when a model acts, bound it.” Without hooks and sensors, you have a chat window with production credentials.

How they meet on one job

Real work is a chain, not a purity test.

Segment 1 — compile. Nightly pull and exception table. Standing-order loop on a workstream. No model.

Segment 2 — collaborate. Humans resolve skips on the run page. Collaborative AI on the same roster. Still no model required.

Segment 3 — draft. For approved exception classes, an agentic workflow drafts customer email or CRM note. Harness engineering applies: tool allow-list, wiki context, eval sensor on tone and facts.

Segment 4 — act. Signed write to CRM. Governance as a multiplayer primitive. Harness sensor: payload hash matches execution.

Segment 5 — record. Lifecycle evidence for replay. Loop run page links to harness trace.

Buying only segment 3 because “we are an AI company” leaves segments 1, 2, 4, and 5 in Slack. Buying only segment 1 because “we hate agents” leaves segment 3 as manual paste from a personal chat tool — the worst of both worlds.

Four pillars of an enterprise AI platform is the hosting story: workstream holds the loop and the harness steps; governance holds the write plane; graph holds the evidence.

McKinsey’s State of AI reports usage ahead of redesign. Segment maps are redesign. A single “AI initiative” slide is not.

What goes wrong when you conflate them

Agent-wrapping a checklist. Every Monday the model re-reads instructions and re-derives spreadsheet logic. Cost scales with repetition. Drift scales with temperature. Audit sees a transcript, not a recipe version. See a loop is not an agent.

Treating eval as admission. A sensor that grades runs does not replace a standing order that starts them. See standing-order loops versus eval loops.

Harness without organisational ownership. Hooks exist; nobody owns skip trends on the compiled side. Incidents become prompt edits, not recipe updates.

Loop without escalation path. Ambiguous rows get “best effort” fills. Unknown path → person or explicit agentic workflow, never silent guess overnight.

Disposable agents ignored. Agents should be disposable for exploration. If the compiled loop depends on one irreplaceable prompt, you have not compiled — you have hidden a harness inside a scheduled job.

One scorecard. How to evaluate loop engineering and how to evaluate an agent harness are sibling sheets. Scoring fluency will buy you a copilot. Scoring skip semantics will buy you a standing order. You likely need both, on different segments.

Religious war. “We do not do agents” leaves judgement in side tools. “Everything is an agent” leaves checklists expensive and unauditable. Map the chain.

Conflation is a common lag pattern — one product category expected to solve operations and generation and governance. It will not.

Governance and risk (both disciplines)

NIST AI RMF applies to both: Map the job, Measure what ran, Manage controls after incidents. Loop engineering contributes Measure via run pages and skip logs. Harness engineering contributes Manage via hooks and eval ratchets.

ISO/IEC 42001 wants documented roles. Loops name roster and owner. Harnesses name who may add tools.

Stanford HAI AI Index tracks deployment velocity. Velocity without segment clarity produces headline pilots that do not survive audit season.

Regulatory texts — Sarbanes-Oxley, EU AI Act, GDPR — rarely name either discipline. They ask operational questions: who decided, what ran, can you replay it. Loops answer for unattended segments; harnesses answer for model segments. Human-in-the-loop remains the bridge for judgement.

A practical control split: compiled segments should be replayable without a model; model segments should be refuse-able without trusting the model’s manners. Write-back governance sits on actions from either path.

A worked example: vendor invoice matching

Accounts payable matches invoices to purchase orders every day.

Loop segment (compile). Trigger: files in the AP inbox folder. Recipe: read invoice metadata via a structured parser, read the purchase-order export, apply matching rules, output an exception list, notify the AP lead. Skips: unknown vendor code, multi-order ambiguity. No model on the happy path.

Harness segment (judgement). For “fuzzy description match” rows escalated to a queue, an agentic workflow proposes line mapping with citations to prior approved matches. Harness: read-only history connector, wiki “AP matching v2,” eval loop samples a tenth of cases for controller review.

Collaborative segment. AP lead and controller work skips on the workstream. How to evaluate collaborative AI: same run page, named signers, stored rejections.

Action segment. Approved match posts to ERP. Write-back governance. Harness sensor on payload.

Score the programme: loop metrics (skip rate, time to list) and harness metrics (refusal rate, eval pass rate). How to evaluate loop engineering and how to evaluate an agent harness are sibling scorecards.

Human–AI team research (Yang et al., Nature Human Behaviour, 2022) supports explicit division of labour. Loops and harnesses are that division made architectural.

Walk a Tuesday. Eighty invoices match by rule. Twelve skip for unknown vendor codes and go to the human queue. Three fuzzy descriptions enter the harnessed workflow; one proposal is refused because the citation is a different legal entity. Two signed posts go to ERP. The run page shows all of that. Nobody asked a channel “did the bot run.”

If you had agent-wrapped the entire inbox, those eighty matches would have been eighty opportunities to drift. If you had compiled only, the three fuzzy rows would have sat until someone invented a private workaround.

How to start this quarter

Do not launch a “loop versus harness” religious war. Map one job.

Draw the chain from trigger to outcome. Box each step.
Mark steps as compile, collaborate, generate, or act. Most chains are mostly compile.
Implement compile first on a workstream with outputs only. What is loop engineering.
Add harness only on marked generate steps with one eval sensor and one refuse case. What is harness engineering.
Run ten cycles. Count skips (loop) and refusals (harness). Update recipe or hooks — not both in one undifferentiated “AI tuning” meeting.
Promote one action class only after outputs match the manual baseline and at least one rejection has been stored.

If your vendor cannot show a run page and a harness trace for the same job, ask which discipline they actually sell.

Staff the work accordingly. Recipe ownership is an operations role. Hook and sensor ownership is a platform or risk role. Do not assign both to “the AI champion” and hope.

How this shows up in Nimbus

The platform hosts both patterns on the same workstream. A Loop is the compiled standing order — trigger, recipe, run page, skips. Harness controls apply when a model step is attached for an exception class or an agentic workflow: tools, stops, eval sensors.

Governance sits on the write plane for either path. Operators should still be able to point at each object separately. See what is a Nimbus Loop and what is harness engineering.

Product surfaces: workstreams and governance.

Sources

Common questions

Two disciplines, one programme

Which comes first — loop engineering or harness engineering?

Start with loop engineering for jobs that already have a checklist and no model on the happy path. Add harness engineering when a step needs generation, tool use, or non-deterministic judgement. Most operational chains are mostly compile: read, rule, table, notify. Generation is a segment, not the programme. Use this order so you do not pay tokens to re-derive VLOOKUP logic every Monday. Refuse a plan that begins with an agent wrap because the vendor demo was fluent.

Can one vendor do both?

A platform can host both patterns. The disciplines stay distinct: compiled recipes with skips are not the same object as hooks and eval sensors around a model. Ask to see a run page for the compiled segment and a harness trace for the generative segment — separately, on the same job. Use one workstream so roster and connectors are shared. Refuse a single slide that calls every scheduled prompt a loop and every checklist an agent. If the vendor cannot show each object, they sell one discipline and market the other.

Does harness engineering replace RPA or loops?

No: harness engineering wraps model steps, loop engineering compiles deterministic paths, and RPA replays screens. Pick the simplest tool for each segment of the job. Use APIs and recorded skips instead of screen replay when the interface will change. Use a harness only where judgement or generation is required. Refuse to replace a working compiled path with an agent because the word agent is in this year's budget, and refuse to call a brittle click-path loop engineering. See loop vs RPA.

Related guides

Loop vs RPA

See what governed AI looks like on your stack.

Connect your tools, run a workstream, and keep every decision on your ledger. Start on Free.

Request Access Talk to our team

Related guides

Loop vs RPA

Agents Should Be Disposable

See what governed AI looks like on your stack.