Goldie Blocks

Owner rulings 2026-09-25 — a Folio joins a Library through one entry row naming a sealed edition, the export prints the Libraries it sits in, a saved Project carries everything beneath it, saving files a snapshot into a separate Library master, anything inside a saved item can be found and inserted on its own, and the holder of Library rights is designed firm-ready while only people are built.

Consolidated 2026-09-25 into Libraries, the current statement. This record is kept as history.

Decision

Owner rulings, 2026-09-25, settling decision-11 (Library master or original) and decision-19 (user or firm), and reconciling the 2026-09-09 membership amendment with A Library Is a Shelf, Not a Folio. Nothing here is implemented. The shelf record's rules 1–24 stand unless amended below.

In plain terms: a Library is a precedent bank with a drawer of index cards. Saving a matter's document to a bank files a card pointing at a frozen copy of it; one document can have cards in several banks. The document's printout lists the banks it is filed in. Who may use a bank is a licence held by a person today, drafted so a firm can hold it later.

Membership

Membership is one entry row per (Library, Folio) — the existing libraryPins row, naming the exact sealed edition on the shelf. It is the only stored truth of which Libraries hold a Folio. A Folio may sit in any number of Libraries.
The Folio's "array of Library IDs" (amendment 2026-09-09) is a projection, not a column. The export and the About face print libraries: [...], derived from the Folio's active entries. No Library-ID array is stored on folios, so the two can never disagree.
The owner's "save to a Library" is the menu's Publish to Libraries › row (ruling 2026-09-11). Ticking a Library files an entry; unticking retires it.
Saving is a snapshot. An entry names a sealed edition (shelf rule 2). Later edits reach the Library only when the owner saves again, which files a new entry and retires the old one (shelf rule 3).
An entry may name a Project and everything beneath it, carried by that edition's own pins, never one entry per descendant. A Workspace entry is the same mechanism and is deferred, not refused.
Anything inside a saved item can be found and inserted on its own. Search reads the pinned descendants of each entry's sealed edition, so a clause inside a saved Project is a candidate like the Project itself. Insertion keeps containment (FOLIO_SCHEMA_CONTAINMENT) and materialises a copy (shelf rules 7–14).

The Library master (settles decision-11)

The first save to a Library makes a separate Library master — a new Folio with fresh identities and recorded lineage — and the owner edits the master from then on. The client Document is not touched and not linked. Whether the master derives from the working draft (as Duplicate does) or from a sealed edition is an implementation choice. Only the second touches Sealed Versions Are Immutable rule 4. Where the master lives is open (see Consequences).

Who holds Library rights (settles decision-19)

The unit of ownership is designed firm-ready and built person-only. New Library rows name a holder whose type is a person today, and a firm can be added later as a second type without rewriting rows. No organisation table, screen or admin is built now. The existing folios.owner is left as it is.
Library access is its own relationship, not Folio sharing. Using a Library (owned, shared, free, bought) and working on a Folio (the future folio membership that replaces browserClientId) are separate records. Access is checked at read time (shelf rule 23) and never copies the Library.

Later the same day

Owner rulings, 2026-09-25, settling decision-30, decision-31 and decision-12, then how a master is updated and filed:

A bought Library is shared by seat licence. The holder assigns the licence's seats to named people; when it lapses, its seats lapse.
Each Library has its own Workspace where its masters are filed and edited; the Library row names it.
A listing shows the name as it was when that edition was saved. Renaming a master changes listings only when it is saved again.
Membership is always a deliberate save. The 2026-09-09 "automatic tagging" means classification tags the system applies when an item is saved to a Library, designed later; it never files an item by itself.
Saving a version of a master does not publish it. Versions are private checkpoints; Publish to Libraries releases the latest saved version, and copies already inserted never change.
A Library Workspace may hold any kind directly, listed by kind — Projects, Documents, Modules, Blocks. Every other Workspace keeps the strict containment rule.
The lists show only masters saved on their own. A saved Project's contents are reached by opening it; search still finds them.

Refused

A Library as a kind of Folio, holding its contents through folioPins. A Folio has one parent and every contents change mints a version; one item in several Libraries would force duplicates that drift.
Library access through the Folio membership table. Purchases need a source, seats and an expiry that Folio sharing has no use for.
A stored Library-ID array on folios beside the entry rows: two truths.
Organisation features now.

Current vs Target

Current. libraries and libraryPins exist empty with no public writer; publishToLibrary is internal and uncalled. The Library menu is a Storybook preview (GB-228). There is no sign-in (GB-10), so no holder can be named yet.

Target. Sign-in and Folio membership first, then Library rows with a holder, access records, Save to Library through the master, and search over entries (GB-245), all under GB-50.6.

Consequences

Rules 10–13 settle decision-30, decision-31 and decision-12.
The shelf record's "Owner decisions still required" now points here for decision-11.

Library Membership Is an Index Card; Access Is Held, Not Copied