Technology · Architecture

From governed evidence to scored outcomes.

Your systems stay in place and in command. Kalyr keeps the reference, provenance and permission behind every use, with predictions and observations as separate records.

Evidence referencePermissionStateSealed predictionObserved resultSettled value

The shape of it

Three planes over one moving world.

Your process keeps running. Its evidence is referenced above it, joined to where it lives. The planned learned layer sits above both, and results come back to be scored.

0 / 3 01YOUR PROCESSRunning continuously02EVIDENCE REFERENCEEach record joined to where it livesSEALED PREDICTIONCandidate A0.71Candidate B0.42Hold0.1903THE LEARNED FIELDPlanned: from scored episodesOBSERVED RESULTSCORED, REVIEWEDSIMILARITYDYNAMICSPROVENANCE · RIGHTSHUMAN REPORT
Maximum useful resolution. Minimum capture burden.

Your systems stay the source of truth and supply most of the state. People add what their systems miss, when the decision needs it.

The target loop

Eleven steps. One loop.

Each step is recorded separately, so every error traces to the step that made it. Steps marked planned are in development.

Open any step for the detail

What is built

One episode contract. A pack per decision.

One episode contract runs under every loop: keep your integration when the model or site changes. A decision-family pack carries what one decision needs, so a proven deployment repeats on the next line. You own the value contract, so you can audit every result.

Built · the same across models and sites

01
Evidence and provenanceEvery object traces to its source system and source record.
02
State at the decision pointWhat the system believes at the moment a decision is due, with the evidence frozen at that instant.
03
Prediction recordWhere a prediction is kept, with every candidate it was compared against.
04
Move and actionWhat was offered and what was done, recorded separately and attributed.
05
Outcome and valueWhat followed at a fixed horizon, valued under the contract your finance team owns.
06
Replay, evaluation and governanceReplay with evidence frozen at each decision, and permission rules in the core.

Built per decision family

01
EntitiesWhat a decision family contains: steps, assets, cases, orders, rules and teams, each with state, actions and constraints.
02
State variablesThe condition of each entity at a time, held with its uncertainty.
03
RelationsHow entities act on each other: this case at this step, this rule over this action.
04
Conditional relationsRelations that hold under stated conditions: a tolerance for one variant, an authority within one procedure.
05
TimeWhen something was true and when it was recorded. Each state carries its own expiry.
06
Causal hypothesesCandidate causes held as hypotheses, distinct from association until a designed test supports them.
07
UncertaintyEvery belief carries its uncertainty. Observation and inference stay separate.
08
ProvenanceSource, time, context and rights on every fact, and the version behind every estimate.
09
Variable definitionsEvery variable states its unit, source, expiry, the decision it can change and the simpler proxy it must beat.
10
VersioningEarlier facts keep the version they were written under, so every result stays auditable.
11
Thin mappingsEach pack reads your systems where they live. Local systems stay in place.

The pack

Each pack is written down. Evidence can show where it is wrong.

When evidence repeatedly separates things the pack treats as the same, a versioned change can be proposed. People decide.

01

Disagreement.

The evidence and the pack diverge.

02

Proposed revision.

A specific change, with the evidence that produced it.

03

Reviewed version.

People decide. Earlier facts keep the version they were written under.

Control

Two questions before every read.

What exists, and where does it live? That is the evidence reference. May it be used for this purpose, now? That is permission. They are answered separately, for every person, system or agent.

Every record keeps its source, its permission and its purpose.

ProvenancePermissionPurposeExpiry
Trust architecture

Recherche

The same episode contract may carry richer state across teams and environments, where permission allows.

Suivant

Compound your intelligence.

See one decision

Follow one decision from state to sealed prediction to settled result.

Get started

Two minutes. Start from what you already know.

Lausanne, Suisse