Skip to content
Sample Report · Evidence-Backed Findings

What doAZ actually catches — with the evidence attached

Below are determinations the doAZ verification modules produced on a public demo project. Every finding carries drawing coordinates, the governing clause, and a confidence level — and when the evidence is weak, the system declares a hold before anyone has to ask.

99.2%Geotechnical review accuracybasis: POSCO E&C frozen gold set
16Enterprise customersbasis: 2023–26 cumulative, signed contracts
24Delivered projectsbasis: 2023–26 cumulative deliveries
15,000+Industrial documents structuredbasis: 2023–26 cumulative
Verdicts · How a finding is reported

Every determination is anchored to a coordinate on the drawing

A finding is never just a sentence. It resolves into one of four verdicts, each one attached to the position on the drawing that produced it — so a reviewer can go straight to the evidence instead of searching for it.

MISMATCHMismatch

Two sources disagree and the evidence is strong enough to say so — a symbol drawn on the plan with no matching schedule entry, for example.

REVIEWReview required

The sources conflict and neither side can be proven right. The decision goes to a reviewer instead of the system choosing the plausible one.

VERIFIEDVerified

Both sides agree at symbol level. The agreement is recorded together with the evidence coordinates on the drawing.

ABSTAINAbstained

The evidence is too weak or the source is unreadable, so the system declines to answer and surfaces the original page instead.

An interactive click-through of these verdicts on a synthetic drawing is available on the Korean version of this page.

Findings · In detail
01CRITICAL

Three symbol types missing from the schedule — drawn on the plan, absent from the order list

Three of the symbol types detected on the unit-plan drawings were never registered in the window & door schedule. This is the pattern that turns into a missed procurement order on site — precisely the kind of error a sampling-based review does not catch.

Plan detection: 118 symbol instances · 9 symbol typesSchedule reconciliation: 4 of 9 types matched on both sidesDetermination principle: symbol-existence based (Zero Wrong-Link)
source: Window & door verification console · run on a public demo project
02CRITICAL

Two symbol types missing from the plans — listed in the schedule, gone from the drawing

Two symbol types registered in the schedule were not detected on any plan. This is the revision-propagation pattern: the symbol was removed during a drawing revision (R2 to R3) while the schedule entry survived untouched.

Revision comparison: change propagation traced into the detail sheetsDesign-guide conformance 0 of 14 — guide reconciliation run in parallel35 items automatically queued for reviewer confirmation
source: Window & door verification console · run on a public demo project
03MAJOR

Floor-height label contradicts the dimension ladder — escalated to REVIEW

The floor-height label on the section drawing did not agree with the sum of the dimension ladder. Instead of picking whichever value looks more plausible, the system escalates the case to REVIEW — zero false-confident determinations is the design goal.

Floor-height verification, three tiers: T0 dimension ladder → T1 token grounding → T2 VLMFloor-count hint guard — automatic hold when the floor count disagreesVerdict: REVIEW (human confirmation required)
source: Floor-height review module · run on a public demo project
04MAJOR

Design review comments — all thirteen items traced end to end

Building committee review comments and the corresponding action plan are parsed automatically, matched one-to-one against the drawing registry, and each item is judged as reflected, partially reflected, or not reflected. On a live project, 13 of 13 items were confirmed as reflected.

Document side: original comment text + action plan p.2 as evidenceDrawing side: matched to elevation A05-021 · confidence 100% · deterministicUnclassified items: none — every item classified together with its evidence
source: Review-comment matching module · live project verification
05INFO

Unreadable spans — reported, never guessed

Where the text encoding of the source PDF was corrupted, the system did not estimate a value. It states plainly that the chunk is unreadable and points the reviewer to the original page — an honest hold instead of a plausible wrong answer.

Corrupted encoding detected → chunk marked unreadableDeep links to the source pages provided (p.57, p.64)LLM layer: weak evidence → Abstain → handed off to a person
source: Evidence-tracing chat · measured on live responses
The Real Console · Actual screen
Window & door verification console · plan reconciliation reviewLIVE IN PRODUCTION
Window and door verification console — symbol instances detected on plans, per-symbol reconciliation bars, and evidence coordinates overlaid on the drawing
The screen where these findings are actually reported — per-symbol reconciliation bars, the drawing overlay, and the governing principle, exactly as the reviewer sees them.

What would we find in your drawings?

A technical verification demo starts with one real set of drawings — we agree on the accuracy definition against a frozen gold set, then measure it.

Request a verification demo