Scope the sentence, attach sources, run checks, and block language that does not survive.
Harness
Test the workflow where it actually runs.
A harness wraps a workflow, system integration, tools, state, permissions, memory, and validation loops. The point is not autonomy theater. The point is a compliance-ready run: what it did, what failed, and what a human still has to approve.
claim
model
workflow
dataset
agent
integration
01 ·
Harnessable surfaces.
You can harness anything worth operating
Wrap prompts, evals, thresholds, run records, and deployment context around behavior.
Bind handoffs, queues, owners, approvals, and receipts into a compliance-ready operating loop.
Pin sources, transforms, lineage, clocks, and readouts so the row can defend itself.
Give a base model tools, state, memory, permissions, tests, and a receipt-bound loop.
Control APIs, auth, retries, schemas, health checks, and failure modes before scale.
02 ·
Harness architecture.
The object is not the operation; the harness makes it operable
Defines the boundary, interface, allowed inputs, and expected outputs for the object.
Sets operating mode, permissions, thresholds, owner rules, and resource limits.
Connects the object to the systems it may inspect, mutate, query, or test.
Preserves goal, context, open changes, decisions, blockers, and run status.
Keeps stable project and domain facts from being rediscovered every cycle.
Runs checks, reads failures, narrows the claim, and emits receipts before handoff.
03 ·
Work loop.
How autonomy becomes useful instead of theatrical
Intake
Bind the user request to scope, files, constraints, and a declared success gate.
Act
Let the agent use approved tools to inspect, edit, run, and refine the code.
Validate
Run tests, linters, browser checks, fixtures, or probes that can actually fail.
Receipt
Return the diff, the checks, the failures, and the next compliance or approval gate.
04 ·
Readout states.
No mystical green checks
PASSThe workflow survived this probe under this context.
PARTIALThe workflow needs narrower language, better source material, or another run.
FAILThe workflow does not survive the harness. Do not ship the claim.
05 ·
Engineering handoff.
What implementation must preserve
state current_goal
The harness knows which object is active and what changed.
memory project_context
Stable customer, domain, and repo facts survive across the work loop.
tooling approved_surface
Every action runs through named tools, permissions, and boundaries.
validation run_receipt
The agent returns checks, failures, source links, and next gates.