The Runtime Theory is organized around engineering domains and the concepts inside them. A topic page is an entry point: it gathers the articles, traces, request flows, videos, practice, and interview prompts currently connected to that area. A concept can then be explored at different levels instead of being reduced to one format.
Start with the question you have
If you want the broad idea, read the article. If you want to know what executes next, open the trace and follow its steps. If the idea involves a request, data path, or state transition, use the interactive flow. Use practice to apply the model, and use an interview prompt to explain it concisely.
Move across the 17 domains
The map spans Programming & Algorithms, Data Structures, Computer Systems, Operating Systems, Computer Architecture, Networking, Databases, Programming Language Internals, Runtime & Execution, Backend Engineering, Software Architecture, System Design, Distributed Systems, Cloud & Infrastructure, Security, Performance Engineering, and Software Engineering.
These are connected lenses rather than isolated silos. A database query depends on data structures, storage, operating-system I/O, and a runtime. A web request crosses networking, security, backend, database, and distributed-system boundaries. The related-topic links and cross-kind references make those connections navigable.
Choose a route
For a cross-layer survey, begin with Software Systems: From Code to Production. For a focused sequence, choose Code to Machine, Networked Services, Data Storage and Consistency, or Build and Operate Reliable Systems.
The map will grow as new concepts get their own connected lessons. A topic with no item in a particular format simply means that format has not been produced yet; planned video entries remain clearly marked until playable media is available.