Four claims nobody checked, and one move that refuses them: write the terminology down, compile it into constraints, bind the claim to the thing it is about, and let a checker say no. You will separate terminology from assertions, read a SHACL shape line by line and the report it produces, watch a validator answer three ways rather than two, compute coverage as a set difference, and handle type hierarchies by deriving the closure offline so the checker on the path stays a string match. The course ends where it started: an agent’s write path, and the one position from which something can refuse a change before it lands.
None of this makes a model correct. It makes wrongness land somewhere visible, with a name, before it reaches anyone who would have believed it.
