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.
How it works
How the software works with your documents
The software runs on the servers your company uses. Your team chooses which documents to follow, who can access them and which checks to perform.
Keep the selected documents.
This example starts with the documents the business wants to follow.
The memory layer, simply
Recover the facts, their links and their history.
A document changes, an approval arrives, a decision is made. Memory Layer by KARL Core connects their versions to recover what was known and which sources were used.
- 01 · Collect
Your business sources
Documents, events, approvals and decisions from your applications.
DMS · ERP · business tools - 02 · Retain and connect
KARL Core
Versioned objects, dated relationships and identified sources.
Versions and eventsRelationships and contextDates and provenance - 03 · Query
KTQ + KTL
KTQ retrieves and compares. KTL composes these queries into a reusable business function.
Executed by KARL Graph Engine - 04 · Use
An explained result
A record, table or graph linked to the versions consulted, with its sources and scope.
For your teams, applications and AI agents
KTQ · KARL Temporal Query
Ask a precise question: recover a state, follow a relationship, compare two dates or aggregate values.
“Which documents were known when this decision was made?”KTL · KARL Temporal Language
Compose multiple KTQ queries into typed, versioned functions that applications can reuse.
Combine documents, a timeline and differences in a review record.Prototype · Early Adopter — Explore KARL Core’s capabilities with KARL Graph Engine. Contact us to test
One business date. Two states of knowledge.
Fictional example: a procedure is corrected after a decision, with an earlier effective date.
- Procedure v1 recorded
It applies from June 10.
- A decision is made
The team knows version v1.
- Correction v2 recorded
Its declared effective date is June 11.
The effective date and the recording date answer different questions. The result depends on available history and declared dates.
Results use retained, authorised sources. Evidence Pack complements this traceability with a signed record that can be verified offline.
Four different roles
Keep your documents
Your company continues to use its chosen storage systems. The IT team checks that the software can work with them.
Find earlier versions
KARL Core keeps recorded versions and links so you can examine a record at an earlier date.
Replicate and protect data
S3Guardian replicates between S3 storage and NFS/SMB shares, with incremental transfers and protective controls.
Share a record for checking
Evidence Pack prepares the selected records for someone else to examine without accessing your servers.
What your team decides before installation
Which documents need to be followed? Who can view them? How long should they be kept? What needs to be recovered after an incident? These choices determine what the software needs to do.
A demonstration should show a complete example: a document added, changed, found at a chosen date and then shared if that is part of your need. It presents the sources used, the versions retrieved and the scope of the result.
Let’s discuss your needs.
Would you like to replicate data, retain its history or share a verifiable record? Tell us about your project.
Let’s discuss your project