Skip to main content
Answer this with a file. A domain-specific harness is the loop, the tools and the rules that make a general model useful for one job: insurance intake, a research desk, a contract review, a company’s own integrations. The model is the same one everyone has; the harness is the part that’s yours, and most of it is process: what runs first, what checks it, what happens when the check fails, and who signs at the end. The general form, one model and one loop, is the neighbour term, an agent harness.

​
In Obversa

Products built on a model end up owning the process around it, and in code that process is a workflow. A contract review is one for a field that isn’t software: the playbook is the brief, one model maps and redlines, a model from another family checks, and a lawyer decides what is sent:
examples/use-cases/business/contract-playbook.ts (excerpt)
The stages that follow name what each role writes, who checks it, and where a failed check goes. The whole file and a real run are on Contract review.

​
The three parts

Claude Code, Codex and the others are the agents the harness drives; each has its own inner loop. The person is part of the harness: write their decision in as a role, as the file does with lawyer, and the run pauses at that stage until the answer arrives through the callbacks client. Use the record as your audit: a run that records writes every step as it happens, so you can read it back later.

​
Next steps