Perfect is not a render brief.

A current archviz discussion imagines the final destination of AI rendering as a simple command: make it nice, like the reference. The system returns a perfect image. It is an attractive idea because the instruction feels obvious to a person looking at both pictures.

It is not obvious at all. “Nice” might mean softer light, more expensive furniture, a quieter palette, better planting, less visual clutter, or a camera that hides the unresolved side elevation. “Perfect” might mean photorealistic to one reviewer, faithful to the BIM model to another, emotionally persuasive to the client, and technically printable to the graphics team.

Before choosing a tool or writing a prompt, define done. A useful definition turns taste into four review gates: project fidelity, communication, image quality, and evidence.

Beauty cannot overrule project truth

AI render products are marketed for speed and range. Chaos currently describes Veras as moving from sketches or 3D models to realistic images, animations, and 3D assets, and says users can explore materials and facade treatments within existing model geometry. Those are vendor-stated capabilities. They do not decide which project facts your image must hold.

The first gate is factual. Name the model issue, camera, required geometry, specified materials, protected graphics, site context, and design decisions represented. Mark uncertain elements as studies. A perfect-looking output that changes an approved canopy is not almost done. It failed the first gate.

A convincing image can fail the project in one pixel. A moved column is not a style choice.

Build a four-gate definition of done

Gate 1: project fidelity

List protected features before generation. Include massing, floor and roof edges, openings, facade rhythm, columns, stairs, guards, visible structure, and any object tied to an approval or specification. Add the camera and crop. If an exact sign, artwork, product, or neighboring building appears, identify its governing source.

Review with an overlay against the approved base, not by memory. Count repeated bays. Trace silhouettes and junctions. Look for the small changes that make an image more attractive while making the project less true: a taller window, a thinner slab, a removed downpipe, a wider aisle, or a tree hiding the service entrance.

The pass condition should be binary. “Mostly faithful” invites a negotiation after every run. Either each protected feature matches within the agreed tolerance, or the image returns for repair.

Gate 2: communication

Name the audience and the decision. A competition image may need a memorable public idea. A planning view may need massing, context, and material character. A client options sheet may need one controlled variable across several images. A construction-sequence illustration may need clarity before atmosphere.

Write the intended sentence before making the image: “This view shows how the lobby connects the street entrance to the garden,” or “These three views compare only the cladding color.” If the reviewer cannot recover that sentence from the output, the image is not done.

This gate protects against beautiful irrelevance. A dramatic evening grade may hide the facade comparison. Dense entourage may animate the plaza while obscuring accessible routes. A wide heroic camera may sell the roof and erase the human-scale entrance the client needed to understand.

Gate 3: image quality

Set the delivery conditions first: pixel dimensions, aspect ratio, color space, file format, intended display or print size, and compression limit. Four thousand pixels across does not guarantee usable detail. Inspect the final delivered file at the size the audience will see and at 100 percent.

Check edges, reflections, glass, hands, faces, signs, vegetation, repeated textures, railings, wheels, shadows, and contact points. Look at people standing near furniture and columns, where scale errors become obvious. Inspect the image corners, not only the focal point. Confirm that dark areas retain information and bright areas have not clipped into flat white.

Then test the full composition. A technically clean image may still have no hierarchy. The eye should reach the project subject before it gets trapped by a bright car, saturated coat, sharp cloud, or invented light source.

Gate 4: evidence

A finished image needs a record. Capture project and model revision, source render, camera, tool and model name, workflow or graph version, key inputs, generated date, editor, reviewer, and approval state. Preserve the base alongside the final output. Record local composites or manual repairs.

Add a disclosure appropriate to the destination. Internal concept work may need a compact label. A client deck should distinguish design facts from exploratory content. Public work may need a clear note that the image is AI-assisted, especially when invented people, products, surroundings, or future conditions could be read as documentary.

Evidence does not make a weak image stronger. It makes the image accountable and repeatable. When the project changes, the team can see whether to regenerate, repair, or retire it.

Use a stop rule, not endless taste

Generative tools make another option cheap enough to feel harmless. Each option still consumes review attention and creates another chance for an unnoticed change. Set a stop rule before the first run.

One useful rule is: stop when all protected facts pass, the communication sentence is clear to a reviewer who did not make the image, no defect is visible at delivery size, and the evidence record is complete. Further work needs a named reason, not curiosity.

Separate blockers from preferences. A changed door, false reflection, unreadable sign, or missing guard blocks delivery. A preference for warmer light or a different jacket color does not, unless it affects the stated communication goal. This prevents senior review from becoming an unpriced sequence of personal tweaks.

Score variants before discussing favorites

When comparing outputs, test the gates in order. Eliminate anything that fails fidelity. Among the survivors, assess communication. Only then compare image quality and aesthetic preference. Evidence is required for whichever option moves forward.

This order matters. Putting all images on a wall and asking which one people like lets spectacle outrank accuracy. The most cinematic result often wins before anyone notices that it changed the project. A pass or fail screen makes beauty compete only after truth.

For early design studies, the fidelity gate can allow named variables. If the team is exploring canopy forms, canopy geometry may change. Everything outside that study boundary remains protected. “Concept” should widen a specific decision, not suspend every standard.

The reference does not define success

A reference image can communicate light, material behavior, camera character, or occupancy better than a paragraph. It still belongs inside the four gates. State what the project should take from it and what it must ignore.

If the reference shows pale oak and soft winter light, decide whether either is an approved direction. Do not let its hidden attributes, room proportions, window size, furniture budget, color grade, and photographer's lens, become an accidental definition of done.

Our take: perfect is a project agreement

No model can infer the exact point at which an architect, client, visualization artist, and communications lead all consider an image complete. That point has to be negotiated in advance and made visible in the review.

Define the project facts. Name the audience decision. Specify delivery quality. Preserve the evidence. Then let the image earn approval gate by gate.

If “make it nice” is the whole instruction, nobody has agreed what done means.

Editorial basis: the 27 September 2026 ArchiGen AI intel sweep, including a current r/archviz discussion that frames advanced AI as producing a perfect render from a simple instruction and reference, plus current Chaos Veras product material describing sketch, model, image, animation, and material-study workflows. Product capabilities are vendor claims. This article reports no hands-on test; the four review gates, stop rule, and evidence requirements are editorial recommendations.