Judgement, and what remains

What the sequence cannot supply

Knowing what the structure does. Every check in Module 12 and 13 depends on having an expectation. Where does it sag, where does it hog, which members are in tension, is this symmetric? That comes from Structural Behaviour and from having looked at a lot of structures, and no procedure substitutes for it. A checklist in the hands of someone with no expectation produces ticks.

Knowing what is unusual. The most valuable diagnostic instinct is that looks wrong, and it is trained by seeing what right looks like many times. The Model Doctor is a substitute for a small part of that experience and not for the experience.

Knowing when the question is wrong. Step 1 says to define the problem. It does not say how to notice that the brief has already given away the answer, which is what happened in the last lesson's project. That noticing is judgement.

Deciding how much checking is enough. Module 13 said the depth of checking should follow the consequence. Judging the consequence is not on any list.

Knowing when to stop. Module 16 gave four stopping criteria and said each gives something up. Choosing between them is a decision about what you are willing to miss.

What this course has not taught

Stated plainly, because a course that implies completeness is misleading:

Any design resistance. This course stops at the analysis output. Member and section design to the Eurocodes is Steel Design and Reinforced Concrete Design, which carry their own verified standards profiles.

Dynamics. Modal analysis, response spectra, time-history and damping are Structural Dynamics. Module 10 covered only what a dynamic analysis needs from the model.

Soil behaviour. Module 12 covered spring supports as a modelling decision; the soil mechanics behind the stiffness is Soil Mechanics.

How to write a solver. Module 9 opened the box far enough to model well and no further.

Any particular software. Deliberately. The concepts here — node, element, restraint, release, geometric stiffness, load path — are the profession's vocabulary, and terminology varies between packages. Reading your own package's documentation for what it does and does not do is a validation activity, and Module 13 said so.

Current capability claims. Nothing here says what any AI system, cloud platform or quantum computer can currently do. Those claims date faster than the page.

What is unverified in the course itself

The currency register tracks 16 time-sensitive claims. Eight are stable principles. Seven require verification against a current authoritative source and are marked as such wherever they appear: explainability, cloud capability, quantum computing's practical status, BIM standard editions, design standards, the embodied-carbon factors and data-protection obligations. One is reported as a 2022-era position. None is claimed as verified.

The carbon factors in particular are illustrative teaching values, and every result the tool returns says so.

That is not a defect to apologise for. It is what an honest course looks like when much of its subject moves faster than a curriculum, and the alternative — asserting things and hoping — is worse.

What to carry

If one sentence survives from the whole course, this:

A wrong model produces neatly formatted results, plausible contours and a converged solution, and nothing in the presentation distinguishes it from a right one.

Everything else — the equilibrium check, the prediction, the sensitivity study, the three-stage check, the model record, the deterministic-check rule — exists because of that one fact. There is no other signal, so the signals have to be made deliberately.