The Alice and Globex example makes the intersection picture concrete. Each set added can only shrink what a call may do, and a check in code the model cannot reach is a boundary, not a suggestion buried in a prompt.
Glad the Alice/Globex example landed that was the hardest part to make concrete. The “boundary, not a suggestion” framing is the whole point: anything the model can read, it can be talked out of, so the only sets that count are the ones enforced in code it never sees. Part 2 takes the intersection and puts tests and a mutation run behind it, so each guard has to prove it earns its keep.