--- a/CR_preface.txt	Sat Nov 02 22:18:44 2024 +0000
+++ b/CR_preface.txt	Sat Nov 02 22:18:57 2024 +0000
@@ -150,8 +150,39 @@
 If you are interested in _real_ semantics, ... what's a poor boy to
 do?
 
- 
+Semantical issues are non-the-less still in the drivers seat---we are
+happy when (+ 2 3) yields 5 because of are awareness of them.
+
+Tracing the fate of those issues, and the vocabulary, are stories that
+need told.
+
+"Things have changed and now we do things differently."  What's
+changed and how is it different?
 
+Answer - the SDK would [be wanted to] track reference relations, not
+just implementation relations.  But that's so complicated that it
+couldn't possibly work.  Suppose you're defining a type [theta], a
+vector type accessible via theta and rho or x and y.  Setting x and
+rho contstrains.  Compiler can ignore this, and just keep one or the
+other, but the type system should 'know' the relationship of both, and
+could therefore track a lot more about a program using vectors than it
+does at the moment.
+
+[HST poses a story about astronomers and air traffic controllers?]
+
+Problem solving is not the motiviation, articulating what is the case
+is, to say what's true.
+
+The effect of PSI is everything that happens, and the PHI relations
+are what matters.  All constraints, norms, requirements are expressed
+in terms of PHI stuff.
+
+What does this book say that requirements engineering etc. haven't
+already
+
+[HST what about program correctness, specification languages ? etc.]
+
+[Chapter 7?]
 ------------
 Foundations of/Philosophy of Computation
 
@@ -161,7 +192,8 @@
 Don't think you have to be a specialist to read this book.
 
 Effective vs non-Effective is actually new: at the book boundaries,
-project onto the effective [?]
+project onto the effective [? - it's not that everything is
+term-rewriting, it's more like ].