TALAMANA · THE AI LITERACY MAP FOR ARCHITECTURE AND DESIGN · Studio Practice · AGE 19—21 · POSITIONAL · METHOD
Checkpoints in automation
A named person approves every crossing, because a reminder is not a gate.
When to use
When designing any workflow that ends in something leaving the studio or becoming irreversible: an issue, a submission, a payment, a published image, a deleted set.
The method
Trace the workflow from first input to last output. Mark every point where the work crosses to the outside or cannot be undone. At each mark, a named, authorised person approves the step and the approval is recorded — a person, not "the team", and not the agent. Where the law or the contract requires an actual signature, it is a signature; elsewhere it is a recorded approval, and the word "signs" on this card is shorthand for that. Make the gate structural: the workflow cannot proceed past it without the sign-off, rather than a reminder someone can dismiss. Record who signed and when. Then count the gates. Too few and errors escape; too many and people start signing without reading, which is worse than no gate because it looks like one.
Watch for this
A gate a rushed person can skip. On the night before a submission, a reminder is not a gate. Only a step that will not run is a gate.
The Lab's note
A named person at every crossing is the Lab's rule. Other studios gate by role, by committee, or by a logged acknowledgement, and some gates genuinely need a review rather than a signature. We name a person because a name is what turns a reminder into a gate: "whoever is there" is the hole on every workflow map we have seen.
Try it
Pick one workflow in your studio that ends outside it. Draw it. Mark the crossings. For each mark, write the name of who signs. If you wrote "whoever is there", you have found the hole.
Prove it
Show one workflow in which the gate is structural — the work genuinely cannot proceed without a named person's sign-off — and say what the agent does up to that point.
How it works
In India the Architects Act, 1972 governs who may call themselves an architect, and the Council of Architecture's Professional Conduct Regulations set the duties of a registered architect; which drawings a local authority accepts, and under whose signature, is set by that authority's own rules. Where a submission carries a registered professional's signature, the liability attached to it does not move because a machine drew the lines or an agent assembled the set. That reading of what automation leaves untouched is the Lab's; the standard-of-care card on this ring carries the framework itself. The signature is where responsibility has long lived; automation changes what happens before it, not what it means. Builders of agent systems say the same from their side: put a human checkpoint before consequential actions. The studio version is older than the technology: a checking signature on every sheet that leaves. The production card on this map, verify loops in production, builds the machinery around the gate; this card fixes where the gate must be.
What this idea builds on
What this idea opens up
Sources
Open this idea on the map · The complete map · Logika · RBDS AI Lab, India · revised every edition.