A Library Holds Documents, Not Projects

In plain terms: a Library is a folder of precedent documents that sits beside your client matters, not above them. You can file a document, a clause group or a single clause in it, but never a whole client matter.

Decision

Owner ruling, 2026-10-01. It reverses the 2026-09-26 ruling "a master may be anything but a Workspace" recorded in Libraries.

1. Save to Library is offered for a Document, a Module and a Block only. A Project is refused with a plain sentence.
2. Insert into… from a Library: a Document into a Project, a Module into a Document, a Block into a Module. A Library itself is linked to Workspaces as a search source (already built).
3. Existing Project masters are split. Each Document under a Project master becomes a Document master on its own in the same Library, keeping its content and versions; the Project master is then removed.
4. Starter packs are made by inserting several Library Documents into a new Project, not by saving a Project.

Revision, 2026-10-01 (later the same day): Documents only

In plain terms: the precedent bank keeps whole precedent documents only. You still borrow a single clause, but you find it inside the precedent it belongs to and photocopy just that clause; the clause is never filed on its own.

Owner ruling, 2026-10-01. It narrows point 1 and point 2 above.

1. A Library holds Documents only. Saving or publishing a Module or a Block is refused with "Libraries hold Documents. Publish the Document this clause belongs to." A Library's Workspace files only Documents.
2. Clause reuse stays, from inside Library Documents. The Insert search card and Goldie's Library search both look inside each Library Document's published edition and offer its Modules and Blocks, each labelled with where it lives: "Termination — in Services Agreement (Precedents)". Inserting copies that clause from the published edition: a Module into a Document, a Block into a Module; a whole Document still goes into a Project. The picker's existing rules stay: kind icon on the section heading, compact rows, tick box in the left gutter, sections ordered by where the search stands.
3. Lineage on the copy names the clause it came from and the exact edition of it (derivedFromFolioKey, derivedFromVersionKey); the Library Document is that clause's parent, so the copy records both.
4. The Library page shows Documents only: no Module or Block shelves or counts.
5. Existing Module and Block masters are dummy data on the development deployment and are retired there, not migrated (owner: throw it away). Production is not touched.

Alternatives refused: keeping Module and Block masters beside Documents (two places to file one clause, and clauses lose the document context that makes them safe to reuse); dropping clause reuse altogether (the main reason lawyers keep precedents).

Why

• Firms keep documents and clauses as precedents, not whole matters.
• Saving a whole Project would carry a full client file into a shared Library.
• Three levels are simpler to learn and to search.

Supersedes

• Libraries, 2026-09-26: "a master may be anything but a Workspace", the Projects shelf on a Library page, Use this project, and Project cards' Publish to Library row.