Necessary storage
Your selected language is stored for twelve months. This setting and the choice made here are used only to operate this website.
Engines · Evidence & provenance
Evidence Engine
Connects sources, executions, results, approvals and artifacts into unambiguously referenced evidence packs. Provenance, integrity and domain context remain traceable throughout the evidence chain.
Engines · Orthevs
Evidence Engine as an execution mechanism
This Engine belongs to the technical target model. A concrete use needs defined inputs, supported versions, security boundaries and traceable outcomes.
Execution mission
Evidence Engine
The Evidence Engine manages evidence references together with the metadata that explains their meaning. Each record includes its source, object and version, producing run, responsible identity, time, integrity marker and associated decision. An evidence pack groups these references through a versioned manifest without conflating evidence with a conclusion. This makes clear what a validation or approval actually relies on and which evidence must be verified again later.
Architecture role
Orthevs Ecosystem
Labs and Factories provide typed evidence references as capability results instead of passing unstructured files without context. Qualification runs and Foundation releases select the required evidence and bundle it with decision references in an immutably addressed pack. Classification, access, retention and export are controlled at the applicable trust and data boundaries. Original domain responsibility for generated evidence remains with its source.
Core functions
Core functions
- Typed evidence references with mandatory context and provenance metadata
- Checksums and unique content identity for subsequent integrity verification
- Linking of source, object version, run, artifact, identity and decision
- Versioned evidence-pack manifests with fully referenced contents
- Classification, retention and access rules for sensitive evidence
- Controlled export with verifiable references for defined recipients and purposes
Control boundaries
Control boundaries
Evidence proves only what was actually measured, checked or decided within the documented scope. It does not extend the conclusion beyond that scope.
Sensitive evidence requires appropriate classification and controlled access, retention and export rules.
A valid checksum confirms integrity, not automatically the domain correctness, completeness or trustworthiness of the source.
For externally stored evidence, availability, retention responsibility and the permitted reference period must be defined explicitly.
EVE · Orthevs
Shape the target model together.
The content will be deepened step by step with concrete concepts, contracts, maturity levels and verifiable evidence.