Source Templates
Start new sources from workspace-managed schemas for common regulated workflows.
A source template is a reusable starting schema for a source: it sets the source kind, an identifier prefix, and a ready-made set of fields. Instead of building a Hazard Log or a Requirements source column by column every time, you apply a template and get a source that is already shaped for the work.
Every workspace starts with a catalog of built-in templates for common regulated-engineering sources. Workspace admins can enable or disable them, duplicate them, and create their own custom templates.
Source templates are not Spec-Driven Development lifecycle templates. They only create Source Library sources and fields. Feature, Spec, Plan, Task, Build Note, and Change Proposal records belong to Spec-Driven Development and have their own grammar.
Built-in templates
Each workspace is seeded with these built-in templates, enabled by default:
| Template | Source kind | Prefix | What it captures |
|---|---|---|---|
| Requirements | Requirement Set | REQ | Requirement, status, priority, rationale, owner, source reference |
| Stakeholder Requirements | Requirement Set | STK | Need, stakeholder, priority, rationale, status, owner |
| System Requirements | Requirement Set | SYS | Requirement, verification method, status, priority, owner, rationale |
| Hazard Log | Hazard Log | HAZ | Hazard, cause, effect, severity, probability, risk level, mitigation, status, owner |
| Verification Cases | Verification Set | VER | Verification case, method, acceptance criteria, status, owner, evidence reference |
| Evidence Register | Evidence Register | EVD | Evidence item, type, result, collected-on date, owner, reference |
| Decision Log | Decision Log | DEC | Decision, status, rationale, alternatives, decided-on date, owner |
| Glossary | Glossary | TERM | Term, definition, acronym, domain, status |
| Standards Register | Standard | STD | Clause, clause text, obligation type, applicability, notes |
Built-in templates are read-only schema definitions. To change one, duplicate it into a custom template and edit the copy. The source kind comes from your workspace kind vocabulary; the fields use the standard field types.
Apply a template when creating a source
Apply a template from the Source Library create flow:
- In the Source Library sidebar, open + → Add to Source Library.
- Choose Templates and browse the gallery. Use the search box to filter by title, description, source kind, or prefix.
- Click a template to open its review step. It shows the source kind, identifier prefix, field count, and the fields the source will get.
- Enter a Source name and click Create source.
The new source appears in the sidebar without a reload, with its template fields in order, its identifier prefix, and its source kind already set.
In this version, applying a template is workspace admin only. Applying a template assigns a non-generic source kind and identifier prefix, which Integrity keeps under admin control. Editors and viewers can browse enabled templates but cannot create a source from one yet.
Only enabled templates whose source kind is enabled appear in the gallery. If a template's source kind is disabled or archived, the template is hidden from the create flow until the kind is re-enabled.
View the template catalog
Open Workspace Settings → Source Library → Templates to see the catalog. It lists every template with its title, source kind badge, field count, identifier prefix, and on/off state, grouped into Built-in and Custom.
Non-admin members see the catalog read-only: the on/off state is shown as the same slider admins use, but it is disabled. There is no New template button, no row actions, and no archived section.
A template whose source kind has been disabled shows an amber Source kind disabled warning so admins know why it is unavailable for new sources.
Enable or disable a template
In Workspace Settings → Source Library → Templates, use a row's on/off toggle to enable or disable it. Disabled templates stay in the catalog but no longer appear in the create flow. Disabling does not affect sources that were already created from the template.
Duplicate a built-in template
To customize a built-in, duplicate it and edit the copy:
- In the Templates tab, open the built-in's ⋯ menu.
- Choose Duplicate. A new editable custom template appears under Custom (for example, Requirements Copy).
- Edit the copy as described below.
The original built-in is unchanged. Duplicating is the supported way to adjust a built-in's fields, because built-in schemas themselves are read-only.
Create a custom template
- In the Templates tab, click New template. This opens the full-page template editor.
- Set a Title, Source kind, and Identifier prefix (1–5 uppercase letters or numbers, such as
RISK). - Add fields. For each field choose a type (text, number, select, multiselect, date, boolean, or people) and optionally mark it required or long text.
- For select and multiselect fields, add options and give each one a color from the standard option palette.
- Drag fields to set their order.
- Watch the live Summary panel on the right update as you edit — source kind badge, example identifier (such as
RISK-001), and the fields in order. - Click Create template.
The editor blocks saving with inline errors — for example, Name your field. or Add at least one option. — until the schema is valid.
Leaving the description blank is fine. The catalog and editor show a muted No description placeholder, but nothing is written to the description — re-opening the editor shows an empty description field.
Edit a custom template
Open a custom template's ⋯ → Edit to change its title, description, source kind, prefix, fields, options, required/long-text flags, and field order. Click Save changes.
Editing a template only changes the template. Sources that were already created from it keep their own fields and are not modified.
Archive or restore a custom template
Custom templates are archived rather than deleted, so the catalog stays clean without losing history:
- ⋯ → Archive removes the template from the create flow immediately and moves it into the collapsible Archived section.
- Expand Archived and choose ⋯ → Restore to return a template to Custom.
Built-in templates cannot be archived — disable them instead.
How applying a template works
Applying a template runs through a single transactional step on the server. In one operation it creates the source, copies the template's fields into it in order, sets the identifier prefix and default column layout, and writes two source history events: Source created and Template applied. If any step fails — a disabled template, a disabled source kind, an invalid folder — the whole operation rolls back and no partial source is left behind.
The Template applied event in the source's History shows which template was used, along with the source kind, prefix, and field count, so an auditor can later see how the source was initialized.
Template catalog changes (enable, disable, duplicate, create, edit, archive) are recorded in Workspace Settings → Logs and broadcast in real time, so the create flow and the settings tab refresh without a reload.
FAQ
Is a template the same as a source kind?
No. A source kind classifies what a source represents. A template is a starting schema that sets a source kind and adds fields. Many templates can target the same source kind — the three requirements templates all create Requirement Set sources with different field sets.
Can I change a built-in template's fields?
Not directly — built-in schemas are read-only. Duplicate the built-in and edit the custom copy, or disable the built-in and use your own.
What happens to existing sources if I change or disable a template?
Nothing. A template is only a starting point. Once a source is created, it owns its own fields. Editing, disabling, or archiving the template never changes sources that were already created from it.
Why can't an editor create a source from a template?
In this version, applying a template is admin-only because it assigns a non-generic source kind and identifier prefix, which Integrity keeps under workspace-admin control. Editors can still create empty sources and add fields themselves.
Do templates create starter rows?
No. Applying a template sets up the source and its fields. It does not add artefact rows — that is content you create or import afterward.