Source & Artefact Kinds
Classify sources and artefacts with workspace-owned kind metadata.
Kinds describe what a Source Library item represents.
- A source kind classifies a source, such as Requirement Set, Hazard Log, Verification Set, Evidence Register, Decision Log, Glossary, Standard, or Generic Source.
- An artefact kind classifies a row, such as Requirement, Heading, Clause, Obligation, Hazard, Verification Case, Evidence, Decision, Definition, or Note.
Kinds are product metadata. They do not add fields, change source permissions, create review workflows, or replace your source's column schema. Use Fields for the data you need to capture on each artefact.
Spec-Driven Development lifecycle records use their own feature, spec, plan, task, build note, proposal, and export states. Source and artefact kinds apply only to Source Library sources and artefacts.
View kinds
Anyone with access to a source can read its kind metadata.
Source kinds appear in Source Library navigation, folder contents, source headers, and source settings. Artefact kinds appear in the artefact table, detail header, edit sheet, activity feed, and Kind filter.
Create a source with a kind
When you create an empty source, choose the source kind that best describes the collection. If you do not choose a specific kind, Integrity uses Generic Source.
You can change the source kind later if you can manage that source.
Change a source kind
Source Managers and workspace governance actors can change a source's kind from source settings.
- Open the source.
- Open Settings.
- In General, choose a value from Source kind.
- Save the settings.
Changing a source kind does not rename the source, change its identifier prefix, alter fields, or change visibility. Integrity records the change in source history with stable kind keys and readable labels.
Set an artefact kind
Editors can set an explicit artefact kind from the artefact edit sheet.
- Open an artefact.
- Open the edit sheet.
- Choose Artefact kind.
- Save the artefact.
Choose Inherit source default when the row should use the default artefact kind for its source.
| Source kind | Default artefact kind |
|---|---|
| Requirement Set | Requirement |
| Hazard Log | Hazard |
| Verification Set | Verification Case |
| Evidence Register | Evidence |
| Decision Log | Decision |
| Glossary | Definition |
| Standard | Clause |
| Generic Source or unknown source kind | Note |
Changing only the artefact kind is a metadata change. It appears in the activity feed, but it does not create a content version or reset approvals.
Filter by artefact kind
Use the artefact table's Kind filter to find rows by their effective artefact kind. The filter includes rows with explicit kind metadata and rows that inherit their source default.
For example, filtering by Requirement includes explicit Requirement rows and rows in a Requirement Set that inherit the source default.
Understand disabled kinds
The workspace kind vocabulary is admin-owned configuration. Built-in kind keys stay stable so imports, exports, traceability, templates, and activity history can keep referring to the same meaning even if labels change.
When a kind is disabled or archived, existing sources and artefacts can still display the historical label. Disabled or archived kinds are not treated as normal choices for new assignments, but they remain readable so old records do not lose context.
FAQ
Is a kind the same as a field?
No. A kind says what the source or row represents. Fields define the columns and values inside a source.
Why does an artefact inherit its source default?
Most sources contain one primary row type. Inheritance keeps those rows easy to classify without forcing editors to set the same artefact kind on every row.
Can a source contain mixed artefact kinds?
Yes. Leave ordinary rows inherited, then set explicit artefact kinds for exceptions such as headings, clauses, obligations, notes, or evidence rows.
Do kinds control traceability rules?
Not directly. Kinds give downstream traceability and import features a stable vocabulary to build on, but they do not enforce relationship rules by themselves.