Artificial Intelligence: The Complete Engineering Guide
What AI really is, how neural networks and large language models work under the hood, every major type of AI and what it's used for, how to use AI tools effectively, how to write AI code in Python and JavaScript, and how to run models on your own hardware — with live, in-browser tools to train a neural network, size a GPU for local LLMs and build better prompts.
How to read this guide. AI moves fast: specific model names, prices and limits change every few months, so this page teaches the durable fundamentals and uses placeholders (like MODEL_NAME) in code. Always check a provider's current documentation before building. Never paste passwords, API keys, personal or client data into a public AI tool.
Artificial Intelligence (AI) is the field of computer science that builds systems able to perform tasks that normally need human intelligence: recognizing images and speech, understanding and generating language, making decisions, planning and learning from experience.
Classic software follows rules a programmer writes by hand. Modern AI flips that around: you show the system thousands or billions of examples, and a training algorithm learns the rules itself, storing them as millions to billions of numbers called parameters (or weights).

- Every major type of AI — by capability, by function, and by learning method
- How neural networks, Transformers, LLMs and diffusion models actually work
- What AI is used for across industries — and in your own DIY & home projects
- How to prompt AI tools well, and how to verify what they say
- Real, runnable code: scikit-learn, PyTorch, LLM APIs, RAG, local models
- How to run AI locally and size the GPU you need
- Risks, ethics, security and regulation (EU AI Act)
New to AI? Read the tabs in order. Already technical? Jump straight to AI Code, Run AI Locally or the Neural Net Lab.
- 1950 Alan Turing asks "Can machines think?" and proposes the Turing Test.
- 1956 The Dartmouth workshop coins the term "Artificial Intelligence".
- 1958 Frank Rosenblatt's Perceptron — the first trainable artificial neuron.
- 1966 ELIZA, the first chatbot, imitates a therapist with pattern matching.
- 1970s–80s "AI winters": funding collapses when promises outrun hardware.
- 1986 Backpropagation popularized — multi-layer networks become trainable.
- 1997 IBM Deep Blue defeats world chess champion Garry Kasparov.
- 2012 AlexNet wins ImageNet on GPUs — the deep-learning era begins.
- 2014 Generative Adversarial Networks (GANs) generate realistic images.
- 2016 DeepMind's AlphaGo beats Go champion Lee Sedol.
- 2017 "Attention Is All You Need" introduces the Transformer.
- 2020 AlphaFold 2 largely solves protein structure prediction.
- 2022 Text-to-image diffusion goes mainstream; ChatGPT launches.
- 2024 Nobel Prizes in Physics & Chemistry honor neural-network and AI protein work.
- 2025+ Multimodal models, reasoning models and AI agents that use tools.
"Type of AI" can mean three different things: how capable it is, how it functions (memory and awareness), or how it learns. Engineers mostly care about the third; the first two are the ones you'll see in news and debates.
| Type | What it means | Examples | Status |
|---|---|---|---|
| Narrow AI (ANI) | Excellent at one task or a bounded family of tasks; can't transfer that skill freely | Spam filters, face unlock, recommendation engines, chess engines, today's chatbots | Exists today |
| General AI (AGI) | Human-level ability across virtually any intellectual task, learning new ones on its own | A research goal — definitions and timelines are actively debated | Debated |
| Superintelligence (ASI) | Hypothetical AI far exceeding the best humans in every domain | Discussed in AI safety research and policy | Hypothetical |
| Paradigm | Training data | Typical tasks | Common algorithms |
|---|---|---|---|
| Supervised learning | Labeled pairs (input → correct answer) | Classification, regression, price prediction, defect detection | Linear/logistic regression, decision trees, random forest, gradient boosting, neural nets |
| Unsupervised learning | Unlabeled data | Clustering customers, anomaly detection, compression | k-means, DBSCAN, PCA, autoencoders |
| Self-supervised learning | Raw data where the label comes from the data itself (e.g. the next word) | Pre-training LLMs and vision foundation models | Next-token prediction, masked modeling, contrastive learning |
| Reinforcement learning | Rewards from interacting with an environment | Games, robotics, control systems, aligning chatbots (RLHF) | Q-learning, policy gradients, PPO |
| Semi-supervised | A few labels + lots of unlabeled data | Medical imaging, speech with limited transcripts | Pseudo-labeling, consistency training |
| Transfer learning / fine-tuning | A pre-trained model + a small task dataset | Custom classifiers, domain chatbots | Full fine-tune, LoRA / QLoRA adapters |
Every neural network is built from one simple unit. A neuron multiplies each input by a weight, adds a bias, and passes the sum through a non-linear activation function.
y = f( w₁·x₁ + w₂·x₂ + … + wₙ·xₙ + b )
# f = activation, e.g.
ReLU(z) = max(0, z)
sigmoid(z) = 1 / (1 + e^(−z))
tanh(z) = (e^z − e^(−z)) / (e^z + e^(−z))Without the non-linearity, stacking layers would collapse into a single linear equation — the activation is what lets deep networks model curves, edges, grammar and meaning.
Feed a batch of examples through the network to get predictions.
Measure how wrong the predictions are: mean-squared error for numbers, cross-entropy for classes and tokens.
Use the chain rule to compute the gradient: how much each weight contributed to the error.
Nudge every weight a small step against its gradient: w ← w − η·∂L/∂w.
Loop over the data for many epochs and check on held-out data to catch overfitting.
| Hyperparameter | What it controls | Typical starting point |
|---|---|---|
| Learning rate (η) | Step size of each update. Too high diverges, too low crawls. | 1e-3 (Adam), 1e-4 – 2e-5 for fine-tuning |
| Batch size | Examples per update — trades memory for gradient stability | 16 – 256 |
| Epochs | Full passes over the training set | Until validation loss stops improving |
| Optimizer | How gradients become updates | AdamW; SGD with momentum for some vision tasks |
| Regularization | Fights overfitting | Dropout 0.1–0.5, weight decay 0.01, early stopping, data augmentation |
| Architecture | Core idea | Best at |
|---|---|---|
| MLP (feed-forward) | Fully connected layers | Tabular data, small classification/regression |
| CNN (convolutional) | Small filters slide over the image, sharing weights to detect edges → shapes → objects | Image classification, detection, medical imaging |
| RNN / LSTM / GRU | Processes a sequence step by step with a hidden memory state | Time series, older speech & translation systems |
| Transformer | Self-attention lets every token look at every other token in parallel | LLMs, translation, code, and increasingly vision & audio |
| Diffusion model | Learns to remove noise step by step, turning random noise into an image | Image, video and audio generation |
| GAN | A generator and a discriminator compete | Super-resolution, style transfer, synthetic data |
| Autoencoder / VAE | Compresses input to a small latent code and reconstructs it | Anomaly detection, compression, latent space for diffusion |
| Graph Neural Network | Passes messages between connected nodes | Molecules, social networks, route planning |
| Mixture of Experts (MoE) | A router activates only a few "expert" sub-networks per token | Very large LLMs with lower compute per token |
Attention(Q, K, V) = softmax( Q·Kᵀ / √d_k ) · V # Q = what each token is looking for # K = what each token offers # V = the information passed along
- Pre-training — predict the next token over trillions of tokens of text and code.
- Supervised fine-tuning — learn from high-quality instruction/answer examples.
- Preference tuning (RLHF, DPO and similar) — learn which answers people rate as more helpful, honest and harmless.
- Tools & retrieval — at run time, connect to search, documents or code execution.
- Training: real images get progressively buried in noise; the network learns to predict and remove that noise.
- Text conditioning: a text encoder turns your prompt into vectors that steer each denoising step.
- Generation: start from pure random noise and denoise over ~20–50 steps into a new image — usually in a compressed "latent" space for speed.
| Training | Inference | |
|---|---|---|
| Goal | Learn the weights | Use the weights |
| Compute | Huge GPU clusters, weeks–months | One GPU, laptop or phone, milliseconds–seconds |
| Memory | Weights + gradients + optimizer state (~16 bytes/param with Adam, mixed precision) | Weights + KV cache (as low as ~0.5 bytes/param quantized) |
| Who does it | AI labs, researchers | Everyone who uses AI |
| Metric | Formula / meaning | Use when |
|---|---|---|
| Accuracy | (TP + TN) / total | Balanced classes |
| Precision | TP / (TP + FP) | False alarms are costly (spam filter) |
| Recall | TP / (TP + FN) | Misses are costly (fault or disease detection) |
| F1 score | 2·P·R / (P + R) | Imbalanced classes |
| MAE / RMSE | Average / root-mean-square error | Predicting numbers |
| Perplexity | e^(cross-entropy) | Language models — lower is better |
| Benchmarks | Standard test sets for knowledge, math, coding, reasoning | Comparing models — but always test on your task |
Neural Network Playground
A real 2-layer neural network, trained with backpropagation, running entirely in your browser.
// Network: 2 inputs → H hidden (activation) → 1 output (sigmoid) for (each point (x, y, target)) { h = act(W1 · [x, y] + b1) // hidden layer out = sigmoid(W2 · h + b2) // probability of class B loss += −[t·log(out) + (1−t)·log(1−out)] // binary cross-entropy dOut = out − t // gradient of BCE through sigmoid dW2 += dOut · h ; db2 += dOut dH = dOut · W2 · act'(h) // chain rule back to hidden layer dW1 += dH ⊗ [x, y] ; db1 += dH } W −= η · dW / N // full-batch gradient descent
| Category | Well-known examples | Good for |
|---|---|---|
| Chat assistants | ChatGPT, Claude, Gemini, Microsoft Copilot, Le Chat | Research, writing, planning, explanations, analysis of files |
| Coding assistants | GitHub Copilot, Claude Code, Cursor, Gemini Code Assist | Writing, debugging and reviewing code in your editor or terminal |
| Image generation | Midjourney, DALL·E / GPT image, Adobe Firefly, Stable Diffusion, FLUX | Concept art, mood boards, product mockups, thumbnails |
| Video & audio | Runway, Sora, Veo, ElevenLabs, Suno | Short clips, voice-overs, narration, music beds |
| Speech-to-text | Whisper, built-in phone & OS dictation | Transcribing tutorials, meetings, voice notes |
| Research & search | Perplexity, "deep research" modes in chat assistants | Cited answers, literature and market research |
| Local / open models | Llama, Mistral, Qwen, Gemma, DeepSeek via Ollama, LM Studio, llama.cpp | Privacy, offline use, no per-token cost — see Run AI Locally |
| Developer platforms | Hugging Face, PyTorch, TensorFlow/Keras, scikit-learn, provider APIs | Building and deploying your own AI features |
| Automation | Zapier, Make, n8n with AI steps; Home Assistant voice | Connecting AI to email, spreadsheets, smart-home devices |
Product names and features change quickly — this list shows the landscape, not an endorsement. Pick tools by task, privacy policy and price, and re-evaluate every few months.
- Diagnose repairs: describe symptoms (or upload a photo) of a noisy boiler, a tripping breaker or a car warning light to get likely causes and a checklist.
- Plan projects: generate cut lists, material lists and step-by-step build plans — then verify them with the calculators on this site.
- Identify things: plants, pests, wood species, fasteners, electronic components.
- Write code for makers: Arduino, ESP32, Raspberry Pi and Home Assistant automations.
- Read manuals faster: summarize a 200-page PDF into the three pages you need.
- Visualize: try paint colors, garden layouts or kitchen ideas before buying.
| Healthcare | Imaging analysis, drug discovery, protein structure |
| Manufacturing | Visual inspection, predictive maintenance, robotics |
| Automotive | Driver assistance, autonomous driving, diagnostics |
| Energy | Grid forecasting, solar output prediction, smart thermostats |
| Agriculture | Crop disease detection, precision irrigation, yield forecasting |
| Finance | Fraud detection, credit risk, document processing |
| Construction | Estimating, site safety monitoring, generative design |
| Retail | Recommendations, demand forecasting, support chatbots |
A prompt is a work order. The model knows nothing about you, your project or your standards unless you tell it. Clear context + a clear task + a clear output format beats "clever tricks" every time.
| Technique | How | Example |
|---|---|---|
| Give a role & audience | Say who the answer is for and what expertise to use | "You're a licensed electrician explaining to a first-time homeowner…" |
| Provide context | Paste the data, specs, error message or document | "Here is my wiring diagram and the breaker label: …" |
| Be specific about the task | One clear goal; split big jobs into steps | "List the 5 most likely causes, most likely first." |
| Show examples (few-shot) | Give 1–3 input → output samples | "Format each tool like: Name — use — price range" |
| Ask for reasoning | Let it work step by step on math, logic and diagnosis | "Work through the load calculation step by step, then give the result." |
| Specify the format | Table, JSON, checklist, word count, language | "Return a Markdown table with columns: Part, Qty, Size." |
| Set constraints | Budget, tools you own, standards, what to avoid | "Only hand tools. Metric units. Under €100." |
| Iterate | Treat the first answer as a draft; refine it | "Good — now make step 3 more detailed and add safety notes." |
| Ask it to check itself | Request assumptions, uncertainty and sources | "List any assumptions and anything I should verify." |
Prompt Builder
Fill the fields — a structured prompt is assembled live, ready to copy into any AI assistant.
Token & Cost Estimator
Estimate how many tokens a text uses, how much of a context window it fills, and what an API call costs.
Estimates use the average characters-per-token of modern sub-word tokenizers; each provider's exact tokenizer differs by roughly ±15%. Output tokens are usually priced several times higher than input tokens.
| temperature | Randomness. ~0–0.3 for facts, code and extraction; ~0.7–1.0 for brainstorming. |
| top_p | Only sample from the most likely tokens whose probabilities add up to p. Tune this or temperature, not both. |
| max_tokens | Hard limit on answer length (and cost). |
| system prompt | Standing instructions: persona, rules, format — applied to every turn. |
| context window | How many tokens (prompt + history + answer) the model can see at once. |
| stop sequences | Strings that end generation early. |
- Check numbers, measurements and load ratings against manufacturer data or a calculator.
- Ask for sources — then open them. Models can invent convincing citations.
- Run generated code in a safe test environment first; read what it does.
- Cross-check important answers with a second source or a professional.
- Watch for outdated information — models have a training cut-off date.
- Keep private data out of tools that train on your inputs; check the privacy settings.
Python is the language of AI. Set up an isolated environment once, then every example below runs as-is (replace MODEL_NAME with a current model ID from your provider's docs).
# 1 · Create and activate a virtual environment python3 -m venv ai-env source ai-env/bin/activate # Windows: ai-env\Scripts\activate # 2 · Install the libraries used on this page pip install numpy pandas scikit-learn torch sentence-transformers anthropic openai requests # 3 · Store API keys as environment variables — never in your code export ANTHROPIC_API_KEY="sk-..." # Windows PowerShell: $env:ANTHROPIC_API_KEY="sk-..." export OPENAI_API_KEY="sk-..."
| Library | Use it for |
|---|---|
| NumPy / pandas | Arrays, math and tabular data wrangling |
| scikit-learn | Classic ML: regression, trees, clustering, metrics, pipelines |
| PyTorch | Deep learning research and production (most popular) |
| TensorFlow / Keras | Deep learning, mobile & edge deployment (LiteRT) |
| Hugging Face transformers | Thousands of pre-trained open models for text, vision and audio |
| sentence-transformers | Text embeddings for semantic search and RAG |
| Provider SDKs | Calling hosted LLMs (Anthropic, OpenAI, Google, Mistral…) |
| Jupyter | Interactive notebooks for experiments |
Train a Random Forest to classify flower species from four measurements — the "hello world" of supervised learning.
from sklearn.datasets import load_iris from sklearn.model_selection import train_test_split from sklearn.ensemble import RandomForestClassifier from sklearn.metrics import classification_report X, y = load_iris(return_X_y=True) X_train, X_test, y_train, y_test = train_test_split( X, y, test_size=0.2, random_state=42, stratify=y ) model = RandomForestClassifier(n_estimators=200, random_state=42) model.fit(X_train, y_train) # training pred = model.predict(X_test) # inference print(classification_report(y_test, pred)) # precision / recall / F1 # Which measurements mattered most? for name, imp in zip(load_iris().feature_names, model.feature_importances_): print(f"{name:<20} {imp:.2f}")
The same training loop as the Neural Net Lab, written the way professionals do it — with automatic differentiation and GPU support.
import torch from torch import nn device = "cuda" if torch.cuda.is_available() else "cpu" # Synthetic "circle" dataset: label 1 if the point is inside radius 0.5 X = torch.rand(2000, 2) * 2 - 1 y = ((X ** 2).sum(dim=1) < 0.25).float().unsqueeze(1) X, y = X.to(device), y.to(device) model = nn.Sequential( nn.Linear(2, 16), nn.ReLU(), nn.Linear(16, 16), nn.ReLU(), nn.Linear(16, 1) # raw logit ).to(device) loss_fn = nn.BCEWithLogitsLoss() opt = torch.optim.AdamW(model.parameters(), lr=1e-2) for epoch in range(500): opt.zero_grad() loss = loss_fn(model(X), y) # 1. forward 2. loss loss.backward() # 3. backpropagation opt.step() # 4. gradient descent if epoch % 100 == 0: acc = ((model(X) > 0).float() == y).float().mean() print(f"epoch {epoch:3d} loss {loss.item():.4f} acc {acc:.2%}") torch.save(model.state_dict(), "circle_model.pt")
import anthropic client = anthropic.Anthropic() # reads ANTHROPIC_API_KEY msg = client.messages.create( model="MODEL_NAME", max_tokens=1024, system="You are a concise DIY expert.", messages=[{ "role": "user", "content": "How do I fix a dripping tap?", }], ) print(msg.content[0].text)
from openai import OpenAI client = OpenAI() # reads OPENAI_API_KEY resp = client.chat.completions.create( model="MODEL_NAME", messages=[ {"role": "system", "content": "You are a concise DIY expert."}, {"role": "user", "content": "How do I fix a dripping tap?"}, ], ) print(resp.choices[0].message.content)
// Run on a server (Node 18+). NEVER call a paid API with your key from browser JavaScript. const res = await fetch("https://api.anthropic.com/v1/messages", { method: "POST", headers: { "x-api-key": process.env.ANTHROPIC_API_KEY, "anthropic-version": "2023-06-01", "content-type": "application/json", }, body: JSON.stringify({ model: "MODEL_NAME", max_tokens: 512, messages: [{ role: "user", content: "Suggest 3 beginner woodworking projects." }], }), }); if (!res.ok) throw new Error(`API error ${res.status}`); const data = await res.json(); console.log(data.content[0].text);
Retrieval-Augmented Generation finds the most relevant passages from your content by meaning (embeddings + cosine similarity) and hands them to the LLM, so answers are grounded in your data and can cite it.
import numpy as np import anthropic from sentence_transformers import SentenceTransformer docs = [ "Use a 6 mm masonry bit and brown plugs for 6 mm screws in solid brick.", "Hollow brick needs long nylon plugs or chemical anchors for heavy loads.", "Plasterboard can hold light shelves with metal cavity (molly) fixings.", ] embedder = SentenceTransformer("all-MiniLM-L6-v2") doc_vecs = embedder.encode(docs, normalize_embeddings=True) # index once def retrieve(question, k=2): q = embedder.encode([question], normalize_embeddings=True)[0] scores = doc_vecs @ q # cosine similarity (vectors are normalized) top = np.argsort(scores)[::-1][:k] return [docs[i] for i in top] question = "What fixing should I use for a heavy shelf on hollow brick?" context = "\n".join(f"- {c}" for c in retrieve(question)) client = anthropic.Anthropic() answer = client.messages.create( model="MODEL_NAME", max_tokens=400, messages=[{"role": "user", "content": f"Answer using ONLY this context. If it's not there, say so.\n\n" f"Context:\n{context}\n\nQuestion: {question}"}], ) print(answer.content[0].text)
For thousands of documents, store the vectors in a vector database (pgvector, Qdrant, Chroma, FAISS) and split long documents into overlapping chunks of ~300–800 tokens.
# Simplified agent loop (pseudo-code) messages = [user_goal] while True: reply = llm(messages, tools=[search, calculator, read_file]) if reply.wants_tool: result = run_tool(reply.tool_name, reply.args) messages += [reply, tool_result(result)] else: return reply.text # goal reached
The model never executes anything itself — your code runs the tool and returns the result. Validate every argument and limit what tools can touch.
import requests r = requests.post("http://localhost:11434/api/chat", json={ "model": "llama3.2", "messages": [{"role": "user", "content": "Explain PWM in one paragraph."}], "stream": False, }, timeout=120) r.raise_for_status() print(r.json()["message"]["content"])
Free, private and offline — the model runs on your own machine. Setup is in the next tab.
The problem, the metric that means success, and a simple non-AI baseline.
Collect, clean, label, split into train / validation / test. Most of the work lives here.
Start with the simplest model or an existing pre-trained one before building your own.
Test on unseen data, check errors by category, test for bias.
Serve via API, app or edge device; version the model and the data.
Track accuracy, drift, latency and cost; retrain when the world changes.
Your documents never leave your machine.
Pay once for hardware and electricity.
Works without internet; integrates with Home Assistant, scripts and your home server.
The trade-off: open models you can run at home are typically smaller than the largest hosted models, so they can be less capable on complex tasks. The key constraint is memory — GPU VRAM, or unified memory on Apple Silicon.
# Linux (macOS / Windows: installer from ollama.com) curl -fsSL https://ollama.com/install.sh | sh ollama pull llama3.2 # download a small model ollama run llama3.2 # chat in the terminal ollama list # installed models ollama ps # what's loaded, CPU/GPU split
Ollama also serves an HTTP API on port 11434 (see Example 6 in AI Code). Add Open WebUI for a ChatGPT-style interface in the browser.
| LM Studio | Desktop app: browse, download and chat with models — no terminal needed |
| llama.cpp | The fast C/C++ engine behind many tools; runs GGUF files on CPU, GPU and Apple Metal |
| vLLM | High-throughput server for NVIDIA GPUs, many users at once |
| ComfyUI | Node-based local image and video generation |
| whisper.cpp | Local speech-to-text |
# llama.cpp: serve a GGUF model, all layers on GPU, 8K context
llama-server -m model-Q4_K_M.gguf -c 8192 -ngl 99 --port 8080Quantization stores each weight with fewer bits. Around 4–5 bits per weight is the usual sweet spot: roughly a quarter of the full-precision size with a small quality loss.
| Format | ≈ Bits / weight | 8B model size | Quality vs. FP16 |
|---|---|---|---|
| FP16 / BF16 | 16 | ~16 GB | Reference |
| Q8_0 | 8.5 | ~8.5 GB | Practically identical |
| Q6_K | 6.6 | ~6.6 GB | Very close |
| Q5_K_M | 5.7 | ~5.7 GB | Excellent |
| Q4_K_M | 4.8 | ~4.9 GB | Good — the popular default |
| Q3_K_M | 3.9 | ~4.0 GB | Noticeable loss |
| Q2_K | ~3 | ~3.2 GB | Significant loss — last resort |
Local LLM VRAM & Speed Calculator
Weights + KV cache + runtime overhead → the memory you need, and a realistic generation speed.
Formulas used
Weights (GB) = params × bits_per_weight ÷ 8 ÷ 1.0735 # → GiB KV cache (GB) = 2 × layers × kv_heads × head_dim × context × kv_bytes × parallel ÷ 1024³ Overhead (GB) = 0.06 × weights + 0.5 # CUDA context, activations, buffers Speed (tok/s) ≈ 0.6 × memory_bandwidth ÷ (weights + KV) # decode is memory-bound If total > memory → layers spill to system RAM and speed drops sharply.
Estimates for dense Transformer models at batch size 1. Mixture-of-Experts models need memory for all parameters but run at the speed of their active parameters. Real numbers vary by ±15% with engine, driver and prompt length.
| Budget tier | Hardware | What runs well (Q4) |
|---|---|---|
| Entry | Any modern PC with 16 GB RAM, or an 8 GB GPU | 1–8B models: chat, summaries, coding help |
| Enthusiast | 12–16 GB GPU, 32 GB RAM | 8–14B models with long context; SDXL-class image generation |
| Prosumer | 24–32 GB GPU, or Mac with 36–64 GB unified memory | 32B models comfortably; 70B only with offload or heavy quantization |
| Workstation | 2× 24 GB GPUs, or 96 GB+ unified memory | 70B-class models at usable speed |
| Edge | Raspberry Pi 5 + AI accelerator, NVIDIA Jetson | Object detection, small vision & speech models, sensors |
The EU AI Act (Regulation (EU) 2024/1689) is the first comprehensive AI law. It entered into force in August 2024 and applies in phases through 2027, classifying AI systems by risk. Other regions (US states, UK, China, Canada) have their own approaches. This is an overview, not legal advice.
| Risk level | Examples | Requirement |
|---|---|---|
| Unacceptable | Social scoring, manipulative techniques that cause harm, untargeted scraping of facial images | Prohibited |
| High risk | AI in critical infrastructure, hiring, education, credit scoring, medical devices, law enforcement | Risk management, data quality, logging, human oversight, conformity assessment |
| Limited risk | Chatbots, AI-generated or manipulated content (deepfakes) | Transparency: users must know they're dealing with AI; synthetic content must be labeled |
| Minimal risk | Spam filters, AI in video games, most everyday tools | No specific obligations |
| General-purpose AI | Foundation models / LLMs | Technical documentation, copyright policy, training-data summary; extra duties for systemic-risk models |
- Tell people when content or a conversation is AI-generated.
- Keep a human in the loop for decisions affecting safety, money or rights.
- Don't upload personal, client or confidential data to consumer AI tools.
- Check licenses before using AI images or code commercially.
- Test models for bias and failure cases before deploying them.
- Log AI decisions so they can be reviewed and explained.
- Give AI agents the minimum permissions they need.
- Keep learning — the technology and the rules change every year.
AI Glossary
Search 0 essential AI terms, explained in plain English.
No matching terms — try a shorter word.
You can learn everything on this page with a normal laptop and free tools. These upgrades matter once you want to run models locally or build AI hardware projects.
Some links on this page are affiliate links — if you buy through them we may earn a small commission at no extra cost to you.
This page covers the fundamentals; the KreatedByU forum is where full AI project walkthroughs live. The cards below are placeholders, ready to link as tutorials are posted.

