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.
Memory Layer by KARL Core
KARL Core retains immutable versions, links documents to events and decisions, and records operations in a signed journal. Your applications can retrieve both retained content and its recorded context.
In this example, the first version of the contract is kept.
Retain successive document versions and the files linked to them. Each recorded version remains identifiable.
Link a document, a source, an event and a recorded approval. Follow those links to understand what a decision was based on.
Use the signed journal to examine recorded actions and check the continuity of the retained history.
KARL Graph Engine · KTL + KTQ
KTQ retrieves states, follows relationships and compares versions in the memory. KTL composes these queries into typed, versioned business functions that your applications can reuse.
KTL and KTQ 0.2 are experimental. Business functions and sources to connect need to be scoped during the pilot.
Prototype · Early Adopter — Explore KARL Core’s capabilities with KARL Graph Engine. Contact us to test
Identities, access permissions and policies determine who can read, add or use data. Organisation spaces are isolated and control decisions are traceable.
KARL Core runs on infrastructure chosen by your business. Storage and interfaces are configured with your team for the applications to connect and information to retain.
REST, JSON-RPC and gRPC APIs let applications record and retrieve authorised data. Connectors build the memory from tools your teams already use.
A document record, software project or artificial intelligence workflow can retain its versions and sources. Links must be recorded by the application or connector before they can be retrieved.
Would you like to replicate data, retain its history or share a verifiable record? Tell us about your project.
Let’s discuss your projectExample 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.