CM distinguishes between libraries that are under development and libraries that are stable. A stable library is created by a call of CM.stabilize (see Section 4.1.1).
Access to stable libraries is subject to less internal consistency-checking and touches far fewer file-system objects. Therefore, it is typically more efficient. Stable libraries play an additional semantic role in the context of access control (see Section 8).
From the client program's point of view, using a stable library is completely transparent. When referring to a library--regardless of whether it is under development or stable--one always uses the name of the library's description file. CM will check whether there is a stable version of the library and provided that is the case use it. This means that in the presence of a stable version, the library's actual description file does not have to physically exists (even though its name is used by CM to find the corresponding stable file).