Examples

Examples from your work

Choose a situation: finding a document, preparing for an audit or explaining a decision.

Explore industriesSee everyday situations
Different situations around the same recordA retained version, a date to examine, a recorded approval and a record to share. The examples below explain these situations.DateRecordVersionApprovalShare
One record, different situations.Explanatory diagram

Business needs · KTL and KTQ

A shared memory. Questions specific to each business.

Choose a domain to see which sources to connect, the question asked with KTQ and the record composed with KTL.

Healthcare & researchRecover the record known when a decision was made.
Clinical reportProtocolDecision
KTQ
Which report and protocol versions were known at that date? Which analyses relate to a correction?
KTL
Combine the timeline, sources and affected analyses in a reusable record-review function.

Expected outcome: A review record separating initial information from subsequent corrections.

Healthcare professionals use retained sources within their authorised scope to review the record.

Finance & bankingExplain why a closing result changed.
EntriesCalculationClose
KTQ
Which entries were known at close? Which amounts and supporting documents differ after corrections?
KTL
Compose queries, aggregations and differences in a versioned reconciliation function.

Expected outcome: An explainable reconciliation linked to the entries and calculation versions used.

Currencies, rounding and accounting rules are defined in the domain model.

Audit & internal controlSubstantiate a control at the audit date.
RequirementControlEvidence
KTQ
Which controls linked each requirement to supporting evidence? What is missing in the reviewed scope?
KTL
Combine coverage, control results and related documents in an audit-preparation function.

Expected outcome: A working file separating documented controls, gaps and unavailable information.

Document selection prepares the auditor’s review. Evidence Pack provides a signed record for sharing.

InsuranceReconstruct the documents in a claim file.
PolicyClaimAssessment
KTQ
Which policy version applied? Which documents were available before the claim-handling decision?
KTL
Group the policy, document timeline and assessment reports in a claim-review function.

Expected outcome: A sourced timeline to explain claim handling and review a dispute.

The handler uses dated documents to assess coverage and explain the decision.

Industry & supply chainIdentify batches affected by a change.
ComponentBatchDelivery
KTQ
Which batches and equipment are linked to this component version during the relevant period?
KTL
Combine dependencies, affected batches and quality checks in an impact-analysis function.

Expected outcome: An investigation scope linked to recorded components and deliveries.

Coverage depends on traceability links actually supplied by business systems.

Construction & engineeringFind which drawing supported an acceptance.
DrawingWorkAcceptance
KTQ
Which drawing revision was linked to the work? Which defects and photos accompanied acceptance?
KTL
Gather drawings, work records, defects and dated documents in a site-review function.

Expected outcome: An acceptance file tracing the versions used and the recorded defects.

Each document remains linked to its source and construction-site scope.

Public sectorRecover the documents behind a decision.
Case fileApprovalDecision
KTQ
Which documents, approvals and reference versions were known during the review?
KTL
Compose the review path, references and missing documents in a review function.

Expected outcome: A history accessible to authorized reviewers handling an appeal or an inspection.

Disclosure and retention rules are defined by the organization.

IT, cybersecurity & MSPsUnderstand what a change affected.
ChangeServiceIncident
KTQ
Which services depended on the changed component? Which configurations and transitions were recorded around the incident?
KTL
Combine impact, dependencies and recovery-test results in an incident-review function.

Expected outcome: An investigation and recovery-planning file with known dependencies and tests.

Recorded links and dates guide the investigation; the technical team analyses causes and validates actions.

Illustrative scenarios to adapt to your sources and business rules. KTL and KTQ 0.2 are experimental; sector-specific integrations and functions need to be built and validated during the pilot.

Prototype · Early Adopter — Explore KARL Core’s capabilities with KARL Graph Engine. Contact us to test

Contact us to testUnderstand KTL and KTQSee everyday situations

Example uses. What you can retrieve depends on what was recorded and how the software is connected to your tools.

Find a document

The document was renamed. How can we find its history?

A drawing was moved to another folder and then renamed. You want to find the right document and its earlier versions.

