AI, ML, Deep Learning, Gen AI: The Russian Doll Explanation Every Business Owner Needs
Most people use AI to mean everything from a thermostat to ChatGPT. They are not the same thing. Here is the four-layer hierarchy explained once, clearly, using one example you already understand.
Kasun WijayamannaFounder & Lead DeveloperPostgraduate Researcher (AI & RAG), Curtin University - Western Australia
Pick up any tech publication, sit through any vendor demo, or listen to most boardroom conversations about technology right now and you will hear AI, machine learning, deep learning and generative AI used interchangeably. Sometimes in the same sentence. Often to mean completely different things.
They are not the same thing. The differences matter. If you do not know which layer you are actually dealing with, you cannot make good decisions about what to build, what to buy, or what to trust.
Here is the clearest explanation: one analogy, one example, all four layers.
The nesting doll model
Picture a set of Russian nesting dolls. Four of them, each one sitting inside the next.
The outermost doll is the largest and most general. Each inner doll is smaller and more specific. Every inner doll is also its outer doll, but the outer doll is not always the inner one. A golden retriever is a dog, but not every dog is a golden retriever.
That is the relationship between these four terms.
Artificial Intelligence is the outermost doll. Machine Learning sits inside it. Deep Learning sits inside Machine Learning. Generative AI sits inside Deep Learning. Each layer inherits everything from the one around it, and adds something specific.
The AI hierarchy as nested layers — every inner layer is a specialised form of its outer layer
AI — the outer doll
Artificial Intelligence is the broadest term. It covers any technique that makes a computer behave in a way that looks intelligent. That definition is wider than most people realise.
A chess program from 1997 that evaluates millions of possible moves and selects the best one. A spam filter that blocks emails containing the phrase "click here to claim your prize." A thermostat that switches the heating on at 6am. All of these are AI in the original and technically correct sense.
This kind of AI — rule-based AI — works by following instructions a human wrote. If X, do Y. It does not learn. It does not adapt. It follows the script exactly until someone changes the script.
The example: A rule-based AI for your customer email inbox says: if the subject line contains "invoice," route it to accounts. It works reliably until a client emails with the subject "Quick question about the project" and mentions an invoice three paragraphs in. The rule never sees it. Rule-based AI does exactly what it was told. Not a word more.
ML — the second doll
Machine Learning is the first layer where things change fundamentally.
Instead of a human writing rules, you feed an ML algorithm thousands of examples of correctly handled decisions from the past. The algorithm finds the patterns itself. It might notice that emails arriving on Monday mornings, from domains ending in .com.au, containing phrases like "still waiting" or "following up again," tend to need urgent attention. Nobody told it that. It found it by analysing the data.
The critical difference: ML does not follow rules a human wrote. It discovers rules from data and applies them to new situations.
The example: An ML system trained on ten thousand past customer emails learns to sort new ones with much higher accuracy than any rule-based system. It does not know why a particular email is urgent — it recognised a pattern. It applies that pattern going forward, and it gets better as more examples come through.
This is why your Gmail spam filter improves over time. Why Spotify recommendations get sharper the more you listen. The model is not following a script — it is learning from behaviour.
ML needs good data to work. Without enough historical examples, the model cannot learn meaningful patterns. The quality of the output is constrained by the quality and volume of the input.
Deep Learning — the third doll
Deep Learning is a specific type of Machine Learning. The distinction lies in the architecture.
Standard ML algorithms work well on structured data: numbers, categories, dates, keywords. They struggle when the data is messier. Images. Speech. A handwritten note. A customer email written in casual language with a typo, a sarcastic tone, and no clear subject line.
Deep Learning uses neural networks — layers of interconnected nodes loosely modelled on how the human brain processes information. Each layer picks up on slightly more abstract features than the layer before it. In image recognition, the first layer might detect edges, the second shapes, the third textures, the fourth objects. By the time you get to the top layer, the model has understood the image in a way that earlier ML methods could not come close to.
The example: A Deep Learning model reads an email that says: "I have been waiting THREE WEEKS and I am absolutely done." It does not need the word "urgent" in the subject. It does not need a specific phrase it was trained to flag. It understands the sentiment, the frustration level, and the likely intent. It routes this email to the most senior available agent with a priority flag. A standard ML model on structured data would probably miss this entirely.
Deep Learning is what made modern voice assistants work. It is what powers face recognition in your phone. It is what allowed AI to finally handle genuinely complex, unstructured inputs at scale.
The tradeoff: Deep Learning requires significantly more data and more computing power than standard ML. A small dataset will not produce a useful Deep Learning model. This is why it remained largely an academic pursuit until the 2010s, when both data volumes and processing power crossed a threshold that made it practical.
Gen AI — the innermost doll
Generative AI is the newest layer and the one generating the most attention. It sits inside Deep Learning. All Gen AI is Deep Learning, but most Deep Learning is not Gen AI.
The distinction is this: everything in the three outer layers takes an input and classifies, predicts, or routes. Generative AI takes an input and creates something new.
Large Language Models, image generators, code synthesisers — these models are trained on datasets so large they are difficult to comprehend. A modern LLM has processed more text than any human could read across multiple lifetimes. That training gives it the ability to generate coherent, contextually appropriate new content rather than just categorising what already exists.
The example: The same frustrated customer email the Deep Learning model flagged as urgent now goes to a Gen AI layer. It reads the email, pulls in the relevant account history from your CRM, and drafts a response. Not a template with fields filled in. A genuinely written reply that acknowledges the specific delay, references what went wrong, and offers a concrete resolution. The agent reviews it, adjusts a line, and sends it in under a minute.
That is a fundamentally different capability from anything in the three outer layers. Classification and prediction are useful. Creation is something new.
The same example through all four
Run the customer email scenario through all four layers to see the progression clearly:
Rule-based AI: If subject contains "invoice," send to accounts. Misses anything that does not match the exact rule.
Machine Learning: Trained on thousands of past emails, learns to sort by urgency, topic and likely intent. Gets better over time. Still struggles with unusual phrasing or emotional subtext.
Deep Learning: Reads the full email in context. Understands sentiment, tone, frustration level. Routes correctly even when the language is ambiguous, casual or emotionally charged.
Generative AI: Reads the email, accesses relevant context, and drafts a personalised, appropriate response. Does not just classify the problem — helps resolve it.
Each layer handles what the previous one could not. Each one requires more data, more compute, and more care to deploy well.
Why the distinction matters
When someone pitches you an AI solution, the first useful question is: which layer are you actually talking about?
Rule-based systems are cheap and quick to build. They are also brittle. One small change in how your customers behave and the rules break — often silently.
ML models need historical data. Without enough examples from the past, the model cannot learn anything useful. If your business is small or your data is messy, this changes what is realistic.
Deep Learning systems need significantly more data, more compute and more specialised expertise. The upside is genuine capability with complex, unstructured inputs. The downside is cost and the data requirements to train well.
Gen AI changes how you think about outputs. The output is not a prediction or a classification. It is content. That changes how you validate it, how much human review it needs, and what happens when it is wrong.
The businesses being sold "AI automation" for $79 a month are usually getting rule-based automation with a better product name. Sometimes that is exactly right for the problem. Sometimes it is not. Knowing the difference lets you ask better questions before signing anything.
One question to ask
Any time someone shows you an AI feature, a product demo, or a capability claim, ask this:
Is this system following rules someone wrote, learning patterns from data, or generating something new?
That one question cuts through most of the noise. Rules break quietly when conditions change. Patterns drift when the data changes. Generated content can be confidently wrong without flagging itself as wrong.
Knowing which layer you are looking at changes how you evaluate it, how you integrate it, and how much you trust it. That is the most practically useful thing you can take from the Russian doll model.
Not every problem needs the innermost doll. A rule that routes invoices to accounts correctly every time is a perfectly fine solution to that problem. The businesses that get into trouble are the ones who reach for Gen AI when a rule would have done, or who trust a rule-based system to handle something that actually requires judgment.
Match the layer to the problem. That is where it starts.
Kasun WijayamannaFounder & Lead DeveloperPostgraduate Researcher (AI & RAG), Curtin University - Western Australia