Computing Fundamentals for the Semantic Architect
"The theoretical physicist doesn't build the particle accelerator — but they understand every layer of the matter being manipulated."
Why this exists
The SSA — Semantic Systems Architect — operates at the interface between human intention and machine execution. This is a new discipline: architecture of meaning. But meaning that will be executed by computers.
A building architect doesn't need to lay bricks, but they need to understand what reinforced concrete is, what a beam does, how gravity works. In the same way, the semantic architect doesn't need to program — but they need to understand what the machine is, how it thinks, and what each piece of the system does.
This module is the theoretical physics of computing applied to SSA. Here you will understand every concept, every acronym, every layer — not to program, but to orchestrate with authority.
Structure: 8 Progressive Levels
The journey goes from the most fundamental (what is a bit?) to the most abstract (what is a SaaS?), passing through every layer that a software system traverses.
| Level | Title | What you will understand |
|---|---|---|
| 0 | The Machine | Bit, byte, binary, CPU, RAM, storage, how the computer "thinks" |
| 1 | Code: the language of the machine | Variable, data type, function, loop, conditional, array, object, class |
| 2 | Data and Persistence | Database, SQL, NoSQL, JSON, XML, schema, query, CRUD |
| 3 | The Web | HTML, CSS, DOM, browser, URL, HTTP, request/response |
| 4 | Client and Server | Frontend, backend, API, REST, GraphQL, endpoint, payload, status codes |
| 5 | Infrastructure | Server, cloud, DNS, container, Docker, CI/CD, deploy, CDN, SSL/TLS |
| 6 | Product Patterns | SaaS, PaaS, IaaS, MVC, authentication, OAuth, JWT, webhook, microservice |
| 7 | AI and LLMs | Token, embedding, context window, temperature, fine-tuning, RAG, agent |
How to use this material
If you are completely new to technology
Start at Level 0 and advance in order. Each level builds on the previous one. Don't skip — understanding is cumulative.
If you already have some familiarity
Use it as a reference. Go straight to the level you need. Each concept is self-contained within its explanation.
If you are a developer
You probably know all of this in practice. But reading it through the SSA lens will shift your perspective: here every concept is seen as semantic raw material — something the architect needs to name, constrain, and orchestrate.
The Lexicon
Beyond the 8 levels, this module includes a Computing Lexicon — a complete dictionary of all terms and acronyms, in alphabetical order, with direct links to the lesson where each concept is explained in depth.
Use the Lexicon as a quick entry point whenever you encounter unfamiliar terminology anywhere in the course.
Connection to the SSA course
Each lesson ends with a section called "Why the SSA needs to know this" — connecting the technical concept to the practice of semantic architecture. Examples:
- Understanding what a variable is helps you define fields in domain ontologies
- Understanding client and server is essential for architecting multi-agent systems
- Understanding tokens and context window is the foundation for context engineering
- Understanding CRUD and APIs is what enables the SSA to specify tool integrations
Computing is not the end — it is the means. And the SSA needs to deeply understand the means they are orchestrating.