This guide brings together technical information from the presentation pages. It retains the original explanations; exact conditions must be checked for each installation.
Which software fits your needs?
Recover a history, govern replication or share a verifiable record: choose your starting point.
| Your need | Component | What it provides |
|---|---|---|
| Recover a past state | KARL Core | Versions, events and relationships between governed records. |
| Decide before replication | S3Guardian | Control policies, suspicious operations held for review and approval. |
| Share verifiable memory | Evidence Pack | A portable export of the selected scope and offline verification. |
Modules in the KARL family
KARL Audit
Integrity checks and preparation of audit records. This scope does not replace an assessment of applicable obligations.KARL IA Studio · Compass · Forge
Document memory and ingestion for AI use cases. Context traceability is distinct from the accuracy of a generated answer.KARL Media · Transit · Connecteurs
Field capture, data flows and document ingestion. Connectors, formats and capture options need to be qualified for your environment.Retrieve a record as it stood on a given date
KARL Core organises versions, events and relationships between your data. You can recover a past state and the recorded context around a decision.
A history you can explore.
Retain each state
Successive document states are linked in a temporal memory rather than treated as an isolated current file.
Retrieve a past state
A temporal query retrieves the state corresponding to the chosen point within the governed history.
Examine the context
Recorded relationships, policies and decisions help explain the history of the record.
This is infrastructure software, deployed in your environment and backed by your S3-compatible storage. Application and team access are part of the scoping work.
Use cases range from a record’s history to document memory supplied to an AI application. Consulted records and their versions can be linked to the recorded execution.
Export a scope with Evidence PackWhat we qualify with you
Where will it run?
The public deployment formats include a Linux binary, container image and Debian/Ubuntu package. The supported version and packaging for your environment must be confirmed during evaluation.
What should an evaluation establish?
A defined corpus, a sequence of changes, a past-state recovery and, where needed, an independently verified export. Access rights, retention policies and recovery conditions must be included.
A suspicious change?
Decide before replicating it.
S3Guardian adds control between your primary S3 storage and its secondary. Operations considered suspicious can be held for approval.
From a detected change to a decision.
Inventory
Examine the primary storage and compare objects, versions and metadata.
Apply policies
Identify relevant changes and anomalies using the configured rules.
Hold suspicious operations
Route the operations requiring a decision to the pending-changes scope.
Review
The operator examines the changes before authorising their propagation.
Restore and verify
Test recovery in a clean target and check the integrity and usability of the selected data.
An evaluation on your topology.
We start with your buckets, volumes, permissions and relevant scenarios. The aim is to observe the expected behaviour, rather than infer universal protection from a demonstration.
Scope the endpoints
Check S3 features, permissions, versions and native protections.
Exercise the scenarios
Test renames, bulk deletions and suspicious modifications on a controlled scope.
Document the result
Record what was detected, what was held, who approved it and what recovery actually restored.
Compatibility and limits
ETags, multipart operations, encryption and copy features vary between storage systems. Comparison and recovery mechanisms must be qualified on the selected providers.
The health of a recovery depends on its checks, scope and deployed protections. Heuristic detection is not a guarantee that every attack will be detected.
A record to share.
A history to verify.
An Evidence Pack exports the history you select. The recipient can check its integrity without accessing the original service.
What you share
The pack organises the states, relationships and evidence included in its export. The selected scope determines what it can be used to examine.
Verification requires the pack, a compatible verifier and the necessary trust material, including the appropriate public keys. These elements must be retainable independently of the service.
Define the scope
Select the record, decision or project phase to export.
Keep the trust material
Retain the keys and compatible verification rules through an appropriate channel.
Verify independently
Check the exported state and report the result within the declared scope.
What must remain distinct
| What is examined | What this does not establish by itself |
|---|---|
| Pack integrity | Business accuracy of every document |
| Declared provenance and authority | Acceptance of a document by every party |
| Exported state and relationships | Events or revocations after the export |
| Exported memory scope | Automatic access to source files not included in the export |
How the software fits into your infrastructure
StratoFoundry develops infrastructure software. It uses S3-compatible storage to organise data states, control flows or prepare a verifiable export.
The architecture, in a useful order
Your existing storage
S3-compatible endpoints store the objects. Available features and permissions are qualified for the deployment.
The governed history
KARL Core records states and relationships within the governed scope. Temporal queries recover a selected past state.
Replication control
S3Guardian examines changes and applies configured policies before propagation to secondary storage.
The exported record
Evidence Pack packages the chosen memory scope for independent verification.
For the technical team
Announced formats include a Linux binary, container and Debian/Ubuntu package. CLI, TUI, REST API and web interfaces are described in the offering; their scope depends on the chosen component and edition.
Scoping covers topology, authentication, permissions, metadata, retention, recovery conditions and compatible versions. The roles of ETags and checksums must be distinguished according to upload and encryption methods.
How to verify an Evidence Pack offline
Offline verification lets a recipient examine an exported state without contacting the service that produced it. It requires the pack and the appropriate trust material.
Identify the scope
Record which data, relationships and point in time the export covers.
Obtain the required materials
Keep the pack, compatible verification software and the necessary public keys or trust roots. Obtain trust material through an appropriate channel.
Perform the checks
Use the compatible verifier to inspect signatures, integrity and relationships within the exported record.
Read the result precisely
Distinguish a verified state, a failed check, missing material and content outside the scope.
Retain the context
Keep the verification result and the materials needed to repeat the examination later.
An export does not automatically provide access to source files that were not included. It also does not describe events or revocations after its creation.
Return to Evidence PackTechnical terms,
in plain language.
A few definitions to help you read the pages and prepare a conversation with the technical team.
- S3-compatible storage
- Object storage exposed through an API compatible with the S3 protocol. Actual features vary by provider and deployment.
- Temporal memory
- An organisation of successive states and their relationships, so a chosen past state can be examined.
- Event log
- A record of the operations captured within a defined scope. Its coverage depends on what was actually recorded.
- Hash
- A computed fingerprint used to compare content. It does not establish the truth of that content.
- ETag
- An object identifier whose meaning depends on how the object was created and encrypted. It is not always a full-object checksum.
- Merkle tree
- A structure that combines fingerprints so the integrity of a collection can be checked.
- WORM / Object Lock
- Retention mechanisms that constrain modifications or deletion under configured conditions. Availability and modes must be qualified.
- PITR
- Point-in-time recovery: recovery to a selected historical state. Its validity depends on the retained states and the checks performed.
- Evidence Pack
- An export of a selected memory scope with the material used to verify its integrity and recorded relationships.
A French infrastructure software publisher
A French infrastructure software publisher based in Courbevoie. Its work focuses on data history, replication flows and the records needed to verify a file’s history.
From storage to context
A file can change content, name or location. A decision may rely on a version that later becomes hard to find. StratoFoundry develops KARL Core around this continuity: retaining the states and relationships needed to reconstruct the recorded history.
S3Guardian addresses replication control. Evidence Pack exports a defined memory scope for independent examination.
Explore the work
ChantierLink Pro × KARL Core
Connect construction documents, events and decisions in a verifiable reference record.
The record keeps the project’s thread.
NordLeadBTP brings the construction workflows of ChantierLink Pro. StratoFoundry brings KARL Core’s document memory. The joint project connects retained records to their context: project, participant, version and decision.
A change request, a revised quotation and client acceptance are distinct records. Keeping them with their relationships helps examine what was agreed, what changed and what remains pending.
From an isolated file to a shared record
Collect in context
Relate documents and observations to the relevant project and participant.
Distinguish the states
Keep a modification, a declared completion and a client approval distinct.
Export a defined scope
Prepare a record for a client, partner or expert, with the appropriate access and trust material.
What verification covers
Offline verification concerns the exported memory at its export date. It requires public keys and compatible rules. To inspect a source file’s content or compare its fingerprint, the relevant file is also needed.
This page describes a partnership and its use cases. It does not claim quantified time savings or customer results without an associated measurement protocol.
Understand Evidence Pack