FOLIO: How Many Grapes Went into the Wine?
An opinion on operational enclosure, ecosystem enclosure, and the reciprocal obligations needed to sustain open-source library software.
Topic
Lab notes on running FOLIO-adjacent ERM capabilities such as Licenses and Agreements in smaller, runtime-composed systems.
An opinion on operational enclosure, ecosystem enclosure, and the reciprocal obligations needed to sustain open-source library software.
A walkthrough of the new Foundry Module SDK profile model: start a production-shaped module runtime, then substitute only the backend or frontend you are actively changing.
A response to Amanda Ferrante's Scholarly Kitchen article, and an argument that library federation is not only about login protocols but also about trust, attestation, and shared circulation across institutions.
Foundry could become a lighter self-hosting substrate for FOLIO, but the immediate goal is a sovereign home for K-Int apps and ILS-neutral library extensions.
Licenses, Agreements, Open Access, Serials Management, and ILL now run together in Foundry through descriptor-selected module-federation artifacts.
How Foundry is separating platform support APIs from FOLIO utility modules, and why acquisition units belong behind a provider-backed platform boundary.
The spike has produced enough evidence to publish the first roadmap: local runtime, artifacts, operational catalog, Kubernetes demo substrate, and external ILS extension.
How Foundry widened a narrow ui-licenses proof into repeatable ERM wrapping evidence across Agreements, Open Access, and ILL.
What the FOLIO Licenses proof now demonstrates, how tenant work happens, and where Foundry goes next.
Turning the standalone FOLIO Licenses proof into the first durable Loom lifecycle foundation.
Running FOLIO Licenses as a standalone, tenant-aware ERM application without Okapi or Eureka.