TALAMANA · THE AI LITERACY MAP FOR ARCHITECTURE AND DESIGN · Studio Practice · AGE 20—22 · POSITIONAL · HELD
Judgment is the job
AI multiplies options faster than a designer can inspect them, so judgment is the job.
Our position
AI multiplies options faster than any designer can inspect them. That makes judgment the bottleneck: deciding what matters, which evidence deserves trust, what gets rejected, what gets developed, and who carries the consequences. That decision chain — not the volume of generated material — is where a designer's authorship lives.
> This is not a consolation prize. It is the job.
Why we hold it
Every earlier tool shift in this profession — drafting to CAD, CAD to BIM — moved production and kept responsibility exactly where it was. Nothing in the current shift moves the signature. Someone still decides, and someone still answers for the decision.
The strongest objection
Judgment in architecture does not belong to one designer. It is distributed: the client decides the budget and the brief, the structural engineer decides what stands, the services consultant what breathes, the contractor what can be built on Tuesday, the regulator what is permitted, the community what is tolerated, the code what is lawful, and the users decide, years later, what the building was. Some decisions are not yours to make. Some are negotiated. Some are statutory. So if authorship lives in "the decision chain", whose chain is it? The card risks replacing the fear of the machine with the old heroic-author picture of architecture, in which one person decided everything, when the honest description was always a chain with many hands on it. And a second objection follows: as models improve, some links in that chain may be automated, and "judgment" shrinks to whatever machines cannot yet do — a retreating territory, not a standing one.
What would make us revise it
If the chain is the right picture, then our position should say which links are the architect's, not claim the chain. We revise the card the day we can no longer name, on a real project, the decisions that were the architect's to make and answer for. We revise it further if clients, juries and regulators come to accept a machine's justification as accountability — a system that can not only make the call but answer for it when it goes wrong. The day responsibility transfers, this card changes. We review it every edition.
Prove it
Write your own working contract with these tools. Then show one full project where every AI contribution passed through a judgment you can state.
Take it to crit
What did you decide that AI could not have decided for you — and where is the proof in the work?
What this idea builds on
- Fifty images is gambling
- An image is not a proposal
- Who is the author
- AI across the project arc
- When not to generate at all
- One full thread, judgment throughout
- People stand behind the machine
- AI and the profession's future
- Convenience is a debt
- Deskilling is a design decision
- Consent, community and the generated monument
- Checkpoints in automation
- Using AI does not lower the standard
- Offloading and atrophy
What this idea opens up
Sources
- judgment is the job — capstone position (Beyond Automation lineage)
- The Architect as Systems Thinker — the-architect-as-systems-thinker
- Systematic review: GenAI's impact on higher-order cognitive skills
Open this idea on the map · The complete map · Logika · RBDS AI Lab, India · revised every edition.