Protect the building before you improve the image.

A basic exterior render lands in the image channel with four comments: better lighting, richer materials, more convincing vegetation, and realistic reflections. The camera and building must stay the same. An operator sends the image through ComfyUI, produces a handsome result, and discovers that the entrance moved, one bay vanished, and the glazing now reflects a skyline that cannot exist behind the camera.

Today's intel sweep again surfaced community requests for workflows that enhance architectural renders while maintaining composition. That final phrase carries most of the risk. Composition can mean camera crop, massing, facade rhythm, landscape boundaries, furniture placement, or simply the general impression. A generative graph cannot protect an instruction the team has not defined.

The remedy is a one-page preservation brief attached to the source image. It divides the frame into locked, adjustable, and replaceable zones, then names the facts that reviewers will inspect. This is a production specification, not a prompt-writing exercise.

Start with three kinds of permission

Color-code the zones on a copy of the render. Add a numbered fact list beside it. “Locked facade” is vague. “Keep six structural bays, five upper windows per bay, continuous parapet, and the entrance centered in bay three” is reviewable. The brief should be understandable to someone who did not build the source model.

Permissions can overlap by attribute. A glass wall may be locked in outline and mullion count, adjustable in tint and roughness, and forbidden from showing invented interior floors. State these separately. The goal is not to freeze every pixel. It is to distinguish design information from visual finish.

Preservation is not a denoise setting. It is a list of architectural facts with an acceptance test.

Attach the evidence the graph can use

The marked-up brief tells the operator what matters. Structural inputs help the workflow act on it. Export the clean source image at the intended aspect ratio. Where the authoring model allows it, also export depth, line, normal, material ID, or object-mask passes from the same named camera. Verify that every pass aligns before building the graph.

Use the least control needed for each task. An edge condition can help retain rooflines, window divisions, and rails. Depth can help retain large spatial relationships. A segmentation or object mask can confine material and planting changes. None proves accuracy by itself. A weak or misaligned map can preserve the wrong edge just as confidently as a good map protects the right one.

Record the source application, camera name, image dimensions, pass names, and export time in the brief. If the design changes, re-export the complete set. Mixing a revised beauty image with an older depth pass creates a quiet contradiction that may look like a model failure.

Turn each request into a bounded operation

Lighting

Name the desired direction and protected shadow facts. “Late afternoon light from camera left, readable entrance, no blown sky, preserve the canopy shadow direction” gives the operator and reviewer a common target. If the source geometry creates a deep recess, do not ask the workflow to erase it for brightness. Use exposure, local finishing, or a revised lighting source.

Materials

Identify material boundaries before describing texture. A richer brick surface is a local appearance change. Turning the concrete plinth into brick or extending timber across a window is a design change. Give each adjustable material a short reference, allowed color range, scale cue, and forbidden neighboring zones.

Reflections

Reflections are scene claims. State whether glazing should reveal interior content, mirror the actual context, or remain visually quiet. Reject duplicated suns, impossible horizons, inconsistent mullion reflections, and scenery that implies buildings absent from the approved view. Attractive glass can still be false glass.

Vegetation and people

Mark planting beds, paths, entrances, accessible routes, and sightlines. Give replacement elements a use rule: species character, mature height, season, density, and areas that must remain clear. People must not block doors, float on steps, or change the apparent use of a space. These elements are expendable pixels but consequential evidence.

Run one operation per pass

A single request to fix light, texture, glass, foliage, people, and sky makes defects hard to trace. Separate the work. Begin with the broadest approved appearance change, compare it with the source, and save a checkpoint. Move to masked local changes only after the locked facts pass.

Keep a contact sheet with the source, each accepted checkpoint, and the final candidate at the same scale. Label workflow revision, main model, controls, dimensions, and the reason each pass exists. ComfyUI can place parts of this record in the workflow, but the project still needs a human-readable review sheet.

Do not interpret a low denoise value as a guarantee. Sampling settings affect the probability and degree of change, while protection is decided by the observed output. If a column shifts, the result fails even when the graph used conservative settings.

Review in the order of failure cost

Check the camera, silhouette, floor count, openings, structural rhythm, and access first. Then inspect material boundaries, glazing, shadows, landscape limits, repeated details, and local artifacts. Finish with atmosphere and taste. There is little value in debating a warmer sky when the stair has lost a riser.

Review at full frame and at 100 percent. The full view exposes crop, balance, and large geometry drift. Close inspection finds melted mullions, doubled people, broken rails, texture scale errors, and foliage crossing hard boundaries. Compare against the source and the marked brief, not against memory.

Use three decisions: accept, repair locally, or reject to the previous checkpoint. Local repair is appropriate when the defect is isolated and the locked structure remains dependable. Reject the pass when errors repeat across the image or the team cannot identify which operation caused them.

Make the brief part of the handoff

Store the preservation brief with the approved image, source render, control passes, workflow file, and review contact sheet. A future operator should be able to see which changes were permitted without reverse-engineering prompts. If the image is revised after a design update, the brief should receive the same revision identifier as the source view.

This package also prevents a common approval error. A project lead may approve the mood of an image without seeing that the workflow changed a design fact. Putting locked facts beside the candidate makes approval more specific: visual finish accepted, stated architecture preserved, remaining exceptions recorded.

Our take: prompts describe desire, briefs assign risk

ComfyUI is useful because it exposes controls, masks, models, and intermediate stages. That visibility does not decide what the architect considers sacred. A preservation brief supplies the missing project judgment. It tells the graph operator where invention is welcome and where it becomes misinformation.

Before the next enhancement pass, draw three colors on the source image and write ten facts. If the team cannot agree on those marks, the render is not ready for generation.

Protect the building. Then make the picture sing.

Editorial basis: the 22 September 2026 ArchiGen AI intel sweep and community discussions surfaced from r/FluxAI, r/ComfyUI, and r/archviz. These sources establish recurring requests for enhancement, control, and tutorials, not measured product performance. The three-zone brief, pass order, and acceptance method are editorial recommendations. This article does not claim hands-on testing.