June 30, 2026 · 8 min read
The Blank Slate Fallacy: Why AI Needs Architecture Before Code
AI is a brilliant junior dev and a terrible architect. Define your schema, auth, and RLS first — or watch it build you a skyscraper with no blueprints.
By Launched team
The pitch is intoxicating: type a sentence, get an app. So you type a sentence and get an app. It even works, sort of. Three weeks later you're trying to add user roles and the agent is rewriting your entire database for the fourth time, because nobody — human or model — ever decided what a "user" was in this system.
AI is a brilliant junior. Juniors don't architect.
Give a junior developer a clear ticket and they'll ship it beautifully. Give them a blank slate and ask them to "build a SaaS" and you'll get five microservices, a graph database, and a circular dependency. AI agents behave identically. The constraint isn't intelligence; it's the absence of decisions.
The decisions AI cannot make for you
- Who are the actors? (User, admin, org owner, guest?)
- What is the ownership model? (Per-user, per-org, per-project?)
- What are the core entities and how do they relate?
- What's public, what's authenticated, what's role-gated?
- What's the RLS policy for every table, written in plain English, before any SQL?
Skip these and the agent will pick for you — differently every session.
The 30-minute architecture pass
1. Write the entities on one page
User, Organization, Project, Document, Comment. One noun per line. Draw arrows for relationships.
2. Write the access rules in English
"A user can read documents in any organization they belong to. A user can write only documents they own. Org admins can write any document in their org." Three sentences. This is your RLS spec.
3. Sketch the auth flow
Email + password? OAuth? Magic link? Org invites? Decide now. Auth is the single area where AI agents flail the hardest.
4. Pick the stack and lock it
React meta-framework, Postgres host, auth provider, deploy target. Tell the agent. Make it boring.
What changes when you do this
The agent stops oscillating. Migrations stop fighting each other. Features stop quietly redefining what a user is. You ship in a third of the time because every prompt has a frame.
Where Launched comes in
The 30-minute architecture pass is the single highest-leverage hour in any AI-assisted project. We do it with founders on the first call, then either hand back a spec the agent can follow or build it ourselves. Book a 20-minute call. Related: Own your build.