OPTIMIZED COREEVIDENCE, ENGINEERED.

How it works

How our products keep evidence.

Every material fact is stored with four answers: where it came from, when it was observed, who reviewed it, and what changed afterwards. This page explains each step with an example and describes how a pilot is agreed.

  1. Source

    Identify the origin and time of an observation. Example: an estimated arrival taken from an arrival notice, page 1.

  2. Record

    Connect relevant information without losing its context. Example: observed at 11:05, recorded at 11:07, linked to the shipment.

  3. Review

    Make uncertainty and the human review step explicit. Example: an operator approves the extracted date, and the approval is stored with it.

  4. Decision

    Agree what must be retained to examine a decision later. Example: the earlier date is kept and marked as superseded, not overwritten.

The same four answers in each product

Preserve the signal and the source context used in the analysis.KANDOR CORE
Keep the document, supplied event or operator entry behind a shipment update in view.MERIDIAN
Preserve the initial account and distinguish it from subsequent assessments.SENTINEL CORE
Keep the source content, campaign context and intended audience together.OCM
Make the member's identity, purpose and responsible owner clear.OCHRE
Make the material used for assistance and its purpose understandable.PARAF
Keep source references beside the information they support, so a reviewer can return to the original context.QUESTER
Clarify why an exchange is needed and the information relevant to it.NEW ERA OF PRIVACY

Working with us

A pilot in three steps.

No data is shared and nothing changes in your operation before scope and readiness are agreed.

  1. Talk

    A first conversation establishes fit: your team, the workflow and the questions a pilot must answer.

  2. Agree

    We agree sources, permissions, review steps, retention, access boundaries and success criteria in writing.

  3. Evaluate

    A bounded pilot runs beside your existing tools, read-only where possible, with a defined way back.

Working with us

Define the evaluation before access.

An initial conversation establishes fit. The next step is an agreed workflow, evidence requirements and readiness review.

Discuss a pilot
  • Sources, permissions and data scope
  • Human review, retention and outputs
  • Access boundaries, recovery and ownership
  • Success criteria and acceptance evidence

Security and control

The same controls in every product.

Every product is built on the same six controls. Implementation details are shared under agreement, not published.

  • Each organisation’s data is kept separate.
  • Roles limit what each person can see and do.
  • Sign-in requires a second factor.
  • Every material action is logged and attributable.
  • Exports are controlled and recorded.
  • Offboarding and retention are defined before access.

Ask for the security summary relevant to your pilot.

What we do not publish

  • Customer names and pilot results, unless the organisation agrees to publication.
  • Internal architecture, data sources and detection methods. These are shared under agreement.
  • Performance figures without an agreed baseline and measurement method.

Start with one workflow.

Describe your team and the workflow you want to evaluate, with an anonymised example if you like. We discuss scope, connections and readiness before any data is shared.

Discuss a pilotTechnical evaluationPartnership discussion

JPH van Mastrigt · Founder & Technical Director