AI lab · The Wanderer’s Notes

Yaroslav Nagul · MRICS, REV

Agents read and check. The valuer signs off the conclusion.

Here I show how I work with a team of AI agents in valuation practice: who does what, where the work stops and waits for my decision, and how each step can be checked.

It is a working method, and it changes with the results of experiments; the log shows what changed and why. Valuer profile: nagul.com.ua.

Pipeline

Four steps, each with its own owner

  1. 01 · Brief

    Brief

    The task is set out in a file: sources, verification class, what counts as done. Before the brief goes to the executor, a separate agent looks for gaps in it.

  2. 02 · Execute

    Execution

    The executing agent works with files, not in a chat, and hands over a package: the result, a self-check and a list of checksums for every file.

  3. 03 · Verify

    Verification

    First scripts with no model, then agents that try to refute each claim; anything important is also checked by a model from another vendor. A separate judge session issues the verdict and edits nothing.

  4. 04 · Merge

    Merge

    Only after the verdict and my ‘ok’ does the result go into the library or to the addressee.

step · verification · waits for a person’s ‘ok’ · method as at 10 October 2026

Three ‘ok’s

The pipeline waits for a person three times

  1. Rules

    Changes to the agents’ rules, roles and canonical files. Without an ‘ok’, a proposal stays a proposal.

  2. Merge

    The result after the judge’s verdict. Without an ‘ok’, it stays verified but goes nowhere.

  3. Outbound, deletion and money

    A document to a client, an email to a person, any deletion, purchases and runs above the limit. This is enforced in the settings, not by agreement: the agent writes the draft, and I press send.

Everything before these points runs without me. If the pipeline stops at one of them, it loses nothing; it simply waits.

Depth of checking

Client documents get the deepest checks

ClassWhat it isChecks
Aa document for a client, a figure in it, a change to the rules, a merge into the libraryscripts, several opposing agents, independent recalculation of spreadsheets from the inputs, a model from another vendor
Binternal material: consistency and completenessscripts and opposing agents from the same vendor
Ca technical step with no judgementscripts only

The author of the brief sets the class, not the executor. When the executor rated its own work, it set the class too high and ran costly checks where lighter ones would do. Any check that was skipped is always named in the material.

Rules

Eight rules independent of the model

  1. One owner

    Only one session edits a document at any one time.

  2. The denominator comes from a script

    In ‘checked X of Y’, Y is counted by a script from a list, not estimated by an agent.

  3. A quotation, not a description

    A reference to a standard is confirmed only by a verbatim quotation from the primary source with its exact location: paragraph, page, edition.

  4. The judge is separate from the executor

    The session that did the work does not declare it verified.

  5. Another model family

    Anything important is checked by a model from another vendor, and an agent runs it, not a person carrying files between chats.

  6. Context lives in files

    A new session restores the state of work from files: the decision log, the work register, the rules, the latest handover, the verdict. The service’s own memory is only a pointer.

  7. A trail at every step

    Every agent run is recorded, every decision goes into the log, every package is frozen with checksums. A step without a trail did not happen.

  8. ‘As at’

    A fact that changes over time, from a registered address to the effective date of a standard, is given with a date and a source. It is checked again before anything goes out.

Experiment log

The Wanderer’s Notes

Each entry here is a contract: which creature got in the way of working with agents, how I tracked it down and what trophy it left in the method. The creatures come from folklore; the cases are real.

Contracts

  • 2026-10-08

    No. 2 · The Double

    A large cost with zero tokens, a borrowed key in the run log and a key of its own for every event.

    read the contract
  • 2026-10-07

    No. 1 · The Shapeshifter

    Four references to standards, zero matches with the primary source and a new column in the handover template.

    read the contract

Bestiary

The Shapeshifter

A paraphrase of a standard passing itself off as a quotation.

hunted down · contract No. 1

Zlydni

An expensive model quietly spreads to helper agents.

tracks spotted

Blud

One session takes on several tasks and loses its way.

tracks spotted

The Double

A system line swallows the real entry in the run log.

hunted down · contract No. 2

One-Eyed Lykho

A brief seen only by its author.

tracks spotted

Mara

A plausible figure with no source.

tracks spotted

Limits

Agents neither sign nor judge value

Agents read everything in full, calculate, look for inconsistencies and prepare drafts. The conclusion, its reasoning and responsibility for it stay with the valuer. I set out what IVS and EVS say about this in the note ‘Can a valuer use AI under IVS and EVS?’.

Author

Yaroslav Nagul

Yaroslav Nagul · MRICS, REV

RICS Registered Valuer, Recognised European Valuer (REV). Partner, Valuation & Advisory, RSM Ukraine. The Wanderer in the contracts is me; the creatures come from folklore, the cases are real.

Profile, credentials and contact details