The metapackages of commons (commons 0036-distributionFR-005 to FR-008): five packages with no code of their own, each a set of libraries at the exact versions of one release. @intellectual-frontiers/commons is every consumer-facing library; foundation, patterns, programs and standards are the four roles of the libraries. A repository other than .github installs commons by installing one of them, or a library, from a registry.
Pure: the libraries as data give the members of a set, the exact dependencies of its package, the file that records them, the package.json and the README that are published. The role of a library is read from ROLE_OF of readme.ts, the one place that says it, and the set of a role is the role's: foundation, pattern (patterns), program (programs) and standard (standards). A library is consumer-facing where its distribution names npm and it is not a metapackage and not held back (HELD_BACK); the package of a member is the package it publishes (publishedPackage). A member whose role is not known is a problem and never a member of no set. The effects (writing the files, packing) are pack-metapackage.ts.
The libraries that are not in any set yet, each with why: they declare npm and are not ready to be installed (commons 0036-distributionFR-006). A library leaves this list when its owner releases it.
The README of a set's package: what it holds, how to install it from npm and from the GitHub package registry, and how to keep one copy of each library.