Introduction
What Integrity is, who it's for, and how it's structured
What is Integrity?
Integrity is a requirements management platform for teams building safety-critical systems. It gives you structured data, traceability links, version history, and formal review workflows — everything you need for standards like EN 50128, ISO 26262, and DO-178C.
Let's walk through the app.
The Dashboard
When you open a workspace, you land on the Dashboard — your home base.
ACME Engineering- Dashboard — stats cards and an activity chart: visits, changes, approvals at a glance
- Inbox — your notifications: access requests, @mentions, review updates
- Reviews — artefacts waiting for your approval
- Recent — jump back to sources you were working on
The dashboard gives you an overview — click Inbox or Reviews in the left rail to see them in full.
You can be a member of multiple workspaces, and each workspace has its own roles: Admin, Editor, Viewer. Data is completely isolated between workspaces.
The Source Library
Click the Library icon in the left rail to open the Source Library — the core of Integrity. This is where all your structured data lives.
ACME Engineering- Source Library — the sidebar tree of folders and sources
- Source — a table with its own schema, holding artefacts as rows
- Artefact — a single row: one requirement, test case, or hazard entry
Each artefact has a unique identifier (e.g., REQ-001) that's set at creation and never changes, field values based on the source schema, version history, and traceability links to artefacts in other sources.
Artefact identifiers are immutable. Once you name it REQ-001, it stays REQ-001 forever. This guarantees reliable traceability and import sync matching.
The sidebar organises sources into folders:
- Folders group related sources (e.g., "Requirements", "Verification")
- Sources define their own columns and hold artefacts as rows
- Views are saved filters on a source — a different lens on the same data
Fields
Fields are the columns that define a source's schema. Each column you see in a source table is a field:
ACME EngineeringIntegrity supports these field types:
| Type | Description | Example |
|---|---|---|
Text | Short or long text content, descriptions, titles | System shall provide... |
Numbers | Numeric values including integers and decimals | 42 |
Select | Single choice from a predefined list of options | Approved |
Multi-select | Multiple choices from a predefined list | SafetyPerformance |
Date | Date values for deadlines, milestones, etc. | Jan 15, 2024 |
Checkbox | True/false toggle for binary states | YesNo |
People | Team member assignments and mentions | JJaneBBob |
Traceability Links
The core differentiator. Artefacts can be linked across sources to form a traceability web. You create links through relation columns — each column is bound to a specific link type and target source, so your traceability structure is defined at the schema level.
Integrity ships with three built-in link types for systems engineering traceability:
Evidence demonstrates requirement is met
"Emergency brake test at 120 km/h" verifies "Brake response < 150ms"
Detailed elaboration of parent
"CAN bus message format for brake signal" refines "Brake-by-wire communication protocol"
Safety measure reduces hazard risk
"Redundant brake pressure sensor" mitigates "Single sensor failure causes undetected brake loss"
Here's what a traceability graph looks like — test points on the left link to safety requirements in the middle, which all converge on a single hazard:
Fault injection on brake command path
Threshold crossing with driver demand
Unlock signal while traction request active
Loss-of-command fail-safe validation
Train protection path shall issue brake request
Door-safe state required before traction enable
Brake controller defaults to safe state
Potential uncontrolled movement while unsafe state exists
Links are directed — each one has a clear source and target — but visible from both sides. Create a "Verifies" link from TST-001 to REQ-001, and REQ-001 automatically shows "Verified by TST-001". Every link change creates a new artefact version, giving you a full audit trail of when traceability was established and by whom.
Open any artefact's Links tab to see its relationships as an interactive graph — click nodes to expand their connections, double-click to navigate. See Links Graph.
Version History & Reviews
Every Change is Tracked
Every time you edit a field value and save, Integrity creates a new version with a timestamp and author. You can:
- View the full history of any artefact
- Compare any two versions side by side (diff view)
- Restore a previous version (creates a new version, like Git revert)
ACME EngineeringFormal Reviews
Artefacts without reviewers are auto-approved. Once you assign a reviewer, the artefact moves to Pending Review and needs explicit approval. Editing any field creates a new version — and all previous approvals are invalidated, sending the artefact back to Pending Review.
Watch the lifecycle unfold:
Baselines
A baseline captures a point-in-time snapshot of approved artefacts across multiple sources — like tagging a release in Git.
Baselines start as drafts: you select which sources to include, and Integrity checks each artefact's approval status. Approved artefacts are captured with their exact version; artefacts still in review are skipped — with the reason recorded for your audit trail.
When you're satisfied, lock the baseline. Locked baselines are immutable and can never be deleted — giving you a permanent record for release milestones, audits, and regulatory submissions.
What's Included
Source Library
Sources, artefacts, fields, folders, views, import/export
Traceability
Link artefacts across sources with typed traceability links
Reviews & Baselines
Formal approval workflows and release snapshots
Version History
Automatic versioning, diffs, and restore
Collaboration
Comments, @mentions, activity feeds, inbox
Permissions
Roles, restricted sources, access requests
Next Steps
- Source Library — Create sources, define fields, and manage artefacts
- Traceability Links — Link artefacts across sources and visualise the graph