TALAMANA · THE AI LITERACY MAP FOR ARCHITECTURE AND DESIGN · The Brief · AGE 18—20 · POSITIONAL · METHOD
Generate the brief, then red-pen it
Generation is a first draft of thinking, and editing is where authorship lives.
When to use
When the client has given you three lines and a phone number, and you need a complete brief to design against. In practice this is more common than the long messy brief.
The method
Write down exactly what the client said: two or three lines, no more. Ask a reasoning model to draft a full brief from it — intent, user groups, spatial priorities, mood, constraints, success criteria, open questions. Add one instruction and never skip it: distinguish what the client stated from what you are inferring; do not invent budget, deadline or site facts. Then take a red pen to the draft. Mark every line as stated, inferred-and-useful, or invented. Strike the invented. Question the inferred. What survives is a brief you can take back to the client.
Watch for this
Letting the generated brief stand because it reads well. It will read well. It will also have invented a budget, a plot size and a completion date from nothing, in the same confident tone as the parts that are true.
The Lab's note
We teach generation and decoding as a pair, and we insist on the red pen. Generation is a first draft of thinking. Editing is where authorship lives. Others treat the generated brief as a time-saver to be used as is; we think that is exactly where the invented budget enters the project.
Try it
Generate a full brief from three lines of client context. Red-pen it. Count the inventions. Then sort the inferences into two piles: useful provocations that raised a question you should ask, and traps that would have quietly become facts.
Prove it
Show a red-penned generated brief with the provenance of every line marked, and name which inferences were worth keeping as questions.
How it works
A model asked to complete a brief from thin context completes it the way it completes everything: with the most probable content. Probable budgets, probable plot sizes, probable deadlines. None of them are facts about your client. The "distinguish stated from inferred" instruction makes the model label where each line came from. That is the cheapest defence against invented facts, and it is only a request: a written instruction asks; the red pen is the control that enforces it.
What this idea builds on
What this idea opens up
- Nothing yet names this as a foundation.
Sources
Open this idea on the map · The complete map · Logika · RBDS AI Lab, India · revised every edition.