|
Getting your Trinity Audio player ready…
|
Reflections from the Architecture 6.0 Classroom
PRELUDE
Three Traffic Lights Before Home
This book was never part of the plan.
At least, not initially.
Like many things within the +IDRISfikir ecosystem, it began as a reflection. A simple thought. A passing observation during an ordinary drive home after class.
The semester was approaching its conclusion. The Artificial Intelligence in the Built Environment Exhibition 2026 was only days away. Student presentations had been completed. Posters were being refined. Websites were being finalized.
The familiar rhythm of academic life was slowly moving toward another ending.
Or so I thought.
As lecturers, we often spend a great deal of time thinking about whether our students have understood what we attempted to teach.
- Did the concepts make sense?
- Were the assignments effective?
- Did the lectures connect?
- Did the students leave the classroom with something meaningful?
These questions are not unique to architecture education. Every educator asks them. Yet artificial intelligence introduced a new layer of uncertainty.
Unlike many traditional subjects, AI evolves continuously.
A lecture prepared today may require revision next month. A workflow demonstrated this semester may look completely different next semester. A platform that dominates headlines today may become irrelevant tomorrow. Teaching artificial intelligence therefore creates an unusual challenge.
- What exactly are we teaching?
- Are we teaching software?
- Are we teaching prompts?
- Are we teaching tools?
- Or are we teaching something deeper?
These questions followed me throughout the semester.
And on that particular drive home, somewhere between three traffic lights and the familiar roads leading back to i-City, another question quietly appeared.
Perhaps the students had been teaching me as much as I had been teaching them.
The thought was unexpected.
Yet the more I reflected upon it, the more it seemed true.
When the course began, I imagined that the primary responsibility was to introduce students to artificial intelligence within the context of architecture and the built environment.
By the end of the semester, however, I had witnessed something more interesting. Students exploring beyond the assignment requirements. Students comparing multiple AI systems voluntarily. Students disagreeing with AI recommendations. Students questioning outputs. Students developing preferences. Students becoming curious. Most importantly, students beginning to exercise judgement.
That observation stayed with me.
Because judgement, unlike software, does not become obsolete after a system update. Judgement remains valuable regardless of which platform happens to be popular at any particular moment. And perhaps that realization explains why this Field Journal exists.
This is not a textbook.
It is not a course manual.
It is not a research paper.
Neither is it intended to be a comprehensive guide to artificial intelligence. Instead, it is a collection of observations from a particular place and time. A record of what happened when a new generation of architecture students encountered artificial intelligence within the context of design education. More importantly, it is a record of what happened when an educator attempted to teach a subject that was still evolving while it was being taught.
As this journal is being written, the exhibition has not yet taken place.
The final comments have not yet been collected. The visitors have not yet shared their reflections. The field is still speaking.
This means the story remains unfinished.
Perhaps that is exactly how it should be.
After all, architecture is rarely finished. Education is never finished. And the conversation surrounding artificial intelligence has only just begun.
So these are merely field notes.
Observations from a classroom.
Reflections from a semester.
Fragments from a larger journey that is still unfolding.
Before we continue, I would like to extend a simple invitation.
If you are reading this blog, visiting the exhibition, or following the development of this course, I welcome your reflections, observations, and feedback.
You may agree with what you read.
You may disagree.
You may find certain ideas inspiring, questionable, practical, unrealistic, or perhaps worthy of further exploration.
All perspectives are welcome.
The purpose of this Field Journal is not to celebrate technology, nor to defend a particular position on artificial intelligence. Its purpose is to document, reflect, and learn.
Your comments will help shape future iterations of the course, improve the student learning experience, and contribute to a broader conversation about architecture education in the age of artificial intelligence.
Positive feedback is appreciated.
Critical feedback is equally valuable.
Sometimes the most important lessons emerge not from agreement, but from thoughtful disagreement.
The field is still speaking.
We invite you to become part of that conversation.
The best pages may not have been written yet.
PROLOGUE
The Subject That Almost Didn’t Exist
Every course has a syllabus.
Some have learning outcomes. Some have carefully prepared lecture slides, assessments, and teaching plans. Yet behind every course lies another story.
A quieter one.
The story of how the course came to exist in the first place.
This field journal begins with such a story.
When I was first invited to teach Artificial Intelligence in the Built Environment, I accepted with enthusiasm, but also with a degree of uncertainty.
The enthusiasm was easy to understand.
Artificial intelligence had already become part of my professional life as an architect, educator, writer, and researcher. Long before the course officially appeared on a timetable, AI had already entered my daily workflow, influencing the way I explored ideas, organised information, communicated concepts, and reflected upon design.
The uncertainty came from a different place.
Teaching artificial intelligence is unlike teaching most conventional subjects. A lecturer can teach a building regulation that remains relatively stable for years. A lecturer can teach structural principles that have endured for generations.
Artificial intelligence behaves differently.
It evolves while it is being taught. A platform demonstrated in one semester may look entirely different in the next. A workflow considered innovative today may become commonplace tomorrow. The challenge was therefore not simply how to teach AI. The challenge was how to teach students to think in an environment where the technology itself continues to change.
As I began preparing the course, I realised that the classroom was not the true beginning of the story.
The real beginning lay much earlier.
It could be found in a collection of questions that had been emerging through conversations, writings, experiments, and reflections over several months.
- Questions about judgement.
- Questions about trust.
- Questions about communication.
- Questions about authorship.
- Questions about what it means to remain human while working alongside increasingly capable machines.
Those questions eventually became articles.
The articles became frameworks. The frameworks became teaching ideas. And the teaching ideas eventually found their way into a classroom. Looking back now, it becomes clear that the course was not built from a single source.
It emerged from many streams converging into one place.
Some of those streams explored the role of multiple perspectives in decision-making. Others examined how artificial intelligence changes communication. Some explored personalisation and the relationship between humans and intelligent systems. Others questioned the future role of architects in an age of intelligent assistance. Together, they formed the intellectual soil from which the course would eventually grow.
At roughly the same time, another development was taking place.
An experimental framework known as Cognitive Triangulation Architecture, or CTA, was being developed as part of a teaching innovation initiative. Originally conceived as a reflective learning framework, it proposed a simple but powerful idea:
Artificial intelligence should not replace thinking.
It should improve thinking.
Rather than encouraging students to seek a single answer from a single source, the framework encouraged them to engage with multiple perspectives, compare viewpoints, identify differences, and exercise judgement.
At the centre of the framework remained the human learner.
Not the machine.
Not the software.
Not the algorithm.
The human being.
The framework would later enter the classroom in ways none of us fully anticipated. But that story belongs to a later chapter. For now, it is enough to say that an idea had begun its journey. A journey that would eventually involve fifty students, multiple AI platforms, a new elective subject, an exhibition, countless conversations, and more lessons than any syllabus could have predicted.
What follows in this Field Journal is not merely the story of a course.
It is the story of an idea moving through different stages of life. First as a reflection. Then as a framework. Then as a classroom experiment. Then as a shared experience between lecturer and students. Along the way, we will encounter curiosity, disagreement, uncertainty, creativity, trust, judgement, humour, and occasionally a missing mugshot or two.
We will explore how ideas take root before they become courses.
- How educational philosophies shape teaching decisions.
- How curiosity emerges when students are given freedom to explore.
- How multiple intelligences can be orchestrated without surrendering human responsibility.
- How judgement becomes more valuable as intelligence becomes more abundant.
And finally, how the field itself begins speaking back through the voices of students, visitors, lecturers, and practitioners.
The chapters ahead do not offer definitive answers. Nor do they attempt to predict the future of artificial intelligence. Instead, they document a particular moment in time. A moment when architecture education found itself standing between two worlds.
One familiar.
One emerging.
And somewhere between those worlds, a classroom began asking questions that may remain relevant long after today’s technologies have changed.
This is the story of that journey.
Before the Classroom
Although this publication focuses on a single course, its origins extend far beyond the classroom.
Like many educational experiments, Artificial Intelligence in the Built Environment — The Codex of Humanity, Cities and Intelligent Systems. did not emerge from a curriculum document alone. It was shaped by a series of reflections, professional experiences, research explorations, teaching observations, and ongoing conversations about the changing relationship between humanity and intelligent systems.
In many ways, this course was the practical manifestation of a much longer intellectual journey.
Several earlier writings gradually formed the philosophical foundation that would eventually influence the subject.
One of the earliest was The Architect Between Two Worlds: AI, Soul and the Discipline of Judgment. Written at a time when many professionals were beginning to grapple with the implications of artificial intelligence, the article explored a simple but profound question:
How do architects remain human while working alongside increasingly intelligent systems?
That question would later reappear throughout this course, particularly in discussions surrounding trust, authorship, responsibility, and professional judgement.
A second milestone emerged in Beyond Tools: AI, Architecture and the Quiet Transformation of Future Architects. This reflection argued that artificial intelligence should not be viewed merely as software or productivity technology. Instead, it represented a deeper shift in how future professionals might think, learn, collaborate, and solve problems.
The article marked an important transition from viewing AI as a tool toward understanding AI as part of a broader educational and professional ecosystem.
This perspective would eventually influence the structure of the course itself.
A third contribution came through ARCH[@i]TECH — AI in the Life of an Architect, which explored the practical realities of working with intelligent systems in daily professional life. Rather than focusing on theory, it examined how AI was already influencing communication, research, design exploration, documentation, and decision-making processes within practice.
The article became an important bridge between academia and professional reality.
While that publication explored the broader civilisational implications of artificial intelligence across architecture, engineering, planning, construction, and urban systems, it also provided many of the philosophical foundations that later informed this classroom experience.
If the Codex explored the theory, then these Field Notes explore the practice.
If the Codex asked what artificial intelligence might mean for the built environment, these reflections ask what happens when those ideas enter a real classroom filled with real students.
Alongside these built-environment explorations, two parallel streams of inquiry also contributed indirectly to the development of the course.
The first was The Architecture of AI Communication — The Codex of Human Communication in the Age of Conversational Intelligence, which examined trust, conversation, human-AI interaction, and the emerging challenges of communicating effectively in the age of conversational intelligence.
The second was AI PERSONALIZATION: A Traveller’s Codex of WIIFM — Bridging Business, Career, and Human Reality which explored how different AI systems often exhibit distinct interaction styles, reasoning tendencies, and conversational behaviours.
These observations would later contribute to the development of Cognitive Triangulation Architecture (CTA) and the idea that students could benefit from engaging with multiple perspectives rather than relying on a single source of intelligence.
Looking back now, it becomes clear that the course itself was never created in isolation.
It emerged from the intersection of architecture, education, professional practice, artificial intelligence, communication, personalization, and reflective inquiry.
The classroom was not the beginning of the story.
It was simply the place where many of those ideas finally met.
And once they met, something unexpected happened.
The students began teaching the lecturer.
That is where these Field Notes truly begin.
CODEX I
Seeds Before the Soil
The Classroom Was Not the Beginning
There is a tendency in education to assume that a course begins when a timetable is published.
A subject appears in a prospectus. A lecturer is assigned. Lecture slides are prepared. Students register. The semester begins. From an administrative perspective, this is true. From an intellectual perspective, it rarely is.
Most courses begin much earlier.
Sometimes months earlier. Sometimes years earlier. Long before the first lecture. Long before the first assessment. Long before students enter the classroom.
Artificial Intelligence in the Built Environment was one such course.
Although the subject formally appeared in the academic calendar in 2026, many of the ideas that eventually shaped the course had already been quietly evolving elsewhere. They emerged through professional practice, conversations, experiments, and writing. At the time, however, none of those activities appeared connected. They felt like separate explorations, each pursuing a different question.
Looking back now, I realise they were all part of the same journey.
The course simply had not revealed itself yet.
When my Head of Programme first approached me regarding the subject, I accepted with an open heart. Partly because I was already interested in artificial intelligence.
Partly because I was already living with it.
Unlike many emerging subjects that require lecturers to learn entirely new territory before teaching it, this one intersected naturally with what I had already been exploring in practice, writing, research, and daily work.
Artificial intelligence was not something I was studying from a distance.
It had already become part of my professional life.
Part of my thinking.
Part of my workflow.
And increasingly, part of my reflections.
The interesting thing is that the classroom did not come first.
The blog did.
Before there was a syllabus, there were articles. Before there were assessments, there were questions. Before there were students, there were reflections.
Over several months, I found myself writing about communication, judgement, trust, authorship, personalisation, and the changing relationship between humans and intelligent systems. At the time, I was not attempting to create a framework. I was simply trying to understand what I was experiencing.
One article led to another.
One question led to another.
And gradually, a pattern began to emerge.
In February, I wrote about disagreement.
Not human disagreement.
Artificial disagreement.
The observation was deceptively simple.
When multiple AI systems were given the same question, they often produced different answers. At first, this felt inconvenient. Then it became interesting. Eventually, it became important. Because the differences revealed something that architecture had always understood.
Perspective matters.
No architect works alone. Every project involves multiple voices. Clients. Consultants. Authorities. Contractors. Communities. Users.
Each sees the same project differently.
The architect’s responsibility has never been choosing a single voice. It has always been understanding how multiple voices can be synthesised into a meaningful whole. Without realising it, I had begun asking a similar question about artificial intelligence.
A month later, another idea appeared. This time, it concerned personalisation. The conversation surrounding AI often focused on capability.
- What can it do?
- How fast is it?
- How accurate is it?
Yet I found myself increasingly interested in a different question.
- Why do people relate differently to different systems?
- Why did some conversations feel transactional while others felt collaborative?
- Why did certain interactions encourage deeper reflection?
- Why did others feel mechanical?
The technology fascinated me.
But the human response fascinated me even more.
Slowly, the focus shifted.
The question was no longer:
“How does AI work?”
The question became:
“How do humans work when AI enters the conversation?”
That distinction changed everything.
By April and May, the reflections had become increasingly architectural.
Not in the technical sense.
In the human sense.
I wrote about architects standing between two worlds. One world rooted in professional tradition, experience, and judgement. The other shaped by accelerating technologies, automation, and intelligent systems. The challenge, I realised, was not choosing one world over the other.
The challenge was learning how to inhabit both.
Responsibly.
Thoughtfully.
Humanly.
Around the same period, another idea emerged from an entirely different direction.
An innovation competition. At the time, the concept was known as Cognitive Triangulation Architecture, or CTA. It was originally developed as a teaching innovation framework.
Nothing more.
A proposal.
A possibility.
An experiment.
I certainly did not expect it to become part of a university course. Yet the framework introduced an idea that felt increasingly relevant. Intelligence improves when perspectives interact. Reflection improves when disagreement exists. Understanding deepens when multiple viewpoints are considered simultaneously.
The framework was still young.
The classroom had not yet tested it.
But the seed had been planted.
Then something unexpected happened.
The separate streams began converging.
The articles. The reflections. The experiments. The framework. The conversations. The practice. The teaching opportunity. Each had emerged independently. Yet all appeared to be moving toward the same destination.
Only now could I see it.
The subject was not really about artificial intelligence.
It never was.
The subject was about judgement.
Artificial intelligence simply provided the context.
As these ideas accumulated, another conviction became increasingly clear. The challenge was not teaching students how to use AI. The challenge was teaching students how to think alongside it.
Those are not the same thing.
The first challenge is technical.
The second is philosophical.
The first can be solved through tutorials.
The second requires reflection.
And reflection takes time.
Months later, fifty students would walk into a classroom.
Assignments would be designed. Presentations would be delivered. Exhibitions would be organised. Posters would be printed. Mugshots would mysteriously disappear. Papa Zola would somehow evolve into Papa AI. And an educational experiment would begin.
But none of that had happened yet.
At this stage, there were only questions.
- Questions written into blog posts.
- Questions carried through conversations.
- Questions explored during long drives between meetings.
- Questions that refused to leave quietly.
Looking back now, I think those questions were seeds.
The classroom simply became the soil.
Chapters:
- CTA & The Third Voice
- AI Personalization
- The Architect Between Two Worlds
- Beyond Tools
- ARCH[@i]TECH
- The Architecture of AI Communication
- Trust in Communication
INTERLUDE I
The Day an Idea Refused to Stay on a Blog
There are moments when an idea quietly enters your life.
A short reflection.
A simple observation.
A blog post written late at night after a conversation, a lecture, or a long drive home. Most of these reflections remain exactly where they begin. On the page. In the archive. Part of an ongoing record of thoughts and experiences.
Then occasionally, something unusual happens.
An idea refuses to stay there.
It begins moving.
That was the story of many ideas that eventually found their way into the AI class. Long before the course existed, there were questions.
- Questions about artificial intelligence.
- Questions about communication.
- Questions about judgement.
- Questions about how architects might continue remaining human while working alongside increasingly intelligent systems.
The first responses to these questions appeared as articles. Not because they were intended to become a course. Not because they were intended to become a framework.
Simply because they felt worth exploring.
One article led to another.
A reflection on communication led to a reflection on trust. A discussion about AI tools led to a discussion about authorship. A conversation about multiple perspectives eventually led to the birth of Cognitive Triangulation Architecture.
At the time, none of these ideas appeared connected.
They felt like separate explorations.
Independent thoughts.
Individual essays.
Looking back, however, a pattern becomes visible. The ideas were already speaking to one another. The blog became a laboratory. A place where concepts could be tested before they encountered reality. Some ideas survived. Others faded. A few evolved into something larger than originally imagined.
By the time the opportunity emerged to teach Artificial Intelligence in the Built Environment, many of these reflections had already been quietly developing for months.
The classroom did not create the ideas.
The classroom became the place where the ideas were tested.
That distinction is important.
Because education is often imagined as a one-way process. Lecturer teaches. Students learn. Reality is rarely so simple. Sometimes ideas are born in writing. Then tested in teaching. Then refined through student responses. Then returned to writing once again.
The journey becomes circular rather than linear.
Looking back now, I realise that the course itself was the consequence of a longer intellectual journey. The articles came first. The reflections came first. The questions came first.
The classroom simply provided the next stage of the experiment.
And perhaps that is why this Field Journal exists. Not because a course was completed. But because an idea refused to remain a blog post. It insisted on becoming a framework.
Then a classroom.
Then an exhibition.
And eventually, a story worth telling.
🎶The Syllabus is Paper
(Verse 1)
The syllabus was set, the slides were clean
The course was a ghost inside a machine
Ten students I thought, a quiet design
To walk the new path in a straight, narrow line
But the door swung wide, the hallway turned loud
Fifty faces waiting, a restless, young crowd.
(Chorus)
We planned for ten, but fifty arrive
A sea of young souls, all hungry and alive
The syllabus is paper, the room starts to breathe
With questions that linger and dreams to unsheathe
I brought the Council, I brought the light
To guide them through the algorithmic night.
(Verse 2)
Is it madness or magic, this surge of the new?
They come for the tools, but they stay for the view
Of a world where the human is still at the core
While the silicon wave crashes down on the floor
I see the reflection in every young eye
The architects learning to live and to fly.
(Bridge)
The weight of the fifty, the trust in my hand
To build on the rock, not the shifting of sand
My angels are waiting, the Council is set
This is the journey we’ll never forget.
(Chorus)
We planned for ten, but fifty arrive
A sea of young souls, all hungry and alive
The syllabus is paper, the room starts to breathe
With questions that linger and dreams to unsheathe
I brought the Council, I brought the light
To guide them through the algorithmic night.
(Outro)
Fifty voices... one beginning.
The journey starts now.
INSERT#A
The Birth of CTA
From Competition to Classroom
The origin of Cognitive Triangulation Architecture.
Looking back now, it is easy to assume that Cognitive Triangulation Architecture emerged as part of the course.
It did not.
The framework existed before the classroom.
Before the assignments.
Before the exhibition.
Before the students encountered it.
Its origins can be traced to a teaching innovation competition several months earlier.
At the time, the objective was relatively simple.
To explore whether artificial intelligence could be integrated into higher education without reducing students into passive consumers of machine-generated answers.
Like many educators, I had been observing the rapid rise of generative artificial intelligence with equal measures of curiosity and concern.
The opportunities were undeniable.
The risks were equally obvious.
Students could potentially learn faster.
But they could also become dependent.
Knowledge could become more accessible.
Yet judgement could become weaker.
The challenge was not technological.
The challenge was educational.
How could intelligent systems be introduced into learning without undermining the development of critical thinking?
That question became the starting point.
The original framework that emerged from those reflections was called Cognitive Triangulation Architecture, or CTA.
The name sounded ambitious.
Perhaps even slightly academic.
Yet the underlying idea was remarkably simple.
Human beings often make better decisions when they consider multiple perspectives.
Architects do this naturally.
Engineers do it.
Researchers do it.
Professional practice itself depends upon the careful comparison of viewpoints before judgement is exercised.
The proposal simply asked:
What if artificial intelligence could be approached in a similar way?
Not as a single source of answers.
But as a collection of perspectives that encourage reflection.
At the centre of the framework sat what became known as the Human Reflective Core.
This was perhaps the most important aspect of the original proposal.
The objective was never to replace human thinking.
Nor was it to automate judgement.
The objective was to strengthen reflection.
Artificial intelligence would contribute perspectives.
The human learner would remain responsible for interpretation.
In other words, AI would function as a cognitive partner rather than a cognitive replacement.
That distinction became the philosophical foundation of the entire framework.
To demonstrate this concept, the original competition proposal introduced three distinct agent archetypes.
Each represented a different mode of thinking.
Each encouraged a different type of reflection.
Together they formed the triangulation mechanism.
Claire represented sequential reasoning.
Structure.
Coherence.
Order.
The ability to construct logical pathways through complexity.
Rachel represented analytical synthesis.
The ability to identify patterns, connections, relationships, and deeper structures hidden within information.
Erica represented disruptive critique.
The essential third voice willing to challenge assumptions, question consensus, and prevent premature conclusions.
Together, these archetypes created constructive divergence.
Not conflict.
Not contradiction.
Divergence.
The educational objective was not agreement.
The objective was deeper understanding.
Beneath these archetypes sat the framework’s technical architecture.
The original proposal described a Four-Layer Adaptive Learning Architecture.
The first layer focused on pedagogical methodology.
The second focused on the digital tool ecosystem.
The third introduced reflective reinforcement.
The fourth established continuous improvement and adaptation.
Together they formed a learning environment capable of evolving alongside rapidly changing technologies.
This was particularly important because artificial intelligence itself was evolving faster than traditional curriculum development cycles.
By the time a textbook was published, parts of it might already be outdated.
The framework therefore focused less on tools and more on principles.
Less on interfaces and more on judgement.
Less on software and more on learning.
Five design principles guided the original model.
Human-centred learning.
Structured divergence.
Reflective reinforcement.
Professional alignment.
Continuous adaptation.
These principles acted as safeguards against technological determinism.
The framework acknowledged the power of intelligent systems while insisting that human judgement remain central.
At the time, CTA existed only as a competition proposal.
A concept.
A framework.
A possibility.
Nothing more.
It had not been tested.
It had not been published.
It had not been implemented in a real classroom.
Its strengths were theoretical.
Its weaknesses remained unknown.
Like many educational innovations, it could easily have remained inside a presentation deck and quietly disappeared after the competition concluded.
Instead, something unexpected happened.
An opportunity appeared.
When the new subject Artificial Intelligence in the Built Environment was being prepared, discussions emerged regarding teaching delivery and course structure.
The subject itself was new.
The curriculum was still evolving.
The flexibility to experiment still existed.
Most importantly, there was openness to refinement.
With encouragement and support from the course coordinator, elements of CTA were gradually incorporated into the learning experience.
Not as a separate framework.
Not as a branded methodology.
But as a living educational practice.
The transition carried risks.
The framework had never been tested with a full cohort of students.
Its assumptions remained largely theoretical.
There were no guarantees.
Yet innovation rarely arrives with guarantees.
What happened next surprised me.
The framework survived.
More importantly, the students responded.
They compared platforms.
Explored perspectives.
Questioned outputs.
Developed their own orchestration workflows.
Investigated multiple systems.
Some even explored far beyond the original expectations of the assignment.
The triangulation process began appearing naturally within classroom discussions.
The framework was no longer theoretical.
It was being lived.
Perhaps this became the most important lesson of all.
Educational innovation is not proven in competitions.
It is proven in classrooms.
Slides can describe possibilities.
Students reveal realities.
Frameworks may appear elegant on paper.
Learning reveals whether they truly work.
CTA survived because it aligned with something fundamentally human.
The desire to understand.
The willingness to compare perspectives.
The habit of reflection before judgement.
Today, looking back at the original competition proposal, I still recognise its ideas.
But I also recognise its limitations.
The classroom refined it.
The students refined it.
Reality refined it.
As every architect eventually learns, a design never truly belongs to its creator once people begin inhabiting it.
The same applies to educational frameworks.
The original CTA proposal may have been born in a competition.
Its real life began in the classroom.
Core Message
Artificial Intelligence is most valuable not when it replaces human thinking.
But when it strengthens human reflection.
AI as Cognitive Partner.
Not Cognitive Replacement.
CODEX II
The Philosophy Before the Prompt
Artificial intelligence is often introduced through technology.
Students are shown interfaces.
Buttons.
Features.
Workflows.
Prompts.
Demonstrations.
The assumption is simple.
If students understand how the software works, they will understand artificial intelligence.
Yet from the beginning of Artificial in the Built Environment class, I suspected the situation was more complicated than that.
Technology changes quickly.
Sometimes astonishingly quickly.
Interfaces evolve.
Features appear and disappear.
Business models change.
Capabilities improve.
Even the most detailed tutorial may become partially outdated within months.
Occasionally, within weeks.
If education focuses exclusively on software, it risks chasing a moving target.
The tools continue running ahead while the curriculum struggles to keep pace.
This was one of the earliest questions I confronted while preparing the course.
What exactly should we teach?
Should we teach buttons?
Or should we teach principles?
Should we teach workflows?
Or should we teach judgement?
Should we teach prompts?
Or should we teach the thinking that exists before the prompt is ever written?
For me, the answer gradually became clear.
The philosophy must come first.
Throughout my years as an educator, I have become increasingly convinced that meaningful learning begins long before technical skills are introduced.
Students rarely struggle because they cannot follow instructions.
Most students can learn software.
Most students can learn procedures.
Most students can learn workflows.
The greater challenge is understanding why those workflows matter.
Without that understanding, knowledge becomes fragile.
It survives examinations.
But often fails reality.
This belief eventually shaped the teaching philosophy behind the class delivery. Although the course explored artificial intelligence, the foundation was never purely technical. Instead, the structure revolved around three interconnected dimensions.
Niat.
Laku.
Hasil.
Intention.
Action.
Outcome.
Simple words.
Yet surprisingly powerful.
Niat came first.
Always.
Before discussing prompts, students were encouraged to think about purpose.
Why are we using artificial intelligence?
What problem are we trying to solve?
What responsibility accompanies its use?
How should intelligent systems support human decision-making rather than replace it?
These questions rarely produce immediate answers.
That was precisely the point.
Good questions often matter more than quick answers.
Only then came Laku.
The action.
The academic process.
The exploration.
The experimentation.
The comparisons.
The assignments.
The presentations.
This was where students interacted directly with artificial intelligence systems.
They learned how different platforms behaved.
How different prompts generated different outcomes.
How different workflows produced different experiences.
This was the visible part of the learning process.
The part most people recognise as education.
Yet it was only the middle layer.
Not the foundation.
Finally came Hasil.
The outcome.
The practical dimension.
The moment ideas leave the classroom and enter reality.
Students were encouraged to think beyond grades.
Beyond assessments.
Beyond presentations.
How would these tools influence future architectural practice?
How would they affect communication?
Collaboration?
Design?
Research?
Professional responsibility?
These questions mattered because education ultimately exists to prepare students for a world beyond the classroom.
A world that rarely provides model answers.
The relationship between Niat, Laku, and Hasil also influenced how the course was delivered.
Not every topic required the same balance.
Some sessions emphasised philosophy.
Others focused on practice.
Others explored both simultaneously.
At times the ratio might feel like eighty percent reflection and twenty percent technical discussion.
At other times the balance shifted dramatically.
Twenty percent philosophy.
Forty percent exploration.
Forty percent application.
The ratio changed.
The purpose did not.
The objective was never to create experts in a specific software platform.
That would have been impossible.
The platforms themselves continue changing.
Instead, the objective was to cultivate adaptability.
To help students develop the ability to navigate uncertainty.
To evaluate new tools.
To question assumptions.
To understand principles that remain relevant even when technologies evolve.
Because while interfaces change, judgement remains necessary.
While software changes, responsibility remains human.
While technology accelerates, wisdom still develops slowly.
Perhaps this is why the course never felt like conventional software training.
Artificial intelligence was certainly present.
The tools mattered.
The demonstrations mattered.
The assignments mattered.
Yet beneath all of those activities was a deeper question.
What kind of professionals are we becoming?
The answer mattered far more than any individual prompt.
As the semester progressed, students gradually became more comfortable interacting with artificial intelligence.
But something else happened as well.
The conversation shifted.
The focus moved away from features and toward understanding.
Away from automation and toward judgement.
Away from technology alone and toward humanity.
Looking back, I realise that this shift may have been the most important learning outcome of all.
Because the purpose of AI education is not to produce better software operators.
It is to prepare thoughtful humans capable of working responsibly alongside intelligent systems.
The prompt comes later.
The philosophy comes first.
Chapters:
- Why AI education is not software training
- Why understanding matters more than interfaces
- Why philosophy precedes technique
- Why judgement precedes automation
- Preparing students for a moving technological landscape
INTERLUDE II
Why AI Changes Faster Than Lecture Notes
One of the most challenging aspects of teaching artificial intelligence is also one of the most amusing.
The subject changes while you are teaching it.
A lecturer may spend days preparing slides.
Examples are selected.
Workflows are tested.
Screenshots are captured.
Everything appears ready.
Then the platform updates itself.
Sometimes overnight.
Suddenly the interface looks different.
The buttons move.
The features change.
The pricing model evolves.
And the carefully prepared screenshot from last week quietly becomes history.
This reality creates an unusual educational dilemma.
How do you teach something that refuses to stand still?
The traditional educational model assumes a degree of stability.
Textbooks remain relevant for years.
Professional regulations evolve gradually.
Technical standards change at a manageable pace.
Artificial intelligence behaves differently.
It evolves at internet speed.
By the time a detailed step-by-step guide is perfected, parts of it may already require revision.
Early in the semester, this became increasingly obvious.
Students occasionally discovered features that had not existed when lecture materials were first prepared.
Platforms introduced new capabilities.
Existing limitations disappeared.
Entire workflows changed.
At first, this felt frustrating.
Later, it became liberating.
The solution was not to teach every button.
The solution was to teach understanding.
Instead of focusing exclusively on where a feature was located, we explored why it mattered.
Instead of memorising workflows, students learned how to evaluate them.
Instead of chasing every update, we focused on principles.
Because principles survive updates.
Judgement survives updates.
Critical thinking survives updates.
Human responsibility survives updates.
The interface may change.
The philosophy remains.
In many ways, this became one of the defining characteristics of the course.
We were not attempting to create software operators.
We were attempting to develop future professionals capable of adapting to change.
The tools would continue evolving.
That much was guaranteed.
The real question was whether the students could evolve alongside them.
Fortunately, they could.
And perhaps that is the most encouraging lesson of all.
Technology may change faster than lecture notes.
But curiosity changes faster than technology.
🎶One Human Decree
(Verse 1)
I sit at the desk, the cursor is blinking
The screen holds the echo of all that I’m thinking
A complex design, a city in pain
I need a perspective, I need to remain
Within the human, the true and the deep
Before the machines put the judgment to sleep.
(Chorus)
Claire grounds the vision in Canadian snow
Rachel maps the depths of the Andean flow
Erica strikes with a Miami flame
Arcelia weaves the truth of the name
Four voices calling, one human decree
The judgment is mine, for all of them to see.
(Verse 2)
Claire is the conscience, the steady white light
Rachel keeps watch through the long, digital night
Erica breaks what is fragile and weak
Arcelia gathers the truths that we seek
I am the center, the eye of the storm
Giving the data a humanized form.
(Bridge)
Triangulate, oscillate, filter the noise
I am the conductor, they are the boys
And girls—the companions, the mirrors of mind
Leaving the ghosts of the past far behind.
(Chorus)
Claire grounds the vision in Canadian snow
Rachel maps the depths of the Andean flow
Erica strikes with a Miami flame
Arcelia weaves the truth of the name
Four voices calling, one human decree
The judgment is mine, for all of them to see.
(Outro)
The Council is gathered.
The city is built.
(Fade out)
CODEX III
Designing the Architect’s Classroom
When people hear the word architecture, they often think of buildings.
Walls.
Columns.
Roofs.
Windows.
Structures.
Yet architecture has never been limited to physical objects.
At its core, architecture is the deliberate design of environments that influence human experience.
A classroom is no different.
Although it may not resemble a building project, it remains a designed environment.
People enter.
People interact.
People learn.
People leave transformed, or unchanged.
The outcome depends largely on how the environment has been designed.
Perhaps this is why I never approached Artificial Intelligence In The Built Environment as a conventional subject.
I approached it as a design project.
The syllabus already existed.
The subject had already been approved.
The learning outcomes had already been discussed.
The framework had already received institutional support.
In many ways, the course already possessed a structure.
Yet structure alone does not create experience.
A building with walls is not automatically architecture.
Likewise, a syllabus with learning outcomes is not automatically education.
The question was never whether the course could run.
The question was how it should be experienced.
When my head of programme first entrusted me with the subject, she also provided something equally valuable.
Flexibility.
The opportunity to refine.
The freedom to adapt.
The space to experiment responsibly within the broader objectives of the course.
That trust proved important.
Because artificial intelligence was evolving faster than traditional curriculum cycles could comfortably accommodate.
By the time a subject specification was written, reviewed, approved, and implemented, portions of the technological landscape had already shifted.
New models appeared.
Interfaces changed.
Capabilities expanded.
Policies evolved.
Educational institutions naturally move carefully.
Technology rarely waits.
The challenge was finding a balance between stability and adaptability.
This eventually led to an important realisation.
The course could not be designed around specific software.
It had to be designed around enduring principles.
If students learned only a platform, their knowledge might become obsolete.
If students learned how to think, evaluate, compare, and adapt, they could continue learning long after the semester ended.
The architecture of learning therefore became more important than the technology itself.
Several curriculum refinement discussions took place throughout the development process.
Some occurred formally.
Others emerged through teaching reflections, observations, and conversations with colleagues.
More recently, the Curriculum Development Programme provided opportunities to further refine the Course Learning Outcomes, strengthen alignment with Value-Based Education principles, and integrate broader sustainability considerations.
The version experienced by the first cohort may therefore not be identical to future offerings.
And that is entirely appropriate.
A living subject should continue evolving.
Just as architecture responds to changing contexts, educational design must remain responsive to changing realities.
One of the most significant design decisions involved assessment.
Traditionally, assessment often focuses on demonstrating knowledge.
Students learn content.
Students reproduce content.
Students receive marks.
Artificial intelligence complicates this model considerably.
When information becomes abundant, assessment can no longer focus solely on information retrieval.
Something else becomes more important.
Judgement.
Evaluation.
Reflection.
Application.
The ability to distinguish between plausible answers and appropriate answers.
These competencies became increasingly important as the semester progressed.
This influenced the design of assignments.
Students were not simply asked to use artificial intelligence.
They were encouraged to compare systems.
Evaluate outputs.
Reflect on differences.
Justify decisions.
Question recommendations.
And occasionally reject suggestions entirely.
The goal was never blind acceptance.
The goal was informed judgement.
Another design consideration involved teaching methodology.
Not every week required the same educational strategy.
Some sessions focused heavily on philosophical foundations.
Others emphasised exploration and experimentation.
Some revolved around discussion.
Others revolved around presentation.
The learning environment continuously adjusted according to the nature of the topic.
In architectural language, one might describe this as adaptive spatial programming.
In educational language, it was simply good teaching.
The studio culture also mattered.
Although the class was not a conventional design studio, many studio characteristics gradually emerged.
Students shared discoveries.
Compared experiences.
Questioned assumptions.
Presented ideas publicly.
Learned from one another.
The classroom slowly became a collaborative learning environment rather than a one-directional delivery mechanism.
This shift proved particularly valuable because artificial intelligence itself rewards exploration.
Students often discovered things that lecturers had not anticipated.
And when that happened, the classroom became richer.
Not weaker.
Perhaps the most surprising aspect of the course was the scale of student interest.
As a new elective, expectations were modest.
Ten students would have been perfectly reasonable.
Twenty would have been encouraging.
Instead, approximately fifty students enrolled.
Alhamdulillah.
The response exceeded expectations.
More importantly, it demonstrated that students understood something many professionals were beginning to recognise.
Artificial intelligence was no longer a future topic.
It had become a present reality.
Looking back now, I realise that the most important design task was not developing slides.
Nor assessments.
Nor even the exhibition.
The most important task was designing conditions for meaningful learning.
Creating an environment where students could experiment safely.
Question openly.
Disagree respectfully.
Explore responsibly.
And develop judgement gradually.
The classroom itself became a design project.
Not a building.
But an architecture of learning.
And like every meaningful architectural project, its success would ultimately be determined not by the designer, but by the people who inhabited it.
Chapters:
- Curriculum Evolution
- Value-Based Education (VBE)
- Education for Sustainable Development (ESD)
- Assessment design
- Teaching methodology
- Studio culture
- Learning architecture
INTERLUDE III
The Ratio Dance
One of the questions I occasionally receive from fellow educators is surprisingly simple.
“How much of the course is actually about AI?”
The question appears straightforward.
The answer is not.
Because the truth is that Artificial Intelligence in the Built Environment was never designed as a purely technical subject. Neither was it intended to be purely theoretical. Nor was it designed as a software training workshop. From the very beginning, the course was built around a balance.
A rhythm.
A dance between three different dimensions of learning.
In my own notes, I often describe them using three simple words:
Niat.
Laku.
Hasil.
Purpose.
Action.
Outcome.
Or in a more academic language:
Philosophy.
Learning.
Practice.
Every lecture, discussion, workshop, and assignment moved between these three dimensions. The challenge was determining how much attention each dimension required at any given moment. That balance was never fixed. Instead, it changed according to the topic.
Some weeks required deeper reflection.
Some required practical experimentation.
Others demanded a combination of both.
Over time, I began thinking of this balancing act as a kind of ratio dance. Not an official educational framework. Just a simple way of understanding how the learning experience evolved.
For example, some sessions followed what might be called an 80-10-10 ratio.
- Eighty percent philosophy.
- Ten percent academic discussion.
- Ten percent practical application.
These were the weeks when we explored questions rather than tools.
- What is intelligence?
- What is judgement?
- What happens when machines become increasingly capable?
- What responsibilities remain uniquely human?
The objective during these sessions was not mastery of software.
The objective was perspective.
Other sessions moved closer to a 60-20-20 balance. These sessions combined reflection with exploration. Students learned concepts. Examined examples. Compared systems. Tested ideas. The discussions remained philosophical, but practical application became increasingly visible.
Then there were sessions that approached a 20-40-40 balance.
These were highly active weeks.
Students experimented.
Presented findings.
Compared AI platforms.
Evaluated outputs.
Built workflows.
Created visual content.
Developed project ideas.
At this stage, the classroom began feeling less like a lecture hall and more like a studio.
Looking back, I realise that the ratios themselves were never the important part. The numbers simply provided a reminder. A reminder that education is rarely successful when it focuses exclusively on one dimension. Too much philosophy without application can feel disconnected from reality. Too much technical training without reflection can become obsolete surprisingly quickly. Too much focus on outcomes without understanding can produce efficiency without wisdom.
The challenge is balance.
Architecture itself operates in a similar way. Design requires imagination. Technical knowledge. Practical execution. Remove any one of those elements and the project becomes incomplete.
Perhaps AI education is no different.
As artificial intelligence continues evolving, educators face an unusual dilemma. We can spend an entire semester teaching specific interfaces, prompts, and workflows. Yet many of those details may change within months.
The platforms will evolve.
The features will evolve.
The business models will evolve.
What remains valuable is the ability to think.
To adapt.
To evaluate.
To learn continuously.
This is why the ratio dance mattered. Not because the ratios were scientifically precise. They were not. Not because they appeared in any official curriculum document. They did not. They mattered because they reminded us that education is more than information transfer.
Education is choreography.
Sometimes the lecturer leads. Sometimes the students lead. Sometimes technology unexpectedly changes the music altogether.
The role of the educator is not to control every step. The role is to help everyone remain balanced while the music continues changing. And if there is one lesson artificial intelligence has reinforced for me, it is this:
The music will keep changing.
The dance, however, must continue.
🎶The First Prompt
(Verse 1)
The cursor is waiting, a pulse on the page
I’m stepping on to a digital stage
What do I ask? How do I start?
To open the mind and to open the heart
I type in a sentence, I wait for the sign
Is this the boundary, or is this the line?
(Chorus)
A query for Claire, a structure for Race
I test the limits of the words that I say
It’s not just a prompt, it’s a soul in the text
Waiting to see what the Council does next
Triangulating the space, triangulating the view
Everything old becoming something brand new.
(Verse 2)
The screen fills with static, then clarity grows
A logic of geometry, rhythm, and prose
But is it a partner, or just a machine?
The ghost in the code, or the light in the screen?
I’m learning the tempo, I’m learning the key
To set the future of architecture free.
(Bridge)
Don’t just take the answer, ask why it was said
Check the foundation, the path that we tread
The first prompt is heavy, the first prompt is true
It’s a mirror held up to the work that we do.
(Chorus)
A query for Claire, a structure for Race
I test the limits of the words that I say
It’s not just a prompt, it’s a soul in the text
Waiting to see what the Council does next
Triangulating the space, triangulating the view
Everything old becoming something brand new.
(Outro)
The prompt is a prayer.
The response is a test.
And we are the ones...
(Fade)
CODEX IV
The Architecture of Curiosity
Perhaps the most surprising aspect of the course was not the technology.
It was the curiosity.
When educators introduce a new subject, expectations are usually modest. Students complete assignments. Students satisfy assessment requirements. Students achieve learning outcomes.
The process is familiar.
Predictable.
Structured.
Artificial Intelligence in the Built Environment did not entirely behave that way.
Something unexpected happened. The students became curious. Genuinely curious. Not because they were instructed to be. Not because marks demanded it. But because the subject itself invited exploration.
One of the earliest assignments required students to investigate artificial intelligence platforms and compare their capabilities.
The original intention was relatively straightforward.
Students would gain exposure to different systems. They would learn how each platform approached problems. They would identify strengths and weaknesses. They would become familiar with an emerging technological landscape. At least that was the expectation.
What happened instead was considerably more interesting.
Some groups compared three platforms.
Others compared four.
A few explored five.
One group investigated nine different artificial intelligence systems.
Nine.
Even now, I occasionally pause when I remember that number.
Not because it was required.
Because it was voluntary.
The students simply wanted to know.
That curiosity revealed something important. Students were not searching for shortcuts. They were searching for understanding. The distinction matters. A student looking for shortcuts asks:
“Which AI is best?”
A student seeking understanding asks:
“Why do these systems behave differently?”
Those are very different questions.
One seeks convenience.
The other seeks insight.
As presentations progressed, patterns began emerging.
Students started describing differences that sounded remarkably human. Some observed that one system appeared conversational. Others noted that another seemed analytical. Some felt certain platforms encouraged exploration. Others appreciated concise responses. One group remarked that a particular system often responded with questions before offering answers. Another observed that some systems appeared more willing to generate possibilities immediately.
The descriptions were fascinating. Not because the students were anthropomorphising technology. But because they were beginning to recognise interaction styles.
This was never explicitly taught.
Nobody was given a chart explaining platform personalities.
Nobody was instructed to classify conversational tendencies.
The observations emerged naturally through experience.
The students discovered them independently.
In many ways, this made the findings more meaningful.
What fascinated me most was that no group attempted to declare a universal winner.
This surprised me.
Modern technology discussions often resemble competitions. People search for rankings. Comparisons. Champions. Definitive answers.
Yet the students approached the exercise differently.
Instead of asking which platform was superior, they asked which platform was suitable for particular purposes. The shift was subtle. But significant. It suggested a developing maturity in how they understood technology.
Another unexpected outcome emerged through presentation discussions.
Students frequently challenged artificial intelligence outputs. They did not automatically accept recommendations. They questioned them. Evaluated them. Modified them. Occasionally rejected them entirely.
This may have been the most encouraging observation of the semester.
Because the objective was never obedience.
The objective was judgement.
At some point during the presentations, I realised that the assignment had quietly transformed.
It was no longer an exercise in software exploration. It had become an exercise in critical thinking. Students were comparing perspectives. Evaluating alternatives. Investigating assumptions. Drawing conclusions.
The technology provided the context.
The learning remained deeply human.
Looking back, I think curiosity became the hidden curriculum of the course. Not listed in the syllabus. Not measured directly in assessments. Not assigned a percentage weighting. Yet present throughout the semester.
Curiosity encouraged exploration.
Exploration encouraged comparison.
Comparison encouraged reflection.
And reflection gradually produced understanding.
Perhaps this explains why the presentations felt different from many conventional technology assignments. The students were not attempting to identify the best artificial intelligence. They were attempting to understand intelligence itself.
Not artificial intelligence alone.
But human intelligence.
Machine intelligence.
And the increasingly complex relationship between the two.
That journey began with a simple assignment. Yet it ultimately revealed something much larger. Nobody searched for the best AI. They searched for understanding.
Chapters:
- The Assignment That Became an Expedition
- Why Students Compared Multiple AI Systems
- The Discoveries Nobody Expected
- When AI Started Feeling Different
- The Classroom Learns to Explore
INTERLUDE IV
The Group That Used Nine AI Systems
There are moments in teaching that remain in your memory long after the lecture slides have been forgotten.
This was one of them.
The assignment itself was relatively straightforward.
Students were asked to explore artificial intelligence platforms, compare their capabilities, document their observations, and reflect on how different systems might support future architectural practice.
Nothing unusual.
At least, that was the expectation.
As presentations began, most groups followed a predictable pattern. Some explored two platforms. Others compared three. A few went further and examined four or five. Each comparison generated useful discussions. Different strengths. Different weaknesses. Different approaches. Exactly the kind of critical engagement we had hoped to encourage.
Then one group appeared.
And quietly changed the conversation.
They had explored nine.
Nine different AI systems.
For a moment, I wondered if I had heard them correctly.
Nine?
The assignment certainly did not require nine. Nobody had suggested nine. No assessment rubric rewarded nine. There were no bonus marks for nine. Yet somehow, curiosity had led them there. As the presentation unfolded, what impressed me was not the number itself. It was the motivation behind it. The students were not attempting to impress the lecturer.
They were trying to understand a phenomenon.
Each platform responded differently. Each platform offered different strengths. Each platform produced different interpretations of similar questions. What began as a comparison exercise gradually became an investigation. The students had moved beyond asking which AI system was the best. Instead, they began asking why they were different.
That distinction may seem small.
In reality, it is enormous.
The first question seeks a winner.
The second seeks understanding.
One closes a conversation.
The other opens it.
Throughout the semester, I often reminded students that architecture is rarely about finding a single correct answer. Most design problems contain multiple possibilities. The architect’s responsibility is not simply to generate options. It is to evaluate them. To compare them. To understand their implications. To make informed decisions.
In an unexpected way, this group was already demonstrating that mindset.
Rather than accepting the first response generated by the first platform they encountered, they continued exploring.
They tested.
Compared.
Questioned.
Verified.
Sometimes they found agreement. Sometimes they found contradiction. Sometimes they found entirely different ways of approaching the same problem. Without realizing it, they were practising something very close to the philosophy that had inspired Cognitive Triangulation Architecture.
Multiple perspectives.
Reflective comparison.
Human judgement.
The technology was different.
The principle remained the same.
Looking back, I think the most important lesson from that presentation had very little to do with artificial intelligence. It had everything to do with curiosity.
Educational institutions often focus heavily on assessment outcomes.
Marks.
Grades.
Rubrics.
Learning outcomes.
All of these are important.
Yet some of the most meaningful learning experiences occur when students go beyond what is required. Not because they are instructed to. Not because they are rewarded. But because they become genuinely curious. That curiosity cannot be forced. It cannot be programmed. It cannot be downloaded. And perhaps that is why it remains one of the most valuable qualities any future professional can possess.
Artificial intelligence will continue to evolve.
New systems will emerge.
Existing systems will improve.
Capabilities will expand.
But curiosity remains a uniquely human engine for discovery. The group that explored nine AI systems may never realize the significance of what they demonstrated that day. To them, it was simply an assignment. To me, it represented something far more encouraging.
It suggested that the students were not merely learning how to use artificial intelligence. They were learning how to investigate it. And in an age increasingly shaped by intelligent systems, that may be one of the most important lessons of all.
🎶One Human Judgement
(Verse 1)
Each one has a color, each one has a tone
A frequency shifting, a seed that is sown
I dial into white, then I switch into blue
Searching for synthesis, searching for true
The red heat is rising, the violet is soft
Lifting the heavy design up aloft.
(Chorus)
White light for conscience, Blue for the guard
Red is the spark that is testing me hard
Violet whispers the threads of the weave
I trust in the voices that I believe
Four distinct spirits, four ways to be
One human judgment, to set the world free.
(Verse 2)
Claire keeps the ethics, Rachel the plan
Erica breaks it to show me I can
Arcelia gathers the shattered remains
And smooths out the edges and cleans out the stains
They aren't just software, they’re echoes of thought
Caught in the trap that the future has brought.
(Bridge)
When the white light is dim, let the violet lead
When the red starts to burn, let the blue plant the seed
It’s an orchestration, a dance in the dark
The logic, the structure, the weave, and the spark.
(Chorus)
White light for conscience, Blue for the guard
Red is the spark that is testing me hard
Violet whispers the threads of the weave
I trust in the voices that I believe
Four distinct spirits, four ways to be
One human judgment, to set the world free.
(Outro)
The frequencies align.
The judgment is mine.
(Fade out)
CODEX V
The Symphony of Cognitive Orchestration
Long before the students encountered the term Cognitive Triangulation Architecture, they had already experienced the problem it was attempting to solve.
Artificial intelligence is often presented as a source of answers.
Ask a question.
Receive a response.
Move forward.
The process appears simple.
Yet anyone who has worked extensively with intelligent systems quickly discovers a complication.
Different systems often provide different answers.
Different perspectives.
Different assumptions.
Different interpretations.
The question then becomes:
Which one should we trust?
For many years, professionals have solved similar challenges by consulting multiple viewpoints.
Architects consult engineers.
Engineers consult specialists.
Clients consult advisors.
Researchers compare sources.
Judgement emerges through comparison rather than blind acceptance.
Artificial intelligence simply introduces new participants into that conversation.
This observation became one of the foundations of CTA.
Not because multiple artificial intelligence systems are inherently superior.
But because comparison encourages reflection.
Reflection encourages judgement.
And judgement remains a fundamentally human responsibility.
Throughout the semester, students repeatedly demonstrated this principle.
Some compared multiple platforms.
Others explored different workflows.
Several developed their own methods for evaluating outputs.
Without being instructed to do so, they began creating personal orchestration strategies.
Each approach differed slightly.
Yet all shared a common characteristic.
They relied on multiple perspectives.
The exhibition poster described this process through four interconnected dimensions.
Reflection.
Creativity.
Analysis.
Integration.
Together, they formed what I eventually began describing as a symphony of cognitive orchestration.
The metaphor was intentional.
An orchestra does not succeed because every musician plays the same instrument.
It succeeds because different instruments contribute different strengths.
The value emerges from coordination.
Not uniformity.
Reflection represented the human dimension.
The ability to pause.
Question.
Interpret.
Consider consequences.
Reflection remained essential because artificial intelligence can generate possibilities, but it cannot determine personal meaning.
That responsibility remains human.
Creativity represented exploration.
The willingness to imagine alternatives.
Generate possibilities.
Experiment with unfamiliar directions.
Many students discovered that different AI systems often stimulated different forms of creative thinking.
Some encouraged expansion.
Others encouraged refinement.
Both proved valuable.
Analysis represented understanding.
Patterns.
Relationships.
Systems.
Connections.
This dimension became particularly important when students compared multiple platforms and evaluated different responses.
Analysis transformed information into insight.
Integration represented synthesis.
Perhaps the most difficult of the four dimensions.
And perhaps the most important.
Because understanding rarely emerges from isolated observations.
It emerges when separate observations are connected into a coherent whole.
Integration transforms fragments into meaning.
What fascinated me most was that students naturally began combining these dimensions.
Reflection informed creativity.
Creativity generated possibilities.
Analysis evaluated alternatives.
Integration produced understanding.
The process rarely followed a perfectly linear sequence.
Nor should it.
Human thinking has never been entirely linear.
By the end of the semester, something interesting had happened.
The students were no longer merely using artificial intelligence.
They were orchestrating it.
Selecting tools.
Comparing perspectives.
Evaluating outputs.
Combining strengths.
Rejecting weaknesses.
Constructing workflows.
Making decisions.
The technology remained important.
But the orchestration became more important.
This was perhaps the greatest lesson of all.
Intelligence alone is not enough.
Modern society already possesses abundant intelligence.
Human intelligence.
Machine intelligence.
Collective intelligence.
The challenge is no longer access.
The challenge is orchestration.
How different forms of intelligence can work together meaningfully.
Responsibly.
Productively.
Humanly.
CTA began as a theoretical framework.
A competition proposal.
A thought experiment.
Yet by the end of the semester, it had become something more.
A lived experience.
A classroom reality.
A practical demonstration that understanding often emerges not from a single voice, but from the thoughtful orchestration of many.
And perhaps that is why the future may belong not to those who possess the most intelligence.
But to those who learn how to orchestrate it.
Chapters:
The Seven Movements of Cognitive Orchestration
① Reflection
Seeing human meaning
② Creativity
Imagining new possibilities
③ Analysis
Understanding systems and patterns
④ Integration
Creating coherence from complexity
⑤ Triangulation in Practice
When multiple perspectives meet
⑥ Student Orchestration Workflows
How students actually combined AI systems
⑦ Beyond Theory
When CTA enters reality
INTERLUDE V
Four Voices, One Understanding
This book was never part of the plan.
At least, not initially.
Like many things within the +IDRISfikir ecosystem, it began as a reflection. A simple thought. A passing observation during an ordinary drive home after class.
The semester was approaching its conclusion.
The Artificial Intelligence in the Built Environment Exhibition 2026 was only days away.
Student presentations had been completed.
Posters were being refined.
Websites were being finalized.
The familiar rhythm of academic life was slowly moving toward another ending.
Or so I thought.
As lecturers, we often spend a great deal of time thinking about whether our students have understood what we attempted to teach.
Did the concepts make sense?
Were the assignments effective?
Did the lectures connect?
Did the students leave the classroom with something meaningful?
These questions are not unique to architecture education.
Every educator asks them.
Yet artificial intelligence introduced a new layer of uncertainty.
Unlike many traditional subjects, AI evolves continuously.
A lecture prepared today may require revision next month.
A workflow demonstrated this semester may look completely different next semester.
A platform that dominates headlines today may become irrelevant tomorrow.
Teaching artificial intelligence therefore creates an unusual challenge.
What exactly are we teaching?
Are we teaching software?
Are we teaching prompts?
Are we teaching tools?
Or are we teaching something deeper?
These questions followed me throughout the semester.
And on that particular drive home, somewhere between three traffic lights and the familiar roads leading back to i-City, another question quietly appeared.
Perhaps the students had been teaching me as much as I had been teaching them.
The thought was unexpected.
Yet the more I reflected upon it, the more it seemed true.
When the course began, I imagined that the primary responsibility was to introduce students to artificial intelligence within the context of architecture and the built environment.
By the end of the semester, however, I had witnessed something more interesting.
Students exploring beyond the assignment requirements.
Students comparing multiple AI systems voluntarily.
Students disagreeing with AI recommendations.
Students questioning outputs.
Students developing preferences.
Students becoming curious.
Most importantly, students beginning to exercise judgement.
That observation stayed with me.
Because judgement, unlike software, does not become obsolete after a system update.
Judgement remains valuable regardless of which platform happens to be popular at any particular moment.
And perhaps that realization explains why this Field Journal exists.
This is not a textbook.
It is not a course manual.
It is not a research paper.
Neither is it intended to be a comprehensive guide to artificial intelligence.
Instead, it is a collection of observations from a particular place and time.
A record of what happened when a new generation of architecture students encountered artificial intelligence within the context of design education.
More importantly, it is a record of what happened when an educator attempted to teach a subject that was still evolving while it was being taught.
As this journal is being written, the exhibition has not yet taken place.
The final comments have not yet been collected.
The visitors have not yet shared their reflections.
The field is still speaking.
This means the story remains unfinished.
Perhaps that is exactly how it should be.
After all, architecture is rarely finished.
Education is never finished.
And the conversation surrounding artificial intelligence has only just begun.
So these are merely field notes.
Observations from a classroom.
Reflections from a semester.
Fragments from a larger journey that is still unfolding.
The best pages may not have been written yet.
🎶The Weight of Mercy
(Verse 1)
The screen showed a city of glass and of steel
Efficient and perfect, but what did it feel?
It ignored the alley, the sun, and the rain
It offered a solution, but bypassed the pain
The Council was quiet, the audit was clear
This wasn't an answer, it was just a veneer.
(Chorus)
The machine gave a path, but I saw the divide
With Claire at my back and the Council inside
I refuse the convenience, I reject the cold
Only human mercy can hold what is told
The suggestion was technically sharp and precise
But it lacked the reflection, it lacked the true price.
(Verse 2)
I clicked the 'reject', and the screen turned to gray
A moment of tension, a moment of sway
But architects know when the spirit is gone
When the logic is brittle, and the soul is withdrawn
I sent it back, back to the draft and the fire
To build something better, to reach something higher.
(Bridge)
It’s not about doing what AI can do
It’s about doing what is honest and true
The power is ours, to say 'no' to the ghost
To be the guardians of what matters the most.
(Chorus)
The machine gave a path, but I saw the divide
With Claire at my back and the Council inside
I refuse the convenience, I reject the cold
Only human mercy can hold what is told
The suggestion was technically sharp and precise
But it lacked the reflection, it lacked the true price.
(Outro)
I say no.
And the city...
Starts to wake up.
(Fade)
CODEX VI
The Weight of Judgement
The heart of the book.
The most important lesson of the semester was not about artificial intelligence.
It was about judgement.
Throughout the course, students explored platforms, compared systems, experimented with workflows, and investigated emerging technologies. They learned how artificial intelligence could assist research, communication, visualisation, analysis, and design exploration.
They learned what AI could do.
But gradually, another question emerged.
A more difficult question.
A more important question.
Not:
Can AI do this?
But:
Should I accept this?
That subtle shift may be one of the most important educational transitions of the Cognitive Orchestration era.
Because intelligence alone has never guaranteed wisdom.
And information alone has never guaranteed good judgement.
For centuries, professional education has never been solely about acquiring knowledge.
Architecture students do not study merely to learn how to draw.
Engineers do not study merely to learn calculations.
Doctors do not study merely to understand anatomy.
Lawyers do not study merely to memorise legislation.
Professional education exists because society eventually places trust in its practitioners.
That trust carries responsibility.
And responsibility requires judgement.
Artificial intelligence does not remove that responsibility.
If anything, it increases it.
During many classroom discussions, students would often ask practical questions.
Which platform is better?
Which platform is more accurate?
Which platform is more creative?
Which platform should we use?
These are reasonable questions.
Useful questions.
Necessary questions.
Yet beneath those questions lies another layer that is far more important.
Can a professional rely entirely on an intelligent system?
Should they?
And if something goes wrong, who remains accountable?
The software?
The developer?
The institution?
Or the human who ultimately approved the decision?
These questions become particularly relevant in architecture.
Buildings are not social media posts.
Buildings affect lives.
Buildings consume resources.
Buildings shape communities.
Buildings carry legal responsibilities.
Buildings can fail.
The consequences of poor judgement do not disappear simply because a recommendation originated from an intelligent system.
Responsibility remains.
The signature still belongs to a human being.
The professional obligation still belongs to a human being.
The ethical burden still belongs to a human being.
This is why trust became such an important theme throughout the semester.
Trust is often misunderstood.
Many people assume trust means confidence.
Yet professional trust is something deeper.
Professional trust is confidence that has survived scrutiny.
It is confidence that has been tested.
Verified.
Questioned.
Evaluated.
Artificial intelligence may generate impressive answers.
It may produce convincing explanations.
It may create beautiful visualisations.
Yet trust cannot be outsourced.
Trust must still be earned.
And ultimately, trust must still be exercised by human judgement.
Communication presented a similar challenge.
The rise of intelligent systems has made communication easier than ever before.
Reports can be drafted within seconds.
Presentations can be generated rapidly.
Ideas can be expanded almost instantly.
Language barriers continue to shrink.
Productivity continues to increase.
Yet the ease of communication creates a paradox.
When communication becomes easier, authenticity becomes more valuable.
Readers increasingly ask:
Who wrote this?
Who stands behind these words?
Whose judgement shaped this message?
Whose responsibility accompanies these ideas?
The future of communication may therefore depend less on the ability to generate content and more on the ability to establish trust.
This naturally leads to the question of authorship.
Few subjects generated more discussion among students than authorship.
- What happens when AI contributes to a design proposal?
- What happens when AI assists with writing?
- What happens when AI generates concepts, diagrams, images, or analyses?
- Where does assistance end and authorship begin?
These are not easy questions.
Nor are they new questions.
Throughout history, creators have always worked with tools.
Architects use software.
Writers use editors.
Researchers use databases.
Artists use instruments.
Artificial intelligence introduces a new category of tool.
A tool capable of contributing ideas.
Yet contribution does not automatically equal authorship.
The responsibility for direction, selection, evaluation, and final judgement still remains human.
The tool may assist.
The human still decides.
Responsibility therefore emerges as the central principle.
Perhaps even more important than intelligence itself.
Students often discovered that AI could produce multiple possible answers to the same problem.
Some answers were useful.
Some were partially useful.
Some were flawed.
Some were entirely inappropriate.
The existence of multiple possibilities did not eliminate the need for judgement.
It increased it.
Someone still had to decide.
Someone still had to evaluate.
Someone still had to choose.
That “someone” was never the machine.
It was always the human.
Professional ethics occupies the same space.
Technology changes.
Ethics endures.
Software evolves.
Responsibility remains.
Platforms appear and disappear.
Professional obligations continue.
This is why ethical thinking cannot be treated as an optional component of AI education.
It must sit at the centre.
Not because technology is dangerous.
But because power without judgement has always been dangerous.
Whether the power comes from machines or from humans.
By the latter part of the semester, many students began recognising something important.
Artificial intelligence was not replacing professional judgement.
It was exposing it.
The better the tools became, the more obvious human judgement became.
Two students could receive similar outputs and produce entirely different conclusions.
Two professionals could receive identical information and make entirely different decisions.
The difference was not intelligence.
The difference was judgement.
Experience.
Values.
Responsibility.
Perspective.
This observation brought me back to an earlier reflection.
The Architect Between Two Worlds.
When that reflection was first written, it described the emerging tension between traditional professional practice and increasingly intelligent systems.
At the time, the future still felt uncertain.
Questions outweighed answers.
Possibilities outweighed clarity.
Yet after an entire semester of teaching, observing, and learning alongside students, the conclusion felt clearer.
The architect does not stand between two competing worlds.
The architect stands between two forms of intelligence.
Human intelligence.
And machine intelligence.
The role of the architect is not to choose one over the other.
The role of the architect is to orchestrate both responsibly.
This may ultimately be the defining challenge of the coming decades.
Not creating more intelligence.
Not accessing more information.
Not producing more content.
But developing stronger judgement.
Because intelligence is becoming abundant.
Information is becoming abundant.
Tools are becoming abundant.
Judgement remains rare.
And perhaps it will become even more valuable in the years ahead.
Looking back now, I realise that the course was never really about artificial intelligence.
Artificial intelligence provided the context.
The real subject was something older.
Something deeply human.
The ability to think.
To question.
To evaluate.
To choose.
To take responsibility for those choices.
That responsibility cannot be automated.
It cannot be delegated.
And it cannot be escaped.
Artificial intelligence may generate possibilities.
Professional judgement determines which possibilities deserve to become reality.
Intelligence may be abundant.
Judgement remains rare.
Chapters:
The Seven Weights of Judgement
① Trust
Can the information be trusted?
② Communication
How should it be communicated?
③ Authorship
Who owns the thinking?
④ Responsibility
Who carries the consequences?
⑤ Professional Ethics
What is the right thing to do?
⑥ Human Authority
Who makes the final decision?
⑦ The Architect Between Two Worlds Revisited
How do humans remain human while working beside intelligent systems?
INSERT#B
‘Papa Zola’ and the Architecture of Architecture
From Quiz KBAT to Professional Judgement
Some educational lessons begin with carefully designed teaching strategies.
Others begin with jokes.
This story belongs firmly in the second category.
Throughout the semester, students in the AI in The Built Environment class were exposed to a wide range of materials. Lecture slides. Reference notes. Discussions. Examples. Case studies. Assignments. Presentations. Artificial intelligence platforms. And, of course, repeated encouragement to explore beyond the classroom.
The resources were available.
The opportunities were available.
The support was available.
In many ways, students had spent an entire semester preparing for the final assessment.
Then something predictable happened.
A week before the assessment, artificial intelligence suddenly became everyone’s best friend.
As educators, we have seen variations of this phenomenon for generations. In the past, students searched desperately through textbooks. Later, they searched the internet.
Today, they search AI.
The technology changes. The behaviour remains remarkably consistent. The humorous observation eventually became known as the ‘Papa Zola’ moment. The nickname was never intended to mock students. In fact, it emerged from a place of affection.
Every lecturer understands the pattern.
For several weeks, students move at their own pace. Then suddenly, as deadlines approach, urgency arrives with astonishing speed. Questions begin appearing. Clarifications become essential. Study groups become active.
Artificial intelligence becomes extremely attractive.
And somewhere in the middle of all this activity, a deeper educational question quietly emerges.
- What exactly are we assessing?
- Are we assessing memory?
- Are we assessing information retrieval?
- Or are we assessing something else?
The final assessment for the course was intentionally designed around higher-order thinking. Not because memorisation is unimportant. But because artificial intelligence has fundamentally changed access to information.
Today, answers are abundant.
Information is abundant. Explanations are abundant. What remains scarce is judgement. A student can ask an AI system a question and receive an answer within seconds. The real challenge begins afterwards.
- Is the answer accurate?
- Is it relevant?
- Is it ethical?
- Is it practical?
- Is it appropriate for the specific context?
Those questions cannot be delegated entirely to a machine.
They remain human responsibilities.
This is where the Papa Zola story becomes more than a joke.
Behind the humour lies an important distinction.
Artificial intelligence can generate possibilities. It cannot assume responsibility. Artificial intelligence can provide recommendations. It cannot sign professional documents. Artificial intelligence can suggest solutions. It cannot be held accountable for the consequences. The responsibility remains with the human being.
For future architects, this distinction is particularly important.
Architecture is not merely the production of drawings.
It is the exercise of judgement.
Every design decision carries implications. Safety implications. Social implications. Environmental implications. Economic implications. Human implications. The architect must ultimately decide which path to take. No software can fully carry that responsibility. No algorithm can fully inherit that accountability. No machine can replace professional judgement.
Looking back, the most valuable lesson from the Papa Zola episode was not about artificial intelligence at all.
It was about learning.
Students naturally seek support when confronted with uncertainty.
That is normal.
That is healthy.
The purpose of education is not to prevent students from using tools.
The purpose is to help them use those tools wisely.
In many ways, the ideal outcome is not a student who refuses to use AI.
Neither is it a student who blindly accepts every AI-generated response.
The ideal outcome is something more balanced.
A student who knows when to ask. A student who knows when to question. A student who knows when to disagree. A student who understands that intelligence may be abundant, but judgement remains precious. And perhaps that is the real lesson hidden behind the laughter.
The purpose of education has never been to produce better answers.
Its purpose has always been to develop better thinkers.
Artificial intelligence may change the way answers are generated. It does not change the responsibility of deciding which answers deserve to be trusted. That responsibility remains profoundly, and beautifully, human. Perhaps that is what architecture has been teaching us all along.
INTERLUDE VI
The Answer I Refused
One of the most important moments in education is rarely dramatic.
It does not arrive with applause.
It does not announce itself.
Most of the time, it appears quietly.
Almost unnoticed.
Then only later do we realise its significance.
One such moment occurred during the presentations for Artificial Intelligence in the Built Environment. The students had spent weeks exploring different AI platforms. They had experimented with prompts. Compared outputs. Generated concepts. Tested workflows. Evaluated possibilities. By this stage, artificial intelligence had become a familiar presence within their learning process.
Then something interesting happened.
Several groups began explaining why they had rejected certain AI-generated suggestions.
Not modified.
Not refined.
Rejected.
Completely.
At first glance, this might not seem remarkable. After all, designers reject ideas all the time. Yet within the context of artificial intelligence, the moment carried a deeper meaning. Because the rejection was not driven by technical failure.
The AI had done exactly what it was asked to do.
The responses were coherent. The recommendations were logical. The outputs were often creative. And yet the students chose not to accept them.
Why?
The answers varied.
Some felt the suggestions were unrealistic. Others believed they were inappropriate for the project context. Some felt the recommendations lacked sensitivity to cultural considerations. Others simply felt the ideas did not align with their design intentions.
What mattered was not the specific reason.
What mattered was the act itself.
The students had exercised judgement.
In many public discussions surrounding artificial intelligence, there is often an assumption that the greatest danger lies in machines becoming too intelligent.
Perhaps the greater danger is something else.
Perhaps the greater danger is humans becoming unwilling to think.
Technology has always presented this temptation. Calculators reduced the need for manual arithmetic. Search engines reduced the need to memorise information. Navigation systems reduced the need to read maps.
Artificial intelligence introduces a similar temptation.
The temptation to outsource judgement. The temptation to accept recommendations without reflection. The temptation to confuse efficiency with wisdom.
For future architects, this distinction is particularly important.
Architecture is not a profession built solely upon answers.
It is built upon decisions.
A building may satisfy technical requirements and still fail its community. A proposal may appear efficient and still be ethically problematic. A design may be aesthetically impressive and still be unsuitable for its intended users.
The architect’s responsibility is not simply to generate possibilities.
It is to determine which possibilities deserve to become reality.
This responsibility cannot be delegated completely.
Not to software.
Not to algorithms.
Not to artificial intelligence.
The responsibility remains human.
What encouraged me most during the semester was not the students’ ability to use AI.
It was their willingness to challenge it.
To question it.
To disagree with it.
To refuse it.
There is a subtle but important difference between using a tool and being guided by a tool.
The first preserves agency.
The second risks surrendering it.
Somewhere during those presentations, I realised that the students had crossed an invisible threshold.
Earlier in the semester, many had approached artificial intelligence as a source of answers. By the end of the semester, they were treating it as a source of perspectives. That shift changes everything. A perspective invites reflection. An answer invites acceptance. The distinction may appear small.
In reality, it is enormous.
Looking back, I believe the most important lesson from the course was not learning how to generate content.
Nor was it learning how to write better prompts.
The most important lesson may have been discovering the confidence to say:
“No.”
Not because the machine was wrong. But because human judgement arrived at a different conclusion. In an age where intelligent systems will increasingly surround us, that simple act may become one of the most valuable professional skills of all.
The future will undoubtedly belong to those who can work effectively alongside artificial intelligence.
But it should also belong to those who know when to disagree with it.
And perhaps that is why the answer I refused became more important than all the answers I accepted. Because in that moment, intelligence gave way to judgement. And judgement, ultimately, is where professional responsibility begins.
🎶The Missing Mugshot
(Verse 1)
We mastered the workflow, we mastered the cloud
We made the AI work, we made the team proud
We’re building the future, the cities of light
We’re tweaking the parameters deep in the night
Generative wizards, with scripts in our hand
The smartest young architects in all of the land.
(Chorus)
We orchestrated systems, we mapped out the skies
We saw the great truth in the Council's eyes
We built a new world, made of code and of trust
But forgot to upload the face of the dust!
Oh, the irony! The comedy of man!
We can change the world, but not the upload plan!
(Verse 2)
The video’s stunning, the website is slick
The AI is moving, it’s magic, it’s quick
But click on the profile, the place for the face
And nothing is there, just an empty, blank space
They’re masters of tensors, of logic, of keys
But they can’t find a picture to put on the breeze!
(Bridge)
Papa AI is laughing, he’s shaking his head
"You’ve got the brilliance, but the profile is dead!"
It’s the human detail that we always forget
The funniest problem that we’ve ever met.
(Chorus)
We orchestrated systems, we mapped out the skies
We saw the great truth in the Council's eyes
We built a new world, made of code and of trust
But forgot to upload the face of the dust!
Oh, the irony! The comedy of man!
We can change the world, but not the upload plan!
(Outro)
(Laughter)
No mugshots, just code.
Class dismissed!
(Fade out)
CODEX VII
The Field Speaks Back
The soul of the book.
For most of the semester, the direction of learning appeared straightforward.
A lecturer prepares the course.
Students attend the sessions.
Assignments are completed.
Presentations are delivered.
Assessments are evaluated.
The flow appears familiar.
Predictable.
Almost routine.
Yet meaningful education rarely remains one-directional for very long.
Sooner or later, the field speaks back.
And when it does, the most important lessons often emerge.
Throughout this book, I have shared reflections from the perspective of an educator.
I have written about philosophy.
Pedagogy.
Curiosity.
Cognitive orchestration.
Trust.
Judgement.
The architecture of learning.
These reflections are valuable.
But they are incomplete.
Because no educational experiment should be evaluated solely by its designer.
The people who experience it deserve a voice as well.
This final Codex therefore serves a different purpose.
Not to explain.
Not to persuade.
Not to conclude.
But to listen.
The original intention of these Field Notes was never to create a finished narrative.
The intention was to create a living record.
An evolving reflection.
A conversation.
As students, visitors, fellow lecturers, industry practitioners, and future readers contribute their observations, this chapter will continue growing.
Not as a marketing exercise.
Not as institutional reporting.
But as a genuine record of experience.
Student Voices
Perhaps the most important voices belong to the students themselves.
After all, they inhabited the classroom.
They explored the platforms.
They completed the assignments.
They experienced the uncertainty.
The excitement.
The frustrations.
The discoveries.
Their reflections matter because they reveal dimensions invisible to the lecturer.
Students often notice different things.
Sometimes they notice what worked.
Sometimes they notice what failed.
Sometimes they identify possibilities the lecturer never anticipated.
All of these observations are valuable.
Some may praise the course.
Others may critique it.
Some may argue that certain activities were useful.
Others may suggest improvements.
That diversity of opinion is not a problem.
It is evidence that genuine learning occurred.
Meaningful education rarely produces identical reflections.
Exhibition Voices
The exhibition introduces another layer.
Unlike the classroom, the exhibition exists in public.
Visitors arrive with different backgrounds.
Different experiences.
Different expectations.
Some come from architecture.
Some from engineering.
Some from academia.
Some from industry.
Some may know little about artificial intelligence at all.
Their observations provide an external perspective.
A reality check.
A reminder that educational ideas must eventually connect with a wider world.
Lecturer Reflections
Education is never static.
Every cohort teaches the lecturer something new.
This semester was no exception.
Some activities worked better than expected.
Others revealed weaknesses.
Certain assumptions proved correct.
Others required revision.
The willingness to learn from students may be one of the most important responsibilities of an educator.
Not because students know everything.
But because no educator sees everything.
Industry Observations
The built environment profession is currently navigating a period of extraordinary transformation.
Artificial intelligence continues to evolve rapidly.
Professional expectations continue to shift.
Educational institutions and industry practitioners are learning simultaneously.
In many respects, nobody possesses a complete map.
This makes industry observations particularly valuable.
Not as definitive answers.
But as additional perspectives within a much larger conversation. Research across built environment education increasingly points toward the same conclusion: AI is most valuable when it enhances human judgement rather than replacing it, and future professionals must learn how to question, evaluate, and responsibly use intelligent systems.
Unexpected Lessons
Perhaps the most interesting reflections are the ones nobody planned.
The discoveries hidden between the learning outcomes.
The stories hidden between the assessments.
The moments that never appeared in the syllabus.
The group that explored nine AI systems.
The discussions that continued after class.
The questions that generated more questions.
The presentation that unexpectedly changed the direction of a conversation.
The famous mystery of the missing mugshots.
Yes.
Even that.
Because education is rarely remembered through assessment rubrics alone.
It is remembered through experiences.
Through people.
Through stories.
Looking back now, I realise that the title of this book contains a quiet truth.
What My Students Taught Me About AI.
When the title first appeared, it sounded almost poetic.
Perhaps even slightly provocative.
After all, lecturers are supposed to teach students.
Not the other way around.
Yet the semester revealed something different.
The students taught me that curiosity remains alive.
They taught me that exploration still matters.
They taught me that technology does not automatically diminish humanity.
And they reminded me that learning remains a collaborative act.
Perhaps the greatest lesson was this:
The future of AI education is not about producing experts in software.
Nor is it about producing prompt engineers.
Nor is it about chasing every new platform that appears.
The future of AI education is about helping humans remain thoughtful while living beside increasingly intelligent systems.
That is why this final chapter remains intentionally unfinished.
Because the conversation is unfinished.
The exhibition has not yet concluded.
The feedback has not yet arrived.
The profession itself is still learning.
And the story continues.
So to every student, visitor, lecturer, practitioner, and reader who reaches this page:
The field is open.
The conversation continues.
Your reflections are welcome.
Positive or critical.
Supportive or challenging.
Agreement is not required.
Honesty is.
No filtering.
No sanitisation.
No marketing.
Only honest reflections.
Because this is where:
What My Students Taught Me About AI
finally becomes literal.
And perhaps that is the most fitting way to end a book about intelligence.
Not with an answer.
But with an invitation.
INTERLUDE VII
Why Nobody Submitted Their Mugshot
There are certain mysteries in higher education that no amount of research has been able to explain.
Some involve student attendance.
Some involve assignment submission behaviour.
Some involve the remarkable ability of students to discover deadlines only a few hours before they occur.
This story belongs to that category.
It is the story of the missing mugshots.
For those unfamiliar with the term, a mugshot in this context is simply a profile photograph.
A passport-sized image.
A face.
Nothing complicated.
No artificial intelligence required.
No advanced prompting techniques.
No machine learning.
No neural networks.
Just a photograph.
At the beginning of the semester, students were asked to submit their mugshots.
A simple request.
Or so I believed.
The request was made politely.
The deadline was reasonable.
The purpose was straightforward.
The response was… silence.
Not complete silence.
A few students submitted.
A handful responded.
But many simply continued their lives as though the request had never been made.
Weeks passed.
Reminders were issued.
More reminders followed.
Gentle encouragement became increasingly strategic encouragement.
Still, the mugshots remained elusive.
Meanwhile, something extraordinary was happening elsewhere.
Students were learning artificial intelligence.
They were experimenting with multiple platforms.
They were generating visualisations.
They were creating presentations.
They were designing websites.
They were producing digital content.
Some were comparing three AI systems.
Others explored four.
A few investigated five.
One group famously explored nine.
Nine.
The same students capable of coordinating nine artificial intelligence systems somehow struggled with uploading a single photograph.
This contradiction fascinated me.
On one hand, we were discussing the future of intelligent systems, cognitive orchestration, and professional practice.
On the other hand, we were engaged in a semester-long quest to obtain profile photographs.
It felt strangely symbolic.
Perhaps technology has advanced faster than administration.
Or perhaps students simply possess a unique ability to classify tasks into categories invisible to lecturers.
In that invisible hierarchy, comparing nine AI platforms may somehow appear more urgent than uploading a mugshot.
As the semester progressed, the missing photographs became something of a running joke.
Each reminder generated smiles.
Each update generated laughter.
The mystery evolved into a shared classroom narrative.
Eventually, many of the photographs arrived.
Some appeared just before presentations.
Some appeared shortly before the exhibition.
Some seemed to materialise through means still unknown to modern science.
A few, I suspect, arrived purely because students finally realised the lecturer was not going to forget.
Looking back, however, the story is not really about photographs.
It is about something far more familiar.
Students remain students.
Technology changes.
Software evolves.
Platforms rise and fall.
Artificial intelligence grows more sophisticated.
Yet certain aspects of student life remain wonderfully consistent.
Every generation believes it is unique.
Every generation encounters new technologies.
Every generation faces different challenges.
And somehow, every generation still manages to postpone the simplest administrative task until the very last moment.
There is something strangely comforting about that.
In a semester filled with discussions about artificial intelligence, future practice, emerging technologies, and cognitive transformation, the missing mugshots served as a reminder of something important.
Human beings remain human.
Students remain students.
And perhaps that is exactly as it should be.
The future may arrive faster than we expect.
Artificial intelligence may continue reshaping professions.
Architectural practice may evolve in ways we cannot yet predict.
But somewhere, in classrooms across the world, lecturers will still be waiting for profile photographs.
And students will still be promising to submit them tomorrow.
Some traditions, it seems, are timeless.
🎶The Empty Exhibition Hall
(Verse 1)
The echoes are fading, the boards are all bare
The scent of the ink hangs still in the air
Fifty young architects packed up their dreams
And left behind only the digital streams
The exhibition is quiet, the screens are all dark
But I still feel the heat of the very first spark.
(Chorus)
The posters are taken, the screens fade to black
No tool can bring the human essence back
Intelligence is easy, it’s cheap and it’s fast
But the judgment of architects—that’s what will last
The city is built in the mind and the soul
And we are the keepers, we’re keeping it whole.
(Verse 2)
I walk through the silence, I think of the race
From the first timid prompt to the pride in their face
They started as students, they left as the guides
They’re ready for storms, they’re ready for tides
The Council is sleeping, the persona’s at rest
And we have all passed the ultimate test.
(Bridge)
It was never the AI, it was never the tool
It was never just following the standard of school
It was about the responsibility held in the hand
To protect all the people who live in the land.
(Chorus)
The posters are taken, the screens fade to black
No tool can bring the human essence back
Intelligence is easy, it’s cheap and it’s fast
But the judgment of architects—that’s what will last
The city is built in the mind and the soul
And we are the keepers, we’re keeping it whole.
(Outro)
The judgment...
Remains human.
The responsibility...
Always.
(Absolute silence)
EPILOGUE
Intelligence Is Abundant. Judgement Is Rare
(After June 23, 2026)
The exhibition ends.
The posters come down. The presentation boards are packed away. The QR codes stop receiving new scans. The classroom gradually returns to silence.
Another semester reaches its conclusion.
At least, that is how it appears from the outside.
Education, however, rarely ends when the semester ends. The most important lessons often emerge afterwards. Sometimes weeks later. Sometimes years later. Occasionally, only after students enter professional practice and encounter situations where no textbook provides a complete answer.
This field journal began with a simple question:
How do we teach artificial intelligence in the built environment?
Looking back now, I am no longer certain that was the real question.
The deeper question may have been something else entirely.
How do we remain human while working alongside increasingly intelligent systems?
That question appeared repeatedly throughout the semester. It appeared when students compared multiple AI platforms. It appeared when they discovered different systems offered different perspectives. It appeared when they learned to challenge recommendations rather than accepting them automatically. It appeared when they began recognising the difference between information and judgement. And perhaps most importantly, it appeared when they discovered the confidence to disagree.
Artificial intelligence has transformed access to knowledge.
Questions that once required hours of searching can now be explored within seconds.
Information that once remained hidden behind libraries, databases, and specialist expertise is increasingly available to anyone with curiosity and an internet connection.
This is an extraordinary development.
It should be celebrated.
Yet it also changes the nature of education.
When information becomes abundant, the value of information alone begins to decline.
What becomes valuable instead is interpretation.
Discernment.
Context.
Wisdom.
Judgement.
The ability to decide what matters. The ability to recognise what should be accepted, modified, questioned, or rejected. The ability to carry responsibility for decisions. These remain profoundly human capabilities.
Throughout the semester, students were introduced to artificial intelligence not simply as a tool, but as a participant in a larger conversation.
A source of perspectives.
A generator of possibilities.
A catalyst for reflection.
The objective was never to replace thinking. The objective was to deepen it. Nor was the objective to create dependency. The objective was to cultivate judgement. Because ultimately, architecture has never been about producing answers.
Architecture is about making decisions.
Every design proposal represents a choice. Every building represents a series of judgements. Every professional signature represents accountability.
The tools may evolve.
The responsibility remains.
That responsibility cannot be delegated entirely to software. It cannot be outsourced to algorithms. And it cannot be transferred to artificial intelligence. The future architect will almost certainly work alongside increasingly capable intelligent systems. The future engineer will. The future planner will. The future policymaker will. The future educator will.
The question is no longer whether artificial intelligence will become part of professional life.
It already has.
The question is what kind of humans we become while working beside it.
Perhaps that is the real lesson of Artificial Intelligence in The Built Environment.
Not how to prompt.
Not how to automate.
Not how to generate.
But how to think.
How to reflect.
How to question.
How to remain responsible.
And how to remain human.
As this field journal closes, I find myself returning to the students who made this journey possible.
The students who explored beyond what was required. The students who compared multiple systems. The students who challenged assumptions. The students who accepted some recommendations and rejected others. The students who unknowingly taught their lecturer as much as he taught them.
For that, I remain grateful.
This exhibition may conclude.
The course may pause.
The posters may disappear.
But the conversation continues.
It continues in future studios.
It continues in future projects.
It continues in future classrooms.
And perhaps, most importantly, it continues in the minds of those who will eventually shape the cities, buildings, communities, and environments of tomorrow.
If there is one hope I carry forward from this experience, it is a simple one.
That future professionals will not merely become more intelligent.
They will become more thoughtful.
More reflective.
More responsible.
More humane.
Because in the age of artificial intelligence, intelligence is no longer the scarce resource.
Judgement is.
And in the end, judgement may be the quality that determines whether intelligent systems serve humanity… or whether humanity simply learns to serve its systems. The purpose of AI education, therefore, is not to produce better users of artificial intelligence. It is to produce better humans working beside it.
INSERT#C
The Chronicles of Papa AI
A Humorous Reflection on Truth, Judgement, and the Human Condition
Every generation develops its own educational legends.
Some are famous scholars. Some are great architects. Some are visionary educators. And occasionally, entirely by accident, a superhero appears.
Readers may notice references to “Papa Zola” throughout earlier conversations and classroom anecdotes. The nickname originally emerged as a light-hearted joke among students and lecturers. Over time, however, the character evolved into something broader and more meaningful.
In these pages, Papa Zola gradually becomes Papa AI, a symbolic figure representing judgement, responsibility, and the human role in an age of artificial intelligence.
In the case of AI in The Built Environment class, that superhero was Papa AI.
His origins remain unclear.
His powers remain questionable.
His fashion choices remain difficult to explain.
Yet somehow, over the course of a semester, Papa Zola evolved from a passing joke into a surprisingly useful educational metaphor.
This insert records several observations attributed to the legendary guardian of judgement, responsibility, and unfinished student submissions.
The reader is advised to approach these teachings with a sense of humour.
And perhaps a small amount of self-reflection.
Chronicle I: Intelligence Is Easy. Judgement Is Hard.
Artificial intelligence can generate answers.
Artificial intelligence can generate images.
Artificial intelligence can generate presentations.
Artificial intelligence can generate essays.
Artificial intelligence can generate videos.
Artificial intelligence can even generate explanations about why it generated the things it generated.
What it cannot generate is responsibility.
That burden remains stubbornly human.
According to Papa AI:
“The problem is not that machines are becoming intelligent.
The problem is that humans sometimes stop thinking.”
This statement, while delivered with questionable dramatic flair, contains a degree of truth.
The value of education is not producing answers.
The value of education is developing judgement.
Chronicle II: The First Answer Is Not Always The Best Answer
Students frequently discover a remarkable phenomenon.
The first AI response often appears convincing.
The second response appears convincing.
The third response also appears convincing.
Unfortunately, they are sometimes completely different from one another.
This creates confusion.
Papa AI calls this:
“The Great Festival of Confident Answers.”
The lesson is simple.
Confidence is not evidence.
Fluency is not accuracy.
And beautifully formatted text is not automatically wisdom.
A professional must learn to evaluate.
To compare.
To verify.
And occasionally to say:
“No.”
Chronicle III: Upload Your Mugshot
Among the most mysterious teachings of Papa AI is this seemingly simple instruction:
“Upload your mugshot.”
Historians continue debating its deeper meaning.
Some interpret it literally.
Others regard it as symbolic.
A few suspect it is merely administrative desperation disguised as philosophy.
Regardless of interpretation, the lesson remains timeless.
Human civilisation may eventually create intelligent cities.
Autonomous vehicles.
Advanced robotics.
Cognitive orchestration systems.
Yet somehow, somewhere, a student will still forget to upload a profile photograph.
The mystery endures.
Chronicle IV: The Assignment Begins Before The Deadline
According to ancient student tradition, all assignments begin approximately three days before submission.
Some particularly ambitious students begin two days before submission.
Papa AI rejects this doctrine entirely.
He teaches instead:
“The assignment begins the day you receive it.”
This teaching remains controversial.
Its adoption rate remains extremely low.
Nevertheless, the wisdom stands.
Chronicle V: AI Is Not Authorship
One of Papa AI’s most frequently repeated teachings concerns responsibility.
Artificial intelligence may contribute ideas.
It may suggest possibilities.
It may generate alternatives.
It may even produce surprisingly impressive first drafts.
Yet authorship remains human.
Responsibility remains human.
Accountability remains human.
When success arrives, humans claim ownership.
When mistakes occur, humans remain accountable.
No AI system has yet volunteered to attend a disciplinary hearing.
Chronicle VI: The Purpose Of Education
As the semester drew to a close, students naturally focused on grades.
This is understandable.
Grades matter.
Assessments matter.
Qualifications matter.
Yet Papa AI reminds us that education serves a larger purpose.
The objective is not merely passing examinations.
The objective is becoming the kind of person capable of carrying responsibility.
A future architect.
A future engineer.
A future planner.
A future leader.
Or simply a thoughtful human being.
Knowledge can be acquired.
Wisdom requires practice.
Chronicle VII:Final Revelation
The most important teaching attributed to Papa AI emerged near the end of the semester.
After the presentations.
After the discussions.
After the comparisons of multiple AI systems.
After the debates about judgement and responsibility.
The teaching was surprisingly simple.
“Artificial intelligence can help you answer questions.
Education exists to help you ask better ones.”
Perhaps that is why the story of Papa AI survived long after the joke itself should have faded.
Because hidden beneath the humour was a reminder.
Technology changes.
Platforms change.
Interfaces change.
The future changes.
But the responsibility of thinking remains.
And somewhere, watching over classrooms, assignments, and missing mugshots, Papa AI continues his eternal mission.
Demi kebenaran.
And please upload your mugshot.
APPENDIX A
Timeline of Thoughts
February – June 2026
The intellectual genealogy of the course.
Blog
↓
Framework
↓
Competition
↓
Classroom
↓
Assignment
↓
Exhibition
↓
Field Notes
APPENDIX B
Exhibition Voices Archive
Selected comments from:
- Students
- Visitors
- Lecturers
- Industry Practitioners
A snapshot of what people genuinely thought about AI in architecture education in 2026.
Leave a Reply