Questions from the pin-up

AI-assisted describes a process in which generative tools contribute to some part of the image. The label does not indicate how much geometry, rendering or compositing remains under direct human control. Describe the actual interventions: for example, a model-based render with generated planting and manually composited people. A more precise description gives reviewers something useful to check.

Potentially, subject to the authority’s requirements and the purpose of the view. An illustrative image is not a substitute for a required verified visual assessment. Agree the methodology with appropriate specialists. Retain camera, survey and model evidence where required, and avoid implying that a polished view establishes acceptability.

Use an approved baseline, bounded masks and suitable conditioning, then compare the output with the model. No control setting guarantees fidelity. Reject or correct architectural drift. If the building itself is the subject of the decision, retaining model-derived architectural pixels may be more appropriate than regenerating the whole frame. See the pipeline essay.

Check applicable law, contracts, platform rules and client requirements. Explain material generative interventions where they affect interpretation. A label does not replace accurate captions or review. “AI-assisted” is less useful than a statement that distinguishes fixed architectural geometry from an indicative landscape treatment.

Not by default. Confirm client permission and review the specific service’s access, retention, training-use and deletion terms. Use an approved environment or do not upload. Remove unnecessary information, but do not assume that removing a project name makes a recognizable building or site anonymous.

There is no universal answer. Ownership and permitted use depend on jurisdiction, human contributions, contracts and source rights. Keep a rights ledger and obtain project-specific advice when needed. Permission to use a service commercially does not automatically clear third-party photographs, designs or identifiable people.

Not necessarily. Keep the approved baseline, significant decision points, relevant settings and the issued output under an agreed retention policy. Avoid unnecessary retention of confidential assets. Preserve enough to explain the selection and resolve later questions, rather than treating an indiscriminate image archive as a reliable audit trail.

Small teams may combine roles, but an independent architectural check is valuable. Separate production, model verification and release approval as far as the project allows, and record responsibility. A fresh reviewer is more likely to notice a changed threshold or an assumption that has become invisible to the image maker.

No. It is an independent editorial resource. Named tools and standards provide context, not endorsements, certifications or claims of affiliation. Our interest is in how a workflow can be questioned and explained, not which interface produces the most immediately impressive result.