Answers are grounded in this paper and cite their sources.
The increasing presence of AI in architectural practice is renegotiating who, or what, holds creative authority over a project. This paper introduces a novel two-construct framework, AI Logic (AL) and Architectural Value (AV), to operationalise this shift. AL captures a tool's computational reasoning across automation, optimisation, and predictive capability, while AV captures design agency support, contextual sensitivity, and exploratory capacity. Positioning fifty AI-driven tools within this AL-AV construct via tension map analysis identifies stage-specific patterns within the selected dataset. It shows that design agency is redistributed unevenly across the project lifecycle, expanding in early design stages where tools act as creative collaborators, and contracting under efficiency-driven logics in later stages where automation prioritises monitoring and compliance over qualitative judgement. Cross-referencing against secondary parameters such as building typology, user group, tool maturity, and regulatory context surfaces fundamental gaps in current AI provision. The selected tools predominantly support residential and commercial applications. Documented regional orientations include North American and European standards, while coverage of other regions and typologies is less evident within the sample. To assess scoring consistency, ten AEC professionals and the author independently evaluated a subset of five tools, with one tool representing each of RIBA Stages 1–5. Intraclass correlation analysis demonstrated strong panel-level inter-rater reliability for both constructs, while comparison of the author's scores with the expert consensus indicated close alignment. Following this calibration, the author independently applied the same evaluation framework to the remaining forty-five tools. Beyond its analytical application, the framework offers a practical means of informing future AI development and adoption. It gives toolmakers a vocabulary for embedding stakeholder values in development decisions, and architects a means of recognising embedded biases before adoption, so that increasing automation extends rather than erodes the disciplinary and cultural values of architecture as a whole.
No takes yet. Share an insight, caveat, or question.
Sudhakaran et al. (2026) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: