Frame the system
Draw a useful boundary, identify stakeholders, and trace feedback rather than analyzing isolated parts.
Field guide 01 / Systems engineering
Learn to see relationships, define boundaries, manage interfaces, and connect engineering evidence—one illustrated lesson at a time.
Reading order
Each lesson stands alone, but the sequence builds a useful vocabulary before adding new kinds of complexity.
The course
Move beyond isolated events to understand boundaries, accumulation, feedback, delay, and emergence.
02Decompose systems around responsibility, hidden decisions, and explicit interface contracts.
03Make a connected model, not a document stack, the primary engineering artifact—SysML, the v2 standards shift, and an honest look at the evidence.
04When the thing you engineer is made of independently owned systems: Maier's five characteristics, the four types, emergence as the core challenge, and the multi-agent AI parallel.
05A live virtual model of a physical system, where twins attach to the Vee, why they need continuous V&V, and what changes when AI is added.
06What happens when an AI agent reads and writes the system model directly—where the MBSE-plus-agent partnership is real today, and where it is still a research proposal.
07The requirements hierarchy, what makes a statement well-formed, EARS syntax and its five patterns, an honest look at the CHAOS-report evidence, and how EARS now constrains AI-generated code.
08Not the diagrams but the decisions underneath them: viewpoints and views, Kruchten’s 4+1, architecting as a heuristic discipline, and what a weighted trade study actually proves.
09Part 1 of the Human Systems Integration primer: function allocation and the Fitts list, the evidence that reversed it, ten levels of automation, the four-function model, and the ironies of automation.
10Part 2 of the Human Systems Integration primer: Endsley’s three levels, the out-of-the-loop problem, use/misuse/disuse/abuse, calibrated trust, and why training alone does not prevent automation bias.
11Part 3 of the Human Systems Integration primer: silent model updates, goal delegation instead of function allocation, failures that sound right, and how many agents one person can oversee.
12A special feature spanning both primers: an interactive timeline from Watt’s governor and cybernetics through Shakey, two AI winters, the DARPA challenges, and the transformer to agentic AI.
Working skills
Draw a useful boundary, identify stakeholders, and trace feedback rather than analyzing isolated parts.
Use cohesion, coupling, interfaces, and event-driven communication to make modular tradeoffs explicit.
Relate needs, requirements, architecture, analysis, and verification through traceability and viewpoints.
Reason about governance, interoperability, emergence, and cascading risk across independent systems.
Lesson format
On the syllabus
These topics are in progress. They will be published as the examples, exercises, and references are ready.
Build evidence that the system was built correctly and fulfills its intended use.
Compare alternatives transparently under competing objectives and uncertainty.
Identify, analyze, treat, and monitor uncertainty across the life cycle.
Define, control, verify, and evolve cross-boundary agreements.
Connect authoritative data, models, workflows, and evidence across engineering work.
Tailor technical and management processes to the system, organization, and life-cycle model.
Design human roles, work, training, safety, and technology as one system.
Reason about failure, recovery, adaptation, and sustained capability.
Keep product definitions, baselines, changes, and evidence coherent over time.
Use measures and indicators to understand progress, performance, and uncertainty.
Engineer data, models, human oversight, change, and assurance as an integrated capability.