Verifying results

Verifying is confirming that each claim points at something you can open and that the thing it opens says what the claim says, without redoing the review. In Nomic that check is a click.

Citations​

Every grounded answer carries citations. They behave by file type:

• PDF and sheets: opens the file at the page. Drawing review findings land on the callout.
• Word, Markdown, text: jumps to the quoted passage in the viewer.
• BIM: opens the model viewer with the element selected.
• CAD: opens the DWG viewer zoomed to the entity.
• Code: opens the retrieved excerpt from the adopted code.

When an answer draws on several files, each claim is cited on its own. Verify the one you doubt without re-reading the rest.

Read the citation, not only the sentence. A sentence with no citation is a hypothesis.

The drawing judge​

Before a drawing review finding is added to the table, the drawing judge checks it against the sheet. It catches a sub-agent that misread a tag, a callout attributed to the wrong sheet, a duplicate.

The judge keeps the false-positive rate low, so reading the table is worth the time, but it does not guarantee a finding is correct. Open the citations on findings you will act on.

The status flow​

Findings in a Drawing Review artifact move New → Accepted → Exported → Addressed or Ignored, with Reopen taking an addressed finding back to Accepted and an ignored one back to New.

• New: the agent's claim. Unchecked.
• Accepted: your judgment that the finding is real. Accepting is the verification step and the gate: only Accepted or Exported findings can be pushed to Forma or Fieldwire.
• Exported: in the project's RFI or issue log.
• Addressed: the issue was fixed.
• Ignored: you reviewed the finding and it did not become an issue. Either way it is closed, with a record.

A table that is all New has not been reviewed. A table with the noise Ignored and the real findings Exported is a record a PM can use.

Artifact versions​

Every report, table, deck, and drawing review is an artifact beside the conversation. Artifacts are versioned. The clock icon shows history; the download icon exports. If a revision makes a report worse, go back. If a reviewer asks what changed between Tuesday's draft and Thursday's, there is an answer.

Permissions follow the conversation or workflow that created the artifact. Organization admins can set a .docx export template so reports leave in the company's format.

Asking the agent to check itself​

Asking the agent to check its own work is cheap, and it catches the obvious errors.

Before I share this: re-check every finding in the table. For each one, confirm the drawing citation lands on the callout and that any spec or standard citation says what the summary claims. Flag any finding where either check fails.

For a submittal, an RFI response, or a code answer: "For each requirement you stated, show me the page or excerpt it came from."

Use it as a first pass. The agent checking its own work has the blind spots it had the first time, so your click on the citation still matters.

Common failure: bulk accepting​

The first ten findings were right, so the next thirty are accepted unread. The eleventh had a fabricated spec paragraph citation and is now an RFI with your name on it.

Open every citation on a finding you will export. Spot-check the rest. If the spot check finds a bad one, stop sampling and read them all. Tell the agent what was wrong so the follow-up improves, and if the pattern recurs, add it to a workflow's instructions.

Next: turning a prompt that works into a workflow the team runs.

Next: Building workflows