Template Library

Template Library defines a Growth-stage Protect setup for central document templates. Start with documents people actually reuse, retain one current version per template and name its owner. Archive superseded variants rather than keeping every variation in active use. The workflow catalogs the template, defines its fields, records the approved version, publishes through the responsible system and tracks usage or updates. The register captures template type, source module, department, owner, update date, content link and status. It points to files already stored elsewhere and does not itself create or distribute business documents.

The default deliverable is a short recommendation. An explicit setup, build or conversion request produces artifacts after essential missing facts are resolved. Advice receives a direct answer, while a review works from the material provided. This keeps the size of the proposed setup tied to the requested outcome.

Use it when old proposal, invoice or handover templates circulate through attachments and drives without clear ownership. It does not create or send documents, store files or synchronize a repository. Publication is a separate authorized operation.

This is an empty-template workflow, not processing of real employee or customer records. Automation, reminders and synchronization require the separate integration layer. Sensitive decisions and adjustments require qualified human review before anything is acted on.

Ask which documents recur, count and user group; fixed versus variable fields, required sections and naming; change approver, version tracking and publication location; current storage and identification of the latest version; and whether a library, naming rule or review cycle is needed. Questions are asked one at a time, excluding anything already answered in earlier messages. Unknown facts stay unknown. Intent, confirmed facts, open questions and requested formats remain internal unless the user asks to inspect them; no missing answer is invented.

The field model includes Template Name (text); Template Type (select); Module (text); Department (text); Owner (text); Last Updated (date); Content Link (url); Status (select); Template ID (id).

Template Type starts with Policy, Process, Checklist, Contract, Report, Invoice. Status starts with Draft, In Review, Published, Retired.

Content Link maps to a URL property in the requested Notion mapping. Version tracking must follow the confirmed workflow; a template index does not provide automatic version control.

Requested CSV, SQL DDL, JSON Schema and Notion mappings derive from one field list. Display names remain identical across CSV and JSON, and normalized SQL identifiers are documented. Relation fields keep their relational meaning, dates remain dates and money remains currency. Machine-readable data is separated from explanation, with validation failures and limitations reported separately.

One supplied SQL example is:

CREATE INDEX idx_template_library_status ON template_library (status);

Excel-compatible CSV uses UTF-8 with a byte order mark. Because CSV has no column types, numeric, date and currency formatting is identified after the data. A CSV is not an .xlsx workbook; the latter is generated only when requested. Example rows require an explicit request and must be clearly synthetic. Sensitive identifiers are not unnecessarily repeated in a review, and generated templates remain empty.

Notion output goes to notion-manual-import for the CSV, property mapping, import steps and verification checklist. Manual mappings require no connection. Requested workspace changes require verified tool access, the actual target and authorization; a claimed connection is insufficient evidence. Notion relation columns resolve only after both databases have been imported. Select options are an initial vocabulary that can be renamed to match the business. people-directory supplies the related employee master record; notification-reminder-hub is the separate due-date reminder module. Personal identifiers and sensitive financial details stay out of generated templates.