Verifying results
How Cizgen checks its own work — both the geometry quality and whether it actually did what you asked.
Cizgen doesn't just draw and hope. It checks its work in two different ways, and you can ask it to do either explicitly.
Self-check before it asks you
Before showing a preview, Cizgen renders the pending change and runs an automatic geometry check. This looks for problems such as:
- dangling ends and gaps,
- duplicate or overlapping objects,
- self-intersections,
- unclosed shapes that should be closed,
- objects colliding with things they shouldn't.
It fixes what it can and surfaces the rest as warnings on the approval bar, so you see any remaining concerns before you approve.
Did it do what I asked?
Cizgen can also verify the result against your intent — not just "is the geometry clean" but "did this accomplish the task." It derives the success conditions from your request (what, how many, on which layer, aligned to what) and reports each one as satisfied or not, with the actual value it found.
Ask for it directly when it matters:
Verify that every room now has exactly one label on the TEXT layer.
Verifying vs. inspection standards
- Verifying is a one-off check of this result against this request.
- An inspection standard is a reusable ruleset you save once and run against many drawings. See Inspection standards.
Both produce a clear pass/fail report; inspection reports can be saved as Markdown, RTF, or PDF.
Verification is read-only. If it finds a gap, fixing it is a normal follow-up request that goes through the approval gate.