Goldie Tags by Instruction

In plain terms: each Library has a note on the cabinet door saying how its files are summarised and labelled. Goldie reads the note and does both for everything put in the cabinet. The owner writes whatever note suits the work — legal precedents, a client list, a marketing campaign. A cabinet with no note gets a sensible default. Nobody keeps a list of labels.

The rule

1. A Library's guide is one instruction for guides and tags. It is the guide of the Library's home folio (libraries.homeFolioKey). Goldie returns an item's guide and tags together, in one turn, from it.
2. The Library's guide decides what tags say. Topics, wording, how many, what counts as a tag: all the owner's choice. The app is not only for legal drafting, so nothing about tags is fixed to one domain.
3. Tags are one flat list of words. No types, no categories, no vocabulary table.
4. The server holds two rules only: at most eight tags, de-duplicated (checkFolioTags). Everything else is instruction.
5. Only Goldie writes tags, and only as a proposal. A person may ask Goldie in chat to tag an item ("tag this"); she runs the same tagging job and files the result as a proposal (owner, 2026-10-07, below). the tags land without a proposal (owner, 2026-10-04) — reversed 2026-10-07. Anything meant to stick goes in the Library's guide.

Owner ruling 2026-10-07: tag changes are proposals

In plain terms: the clerk no longer sticks labels on files herself. She writes on a slip which labels she would add and which she would strike, one line per file, and the labels change only when the partner signs the slip.

Reverses the 2026-10-04 "tags land at once" (rule 5).

• Every tag change Goldie makes is a proposal: tags she proposes in conversation (tagItem) and the background re-tagging after an item is added to a Library or a Library's guide is edited (rules 7 and 8). None lands directly.
• Everywhere Goldie works: the document canvas and the list screens (Home, Project and Library rows).
• One step row per item in the chat's list of changes, reading e.g. "Tags: +Estate planning, −Draft", accepted or rejected as a whole set. Accepting applies the additions and removals to the tags as they then stand; rejecting leaves them unchanged.
• Clearer step wording for the other About writes: a guide write reads "Guide changed", with the old and new words redlined; a name write reads "Title changed".

Build: the proposal grammar carries a write-tags step (add, remove, an optional library naming the item's entry, and the guide Goldie wrote with the tags, if any). goldie/tagProposals.ts files it — through the canvas's proposal door on a document's conversation, on the row for a list row's, and with no thread for the background re-tagging, decided on the item's card by an editor of its Library. Acceptance applies it through Goldie's door (goldie/tagWrites.ts, applyTagChangeStep).

The default guide

When a Library's guide is blank, Goldie follows the default guide. The guide field shows it as muted placeholder text. It is stated once, as LIBRARY_DEFAULT_GUIDE in packages/domain/src/library/library-guide.ts:

Guide each item in one or two short sentences: what it is and when to use it. Tag each item with its most important concepts: three to eight tags, more for longer items that cover more.

Guiding and tagging

6. Guide and tags are part of every folio Goldie proposes, as members of the proposal. A folio proposed inside a Document is written to the default guide; a Library's own guide applies once it is added there.
7. Guide and tags are per Library. An item in two Libraries carries a guide and tags for each. On adding, the entry starts with the guide and tags the item already has; Goldie then rewrites them to that Library's guide.
8. Editing a Library's guide redoes every item in it, and the Library's own card. Goldie decides when else to redo an item.
9. Wording is per Library. Goldie reuses wording within a Library; there is no global rename.

A recommended guide for legal precedent Libraries

A starting point for Libraries of legal clauses, and for public Libraries that ship with the app. A Library owner may use it, adapt it, or ignore it.

Precedents for [who and what]. Guide each item in two short sentences: the verdict, then the catches. Tag up to three per item: which party the clause favours, its main topic, and how it is drafted. Write tags as positive statements ("Uncapped", not "no cap"). Dates, amounts and party details are not tags. [Name your parties, preferred topic words, and jurisdiction by state or country if relevant.]

Example, for this clause:

Party A indemnifies and must keep indemnified Party B against all loss, damage, liability, costs (including legal costs on a full indemnity basis) and expenses arising out of or in connection with any claim, demand, action or proceeding by any person in respect of personal injury, death, or property damage caused by Party A in performing the Services.

Build

• libraryPins carries guide and tags, seeded from the edition on adding; goldie/tagging.ts proposes new ones (goldie/tagProposals.ts), written through Goldie's door goldie/tagWrites.ts on acceptance.
• folioVersions.tags holds words. The tags vocabulary table is emptied by migrations:tagKeysToWords and migrations:dropTagVocabulary, then dropped from the schema.
• People have no tag door; no public mutation takes tags.
• Goldie's folio proposals carry guide and tags on insertion steps.