---
title: "Safety Policy"
description: "The safety policy of Slint SC, and who is responsible for it."
---
The safety and quality of Slint SC are the primary objectives of all management, development, maintenance and support activities.

## Commitments

Each commitment names where it's implemented, so it can be checked rather than taken on trust.

* Every change follows a defined process. See [Development Process](/qualification-plan/development-process/) and [Development Phases](/qualification-plan/development-phases/).
* Every change is verified by automated tests before it's merged. See [Test Suites](/qualification-plan/test-suites/).
* Every requirement is traced to the tests that verify it. See [Traceability Matrix](/qualification-report/traceability-matrix/).
* Known safety-critical problems are recorded, with the fix and the test that covers each. See [Known Problems](/user-manual/known-problems/).
* The process and the tooling are improved as we go, and what can be automated is automated.

## Responsibilities

The administrators of the slint-ui GitHub organization are the founders of SixtyFPS GmbH.
All employees of SixtyFPS GmbH are members of the organization.
External contributors may also be invited to become members of the GitHub organization.

## Confirmation Measures

**Addresses:** ISO 26262-2 Clause 6

Confirmation measures check that the work products, the process, and the resulting safety are adequate.
Each one needs a level of independence from the people who did the work, which depends on the ASIL.

| Measure | Independence at ASIL B | Performed by |
| --- | --- | --- |
| Confirmation reviews of the work products | Not stated yet | Not decided yet |
| Functional safety audit of the process | Not stated yet | Not decided yet |
| Functional safety assessment | Not stated yet | TÜV Nord |