diff --git a/README.adoc b/README.adoc
index 62d51ba..5bfd71b 100644
--- a/README.adoc
+++ b/README.adoc
@@ -355,6 +355,11 @@ We can also test our hacked glibc on <<user-mode-simulation>> with:
 
 I just noticed that this is actually a good way to develop glibc for other archs.
 
+In this example, we got away without recompiling the userland program because we made a change that did not affect the glibc ABI. TODO: find the best list of ABI stability rules available:
+
+* https://plan99.net/~mike/writing-shared-libraries.html
+* https://stackoverflow.com/questions/2171177/what-is-an-application-binary-interface-abi
+
 Note that for arch agnostic features that don't rely on bleeding kernel changes that you host doesn't yet have, you can develop glibc natively as explained at:
 
 * https://stackoverflow.com/questions/10412684/how-to-compile-my-own-glibc-c-standard-library-from-source-and-use-it/52454710#52454710