Editorial
Hello, World.
At least that is what they taught us to type in my very first HTML course. It was fun. It was intimidating. It was engaging. And it taught me a lot.
I took that class at the urging of a friend who was a computer science major and insisted that I should learn how to code. At the time, I did not really know what that meant. The only “code” I was familiar with was building code. The Uniform Building Code, the International Fire Code, and the many regulatory frameworks adjacent to architectural practice. My world was architecture, and it would remain so for the next decade.
Still, technology had always been a quiet constant in my life. I had a natural inclination toward it, even if I did not yet have the language for that interest. Eventually, I pursued a media and technology certificate, one that essentially confirmed I understood HTML and CSS and could, at best, amateur engineer an iMovie or a GarageBand audio or video project. It was not glamorous, but it gave me access to a way of thinking that felt adjacent to architecture, even if it was not yet embraced by it.
As my technical skills grew, both inside and outside architectural education, I began to question why architecture resisted deeper engagement with media and technology. Why were we not diversifying our skill sets toward fields that clearly overlapped with our own? At the time, I assumed those adjacent fields were film and computer game development. I was not entirely wrong. But I quickly learned that finding an architect willing to mentor, let alone apprentice, someone in something so computationally intensive was rare.
Once I entered professional practice, a few realities became clear. Computers in architecture were often treated as tools for presentation and compliance, necessary but not central. That may sound exaggerated, but not by much. Drafting software, computational literacy, and broader technological awareness frequently sat low on the list of skills architects were encouraged to develop. Architecture, as a profession, has historically been cautious, and sometimes resistant, when it comes to expanding its technical fluency.
Today, that resistance is no longer sustainable.
Whether prompted by the rise of artificial intelligence or by the unavoidable reality that technology is advancing faster than the profession’s willingness to absorb it, architecture is being forced into a moment of reckoning. The future of design is not architecture versus technology. It is architecture through technology.
This journal exists to support that transition.
Arqwell was created to publish thoughtful, accessible, and rigorous work that helps architects understand the technologies reshaping their field, including AI, Web3, automation, and systems that increasingly operate beneath the surface of practice. Just as importantly, it exists to examine how architecture itself is changing as it becomes adjacent to industries far beyond traditional AEC boundaries.
Architects are not yet the most technologically fluent or easily transferable skill group entering the AI and Web3 landscape. Acknowledging that is not an indictment. It is a starting point. This journal is not about evangelizing tools or predicting futures. It is about documenting change, building understanding, and creating space for architects to engage emerging systems with clarity, responsibility, and agency.
Get Arqwell’s stories in your inbox
Join Medium for free to get updates from this writer.
What follows is an edited editorial with less drift and a clearer academic footing, written for a publication committed to helping architecture think earlier about the systems shaping its future.
The Real Editorial
Why Arqwell Exists
Architecture is changing, but not always in ways that are visible.
New systems are entering practice quietly , through software updates, contractual mechanisms, automated workflows, data infrastructures, and platforms that promise efficiency while redistributing responsibility. Artificial intelligence generates drawings before intent is fully articulated. Blockchain-based systems manage authorship, ownership, and verification without being named as such. Decisions once made explicitly by architects are increasingly shaped by tools, vendors, and embedded logic operating in the background.
Arqwell exists because these changes are happening faster than architecture is able or willing to fully acknowledge them.
This publication was not created to celebrate technology, nor to resist it. It was created to document it: to examine how emerging and adjacent technologies are reshaping architectural practice, professional responsibility, and building science before those shifts become invisible norms.
Architecture has always absorbed innovation indirectly. New materials arrive through engineering standards before they enter design language. Regulatory changes reshape form without announcing themselves as theory. Software alters labor, liability, and authorship long before it is debated in studios or journals. Today’s technological moment is no different except in speed, scale, and consequence.
Arqwell treats architecture as a system of responsibility. Drawings are not merely representational; they are legal instruments. Models are not neutral; they encode decisions about coordination, risk, and control. Buildings are not endpoints; they are material outcomes of layered technical, contractual, and social processes. When technology intervenes in any of these layers, architecture is affected whether the profession names it or not.
The goal of Arqwell is to make those interventions visible.
We are particularly interested in technologies that sit adjacent to architecture rather than neatly inside it — AI systems developed outside the discipline but embedded into design workflows; Web3 infrastructures shaping ownership, authorship, and verification without being framed as architectural tools; automation that alters professional judgment while claiming neutrality. These systems matter not because they are new, but because they reorganize how architecture is produced, governed, insured, and taught.
This journal values novelty, but not novelty for its own sake. We are not interested in technological evangelism or speculative futurism divorced from architectural consequence. At the same time, we reject the idea that architectural rigor requires waiting for full adoption or institutional comfort. Early-stage inquiry, pilot studies, and speculative frameworks are essential precisely because they allow architects to think before systems harden into standards.
Arqwell is built for researchers, practitioners, technologists, and educators who understand that the future of architecture will not be shaped only by iconic buildings or formal innovation, but by infrastructures that operate quietly beneath them. Our work asks difficult questions early: Who is the author when systems generate outcomes? Where does liability reside when decisions are automated? What happens to professional judgment when tools mediate awareness? How does building science adapt when data, contracts, and performance models converge?
This issue focuses on artificial intelligence, architecture, and Web3 technologies not as isolated topics, but as intersecting forces that challenge long-held assumptions about authorship, control, and responsibility. The articles that follow do not claim to resolve these tensions. Instead, they map them, document them, and insist that architecture take them seriously.
Arqwell’s goal is simple, but not easy: to help architects think earlier, more clearly, and more responsibly about the systems shaping their work. If architecture is to remain a profession grounded in care, accountability, and stewardship, then it must be willing to examine the forces that shape it — even when those forces are uncomfortable, unfamiliar, or still emerging.
This journal is an invitation to that examination.
