Document created
An initial version of this presentation brings together the software pages and the contract example.
This is the starting point of the history shown here.
Evidence Pack · Prototype
Evidence Pack brings selected items together in a sealed record. A manifest describes the files and their hashes; a signature lets recipients verify integrity and origin using trusted public keys, independently of the issuing service.
Join the Early Adopter programme to test this prototype and explore KARL Core’s capabilities with our team.
In this fictional example, two document versions are selected.
Select the documents, exports, reports or delivery files needed for the operation.
The manifest lists each file, its size and its cryptographic hash, together with the record’s context.
The evidence service seals the manifest under an identified signing policy and key.
The recipient checks the pack offline with the verifier and public trust information obtained through a reliable separate channel.
The recipient holds the files, manifest and signature. The verifier compares hashes, checks the signature and determines whether the key is trusted for the expected use. The check uses trusted public keys.
The record can be verified without network access or access to KARL Evidence. Keep the verifier and trust information so the check can be repeated later.
| Check | What is examined |
|---|---|
| File integrity | The verifier compares received files, sizes and hashes with the manifest. |
| Manifest signature | The signature binds the file inventory to the identified signing key. |
| Trusted keys | Public keys received through a trusted channel support origin verification for the expected scope and use. |
Prepare audit materials, seal a software delivery or retain incident records. The same principle applies: an explicit scope, a signed inventory and a repeatable check by the recipient.
Join the Early Adopter programme to explore KARL Core’s capabilities through this prototype. Your use case and feedback help shape its development.
Contact us to testExample of history applied to this page.
An initial version of this presentation brings together the software pages and the contract example.
This is the starting point of the history shown here.
Seven situations explain how to find a document, prepare an audit or review a decision.
Each example distinguishes what can be found from the limits that need checking.
The contract has five stages that can be explored by swiping or using the buttons.
A vertical gesture on the document still lets the page scroll normally.
The presentation pages use more familiar words.
The comparison below shows the home-page sentence before and after this change.
Before
KARL Core keeps document versions and recorded decisions. Software for businesses, installed on your servers.
After
KARL Core is software for your business. It keeps document versions and recorded approvals so you can find what changed.
Illustrations explain levels, versions and links between documents.
They support the explanations in this preview.
An initial version of this presentation brings together the software pages and the contract example.
This is the starting point of the history shown here.
Seven situations explain how to find a document, prepare an audit or review a decision.
Each example distinguishes what can be found from the limits that need checking.
The contract has five stages that can be explored by swiping or using the buttons.
A vertical gesture on the document still lets the page scroll normally.
The presentation pages use more familiar words.
The comparison below shows the home-page sentence before and after this change.
Before
KARL Core keeps document versions and recorded decisions. Software for businesses, installed on your servers.
After
KARL Core is software for your business. It keeps document versions and recorded approvals so you can find what changed.
Illustrations explain levels, versions and links between documents.
They support the explanations in this preview.
Example of history applied to this page.