Memory Layer by KARL Core

A connected, verifiable business memory

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.

A document, its versions and an approvalThe document enters the record. In this example, the first version of the contract is kept. The document changes. A new version is kept, linked to the previous version. The approval joins the right version. The recorded approval is linked to version 2 of the contract.v1ContractVersion 1Version 1ApprovalRecord
The document enters the record.

In this example, the first version of the contract is kept.

Interactive diagramFictional example · Simulation

Keep content and its context

  1. Version documents and attachments

    Retain successive document versions and the files linked to them. Each recorded version remains identifiable.

  2. Connect the information

    Link a document, a source, an event and a recorded approval. Follow those links to understand what a decision was based on.

  3. Trace operations

    Use the signed journal to examine recorded actions and check the continuity of the retained history.

KARL Graph Engine · KTL + KTQ

Query the memory. Compose a business record.

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

Memory governed by your business

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.

Connect your applications to this memory

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.

Find what was recorded

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
Illustrated history

Example of history applied to this page.

  1. 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.

  2. Section added

    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.

  3. Document linked

    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.

  4. Sentence changed

    The presentation pages use more familiar words.

    The comparison below shows the home-page sentence before and after this change.

    See the changed sentence

    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.
  5. Illustration added

    Illustrations explain levels, versions and links between documents.

    They support the explanations in this preview.