Engine layer

Declare a target. Get a calibrated forecast of what's next.

This is the wedge. MemMesh doesn't just remember — it forecasts. Declare any target (an event, a number, a time, an anomaly) and the engine predicts it from a subject's history, with a confidence score checked against what actually happened and recalibrated over time. When it says 80%, it means it.

lattice.predict (event · numeric · time · anomaly)

What you get

01

Forecast any target

Event, number, time-to-event, or anomaly — one general predict() surface.

02

Calibrated confidence

Every forecast is scored against reality and recalibrated, so the number is honest.

03

Abstains when unsure

Thin signal yields a hedge or a pass, not fabricated certainty.

How it works

The loop, three calls.

  1. STEP 01

    Learn from history

    Predictions build on the subject's accumulated memory.

  2. STEP 02

    Declare a target

    Ask for any outcome; the engine forecasts it with a confidence score.

  3. STEP 03

    Record & recalibrate

    Feed the outcome back; the next forecast gets sharper.

Surfacelattice.predict (eventnumerictimeanomaly)

Features

Predict any target

Event, numeric, time-to-event, or anomaly — one general predict() surface, not a fixed menu.

Calibrated confidence

Every forecast is scored against reality and recalibrated, so the number is honest.

Abstains when unsure

Thin signal? The engine hedges or abstains instead of fabricating certainty.

FAQ

Questions, answered.

What can it predict?+

Any declared target — an event, a numeric value, a time-to-event, or an anomaly — from a subject's history.

How honest is the confidence?+

Calibrated against actual outcomes: across the times it says 80%, the event should happen about 8 in 10. When the signal is thin, it abstains.

Foresight, not just recall.

Declare any target and the engine predicts it from a subject's history — calibrated, provenanced, and abstaining when the signal is thin. This is the layer mem0 and MemoryLake have no answer for.