Level 4: AI and Building

A black prism refracting a red laser beam into a precise output: transformation from raw input to structured, directed result. — A language model does exactly this. Raw text enters, the model transforms it through learned patterns, and a structured, directed result emerges. The precision comes from training. The direction comes from you.

Level 4 of 4

This is where everything connects

Level 4 is the destination. Infrastructure from Level 3 hosts your AI. Git from Level 2 manages your code. Terminals from Level 1 deploy it. Hardware from Level 0 runs it. This level does not introduce a new domain: it shows you how all four previous domains combine into production AI systems, and how to use AI tools to build software whether or not you know how to code.

Two articles. Each one is dense. The material here changes how you think about AI, not as a magic service or an existential threat, but as a specific technical system with known properties, known limits, and known patterns for building on top of it.

What you know after Level 4

ML fundamentals

Training Inference Parameters Tokens What machine learning actually does: optimise a function on data until predictions become accurate

Language models

Transformers Attention Context window Temperature How LLMs predict the next token, what the context window limits, and why temperature affects output randomness

Prompt engineering

System prompts Few-shot examples Chain of thought How to direct model behaviour through input structure rather than model retraining

Production AI stack

RAG pipelines Vector databases Evals Observability The infrastructure that turns an LLM API call into a reliable, auditable, production feature

Vibe coding

Cursor / Claude Code Directing AI tools Prompt patterns Building software by describing intent; the Levels 0-3 vocabulary makes AI direction precise and effective

Learning path

Start here ML fundamentals Training, inference, parameters, and loss functions. What the model is and how it got its capabilities.

→

Layer 2 Language models Transformers, attention, context windows. Why LLMs can write code but cannot count letters reliably.

→

Layer 3 Prompt engineering System prompts, few-shot examples, and chain of thought. How to direct model behaviour without touching weights.

→

Layer 4 Production AI systems RAG, evals, observability, and the infrastructure that makes an AI feature reliable enough to ship.

→

Build Your first AI product Vibe coding tools, architectural direction, and the vocabulary to brief an AI coding assistant precisely.

Before and after

	Before Level 4	After Level 4
AI	Magic / hype / opaque API	A statistical model trained on text; inference is prediction; hallucination is confident wrong prediction
LLM limitations	“AI sometimes makes things up”	Context window limits what the model can see; temperature controls randomness; retrieval fixes knowledge gaps
Prompts	Copy from Reddit, hope for the best	System prompts set behaviour; few-shot examples calibrate format; explicit constraints reduce hallucination
RAG	A three-letter acronym in architecture docs	Retrieval-Augmented Generation: retrieve relevant documents at query time and inject them into the model’s context
AI product cost	A monthly bill that grows mysteriously	Token cost per request times volume; context length and model size are the two main levers
Vibe coding	AI writes code for you, sometimes works	Directed iteration: you own the architecture; AI implements; Levels 0-3 vocabulary makes direction precise

Articles in this level

What is AI?

Machine learning, neural networks, and language models explained without mathematics. Covers supervised learning, the training process, what parameters are, how transformer architecture enables language understanding, and why GPUs are the limiting resource in AI development. Includes an honest account of what language models cannot do and why.

You should read this if: You use AI tools daily but could not explain to a stakeholder why an AI system made a specific decision, or you need to evaluate an AI vendor’s claims against what the technology actually does.

What is Vibe Coding?

Building software by describing intent and letting AI write the code. Covers the current landscape of vibe coding tools (Cursor, Claude Code, v0, Bolt), the mental model shift from writing code to directing a system, and the patterns that separate effective vibe coders from frustrated ones. Explains why Levels 0-3 vocabulary makes AI direction precise and effective.

You should read this if: You want to build a prototype, an internal tool, or a product MVP without hiring a full development team, and you want to understand how to do it reliably rather than getting stuck on the first error message.

Why this matters in practice

AI is infrastructure, not magic: A language model is an HTTP API. It takes a JSON body with a prompt and returns a JSON body with a completion. It runs on GPU servers in a cloud region. It has rate limits, token costs, and latency characteristics. Treating it as infrastructure, rather than magic, is what separates products that scale from prototypes that do not.

Hallucination is a design problem: LLMs predict plausible next tokens based on training data. When the training data does not cover a topic accurately, the model generates plausible-sounding text that is factually wrong. This is not a bug to report to the vendor. It is a known property to design around: retrieval, grounding, and evals are the design solutions. Level 4 covers all three.

The vocabulary gap costs money: When a product team cannot evaluate AI vendor claims, they sign contracts for capabilities the model does not reliably have. When a product team cannot write a precise system prompt, they get inconsistent outputs they cannot debug. The concepts in Level 4 close that gap.

Vibe coding scales further than you expect: The constraint on vibe coding is not the AI. It is the quality of architectural direction. A person who understands what a database schema is, what an API endpoint does, and how a server handles requests can direct an AI coding tool to build a production-quality feature. That same person without Levels 0-3 will build a fragile prototype and not know why it fails.

The workshop connection

The three-workshop method used at ai-workshops.online maps directly to the concepts in this level.

Workshop 1 (Discovery) is use case prioritisation: which AI capabilities map to which business problems, and which are technically feasible with current models. That evaluation requires understanding what language models can and cannot do reliably, covered in “What is AI?”

Workshop 2 (Concept) is architecture: where does the model fit in the system, what data sources feed it, how does retrieval work, and where do evals run. Reading that architecture requires Level 3 vocabulary. Designing it requires Level 4 knowledge of production AI patterns.

Workshop 3 (Prototype) is building: a working demo using the vibe coding approach, with real infrastructure behind it. The prototype is built using the techniques in “What is Vibe Coding?” and deployed on the infrastructure from Level 3.

The wiki is the theory. The workshops are the practice. Level 4 is where both converge.

What comes next

You have completed the foundations curriculum. The next step is depth.

Production AI

Building RAG Systems LLMOps Step-by-step guides to production AI implementation

Infrastructure

From Zero to Production Capacity Planning for AI How to deploy and scale what you build

Glossary

Transformer Architecture Attention Mechanism Foundation Models Precise definitions for the technical vocabulary of AI systems

Deep dives:

Building RAG Systems : document ingestion, chunking, embeddings, and retrieval in production
LLMOps : the operational discipline of running language models reliably at scale
From Zero to Production : the full path from prototype to deployed product