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.
Archive
Posts
Each entry should document one useful increment: the trigger, the change, and the next question.
What is ORS-Appliance?
How ORS-Appliance gives libraries a practical, interoperable path into OpenRS and wider resource-sharing networks.
OpenRS check-in: pickup-aware pull slips and a completed return
A fresh local evidence run adds printable pickup routing and closes the returnable-print lifecycle at the supplier and DCB.
OpenRS-Appliance returnable print lending: a clean lifecycle checkpoint
A current, screenshot-backed journey from SFTP record intake and discovery through return transit.
Interim update: ORS-Appliance as the fallback path into DCB
ORS-Appliance can let libraries participate in a DCB network even when they do not have a supported ILS integration.
NCIP as the adapter boundary for direct consortial borrowing
A checkpoint showing DCB and ORS-Appliance using NCIP as the protocol substrate for request, supply, borrower acceptance, circulation, and return transit.
DCB can now ask a Fallback Host to supply
A current OpenRS/DCB happy-path checkpoint: DCB posts NCIP RequestItem to ORS-Appliance, and ORS-Appliance can answer with will-supply or not-supplied messages after staff decision.
Turning Library Patron Authentication Into OIDC
A local QA checkpoint showing DCB turning proprietary patron authentication into standards-based OIDC for OpenRS Discovery and future library applications.
No collection is too small, no request too local
A visible checkpoint for local DCB and OpenRS resource-sharing development, with ORS-Appliance, DCB Admin, and the shared index running together.
Foundry's operational spine is starting to show
A short bookend on the hosted Foundry work after the Console adoption-loop proof, and why the next lab pivot turns toward OpenRS and ORS-Appliance.
The business layer is infrastructure for the mission
A working note on ki-console, Foundry, and why sustainable open library infrastructure needs an adoption loop as well as a developer loop.
Foundry Module SDK: profiles for a smaller FOLIO dev loop
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.
Federated Identity in Libraries Is Already Happening
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.
Why not the whole of FOLIO?
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.
Foundry now runs a small FOLIO app suite on a laptop
Licenses, Agreements, Open Access, Serials Management, and ILL now run together in Foundry through descriptor-selected module-federation artifacts.
Foundry platform services and the docking layer
How Foundry is separating platform support APIs from FOLIO utility modules, and why acquisition units belong behind a provider-backed platform boundary.
The first Foundry roadmap: FOLIO ERM, artifacts, Kubernetes, and external ILS
The spike has produced enough evidence to publish the first roadmap: local runtime, artifacts, operational catalog, Kubernetes demo substrate, and external ILS extension.
From FOLIO Licenses and Agreements wrappers to a UI artifact supply chain
How Foundry widened a narrow ui-licenses proof into repeatable ERM wrapping evidence across Agreements, Open Access, and ILL.
Foundry from spike to shape: FOLIO Licenses, Loom, Lattice, and Envoy
What the FOLIO Licenses proof now demonstrates, how tenant work happens, and where Foundry goes next.
Foundry after the spike: from FOLIO Licenses proof to Loom lifecycle
Turning the standalone FOLIO Licenses proof into the first durable Loom lifecycle foundation.
A first look at Foundry: FOLIO Licenses without Okapi
Running FOLIO Licenses as a standalone, tenant-aware ERM application without Okapi or Eureka.
Starting the lab notebook
Why this blog exists and how it will capture exploratory increments across K-Int projects.