diff --git a/README.rst b/README.rst
index b15fa5277e..ae0ecea6eb 100644
--- a/README.rst
+++ b/README.rst
@@ -82,6 +82,12 @@ instance, if a dependency has dropped Python 2.7 support.
 ``upper-constraints.txt`` is machine generated and nothing more or less than
 an exact list of versions.
 
+``lower-constraints.txt`` is manually maintained and can be consumed by projects
+for tracking their individual project specific constraints as well as giving a
+good indication to deployers what the global minimum requirements are
+for the set of projects in the integrated gate.
+
+
 Enforcement for Test Runs
 -------------------------
 
@@ -176,6 +182,10 @@ dependencies. As such you should always generate a diff against the current
 merged constraints, otherwise your change may fail if it is incompatible with
 the current tested constraints.
 
+A change to the minimum specified vesion of a library in ``global-requirements.txt``
+currenty requires adjusting the ``lower-constraints.txt`` file alongside with the
+new constrainted coinstallable version of minimums.
+
 Regenerating involves five steps.
 
 1) Install the dependencies needed to compile various Python packages::