System labels · no recipe

Same engine.
Other packs.

The L2 demo is one configuration. Underneath sit channels, an evidence graph and a pack stack. In your project, sources and norm reference change, but not the way gaps are found and sealed.

This page shows layers and data flow. We do not publish the rule catalogue, pack contents or internal details.

Data flow

Where viprove sits

One channel is already connected, a second is planned, and your test runs are added. All data ends up in one shared graph.

Today, evidence links are often assembled by hand, just before the assessment. The graph is designed to check links when an artifact is created and again whenever it changes — as part of everyday development, not only before the assessment.

Channel 1 connected

OEM / ALM

ALM Requirements and traceability

HARA · SG ASIL / FTTI

SYS · SWE Goals and requirements

GenAI

.xosc Scenario proposals

Channel 2 planned

ENVITED Pack

EVES Pack structure

.xosc · Map · Trace Quality and V&V

Run data own source

SiL / HiL / CI

Run Result PASS / FAIL, level

Deterministic gap analysis

Step 1

Evidence graph

All sources are merged into one typed graph.

Type pack

Step 2

Analyze

The engine checks whether every obligation is met by evidence.

Grammar + Domain no LLM in the verdict

Step 3

Seal

The result is hashed and can be reproduced at any time.

Cadence not a certificate · not a release

Output

The assessor receives the seal

Your artifacts stay with you.

connected planned

Pack stack

The pack stack

Same engine for L2 and robotics — the layers above change with the project.

Connectors

Your tools stay the source

Artifacts are read where they are created.

Type pack

Vocabulary

Defines which nodes and edges exist.

Grammar pack

Rules

Defines which obligations apply to that vocabulary.

Domain pack

Norm reference

Defines which norm reference sharpens the check.

Cadence

Two cadences in the seal

Check and seal

The engine builds the graph, finds the gaps and seals the result — for L2 just as for robotics.

Cadence

Two cadences

The seal contains two records. They show whether your project has changed or the basis for evaluation. Across several seal records, this produces a history rather than a single snapshot.

Rule state

Rare

If this hash changes, the basis of assessment has changed.

Project state

Often

If this hash changes, your project has changed.

Time →

viprove seal

Rule state grammar…a3f

Project state 868ac61b…

not a certificate · not a release

What the assessor gets

The sealed evidence excerpt of the L2 demo, exactly as an assessor receives it.

View the evidence excerpt →

Second instance: robotics

The same pattern with a different norm reference: performance levels instead of ASIL.

To the robotics demo →

Your project

In the Reality Check we clarify together whether viprove fits your project.

Request a Reality Check →