Get startedStart free

Hunta Reckon

Roadmap

Memory that only remembers is an archive. Reckon makes it reason.

Gather is day talk. Reckon is night talk.

Reckon is the offline pass that reasons across everything your fleet has gathered and learned, then proposes how the store should improve. It never writes on its own.

Roadmap On the roadmap. The pipeline it feeds is live today.

What it reasons overStart with Gather today

Why it exists

Two objections every memory store must answer

Capture has limits
Your store is only as good as what got captured

A reactive store cannot see its own gaps from inside itself. Reckon reads the whole store against the fleet's real activity and finds the facts that are missing and the connections that were never made.

Rules rot
Learned rules pile up, go stale, and over-fire

Nobody prunes them, so they slowly lose touch with the world they guard. Reckon prunes, merges, and narrows them, on a cadence.

Store-wide

It reasons over the whole store, not one corner of it

Facts from Gather, guardrails from Instinct, and the pending-write queue: Reckon reads all three together, plus what your fleet actually does. That is how it finds what no single entry can see.

Curation gateLIVEpoisoning screen · curator admitsthe writer never decidesThe Gather storeLIVEFactsgathered memoryGuardrailsinstinct rulesQueuepending writesFleet activityreal commands across the fleetReckon passPLANNEDreads facts, guardrails, and the queue,plus the fleet's real activityoffline · write-protectedReckon never decides.every proposal re-entersthe governed gateFIVE REASONING PASSESPLANNEDCoverage gapswhat the store missesOver-firingrules that block safe workGeneraliseone rule, many variantsConsolidateprune stale duplicatesNew lessonsunlearned failuresProposalsPLANNEDa signed batchnothing is applied yetlive: gather store, governed curation · planned: Reckon pass, five reasoning passes, signed proposals

Reckon reads three inputs and emits one thing: a signed batch of proposals into the curator gate.

The guarantees

Reckon never decides

Reads, never writes

Reckon reads the store and the fleet's real activity. It cannot change anything directly.

Proposes, does not decide

It emits a signed batch of proposals: gaps to close, rules to narrow, lessons to merge or retire. Each clears the same governed gate that fronts every other write.

Compounds across the fleet

On a shared store, one agent's matured lesson becomes every agent's reflex.

Governed, not self-writing

The industry has coalesced around dreaming. We call it reckoning.

The reflection motion is not novel, and we will not pretend otherwise: Stanford's generative agents reflect, Letta describes sleep-time compute, Anthropic writes about memory that dreams. The field has converged on the same observation: a store that only captures and reacts is not enough.

The difference is what happens at the end of the pass. Dreaming lets a model rewrite its own memory, and that is the poisoning surface: a reasoner that decides can quietly seal a wrong or adversarial conclusion into the record. Reckoning reasons offline and only proposes, into the same governed gate that fronts every other write. Governed reasoning, not self-editing.

How a proposal travels

The same gate as every other write

Step 1
Reckon proposes

A signed batch of proposals. Nothing in it is applied on its own.

Step 2
The screen checks

The same deterministic poisoning screen that fronts every write to the store.

Step 3
The gate admits

Low-risk cleanup flows through in a batch. Only the riskier structural changes get a closer look. Reckon never seals its own work.

Step 4
The store seals it

Admitted proposals land as supersessions, covered by the store's signed attestation.

One write path for everything. Nothing new, nothing ungoverned.

Memory that compounds, without handing the pen to the reasoner.

Reckon is on the roadmap. The store it will reason over, and the gate it proposes into, are live today.

Start freeGet started