Your judgment is the product. Where does it live?

In short. Expert engagements run on digital meetings, live or recorded, and on the slides, diagrams and chats that follow. None of these record who confirmed what. Agents now draft findings in minutes, so "who decided" gets blurrier. We propose a workspace per engagement that runs the Judgment Work pattern: agents draft and one named person confirms. We want to test whether you and your clients would trust it.

The engagement you already run

You interview a dozen people at a client, on calls and in meetings. You read what documentation exists. You form a view and write it up. Weeks later, someone asks which conversation a conclusion came from, which findings you examined yourself, and where the client's confidential material is now. Most firms can't answer quickly.

Even as offices refill, knowledge work stays digital: web and phone meetings, one-to-one or in groups, live or recorded, with chat and shared files in between. The whiteboard has become Figma or draw.io, and now an AI draws the diagram. The work is richer than ever, and the judgment inside it is no easier to trace.

The most valuable part of the work is the part no tool records.

What agents change

Agents can interview, transcribe and draft. In a field study of 758 consultants, access to a model improved speed and quality on tasks inside its ability, and made people less likely to get the right answer on a task just outside it. The edge of the model's ability isn't visible to the person using it.

That removes much of the junior work, and it raises a harder question than speed: when an agent drafts a finding and a person forwards it, who decided?

Three questions your client will ask

Who owns what? What the client's people said belongs to the client. Your method belongs to you. Where does it live, and who can reach it? Including which model services see it. How can you prove it? In the language their security team already uses.

If a workspace can't answer these in the system itself, not just in a contract, a careful client won't let an agent interview its people.

The “Judgment Work” pattern

Judgment work is work where you are paid to draw out what other people know and then put your name to a verdict: a due-diligence finding, a readiness assessment, a migration plan. It has the same shape every time, and agents make that shape worth writing down. We call it the Judgment Work pattern. It has three moves, which the paper names Draft, Confirm and Commit.

1. Draft. Agents interview the client's people and draft each finding, with a proposed score and a link to the interview it came from.
2. Confirm. You, as the named Lead, confirm or change every record. No one else can, and nothing is authoritative until you do.
3. Commit. The mission closes. The client sees the result read-only, and every finding traces back to its source.

Here is one record, with invented content, moving through the pattern:

The agent proposes; the person decides. No fork of the software can remove the Confirm step.

After the pyramid

If agents absorb the junior tasks, the staffing pyramid thins. We describe a smaller team: a Lead who is accountable and the only one who confirms, and an optional Operator who runs the room. The open worry is apprenticeship. Juniors used to learn judgment by doing the work the agents now do.

What we don't know

This is a position paper. We have no field data. We state eight hypotheses, for instance how often leads override an agent's score, and whether interviews change conclusions that documents alone would reach. If the answers are "rarely" and "no", the idea is weaker than we think, and we will say so.

Research supported by Theoremlabs.io, which also develops the open-source Tacit Chassis (in development, not yet public).