# An Architecture Firm Lost a Pursuit Because Their AI Rendering Looked Too Perfect

**By Dan Cumberland** · Published May 19, 2026 · Categories: AI Strategy

> Renderings cross into the uncanny valley when they become almost— but not quite— indistinguishable from photographs.  The brain registers the mismatch before...

## The Uncanny Valley, Applied to Buildings

Renderings cross into the uncanny valley when they become almost— but not quite— indistinguishable from photographs\.  The brain registers the mismatch before the conscious mind can name it, and the response is discomfort\.  The term was coined by Japanese robotics professor Masahiro Mori in 1970, in the context of humanoid robots that look *nearly* but not *quite* human\.[3](/blog/blog-architecture-rendering-ai#ref-3)  The same phenomenon shows up the moment AI architectural rendering starts achieving near\-photorealism without the imperfections that real photography carries\.

Matthew Maganga's ArchDaily essay catalogs the specific tells\.  The list is short and brutal:

- **Impossibly polished surfaces**— concrete, metal, glass with no weathering, no fingerprints, no specular noise
- **Improbably perfect grass**— uniform color, no thin patches, no leaf litter, no shadow play from real foliage above
- **Implausible stillness**— no wind in trees, no people mid\-stride, no flag movement, no parked cars at slight angles
- **Weightless CG figures**— staffage people standing without quite making contact with the ground

> "Impossibly polished surfaces, improbably perfect grass in the landscape, or an implausible amount of stillness in a render can make a render venture into uncanny valley territory, as our brains struggle to process an image that is simultaneously real and not real\."[4](/blog/blog-architecture-rendering-ai#ref-4)

These signals concentrate in current AI rendering output for a simple reason: the underlying models are optimized for aesthetic reward, not physical accuracy\.  Generative AI lives in a latent space trained on millions of images, and it produces what statistically resembles a "good rendering\."  AI does not know what a Tuesday in November looks like\.  Sophisticated clients do\.

The architects themselves are sensing this\.  The AIA's 2025 Adoption Study found that 94% of architects expressed concerns about AI inaccuracy and 90% about authenticity\.[5](/blog/blog-architecture-rendering-ai#ref-5)  And from the practitioner side, the Chaos 2026 *State of AI in Architecture* survey found that 48% of respondents cite inconsistent or poor output quality as their biggest challenge, while 69% describe themselves as only "somewhat" satisfied with AI output\.[6](/blog/blog-architecture-rendering-ai#ref-6)

The uncanny valley in architecture is not a flaw in any one tool\.  It is the predictable result of a system optimized for aesthetic plausibility over physical truth\.  And as Common Edge essayist Eric J\. Cesal has argued, AI's almost\-human work is more uncomfortable than obviously\-machine work— which is the trap\.[7](/blog/blog-architecture-rendering-ai#ref-7)

Detection is only half the problem\.  The other half is what happens when a client *doesn't* detect the AI— and falls in love with a building that can't actually be built\.

## The Aesthetic Anchoring Trap

Even when an AI rendering doesn't tip a client off, it can still trap them— and the firm— by anchoring expectations to a concept the project cannot actually deliver at the agreed budget or site\.  Aesthetic anchoring is an old rendering problem\.  AI didn't create it\.  AI compresses it to days instead of weeks, and that compression is exactly the problem\.

The pre\-AI catalog is long and well\-known to anyone who's been around the profession for a decade:

- **Sydney Opera House \(1957–1973\):** The original $7M budget grew to $102M— a 1,400% overrun— because Utzon's competition\-winning sail concept was structurally impossible at the original cost\.[8](/blog/blog-architecture-rendering-ai#ref-8)
- **20 Fenchurch Street, London \("Walkie\-Talkie," 2014\):** The concave glass facade focused sunlight intensely enough to warp the bodywork of a Jaguar parked on the street below\.[9](/blog/blog-architecture-rendering-ai#ref-9)
- **Vdara Hotel, Las Vegas:** A crescent facade by Rafael Viñoly melted lounge chairs at the pool through the same kind of solar\-concentration effect\.[9](/blog/blog-architecture-rendering-ai#ref-9)

None of these were AI failures\.  All three illustrate the gap between what a beautiful image suggests and what the building physically becomes\.  Curved custom glass runs $100–$500 per square foot\.  Flat glass runs $18–$25 per square foot\.[10](/blog/blog-architecture-rendering-ai#ref-10)  An AI rendering tool, working in a latent space of trained images, cannot perceive that 20x cost difference\.  It produces what looks like the right answer\.  It produces the wrong project\.

What AI changes is the *rate* at which a developer client can fall in love with a concept the project can't deliver\.  Pre\-AI rendering took days or weeks, which created a natural delay during which someone on the team usually said, "Wait— can we build this?"  AI rendering takes hours\.  The anchoring happens before the cost estimator gets a look\.  Generative AI lives in latent space\.  Buildings live in physical space\.  That gap was always there\.  Now it closes faster than the firm's internal feedback loop can react\.

If this all sounds like a fringe problem, the adoption data says otherwise\.

## The Adoption Wave Is Already Here

AI in AEC is mainstream\.  Bluebeam's 2025 report on AEC AI adoption put the firm\-level number at 27%, with 94% of those current users planning to expand AI use in 2026\.[11](/blog/blog-architecture-rendering-ai#ref-11)  Chaos's 2026 survey of nearly 800 architects found 64% have experimented with AI tools and 20% have fully embraced AI in their workflow\.[12](/blog/blog-architecture-rendering-ai#ref-12)  The catch is the satisfaction gap: only about a third are more than "somewhat" satisfied with the output\.[6](/blog/blog-architecture-rendering-ai#ref-6)

The generational gradient is sharper still\.  The AIA's 2025 study found that 67% of architects under 35 use image generators, compared to 55% of architects aged 36–50 and 41% of architects over 50\.[13](/blog/blog-architecture-rendering-ai#ref-13)

```html-table
<table><thead><tr><th>Indicator</th><th>2025–2026 Value</th><th>Source</th></tr></thead><tbody><tr><td>AEC firms using AI in operations</td><td>27%</td><td>Bluebeam 2025<sup><a href="#ref-11" class="footnote-ref">11</a></sup></td></tr><tr><td>Architects who have experimented with AI tools</td><td>64%</td><td>Chaos 2026<sup><a href="#ref-12" class="footnote-ref">12</a></sup></td></tr><tr><td>Architects who have fully embraced AI in workflow</td><td>20%</td><td>Chaos 2026<sup><a href="#ref-12" class="footnote-ref">12</a></sup></td></tr><tr><td>Architects under 35 using image generators</td><td>67%</td><td>AIA 2025<sup><a href="#ref-13" class="footnote-ref">13</a></sup></td></tr><tr><td>Cite inconsistent/poor output quality as biggest challenge</td><td>48%</td><td>Chaos 2026<sup><a href="#ref-6" class="footnote-ref">6</a></sup></td></tr><tr><td>Only "somewhat" satisfied with AI output</td><td>69%</td><td>Chaos 2026<sup><a href="#ref-6" class="footnote-ref">6</a></sup></td></tr><tr><td>Early adopters who saved $50K+</td><td>68%</td><td>Bluebeam 2025<sup><a href="#ref-14" class="footnote-ref">14</a></sup></td></tr><tr><td>Early adopters who reclaimed 500–1,000 hours</td><td>46%</td><td>Bluebeam 2025<sup><a href="#ref-14" class="footnote-ref">14</a></sup></td></tr></tbody></table>
```

Two things are true at once\.  ROI for firms getting it right is real and well\-documented\.  Satisfaction across the broader user base is mediocre\.  Adoption is mainstream\.  Satisfaction isn't\.  That gap is where firm\-level policy decisions live\.

Two\-thirds of architects under 35 are using image generators\.  Whatever your firm's posture, the staff has already taken theirs\.

Adoption is the easy part\.  The harder question— and the one firm principals are actually wrestling with— is when AI rendering helps and when it hurts\.

## A Framework: When AI Rendering Helps, When It Hurts

The right line on AI rendering is a function of project phase, client audience, and tool class\.  AI excels at concept\-stage ideation and breaks down at pursuit\-stage deliverables for sophisticated clients\.  As Dan likes to say, just because it's easy doesn't mean it's good— and the work of firm leadership right now is figuring out how to make AI rendering *both* good and easy\.

Start with phase\.  Chaos found that 43% of architects cite concept and pre\-design as the area of greatest AI impact, with 85% reporting overall efficiency gains\.[12](/blog/blog-architecture-rendering-ai#ref-12)  This is the sweet spot\.  Speed advantage is real, the anchoring risk is low, and the cost of being wrong is one charrette, not one pursuit\.  Construction documents are the opposite end of the spectrum: AI's geometric fidelity gaps make it a liability where dimensional accuracy is the whole point\.

Now layer in audience\.  An internal team or a repeat sophisticated client gives the firm room to show provisional work\.  A first\-time aspirational client, an institutional owner, or a regulatory body does not\.  Sophisticated clients increasingly recognize AI tells\.  Aspirational clients may be impressed by polish in the moment and disappointed when the building shows up looking different\.  Both are real risks\.  They live in different places\.

### Decision Matrix: Phase × Audience

```html-table
<table><thead><tr><th>Project Phase</th><th>Internal Team</th><th>Repeat Sophisticated Client</th><th>First-Time / Aspirational Client</th><th>Institutional / Public Owner</th><th>Regulatory / Permit</th></tr></thead><tbody><tr><td>Concept / Pre-Design</td><td><strong>Use</strong></td><td><strong>Use</strong></td><td>Caution</td><td>Caution</td><td>Avoid</td></tr><tr><td>Schematic Design</td><td><strong>Use</strong></td><td>Caution</td><td>Caution</td><td>Caution</td><td>Avoid</td></tr><tr><td>Design Development</td><td>Caution</td><td>Caution</td><td>Avoid</td><td>Avoid</td><td>Avoid</td></tr><tr><td>Pursuit / Interview Deliverable</td><td>Caution</td><td>Caution</td><td>Avoid</td><td><strong>Avoid</strong></td><td>Avoid</td></tr><tr><td>Construction Documents</td><td>Caution</td><td>Avoid</td><td>Avoid</td><td>Avoid</td><td>Avoid</td></tr></tbody></table>
```

Then layer in tool class\.  This is where the AI rendering tools conversation actually gets useful\.  There is a real divide between BIM\-integrated rendering systems and general\-purpose image generators, and the divide matters for every cell of the matrix above\.

### Tool Class: BIM\-Integrated vs\. General Image\-Gen

```html-table
<table><thead><tr><th>Attribute</th><th>BIM-Integrated (Veras, LookX)</th><th>General Image-Gen (Midjourney, Krea)</th></tr></thead><tbody><tr><td>Source-of-truth geometry</td><td>Yes— wraps Revit, SketchUp, Rhino, etc.</td><td>No— text or reference-image prompt</td></tr><tr><td>Geometric fidelity to design</td><td>High— preserves source-model dimensions</td><td>Low— known hallucination</td></tr><tr><td>BIM/CAD platform integration</td><td>Veras: 7 platforms<sup><a href="#ref-15" class="footnote-ref">15</a></sup></td><td>None</td></tr><tr><td>Best-fit phase</td><td>Schematic through DD</td><td>Concept ideation, mood boards</td></tr><tr><td>Pursuit-stage risk</td><td>Lower (with human review)</td><td>Higher</td></tr></tbody></table>
```

The Chaos comparison is direct: Veras integrates with Revit, SketchUp, Rhino, Vectorworks, Archicad, Autodesk Forma, and AllPlan— seven major BIM/CAD platforms as of mid\-2026\.[15](/blog/blog-architecture-rendering-ai#ref-15)  Midjourney has no BIM integration and "known geometry hallucination issues," making it useful for mood boards and inspiration but unsuited for design development\.[16](/blog/blog-architecture-rendering-ai#ref-16)

Before any client\-facing AI rendering, a small set of questions clears most of the trouble:

1. Is the audience sophisticated enough to detect AI tells?
2. Will this rendering anchor cost or schedule expectations the project can't deliver?
3. Did the rendering originate from BIM source geometry, or from a text prompt?
4. Has someone outside the project team reviewed it for "too perfect" signals?

This framework sits inside a larger pattern\.  AI rendering is one node in a firm's broader AI strategy, and the same kind of phase\-and\-audience thinking applies to specifications, scheduling, drawing review, and proposal writing\.  This is the territory covered in [the broader AEC AI roadmap](/blog/aec-ai-roadmap/)— and in the [AI decision framework most founders use](/blog/ai-decision-framework-founders) to sort high\-leverage uses from high\-risk ones\.

Even with a clear internal posture, one question keeps surfacing in firm\-leadership conversations\.  Do we tell clients?

## The AI Rendering Disclosure Question

As of mid\-2026, there is no settled answer on whether architecture firms must disclose AI use in renderings\.  The legal terrain is moving, and the strategic posture matters more than the legal minimum\.  Construction law firm Fabyanske, Westra, Hart & Thomson notes that copyright ownership of AI\-generated images, client disclosure requirements, and professional liability when AI visuals are used in permit submissions all remain unsettled\.[17](/blog/blog-architecture-rendering-ai#ref-17)  AIA Trust separately warns that AI inputs and outputs may become discovery material in disputes— a real consideration for the way firms store, version, and reference AI\-generated work product\.[18](/blog/blog-architecture-rendering-ai#ref-18)

Three postures firms are currently taking:

- **Silent**— AI is used internally; nothing is disclosed to clients
- **Disclose\-on\-request**— Used in a wide range of work; volunteered only when asked
- **Proactive disclosure**— AI use is named in the deliverable itself

The defensible posture for most $20M–$100M AEC firms looks like proactive disclosure for institutional and public work, case\-by\-case for developer work, and never AI\-generated visuals in permit submissions without an explicit written policy\.  This is positioning, not legal advice\.  Firms that disclose AI use thoughtfully in 2026 will look credible in five years\.  Firms that hid it will look something else\.  [AI governance and firm\-level policy](/blog/ai-governance-strategy) is the larger conversation this sits inside\.

Which leaves the question every principal is actually trying to answer\.  What should we do about this, this quarter?

## What Firm Leaders Should Do This Quarter

AI rendering policy is not a 2027 problem\.  The staff is already using these tools\.  The clients are already developing detection instincts\.  The longer firms operate without an explicit posture, the more individual project teams improvise their way into trouble\.

Five actions worth taking before the next pursuit cycle:

1. **Draft a one\-page firm\-level AI rendering policy\.**  Phase, audience, tool class\.  One page\.  Signed by the principal\.  This is the artifact\.
2. **Train staff on phase\-appropriate use\.**  Especially the line between studio exploration and client\-facing deliverables\.  This is where [building an AI\-aware firm culture](/blog/building-ai-culture) starts to compound\.
3. **Audit current pursuit materials for AI tells\.**  Run them past someone outside the project team— you can't read the label from inside the bottle\.
4. **Decide a disclosure posture per client type and document it\.**  Institutional, public, developer, repeat, first\-time\.  Five lines\.  Done\.
5. **Tie the policy back to the firm's broader AI roadmap\.**  AI rendering is one node\.  Governance is the system\.

Firms navigating this— drawing the line between exploration and pursuit, training staff on phase\-appropriate use, building a firm\-level AI policy— is the kind of work [Dan Cumberland Labs' AI strategy services](/services/ai-strategy) does with mid\-market AEC clients\.  If the framework above feels right but the implementation feels heavy, an outside perspective tends to compress the timeline\.

The firms that win the next five years of AI rendering aren't the firms with the best tools\.  They're the firms whose principals decided what they were doing— and trained the staff accordingly\.

## Frequently Asked Questions

### What is AI rendering in architecture?

AI rendering in architecture is the use of generative AI to produce or enhance architectural visualizations, typically by transforming sketches, 3D models, or text prompts into photorealistic images of buildings\.  Chaos's 2026 survey of nearly 800 architects found that 64% have experimented with these tools and 20% have fully embraced them\.[12](/blog/blog-architecture-rendering-ai#ref-12)

### Why do AI renderings sometimes look "too perfect"?

Generative AI tends to overpolish surfaces, render improbably perfect grass and lighting, and produce scenes that lack the small imperfections of real photography\.  ArchDaily's Matthew Maganga catalogs these as impossibly polished surfaces, improbably perfect grass, and implausible stillness— the visual fingerprints that push an image into the uncanny valley\.[4](/blog/blog-architecture-rendering-ai#ref-4)

### What percentage of architecture firms use AI rendering?

Roughly 27% of AEC firms use AI in operations as of late 2025, per Bluebeam's adoption report\.[11](/blog/blog-architecture-rendering-ai#ref-11)  At the practitioner level, 64% of architects have experimented with AI tools and 67% of architects under 35 use image generators specifically\.[12](/blog/blog-architecture-rendering-ai#ref-12)[13](/blog/blog-architecture-rendering-ai#ref-13)

### Which AI rendering tool has the best BIM integration?

Veras has direct integration with seven major BIM/CAD platforms— Revit, SketchUp, Rhino, Vectorworks, Archicad, Autodesk Forma, and AllPlan— per Chaos's 2026 tool comparison\.[15](/blog/blog-architecture-rendering-ai#ref-15)  This is the broadest BIM integration available in the AI rendering category as of mid\-2026\.

### Should architecture firms disclose AI use to clients?

As of mid\-2026, disclosure norms are unsettled and vary by jurisdiction\.  Most legal commentary recommends transparency, especially for institutional clients and permit submissions, but no single rule applies across the profession\.[17](/blog/blog-architecture-rendering-ai#ref-17)  A defensible posture is proactive disclosure for institutional and public work, case\-by\-case for developer work, and never AI\-generated visuals in permit submissions without an explicit policy\.

## The Real Differentiator

AI rendering will keep getting better\.  So will sophisticated clients' ability to detect it\.  The advantage doesn't sit with the firms using the most AI\.  It sits with the firms that decided, on purpose, when to use it and when not to\.

Eric Cesal said it cleanly: AI will figure out how to do the labor of architects, but without understanding why architecture matters, it will never achieve identical results\.[7](/blog/blog-architecture-rendering-ai#ref-7)  That's the persistent edge\.  Not the tool\.  The judgment about where the tool belongs\.

AI amplifies human capability\.  It does not replace the judgment that decides where capability should be amplified\.

## References

1. Royal Institute of British Architects, "What are the risks to architects and practices who use AI" \(2024\) — [https://www\.riba\.org/work/insights\-and\-resources/professional\-features/ai\-professional\-features/what\-are\-the\-risks\-to\-architects\-and\-practices\-who\-use\-ai/](https://www.riba.org/work/insights-and-resources/professional-features/ai-professional-features/what-are-the-risks-to-architects-and-practices-who-use-ai/)
2. AEC Associates, "Why Architectural Renderings Lose Clients Before The Proposal Is Reviewed" \(2024\) — [https://theaecassociates\.com/blog/why\-architectural\-renderings\-lose\-clients\-before\-proposals\-are\-even\-reviewed/](https://theaecassociates.com/blog/why-architectural-renderings-lose-clients-before-proposals-are-even-reviewed/)
3. Maganga, Matthew, "Architectural Rendering and the Slippery Slope of the Uncanny Valley," ArchDaily \(April 18, 2021\) — [https://www\.archdaily\.com/959563/architectural\-rendering\-and\-the\-slippery\-slope\-of\-the\-uncanny\-valley](https://www.archdaily.com/959563/architectural-rendering-and-the-slippery-slope-of-the-uncanny-valley)
4. Maganga, Matthew, "Architectural Rendering and the Slippery Slope of the Uncanny Valley," ArchDaily \(April 18, 2021\) — [https://www\.archdaily\.com/959563/architectural\-rendering\-and\-the\-slippery\-slope\-of\-the\-uncanny\-valley](https://www.archdaily.com/959563/architectural-rendering-and-the-slippery-slope-of-the-uncanny-valley)
5. American Institute of Architects, "Architects are excited about the potential of AI, but concerns abound" \(March 3, 2025\) — [https://www\.aia\.org/aia\-architect/article/architects\-are\-excited\-about\-potential\-ai\-concerns\-abound](https://www.aia.org/aia-architect/article/architects-are-excited-about-potential-ai-concerns-abound)
6. Chaos / Architizer, "The State of AI in Architecture: How AI is reshaping architectural design & visualization in 2026" \(March 23, 2026\) — [https://blog\.chaos\.com/the\-state\-of\-ai\-in\-architecture\-survey\-insights](https://blog.chaos.com/the-state-of-ai-in-architecture-survey-insights)
7. Cesal, Eric J\., "AI, Architecture, and the Uncanny Valley," Common Edge \(September 9, 2024\) — [https://commonedge\.org/ai\-architecture\-and\-the\-uncanny\-valley/](https://commonedge.org/ai-architecture-and-the-uncanny-valley/)
8. Veriprajna, Ashutosh, "The Building That Melted a Jaguar: Why I Stopped Trusting AI to Design Anything," Medium \(2024\) — [https://medium\.com/@ashutosh\_veriprajna/the\-building\-that\-melted\-a\-jaguar\-why\-i\-stopped\-trusting\-ai\-to\-design\-anything\-aafb6b8d94ae](https://medium.com/@ashutosh_veriprajna/the-building-that-melted-a-jaguar-why-i-stopped-trusting-ai-to-design-anything-aafb6b8d94ae)
9. Veriprajna, Ashutosh, "The Building That Melted a Jaguar," Medium \(2024\) — [https://medium\.com/@ashutosh\_veriprajna/the\-building\-that\-melted\-a\-jaguar\-why\-i\-stopped\-trusting\-ai\-to\-design\-anything\-aafb6b8d94ae](https://medium.com/@ashutosh_veriprajna/the-building-that-melted-a-jaguar-why-i-stopped-trusting-ai-to-design-anything-aafb6b8d94ae)
10. Veriprajna, Ashutosh, "The Building That Melted a Jaguar," Medium \(2024\) — [https://medium\.com/@ashutosh\_veriprajna/the\-building\-that\-melted\-a\-jaguar\-why\-i\-stopped\-trusting\-ai\-to\-design\-anything\-aafb6b8d94ae](https://medium.com/@ashutosh_veriprajna/the-building-that-melted-a-jaguar-why-i-stopped-trusting-ai-to-design-anything-aafb6b8d94ae)
11. Bluebeam, "New Bluebeam Report Shows Early AI Adopters in AEC Seeing Significant ROI Despite Uneven Adoption" \(October 28, 2025\) — [https://press\.bluebeam\.com/2025/10/new\-bluebeam\-report\-shows\-early\-ai\-adopters\-in\-aec\-seeing\-significant\-roi\-despite\-uneven\-adoption/](https://press.bluebeam.com/2025/10/new-bluebeam-report-shows-early-ai-adopters-in-aec-seeing-significant-roi-despite-uneven-adoption/)
12. Chaos / Architizer, "The State of AI in Architecture survey" \(March 23, 2026\) — [https://blog\.chaos\.com/the\-state\-of\-ai\-in\-architecture\-survey\-insights](https://blog.chaos.com/the-state-of-ai-in-architecture-survey-insights)
13. American Institute of Architects, "Artificial Intelligence Adoption in Architecture" \(March 3, 2025\) — [https://www\.aia\.org/aia\-architect/article/architects\-are\-excited\-about\-potential\-ai\-concerns\-abound](https://www.aia.org/aia-architect/article/architects-are-excited-about-potential-ai-concerns-abound)
14. Bluebeam, "AEC AI Adoption Report 2025" \(October 28, 2025\) — [https://press\.bluebeam\.com/2025/10/new\-bluebeam\-report\-shows\-early\-ai\-adopters\-in\-aec\-seeing\-significant\-roi\-despite\-uneven\-adoption/](https://press.bluebeam.com/2025/10/new-bluebeam-report-shows-early-ai-adopters-in-aec-seeing-significant-roi-despite-uneven-adoption/)
15. Chaos, "Best AI rendering tools for architects 2026: 6 options compared" \(March 25, 2026\) — [https://blog\.chaos\.com/best\-ai\-rendering\-tools\-for\-architects\-compared](https://blog.chaos.com/best-ai-rendering-tools-for-architects-compared)
16. Chaos, "Best AI rendering tools for architects 2026" \(March 25, 2026\) — [https://blog\.chaos\.com/best\-ai\-rendering\-tools\-for\-architects\-compared](https://blog.chaos.com/best-ai-rendering-tools-for-architects-compared)
17. Fabyanske, Westra, Hart & Thomson, "Legal Risks of the Use of AI in the Design\-Build Process" \(May 16, 2025\) — [https://www\.fwhtlaw\.com/blog/2025/05/16/legal\-risks\-of\-the\-use\-of\-ai\-in\-the\-design\-build\-process/](https://www.fwhtlaw.com/blog/2025/05/16/legal-risks-of-the-use-of-ai-in-the-design-build-process/)
18. AIA Trust, "When AI Legal Searches Become Exhibit A: Discovery Risk for Architects and Engineers" \(2025\) — [https://theaiatrust\.com/when\-ai\-legal\-searches\-become\-exhibit\-a\-discovery\-risk\-for\-architects\-and\-engineers/](https://theaiatrust.com/when-ai-legal-searches-become-exhibit-a-discovery-risk-for-architects-and-engineers/)


---

Source: https://dancumberlandlabs.com/blog/architecture-rendering-ai/