A renamed documentPlan APlan BOld nameNew name
A fictional example to explain this situation.

What you can find or check

The document, its earlier versions, and recorded changes to its name, folder or links to another tool.

With KARL Core

In practice: Applications and connectors record links between tools to follow a document through its changes.

Read the technical explanations

Source article in French: Un document change de nom. Son histoire doit rester lisible.

Choose another example

Prepare for an audit

What was in this file at the date under review?

An auditor asks what was in a file at a particular date, such as the day a contract was accepted.

A record at a given dateDateRecordItems kept at that date
A fictional example to explain this situation.

What you can find or check

The versions kept and the actions recorded, along with their supporting documents. The selected items can be brought together in a record to share.

With KARL Core, Evidence Pack

In practice: The record brings together retained documents and versions for the auditor’s review of a defined scope.

Read the technical explanations

Source article in French: La preuve qui se vérifie sans vous : la vérification hors ligne de KARL Core

Source article in French: Du premier bug à la vérification chez le client : l’histoire d’une livraison S3Guardian

Choose another example

Find a decision

The contract has changed. Which version was accepted?

There are several versions of a contract. You want to find the one that was agreed, rather than just the latest change.

The agreed versionv1v2ApprovalrecordedChangedlater
A fictional example to explain this situation.

What you can find or check

The relevant version, the recorded approval and the information kept when that approval was given.

With KARL Core

In practice: Each recorded approval is linked to the relevant version, its context and date.

Read the technical explanations

Source article in French: La preuve qui se vérifie sans vous : la vérification hors ligne de KARL Core

Source article in French: Du premier bug à la vérification chez le client : l’histoire d’une livraison S3Guardian

Choose another example

Have a record checked

Can an auditor check the record without connecting to our servers?

You send a record to an auditor or a partner. They want to check that the items received have not changed since it was prepared.

A record to checkRecordReceivedTools and information needed
A fictional example to explain this situation.

What you can find or check

The recipient can check that the items received have not changed since the record was prepared, along with the links kept between them.

With Evidence Pack

In practice: Verification covers the integrity of included files and their signature. The recipient uses the record, the verifier and public keys received through a trusted channel.

Read the technical explanations

Source article in French: La preuve qui se vérifie sans vous : la vérification hors ligne de KARL Core

Source article in French: Du premier bug à la vérification chez le client : l’histoire d’une livraison S3Guardian

Choose another example

Find the documents used by AI

Which documents did the AI use for this answer?

An AI answer needs to be reviewed later. You want to find the documents used at that time, rather than today’s versions.

The sources of an AI answerv1v2AnswerSourceslinked
A fictional example to explain this situation.

What you can find or check

The documents used and their versions, with the links recorded for that answer.

With KARL Core

In practice: The AI application records the references and versions used in KARL Core. Your team can consult them to review the answer in context.

Read the technical explanations

Source article in French: La preuve qui se vérifie sans vous : la vérification hors ligne de KARL Core

Choose another example

Choose a version after an incident

Why choose this version after an incident?

After an incident, you have several versions of your data to choose from. Before putting them back into use, you want to understand what happened and explain your choice.

After an incidentv1v2v3BeforeAfterVersions to examine
A fictional example to explain this situation.

What you can find or check

The versions kept and the information recorded about them: what changed, the people or accounts involved, the rules in place and the supporting documents.

With KARL Core

In practice: The retained history helps your team choose a version, document its analysis and prepare checks before returning it to use.

Read the technical explanations

Source article in French: Restaurable ne veut pas dire fiable

Choose another example

Check changes before copying them

Should this deletion also be applied to the other copy?

Files are being deleted unexpectedly where you keep the originals. You need to decide whether the same deletion should affect the other copy.

A copy to reviewFilesCopyChangeOther copyReview before copying
A fictional example to explain this situation.

What you can find or check

The changes held for review and the available information for deciding whether to apply them to the other copy, under the rules you chose.

With S3Guardian

In practice: Profile rules, access rights and the approval workflow govern replication. An evaluation on your storage helps prepare protection for the secondary copy.

Choose another example

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.